Apologies for the interruption this morning. This was a purely front-end website matter. That is why the service has been running fine in the background, and races started and completed on time even while it was ongoing. If you were connected to a viewer, you probably didn't even notice it happened.
The cause has been identified and resolved, so it won't happen again. This was not the same issue we've seen all week, but a new one which could only happen this one time.
It might not look like it, but we are very quickly stopping the ways that this can happen overall. We'll be moving the whole service to a new server configuration at some point this week which should address all the things we've seen this week.
I can only thank everyone for their patience and understanding during what has been a very difficult period for us. We're getting on top of it, but I understand if everyone's patience is wearing thin. We have no patience for stuff like this and are working our socks off to get on top of it.