Fire - Notice history

All systems operational

Bot - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.95%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Website - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Notice history

Apr 2025

Discord Outage
  • Resolved
    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

  • Update
    Update

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

  • Update
    Update

    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

  • Update
    Update

    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

  • Update
    Update

    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.

  • Investigating
    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

Mar 2025

No notices reported this month

Feb 2025

Vanity URL & Redirects Unavailable
  • Resolved
    Resolved

    An issue has just been resolved where the inv.wtf domain was returning 404s for all requests due to a mistake in an earlier deploy. Existing monitoring was unfortunately unable to detect the issue and fire alerts which meant it went unnoticed for longer than it should have.

    Apologies for any inconvenience caused. I will be looking into improving monitoring to detect these kinds of issues and ensure they do not happen (or at least not for as long) in the future

Potential disruption to Fire (Automatic)
  • Resolved
    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

  • Investigating
    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

Services Unavailable
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Fire now has about double the storage it used to and after a slight hiccup with InfluxDB not wanting to start, everything should be back online. I will be monitoring the situation alongside trying to figure out what caused the sudden increase in disk space (my current suspicion is InfluxDB considering the trouble I had getting it to come back)

  • Identified
    Identified

    It looks like Fire's VPS has ran out of available space. I knew this was approaching but I thought I had more time than I did. I have shut it down for now and will attempt to increase the partition size (as the disk itself had already been increased) and then bring it back online

Feb 2025 to Apr 2025

Next