I am now removing the bot out of holding mode and preparing the "May" (really June) update for rollout. This will take some time as I am first applying some bug fixes to the existing bot to fix some issues that cause memory leaks and take the bot down. After today's outage we also found a problem with our router configuration (generated 30Gb of logs and bricked itself because I had forgotten to set a limit), but this has now been fixed.
Infrastructure wise, everything seems to be running fine. The code will receive incremental updates after the May/June update to improve its capacity in handling 40k+ servers before the next big feature update.
Hello folks!
I am now removing the bot out of holding mode and preparing the "May" (really June) update for rollout. This will take some time as I am first applying some bug fixes to the existing bot to fix some issues that cause memory leaks and take the bot down. After today's outage we also found a problem with our router configuration (generated 30Gb of logs and bricked itself because I had forgotten to set a limit), but this has now been fixed.
Infrastructure wise, everything seems to be running fine. The code will receive incremental updates after the May/June update to improve its capacity in handling 40k+ servers before the next big feature update.
Thank you again for your patience and support!