Bot - Operational
Bot
Previous page
Next page
Beta Bot - Operational
Beta Bot
Website - Operational
Website
Expand group
Backend
External
Extras
From 05:05 to 09:04 (UTC), Cluster 0 was offline. It is currently unknown why the cluster went offline and why it was not detected and resolved automatically but I will be investigating later today and will post any findings in the Fire Discord server ( https://inv.wtf/fire ) I know that a lot of people rely on Fire and its usual amazing uptime and I apologize for any inconvenience this caused. I will be working on improving detection and automatic resolution of outages soon
It seems that filtering commands is working once again in most servers, hopefully the rest will get resolved soon. Marking this as resolved as the number of servers still affected seems to be quite minimal
The fix was deployed but the issue seems to persist. I've changed this incident back to investigating for now as it seems there's more going on
The cause of the 500s has been identified and a fix is about to be deployed on Fire's end to fix it (as it is bad command data that is causing the issue)
It seems Discord may be having issues with slash commands returning a 500 error when querying commands in some servers so you may encounter issues with filtering commands by hitting / and typing a command name. Clicking the Fire logo in the list of applications on the left will bring up the commands list and allow you to run it from there if typing a command name doesn't work
This incident has been resolved.
Fire is currently having issues responding to interactions & quoting messages via webhooks. The slash command restriction on commands has been temporarily lifted and webhook quotes have been temporarily disabled until this is resolved. For now, please use message commands instead of slash commands. If you use slash commands, the command may still run but it won't respond.
The button in the invite command response is currently unusable seemingly due to a change on Discord's end. Please use the "Add to Server" button on Fire's profile instead
We are continuing to monitor for any further issues.
Fire has been turned back on and I am monitoring the situation as everything recovers
Discord seems to be slowly recovering. The bot was shut down while it was fully unavailable and will not be turned back on until the platform becomes more stable so for now, the bot will be offline even if you can access the app
Just realised I didn't switch to "Identified" when I opened this so here it is No updates, Discord is still dead :(
Discord is currently unavailable which means Fire is also unavailable.
Mar 2022 to May 2022
Next
