Discord: Impacted availability - sending messages, logging in, all functions
Timeline of updates
- resolved
This incident is resolved. The root cause was on us. We were performing maintenance on our API cluster and unintentionally reduced the API cluster capacity too far, leading to latency. Unfortunately, this also caused our Envoy front proxy to become unhappy and get into an unrecoverable state. We resolved the incident by doing a rolling restart of the Envoy proxy after we fixed the API cluster capacity to handle user traffic.
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-04-03 07:28 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Impacted availability - sending messages, logging in, all functions
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/3mmq6n0wl67m
Discord profileRecent Discord incidentsAll outages on April 3, 2020Discord in April 2020MarkdownJSON