Fire experienced a minor incident on January 22, 2025, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Jan 22, 2025, 11:16 PM UTC
Type: Maintenance Duration: 53 minutes Affected Components: Bot, Aether Jan 22, 23:41:46 GMT+0 - Identified - After some small reminder related bugs (mainly related to edits) discovered after the staging deploy, it is now ready to go to production. The main Fire bot & Aether instance will now go offline Jan 22, 23:45:44 GMT+0 - Identified - Fire & Aether are now back online with everything deployed. I'll be keeping a close eye on things for roughly 15 minutes before I mark this as complete Jan 23, 00:10:15 GMT+0 - Completed - 👍 Jan 22, 23:16:00 GMT+0 - Identified - At this time, I will be deploying changes to both Fire & Aether which need to be done simultaneously, meaning both need to be taken offline temporarily These changes are primarily related to new reminders code but also contain some changes which should help with internal monitoring falsely claiming that a cluster has been disconnected, resulting in alerts being sent to me and this page updated. These changes were not intended to go out just yet but with the changes to fix monitoring issues, it has moved all changes up. The reminder changes have been tested thoroughly but there may be some edge cases that I missed in testing so if you encounter any issues related to reminders, please let me know in the Fire Discord (discord.gg/firebot) Jan 22, 23:17:19 GMT+0 - Identified - Staging instances of Fire & Aether will soon go offline to deploy the updates there for a final check before being deployed to production