Fire experienced a major incident on April 10, 2025, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Apr 10, 2025, 07:59 PM UTC
Type: Incident Duration: 28 minutes Affected Components: Bot Apr 10, 19:59:48 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 Apr 10, 20:02:12 GMT+0 - Investigating - It seems that Discord may be having issues with the gateway at the moment. All of Fire's websocket connections were dropped simultaneously and are unable to reconnect along with my own websocket connection in the app experiencing the same issue There are also many reports flooding in on Twitter about issues connecting so it doesn't seem like I or Fire are alone in this. Apr 10, 20:13:04 GMT+0 - Investigating - Shard 3 has been able to successfully reconnect so the rest should hopefully follow suit but unfortunately I am still unable to get in myself and therefore unable to verify if that shard is functioning correctly Apr 10, 20:18:51 GMT+0 - Investigating - Shard 2 has now been able to reconnect. I tried restarting cluster 0 (shard 0) to see if that would help but it is still stuck in the same loop as shard 1 Apr 10, 20:27:14 GMT+0 - Investigating - Shard 0 has risen from the dead, now just waiting on shard 1... Apr 10, 20:27:44 GMT+0 - 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