# Discord: User traffic anomaly

> Discord status incident “User traffic anomaly” on 2020-11-07: impact none (vendor’s label), 48 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/discord/incidents/2vz211zd63p4
Last updated: 2020-11-07T14:34:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2020-11-07 13:46 UTC · Resolved: 2020-11-07 14:34 UTC · Duration: 48 min
- Updates: 1
- [Vendor status page: https://discordstatus.com/incidents/2vz211zd63p4](https://discordstatus.com/incidents/2vz211zd63p4)
- [Company: Discord](https://rewindex.com/company/discord.md)

## Timeline of updates

- **resolved** 2020-11-07 14:34 UTC: The root cause upstream has been fixed and the secondary incident on our end (our Envoy cluster got into a permanently "circuit broken" state and needed a reboot) has been mitigated, so we are declaring this incident to be resolved. We will continue to work to understand the degenerate behavior in our load balancing layer and implement a more permanent fix so that this does't recur.

_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 2020-11-07 13:46 UTC, resolved after 48 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/discord/incidents/2vz211zd63p4
- Citation: Discord, “User traffic anomaly” (2020-11-07 13:46 UTC). Archived by Rewindex: https://rewindex.com/company/discord/incidents/2vz211zd63p4 (CC BY 4.0).
- Markdown link: `[Discord: User traffic anomaly (2020-11-07)](https://rewindex.com/company/discord/incidents/2vz211zd63p4)`


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