Discord: Investigating Service Degradation
Timeline of updates
- resolved
Discord has been operating normally for more than an hour. All graphs are nominal and we understand what happened. The very brief synopsis is that we had table contention on the MongoDB instance that underlies a portion of our system. We do not believe this particular incident will recur in the near future.
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 2018-03-17 19:34 UTC, resolved after 3.3 h, 1 update(s).
- Title
- Investigating Service Degradation
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/2cb5jc53jq28
Discord profileRecent Discord incidentsAll outages on March 17, 2018Discord in March 2018MarkdownJSON