Discord: Outage
Timeline of updates
- resolved
At this time, we think service has fully recovered. It looks like the fault of this incident was an internal networking issue between one of our backend services. This outage is similar to others in the past, and our team is aware of the root cause. We're still working on fixing the underlying faults in our system that caused this to escalate to a major outage - however we're happy to report that the time it took to fully restart Discord during one of the busiest days in Discord history is roughly 20 minutes.
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 2017-12-30 21:58 UTC, resolved after 45 min, 1 update(s).
- Title
- Outage
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/x5cd4vb7cljk
Discord profileRecent Discord incidentsAll outages on December 30, 2017Discord in December 2017MarkdownJSON