Fire Outage History
Fire degraded View live status →Pingoru has recorded 51 incidents for Fire: 31 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 1 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 2 | 1 of 720 (0%) |
| October 2026 | 0 | 0 of 566 (0%) |
Incidents, newest first
Major September 24, 2026 Hetzner Outage 32m
Started Sep 24, 2026, 06:56 PM UTC· resolved Sep 24, 2026, 07:28 PM UTC
- identified Sep 24, 2026, 06:56 PM UTC
Hetzner has reported a fault on the node that Fire is hosted on. This outage is out of Fire's control but once resolved, everything should come back automatically.
- resolved Sep 24, 2026, 07:28 PM UTC
Health checks have recovered and Fire is back online along with Hetzner stating the incident has been resolved.
Major April 9, 2026 Fire Beta unavailable 35m
Started Apr 09, 2026, 01:05 AM UTC· resolved Apr 09, 2026, 01:40 AM UTC
- identified Apr 09, 2026, 01:05 AM UTC
Fire Beta is currently unavailable due to an incident at Hetzner resulting in the server being offline .
- resolved Apr 09, 2026, 01:40 AM UTC
This incident has been resolved and services have returned to normal operation..
Major March 15, 2026 Beta Bot outage 15m
Started Mar 15, 2026, 04:41 PM UTC· resolved Mar 15, 2026, 04:56 PM UTC
- investigating Mar 15, 2026, 04:41 PM UTC
Beta Bot cannot be accessed at the moment. This incident was created by an automated monitoring service..
- resolved Mar 15, 2026, 04:56 PM UTC
Beta Bot is now operational! This update was created by an automated monitoring service..
Minor March 12, 2026 Discord API Issues (dsv750sj44fn) 40m
Started Mar 12, 2026, 08:30 PM UTC· resolved Mar 12, 2026, 09:10 PM UTC
- identified Mar 12, 2026, 08:30 PM UTC
Fire is currently experiencing elevated latency & error rates due to issues with Discord's API. Discord has posted about the issue on their own status page, [https://discordstatus.com/incidents/](https://discordstatus.com/incidents/dsv750sj44fn).
- monitoring Mar 12, 2026, 08:59 PM UTC
Discord has implemented a fix and both error rates & latency have returned closer to expected levels. I will continue monitoring for some time to ensure things are fully resolved.
- resolved Mar 12, 2026, 09:10 PM UTC
This incident has been resolved..
Minor February 25, 2026 Networking Issues 29m
Started Feb 25, 2026, 09:08 PM UTC· resolved Feb 25, 2026, 09:37 PM UTC
- investigating Feb 25, 2026, 09:08 PM UTC
It seems Fire and related services are currently unavailable due to possible networking issues. Services are running but it seems that all connectivity on both machines (production & staging) has been lost It's unknown what exactly is causing this issue but my guess is Hetzner due to how both machines lost connectivity at the same time and I'm unable to access the Hetzner console.
- monitoring Feb 25, 2026, 09:13 PM UTC
Connectivity appears to have returned and services are now reporting as healthy. Active monitoring will continue for a period of time in the event of issues returning.
- resolved Feb 25, 2026, 09:37 PM UTC
This incident has been resolved..
Minor February 18, 2026 Infrastructure Upgrades – Overall
Started Feb 18, 2026, 11:00 AM UTC· resolved Feb 18, 2026, 11:00 AM UTC
No vendor updates were posted for this incident.
Minor February 3, 2026 Potential disruption to Fire (Automatic) 1h 40m
Started Feb 03, 2026, 03:35 PM UTC· resolved Feb 03, 2026, 05:15 PM UTC
- investigating Feb 03, 2026, 03:35 PM UTC
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.
- resolved Feb 03, 2026, 05:15 PM UTC
Automated systems have detected new connections from previously unavailable clusters and all clusters are now connected. Fire should no longer have any availability issues.
Minor January 19, 2026 Server Upgrades – Overall
Started Jan 19, 2026, 10:00 AM UTC· resolved Jan 19, 2026, 10:00 AM UTC
No vendor updates were posted for this incident.
Minor December 31, 2025 Internal Restructuring 1h
Started Dec 31, 2025, 08:24 AM UTC· resolved Dec 31, 2025, 09:25 AM UTC
- investigating Dec 31, 2025, 08:24 AM UTC
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.
- investigating Dec 31, 2025, 08:29 AM UTC
As part of some internal restructuring, it seems that the websocket connection to Aether is not working correctly, preventing the bot from launching correctly. I'm currently investigating this and hope to get this resolved as soon as possible.
- monitoring Dec 31, 2025, 08:36 AM UTC
We implemented a fix and are currently monitoring the result..
- resolved Dec 31, 2025, 09:25 AM UTC
This incident has been resolved..
Major December 19, 2025 Discord Outage - Slow and failing requests (xt705bsck7sk) 39m
Started Dec 19, 2025, 11:00 PM UTC· resolved Dec 19, 2025, 11:39 PM UTC
- investigating Dec 19, 2025, 11:00 PM UTC
Many of Fire's API requests to Discord are currently failing indicating a potential outage. I have had to shut down one of Fire's clusters as it got stuck in a loop retrying requests due to this issue and am working on a solution so that it can be restored.
- monitoring Dec 19, 2025, 11:22 PM UTC
Things look to have improved, requests aren't failing nearly as often and latency has returned to normal levels. I will continue to monitor requests for some time just to be sure it's fully resolved.
- resolved Dec 19, 2025, 11:39 PM UTC
This incident has been resolved..
Major November 18, 2025 Cloudflare Outage 6h 59m
Started Nov 18, 2025, 11:52 AM UTC· resolved Nov 18, 2025, 06:52 PM UTC
- identified Nov 18, 2025, 11:52 AM UTC
Cloudflare's network is currently experiencing issues which will affect Fire due to both it and Discord making use of Cloudflare's services You may experience slow responses or failed interactions when attempting to use commands in the bot and web services may return 5XX errors.
- resolved Nov 18, 2025, 06:52 PM UTC
Cloudflare have stated that things are now operating normally.
Minor November 10, 2025 New Website – Overall
Started Nov 10, 2025, 03:00 PM UTC· resolved Nov 10, 2025, 03:00 PM UTC
No vendor updates were posted for this incident.
Major September 8, 2025 Discord Outage - Guilds Unavailability (9bm86bnmfhfr) 1h 34m
Started Sep 08, 2025, 10:21 PM UTC· resolved Sep 08, 2025, 11:56 PM UTC
- investigating Sep 08, 2025, 10:21 PM UTC
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.
- identified Sep 08, 2025, 10:41 PM UTC
Upon investigating, it appears that the issues Discord are having at the moment have resulted in the gateway connections for Fire's clusters getting stuck in a form of limbo state where it appears to be connected but nothing is being received (and I have no way to test if anything can be sent as I'd normally do that via a command) I will attempt to restart clusters, starting with the cluster that has the least unavailable servers (cluster 3 with only a single unavailable server), since servers being unavailable on connect can slow down startup and might result in further issues.
- identified Sep 08, 2025, 10:44 PM UTC
The restart was successful meaning cluster 3 is now online and functioning. I will continue going in order of least unavailable servers as that seems like the best thing to do right now.
- resolved Sep 08, 2025, 10:46 PM UTC
Automated systems have detected new connections from previously unavailable clusters and all clusters are now connected. Fire should no longer have any availability issues.
- monitoring Sep 08, 2025, 10:47 PM UTC
All clusters are back online, however, they may have slow responses or other issues related to the Discord outage. Monitoring will continue until Discord has marked their incident as resolved.
- resolved Sep 08, 2025, 11:56 PM UTC
This incident has been resolved..
Minor June 22, 2025 Quotes Disabled 16m
Started Jun 22, 2025, 12:04 PM UTC· resolved Jun 22, 2025, 12:21 PM UTC
- investigating Jun 22, 2025, 12:04 PM UTC
Quotes are currently disabled while an issue is being investigated.
- identified Jun 22, 2025, 12:17 PM UTC
The issue has been identified and a fix is being made.
- resolved Jun 22, 2025, 12:21 PM UTC
The fix has been deployed and quotes have been re-enabled.
Minor May 14, 2025 Slow responses and failed interactions 14m
Started May 14, 2025, 12:49 AM UTC· resolved May 14, 2025, 01:04 AM UTC
- identified May 14, 2025, 12:49 AM UTC
Discord turned 10 years old and is now old and slow. Rest latency started to increase at 00:20 UTC but not enough to trigger alerts so I only discovered things are broken a few minutes ago and seems like Discord did too as they only posted about it now too.
- monitoring May 14, 2025, 12:58 AM UTC
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.
- resolved May 14, 2025, 01:04 AM UTC
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.
Major April 10, 2025 Discord Outage 27m
Started Apr 10, 2025, 07:59 PM UTC· resolved Apr 10, 2025, 08:27 PM UTC
- investigating Apr 10, 2025, 07:59 PM UTC
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.
- investigating Apr 10, 2025, 08:02 PM UTC
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 Apr 10, 2025, 08:13 PM UTC
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.
- investigating Apr 10, 2025, 08:18 PM UTC
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.
- investigating Apr 10, 2025, 08:27 PM UTC
Shard 0 has risen from the dead, now just waiting on shard 1....
- resolved Apr 10, 2025, 08:27 PM UTC
Automated systems have detected new connections from previously unavailable clusters and all clusters are now connected. Fire should no longer have any availability issues.
Major February 23, 2025 Vanity URL & Redirects Unavailable –
Started Feb 23, 2025, 02:39 PM UTC· resolved Feb 23, 2025, 02:39 PM UTC
- resolved Feb 23, 2025, 02:39 PM UTC
An issue has just been resolved where the [inv.wtf](http://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.
Major February 1, 2025 Services Unavailable 48m
Started Feb 01, 2025, 10:43 PM UTC· resolved Feb 01, 2025, 11:31 PM UTC
- identified Feb 01, 2025, 10:43 PM UTC
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.
- monitoring Feb 01, 2025, 11:07 PM UTC
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).
- resolved Feb 01, 2025, 11:31 PM UTC
This incident has been resolved..
Minor January 30, 2025 Migration to rewrite of Vanity URLs & Redirects –
Started Jan 30, 2025, 04:00 PM UTC· resolved Jan 30, 2025, 04:00 PM UTC
No vendor updates were posted for this incident.
Minor January 22, 2025 Deploying various updates –
Started Jan 22, 2025, 11:16 PM UTC· resolved Jan 22, 2025, 11:16 PM UTC
No vendor updates were posted for this incident.
Minor November 24, 2024 Config handling update –
Started Nov 24, 2024, 02:00 PM UTC· resolved Nov 24, 2024, 02:00 PM UTC
No vendor updates were posted for this incident.