# Discord: Session Servers Impacted

> Discord status incident “Session Servers Impacted” on 2018-01-22: impact none (vendor’s label), 1.4 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/discord/incidents/pj6k93rh0yg4
Last updated: 2018-01-22T08:13:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2018-01-22 06:50 UTC · Resolved: 2018-01-22 08:13 UTC · Duration: 1.4 h
- Updates: 1
- [Vendor status page: https://discordstatus.com/incidents/pj6k93rh0yg4](https://discordstatus.com/incidents/pj6k93rh0yg4)
- [Company: Discord](https://rewindex.com/company/discord.md)

## Timeline of updates

- **resolved** 2018-01-22 08:13 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/discord/incidents/pj6k93rh0yg4
- Citation: Discord, “Session Servers Impacted” (2018-01-22 06:50 UTC). Archived by Rewindex: https://rewindex.com/company/discord/incidents/pj6k93rh0yg4 (CC BY 4.0).
- Markdown link: `[Discord: Session Servers Impacted (2018-01-22)](https://rewindex.com/company/discord/incidents/pj6k93rh0yg4)`


---
Canonical: https://rewindex.com/company/discord/incidents/pj6k93rh0yg4 · Markdown: https://rewindex.com/company/discord/incidents/pj6k93rh0yg4.md · JSON: https://rewindex.com/api/v1/companies/discord/incidents/pj6k93rh0yg4 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T18:10:27.805Z