Fire experienced a minor incident on November 24, 2024, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Nov 24, 2024, 02:00 PM UTC
Type: Maintenance Duration: 1 hour and 2 minutes Affected Components: Bot, Website, Aether Nov 24, 14:29:53 GMT+0 - Identified - After a slight hiccup with one of the new additions to Aether, the deploy to the beta services has been successful. Fire & Aether will now be turned off to facilitate the deploy Nov 24, 14:45:15 GMT+0 - Identified - All clusters are now back online with the update deployed. I will be actively monitoring for the next 15 or so minutes to ensure everything is working as it should Nov 24, 15:02:20 GMT+0 - Completed - Everything looks to be running perfectly and my small bit of testing on the production services has been successful so I consider this maintenance complete! Nov 24, 14:00:00 GMT+0 - Identified - An update will be releasing to Fire & Aether (the service which manages Fire's clusters) to change how configs are handled to make reading them from external services (such as the website) easier and allowing better syncing across clusters and better handling of failures to update the config These updates are closely linked so they cannot be updated seamlessly like most incremental changes and will require both services to be offline to update them. I do not anticipate this taking a long time but I've left in room for error (which hopefully will not happen 🤞) just in case Nov 24, 14:01:57 GMT+0 - Identified - Fire Beta & the matching beta instance of Aether will now be turned off to deploy the update to those two first The main bot will not currently be affected. Nov 24, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 24, 14:36:57 GMT+0 - Identified - The deploy to production Aether was successful. Fire's clusters will start coming back online now though there will be some spacing in-between the launch of each cluster just to ensure things are going smoothly