Fire experienced a minor incident on December 28, 2025, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Dec 28, 2025, 02:55 AM UTC
Type: Incident Duration: 1 hour and 58 minutes Affected Components: Aether, Bot, Website Dec 28, 02:55:47 GMT+0 - Investigating - Automated systems have detected a prolonged issue with the connection to one or more Fire clusters. This may not necessarily mean the bot is down but it will at minimum result in features being unavailable Dec 28, 02:57:52 GMT+0 - Investigating - Fire's VPS appears to have been blocked from accessing Discord's API due to exceeding ratelimits. It's unknown how this occurred at this time but for now, the bot has been turned off to avoid making requests while ratelimited. It looks to be only an hour long block with about 50 minutes remaining so it shouldn't be down for long but unfortunately there's nothing that can be done other than waiting Dec 28, 03:51:00 GMT+0 - Monitoring - Fire is now back online and looks to be operating just fine. I've made some changes that may help prevent the issue re-occurring but I'll be looking further into what caused this issue so that I can properly resolve it Dec 28, 04:53:41 GMT+0 - Resolved - The issue seems to have stemmed from Fire being stuck in a loop, constantly making requests to edit a channel, which resulted in it getting ratelimited. As far as I can tell, the edits were part of the permission role feature, so I've made a few changes to it which should a) help identify it and b) help resolve the issue This feature is pretty old so it likely needs a rewrite to ensure things work smoothly, which has been added to my lengthy to-do list for Fire For now, Fire is operational and should stay that way. If you encounter any issues, please report them in the Fire Discord (discord.gg/firebot)