Discord: Session Servers Impacted
Timeline of updates
- resolved
Service is fully restored. We believe the root cause was a network layer event within Google Cloud and we are talking to their oncall engineers to try to understand what happened.
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-01-22 06:50 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Session Servers Impacted
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/pj6k93rh0yg4
Discord profileRecent Discord incidentsAll outages on January 22, 2018Discord in January 2018MarkdownJSON