Fire - Notice history

All systems operational

Bot - Operational

100% - uptime
Apr 2022 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2022
May 2022
Jun 2022

Website - Operational

100% - uptime
Apr 2022 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2022
May 2022
Jun 2022

Notice history

Jun 2022

No notices reported this month

May 2022

Outage on Cluster 0
  • Resolved
    Resolved

    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

Apr 2022

Slash commands partially unavailable in some servers
  • Resolved
    Resolved

    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

  • Investigating
    Investigating

    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

  • Identified
    Identified

    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)

  • Investigating
    Investigating

    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

Fire not responding to interactions, quotes not working
  • Resolved
    Resolved

    This incident has been resolved.

  • Identified
    Identified

    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.

Apr 2022 to Jun 2022

Next