Bot - Operational
Bot
Previous page
Next page
Beta Bot - Operational
Beta Bot
Website - Operational
Website
Expand group
Backend
External
Extras
This incident has been resolved.
It is still unknown what initially caused the issue but there was have been a brief period of time where Fire's VPS was unable to reach the internet. Fire is once again able to access the internet and should be back in action! I am monitoring network activity to ensure things are back to normal.
Fire is currently having issues sending requests to certain services, including Discord. This may cause long response times or no response at all. I am currently investigating the cause and attempting to mitigate the issue
Latency and error rates have returned to normal, keeping this open for a while so if it happens again I don't need a third incident...
I am seeing elevated latency & 5XX responses coming from Discord and duplicated messages. This usually indicates an outage on Discord's end.
It seems the ongoing outage may be affecting Fire as I've noticed some high latency on requests and a few failed interactions. It seems to have calmed down now as it happened a few minutes ago while I was away but I thought I'd open an incident just in case more issues occur
Error rates have decreased so I have switched one cluster back to the Canary API and will wait to ensure things are working fine before switching the other
Discord's Canary API seems to be having issues so I've switched Fire over to stable so that should eliminate some of the issues. Lowering status to partial outage.
Almost all requests are now 5XX errors so I'm changing the status to major outage.
I've started seeing 502 errors in Fire's logs, changing status to partial outage
We're experiencing elevated latency on Fire. This is most likely an issue on Discord's end rather than ours. We're currently investigating the issue
Discord has marked their incidents as resolved however due to the amount of outages today, I am going to leave this open a little longer just in case.
Discord seems to be having major issues at the moment and it has started to affect Fire. You can keep up to date with Discord's incidents using the links below: https://stspg.io/mnbt34n1c6nc?u=684bns7mjtnh https://stspg.io/klccjhq8sf47?u=jm3l03t7tr5f
Welp, right before I posted the previous update, Discord updated their incident stating the issue is resolved. So I guess this is resolved too now...
From about 1:13 UTC to 1:21 UTC, Fire experienced elevated latency and failed requests. These issues seem to have calmed down for now but it's unknown whether Discord has fully resolved the issue yet. For now, Fire seems to be having minimal issues, so I will change the status to "Degraded Performance" until I have confirmation the issues are resolved
Discord's API is currently having major issues. As I am currently on my phone I am unable to monitor the impact on Fire and other services but I will update this incident with more info as soon as I can
Fire does not seem to be experiencing high latency anymore. I will keep this open for a little while longer to be sure
Fire is currently experiencing high latency on some requests, indicating there may be some issues with Discord (or Cloudflare, since they currently have an open incident) Updates will follow once I get more details of any potential issues
Everything is coming back online. I'll be monitoring requests to ensure this does not happen again.
Fire & other services should be back online in ~20 minutes
It seems Fire's VPS has gotten a temp Cloudflare ban and I'm pretty sure Donald Duck is the cause (if you know, you know) meaning any service that uses Discord will be offline (likely for about an hour)
It seems Fire has gone offline, I am currently investigating the cause
Apr 2021 to Jun 2021
Next
