In the hours immediately following the distribution of the 0.5.7 Gang Beasts Early Access build (publish on Thursday 29 June) we identified some performance issues on the Gang Beasts public servers, these issues escalated on over the subsequent days on populated servers triggering administration scripts to force server instances to restart and abruptly end game sessions on servers with the issue (the administration scripts are necessary to stop servers from terminally failing). On Monday 3 July at approx 8pm BST we made the decision to take down the servers to address and patch for stability issues (and some matchmaking and connection issues) and have subsequently made multiple tests with a series of client and server builds. We have publicised the 0.5.7p1 build concurrently with this post and have provisions number of public servers at for testing. Sorry for the protracted unavailability of public servers this week, together with Coatsink we have tried to maintain a high level of availability for public servers for the Early Access community by aggressively patching servers but were unfortunately not able to avoid taking public servers offline in this instance. Other Information For reference the key issue compromising the headless Linux server builds (that run on AWS architecture) was a severe memory leak that made disconnections, stage loading failures, and other stability issues more frequent until server administration scripts triggered the server to restart. We were not able to reproduce the memory leak in testing before publishing the 0.5.7 Early Access build and the associated public server builds last Monday (the issue was only identified when public servers were populated with a high volume of concurrent players). For reference the 0.5.7p1 builds is a separate branch to the coming 0.5.8 build and has no modifications from the 0.5.7 Early Access build (other than being built from Unity 0.5.6p1 not 5.6.2f1 and having online support for the incinerator stage temporarily disabled for this build).