# Discord: Major Service Impact

> Discord status incident “Major Service Impact” on 2018-04-12: impact none (vendor’s label), 2.0 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/discord/incidents/xz52r2qb2y4v
Last updated: 2018-04-13T00:06:00Z

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

## Timeline of updates

- **resolved** 2018-04-13 00:06 UTC: Discord is stable and we do not believe there will be a recurrence of today's issue at this time. We are still working on root causing what happened but are pushing out some mitigations to address some of the problems we saw in the incident.

_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-04-12 22:08 UTC, resolved after 2.0 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/discord/incidents/xz52r2qb2y4v
- Citation: Discord, “Major Service Impact” (2018-04-12 22:08 UTC). Archived by Rewindex: https://rewindex.com/company/discord/incidents/xz52r2qb2y4v (CC BY 4.0).
- Markdown link: `[Discord: Major Service Impact (2018-04-12)](https://rewindex.com/company/discord/incidents/xz52r2qb2y4v)`


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