Discord Extreme List had 11 outages in the last 2 years totaling 2690h 28m of downtime — averaging 0.5 incidents per month.
There were 11 Discord Extreme List outages since November 2, 2024 totaling 2690h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
This issue has been identified. We are contacting our co location provider for more updates.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The Redis instance ran out of memory as a result of the container setting the ram limits unreasonably low, this issue has been corrected and should not occur again. The Redis instance was also set to the wrong storage class, this has been is updated and should not occur again.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
DEL is fully operational worldwide, however, we continue to experience a full outage in Aotearoa/New Zealand. We are working to identify the issue.
This is an issue with CloudFlare, we are monitoring for updates.
Regional connectivity issues remain in Aotearoa/New Zealand and Australia. Users in this region should continue to expect connectivity issues, occasionally resulting in 522 errors, and often long loading times. We are awaiting further work from Cloudflare to remedy the issue.
This issue remains unresolved, but is being marked as resolved in the meantime.
We are currently investigating this issue.
We suspect that DEL suffered a DDoS attack, performance has improved so we will be marking all components as degraded as we continue to investigate and monitor the situation.
We have identified the issue, implemented a fix, and are monitoring the result. Website and load balancer are both fully operational, but API remains at degraded performance.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently aware of the API endpoint /v2/bot/:id/stats (POST) intermittently going between functioning and reporting errors, potentially due to issues with the MongoDB Replicaset. We are investigating the issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue occurred on some pages as `req.del` is undefined as req is not passed on most pages. We switched to `res.locals.del` to fix the issue, as res is accessible on every page. This only occurred now due to `Sentry.init()` \(which is used on every page\) now calling `req.del.version` when in the past it didn't, so `req` was required on every page as a result, leading to the issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are aware of the issue and what it is, and working on fixing it.
A fix has been implemented and we are monitoring the results.
Another issue has been found affecting the /server and /template endpoints on the site, and we are working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.