Hello friends 
I am writing to update you on the situation regarding "restart loops" for Windrose servers hosted on Nitrado.
Our team has been working through the night to help users affected by the issue. For context, the issue affects only a small fraction of our Windrose servers, estimated at about 1.3%. But with the many, many thousands of Windrose servers we are hosting by now, and with the manual effort required in each fix, we have built up a backlog of requests that still require resolution.
We have therefore pivoted our approach from manual resolution on a case-by-case basis to automatically detecting and repairing servers that are in this state. That means that our manual resolution speed has slowed down for the moment, in favor of trying to resolve the situation at scale before Sunday prime time.
We believe that the current initiative will be able to resolve 80-90% of cases currently stuck in a restart loop, and will free up resources in our customer support team to investigate the remaining 10-20% of affected servers in more detail.
If your server is currently in a restart loop, there is nothing else you will need to do for now, just wait. In fact, we recommend that you don't try to manually fix the issue yourself unless explicitly instructed by our support agents. We will be posting an update in this thread once the automatic fix strategy has been applied and validated.
That also means that, until that time has come, we will be a little less active on here while we focus on resolving the issue at its root.
Lastly, I want to highlight that we take the current situation very seriously. 1.3% might not sound like much, but is still not a number we intend to ignore. We will not rest until every single one of you can enjoy their time on the high seas.
Update
We have successfully implemented and validated a fix for the vast majority of "hanging restart" cases. It is currently rolling out globally.
Please note that, if you were affected, the first restart after we have deployed the fix may still take a significant amount of time. The same is likely to occur on the first restart after you have restored a backup. We highly recommend to not interrupt that long startup process, even if it might seem that it is stuck.
In extreme cases, when the underlying save file has grown extremely large, this initial process may take more than an hour to finish.
If, starting from now, your server is briefly displayed as "running", but then enters "restarting" again, it is likely that your game server has crashed on startup due to a different cause. We recommend to review your newest R5.log for any indicators, and reach out to us so that we can assist you.
Please also note that, due to the backlog from the previous issue, responses from our support team might still be delayed. Please be assured that we are working as fast as we can to get every single one of you back on your servers.
Game on 