Solved

we remain the same

A server is running out of memory. It is a memory leak. It only impacts races on that specific server, not the whole service, but during peak hours every server gets a lot of races.

The current reality I live with is if I am 10 minutes late to my desk to stop a memory leak, for some of you it's the same as nothing works for an entire week, because it's happening when your race is on. I understand and accept that reality, and will be building in as much redundancy as I can in the next few days to stop this from being necessary (I should not be a necessary part of the system).

I'm here now and working to ensure this doesn't happen again for the rest of the night, and from tomorrow will be able to work on it full-time on this stuff. I have been unable for a few days as I was parenting my children and that split my focus significantly. For the next week I will be working solidly on iGP and can finish addressing the last few problems like this.

Your race is the one that caused the memory leak on that server. I have identified the issues are consistently appearing on 2 tracks (Abu Dhabi and Netherlands), so I'm re-exporting those now and will be uploading them to the service shortly.

The cause of the issues is outlined in this thread:
https://igpmanager.com/forum-thread/64092

I'm going to close this thread to move all discussion there. I want to to centralise discussion around the real cause and the solution in the other thread, avoid any more "nothing is happening" or "nobody cares" talk. We're fixing it, taking it very seriously, going as fast as we can, and perhaps it's already fixed (initial signs look good). See the other thread for more info.