Get updates
Preferences
Bot - Operational
Bot
Previous page
Next page
Beta Bot - Major outage
Beta Bot
Website - Operational
Website
Expand group
Backend
Collapse group
External
Discord API - Operational
Discord API
Discord Realtime - Operational
Discord Realtime
Discord Media Proxy - Operational
Discord Media Proxy
Cloudflare (FRA) - Operational
Cloudflare (FRA)
Cloudflare Websockets - Operational
Cloudflare Websockets
Cloudflare DNS - Operational
Cloudflare DNS
Cloudflare Firewall - Operational
Cloudflare Firewall
Cloudflare DNS Updates - Degraded performance
Cloudflare DNS Updates
GitHub API - Operational
GitHub API
GitHub Webhooks - Operational
GitHub Webhooks
GitHub - Git operations - Operational
GitHub - Git operations
Sentry API - Operational
Sentry API
Stripe API - Operational
Stripe API
Extras
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
No notices reported this month
All clusters are back online, however, they may have slow responses or other issues related to the Discord outage. Monitoring will continue until Discord has marked their incident as resolved
Automated systems have detected new connections from previously unavailable clusters and all clusters are now connected. Fire should no longer have any availability issues
The restart was successful meaning cluster 3 is now online and functioning. I will continue going in order of least unavailable servers as that seems like the best thing to do right now
Upon investigating, it appears that the issues Discord are having at the moment have resulted in the gateway connections for Fire's clusters getting stuck in a form of limbo state where it appears to be connected but nothing is being received (and I have no way to test if anything can be sent as I'd normally do that via a command)I will attempt to restart clusters, starting with the cluster that has the least unavailable servers (cluster 3 with only a single unavailable server), since servers being unavailable on connect can slow down startup and might result in further 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
Previous
Sep 2025 to Nov 2025
Next