Discord outage — August 14, 2026
Issue with establishing a call
Discord’s Multiple services was disrupted for 6h 16m on August 14, 2026. 503Radar’s sensors raised the first signal at 00:38 UTC, 5h 44m before the official status page acknowledged impact.
Key facts
| Detected | August 14, 2026 · 00:38 UTC |
| Confirmed | 06:23 UTC · lead time 5h 44m |
| Resolved | 06:54 UTC |
| Duration | 6h 16m |
| Service | Multiple services |
| Official record | https://stspg.io/kg7n5686hk7n |
Timeline
- 00:38Z
Detected · Signal
4 crowd signals for Multiple services on DISCORD crossed the signal threshold. - 06:23Z
Confirmed · Official
An official DISCORD status-page notice corroborated the event — 5h 44m after detection. - 06:54Z
Resolved
Signal volume fell back below the threshold; the event was closed.
How this was detected
1 independent evidence class for Multiple services on DISCORD. 8 crowd reports across bluesky (single platform — not corroborating), z=-0.3σ vs the cell baseline. Official notice confirms it, 5h 44m after the crowd.