Jack
I know why this happened. I was surprised we didn't get more reports, I ran the entire service in a single server at peak hours. The CPU never broke a sweat, but I bet the network struggled. It should be totally different for your next race.
The reason for this was I didn't want league races using the broken qualifying issues the other servers were having. I felt it was a higher priority to get the accuracy of the simulation than the network stability tonight.
Thanks for the explanation, Jack. I really appreciate the transparency and, above all, the decision to prioritize simulation accuracy above everything else. We understand that during peak hours these kinds of issues can happen, especially in a period with big changes.
I’m reassured knowing you’ve already identified the cause and that the next race should run much better. I’ll also send you more videos from the upcoming races to help with any further testing or feedback. Thanks for the effort and for protecting the overall quality of the game, even when it requires tough short-term decisions.
CEO & CTO