Fire incident
Discord Outage - Guilds Unavailability (9bm86bnmfhfr)
Fire experienced a major incident on September 8, 2025, lasting 1h 34m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Sep 08, 2025, 10:21 PM UTC
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.
- identified Sep 08, 2025, 10:41 PM UTC
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.
- identified Sep 08, 2025, 10:44 PM UTC
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.
- resolved Sep 08, 2025, 10:46 PM UTC
Automated systems have detected new connections from previously unavailable clusters and all clusters are now connected. Fire should no longer have any availability issues.
- monitoring Sep 08, 2025, 10:47 PM UTC
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.
- resolved Sep 08, 2025, 11:56 PM UTC
This incident has been resolved..