# Discord: Investigating Service Degradation

> Discord status incident “Investigating Service Degradation” on 2018-03-17: impact none (vendor’s label), 3.3 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/discord/incidents/2cb5jc53jq28
Last updated: 2018-03-17T22:49:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2018-03-17 19:34 UTC · Resolved: 2018-03-17 22:49 UTC · Duration: 3.3 h
- Updates: 1
- [Vendor status page: https://discordstatus.com/incidents/2cb5jc53jq28](https://discordstatus.com/incidents/2cb5jc53jq28)
- [Company: Discord](https://rewindex.com/company/discord.md)

## Timeline of updates

- **resolved** 2018-03-17 22:49 UTC: Discord has been operating normally for more than an hour. All graphs are nominal and we understand what happened. The very brief synopsis is that we had table contention on the MongoDB instance that underlies a portion of our system. We do not believe this particular incident will recur in the near future.

_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-03-17 19:34 UTC, resolved after 3.3 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/discord/incidents/2cb5jc53jq28
- Citation: Discord, “Investigating Service Degradation” (2018-03-17 19:34 UTC). Archived by Rewindex: https://rewindex.com/company/discord/incidents/2cb5jc53jq28 (CC BY 4.0).
- Markdown link: `[Discord: Investigating Service Degradation (2018-03-17)](https://rewindex.com/company/discord/incidents/2cb5jc53jq28)`


---
Canonical: https://rewindex.com/company/discord/incidents/2cb5jc53jq28 · Markdown: https://rewindex.com/company/discord/incidents/2cb5jc53jq28.md · JSON: https://rewindex.com/api/v1/companies/discord/incidents/2cb5jc53jq28 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:00:57.103Z