Get updates
Preferences
Bot - Operational
Bot
Previous page
Next page
Beta Bot - Major outage
Beta Bot
Website - Operational
Website
Expand group
Backend
External
Extras
Maintenance has completed successfully.... almost.During the upgrades, Fire's postgres installation got completely removed along with all the data. Fortunately, I have backups, but only for the main bot. Fire Beta has had its database recreated from scratch so no previous data will be present there so if you were relying on that, you shouldn't have!Aside from that, everything looks to be in working order. NodeJS has been updated to the latest LTS release, nginx has been updated to the latest release, postgres has been updated to the latest release and internal tooling (e.g. Grafana, Telegraf) has also been updatedI'll be keeping a close eye on things throughout today to ensure things continue running smoothly. If you encounter any issues, let me know in the Fire Discord (discord.gg/firebot)
The snapshot has been taken and the software side of the upgrades is now in progress
The hardware of the server has been upgraded slightly (more vCPUs, more RAM & more storage) and I am now taking a snapshot of the server that I hopefully won't have to use but is there just in case anything goes wrong
Redirects have now been put in place to redirect any traffic to Fire's web services towards a dedicated maintenance page. I will now be turning off all services to start the upgrades
During this time, several upgrades (both hardware & software) will be performed on Fire's VPS which will result in some lengthy downtime of ALL SERVICES.This downtime is unfortunate but necessary to ensure stability, security and open the door for new features that require newer software versionsDuring this time, I will be keeping an eye on the Fire Discord (discord.gg/firebot) to answer any questions and let people know the current status of the upgrades.I'll also be around for the next while to answer questions about this maintenance if you have any so feel free to join the Discord server and ask in the #fire-help channel
Automated systems have detected new connections from previously unavailable clusters and all clusters are now connected. Fire should no longer have any availability issues
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
As part of some internal restructuring, it seems that the websocket connection to Aether is not working correctly, preventing the bot from launching correctly.I'm currently investigating this and hope to get this resolved as soon as possible
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 issueThis 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 FireFor now, Fire is operational and should stay that way. If you encounter any issues, please report them in the Fire Discord (discord.gg/firebot)
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
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
Cloudflare have stated that things are now operating normally
Cloudflare's network is currently experiencing issues which will affect Fire due to both it and Discord making use of Cloudflare's services
You may experience slow responses or failed interactions when attempting to use commands in the bot and web services may return 5XX errors
The new website has been successfully deployed and final checks are being ran to ensure everything is working as intended
The bot has been updated so now the website is going to be changed over
During this time, the new website will be deployed alongside some updates to the bot. This is not expected to take long nor should there be any problems as both the website & bot changes have been tested locally & in stagingThe website will be unavailable for a brief period of time while a production build is deployed and configured while the bot should only be unavailable for a few seconds while it restarts for a normal deploy
Previous
Nov 2025 to Jan 2026
Next
