Discord: Elevated latency and errors
Timeline of updates
- resolved
Traffic and latency are fully restored, Discord is fully operational. The underlying issue was due to an operation we performed on our authentication database cluster which resulted in too much reduced capacity in the database cluster. We performed some load shedding to enable some traffic to recover, but due to the nature of this cluster's topology and the incident, only about 50% of our userbase was able to get back online in the interim and we had to wait for the maintenance to complete on the impacted database nodes before we were able to fully restore the service. We'll be following up internally with a postmortem and will plan to publish a public blog post describing the incident and our followups to ensure that this issue cannot recur. Our goal is that Discord just works when you need it; we know many of you (and all of us!) rely on Discord. Please accept our apologies and thank you for your patience today as we worked through this incident.
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 2023-11-06 18:57 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Elevated latency and errors
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/bmx00xx7btkr
Discord profileRecent Discord incidentsAll outages on November 6, 2023Discord in November 2023MarkdownJSON