Discord: User traffic anomaly
Timeline of updates
- resolved
The root cause upstream has been fixed and the secondary incident on our end (our Envoy cluster got into a permanently "circuit broken" state and needed a reboot) has been mitigated, so we are declaring this incident to be resolved. We will continue to work to understand the degenerate behavior in our load balancing layer and implement a more permanent fix so that this does't recur.
From Discord’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on discordstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Discord, started 2020-11-07 13:46 UTC, resolved after 48 min, 1 update(s).
- Title
- User traffic anomaly
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/2vz211zd63p4
Discord profileRecent Discord incidentsAll outages on November 7, 2020Discord in November 2020MarkdownJSON