Bot - Operational
Bot
Previous page
Next page
Website - Operational
Website
Expand group
Backend
External
Extras
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
A fix for the issue is being rolled out now. It is unknown when it will be fully rolled out but I will do my best to update this incident when it is
The issue on Discord's end has been identified so a fix should be out soon. In the meantime, slash command restrictions have been disabled so all commands are available via message commands but some may not function correctly.
It seems Discord is having issues with slash commands as Fire and various other bots are not responding when invoked via a slash command. I will attempt to disable the slash command restrictions to allow all commands via messages temporarily until the issue is resolved
Network traffic has returned to expected levels as services begin to recover. Degraded performance is expected as things warm up but should be stable and fully functioning. It is unknown what caused this outage at this time but it is possibly related to ongoing issues at Hetzner (https://status.hetzner.com/incident/286dfd0d-7762-493f-8477-d0c8c0db138a)
Services are slowly coming back online but stability is not guaranteed.
Upon further investigation, it seems there's some networking issues as the VPS is unable to resolve hostnames
It seems Fire's VPS is unable to connect to Discord. Any service that relies on Discord is currently unavailable
It seems Fire isn't responding to commands. I am starting to investigate and will update this with information as I find it
Things are stabilizing and Discord has confirmed they have mitigations in place. I'll be keeping a close eye on things until Discord closes their incident
Fire is once again unable to connect to Discord with most requests failing
We are continuing to monitor for any further issues.
Discord is aware of the issues and has opened an incident on their status page, https://discordstatus.com/incidents/bcqpwv2cvn06?u=5dvhg4y2dxn9
Right as I opened this incident, everything started working again 🙃 I'll keep this open just in case it stops
Fire is currently having issues connecting to Discord (as am I) so there may be an ongoing outage somewhere along the way.
It seems that my instance of Hoppscotch encountered an error and got stuck in a reboot loop. This is (as far as I can tell) the cause of the excessive disk throughput and CPU usage which exhausted the resources of the machine preventing other applications from operating normally. The issue has been resolved and all services are fully functioning
Both incoming and outgoing traffic suddenly came to a halt and disk throughput spiked to 800 MBps. It is unknown what caused this issue but it is likely the cause of the unresponsiveness. The VPS has been restarted and services are coming back online but may appear slow for a short while as everything warms back up.
It seems services are timing out and/or returning errors. I am investigating and attempting to restore access as soon as possible.
Fire & related services are currently experiencing degraded performance. This is likely caused by ongoing issues at Cloudflare, https://stspg.io/d0dg70t9b8sb?u=gnfv9zt4lprr
Dec 2021 to Feb 2022
Next
