Discord: Connection Loss / Failure to Reconnect
Timeline of updates
- resolved
Tonight's issue is over and Discord is working normally again. We're very sorry for the interruption this caused. The root cause is under investigation. The team is actively working to understand the chain of events that led to this (and the last few) outages. We've got some good data on this crash and are putting together hypotheses that we can test in our staging & load test environments. As mentioned in the last update, we do know the triggering event: a crash of one of our very large guilds that triggered a cascading failure in our sessions cluster. The crash is well understood and will not happen again, so we're confident we won't see a repeat of this cascading failure at this time.
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-04-19 06:41 UTC, resolved after 48 min, 1 update(s).
- Title
- Connection Loss / Failure to Reconnect
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/782x5rl48964
Discord profileRecent Discord incidentsAll outages on April 19, 2018Discord in April 2018MarkdownJSON