Fire - Notice history

Some requests (primarily adding roles to members) are still showing somewhat higher latency than normal but things are generally fine and Fire should be functioning normally

Discord claims that things are fixed but I don't trust them so this will stay open a little longer while I keep an eye on boring graphs to see if it goes stonks (but in a bad way) again

Automated systems have detected new connections from previously unavailable clusters and all clusters are now connected. Fire should no longer have any availability issues

Shard 0 has risen from the dead, now just waiting on shard 1...

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

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

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.