Amazon Web Services outage — July 24, 2026
Connectivity Issues
Amazon Web Services’s Multiple services was disrupted for 1h 35m on July 24, 2026. 503Radar’s sensors raised the first signal at 11:33 UTC, 9m 08s before the official status page acknowledged impact.
Key facts
| Detected | July 24, 2026 · 11:33 UTC |
| Confirmed | 11:43 UTC · lead time 9m 08s |
| Resolved | 13:09 UTC |
| Duration | 1h 35m |
| Service | Multiple services · us-west-2 |
| Official record | https://health.aws.amazon.com/health/status |
Timeline
- 11:33Z
Detected · Signal
3 crowd signals for Multiple services on AWS crossed the signal threshold. - 11:43Z
Confirmed · Official
An official AWS status-page notice corroborated the event — 9m 08s after detection. - 13:09Z
Resolved
Signal volume fell back below the threshold; the event was closed.
What people reported
“🔴 TecAlliance TecDoc is reporting a Major Outage since 11:06 UTC "TecDoc Web Service Region Specific…" Affects: US-West-2, Region AWS US-West-2 Live timelin”@pingoru.bsky.social · 11:14 UTC
“🟠 Amazon Web Services is reporting a Partial Outage since 11:40 UTC "Multiple services — Oregon: Connectivity Issues" Affects: Multiple services — Oregon Liv”bluesky_jetstream · 11:49 UTC
“Don't be surprised if you see some service outages right now. Amazon AWS West-2 in Oregon is apparently down/impacted which is causing Blizzard's BattleNet and ”bluesky_jetstream · 12:45 UTC
How this was detected
1 independent evidence class for Multiple services on AWS. 3 crowd reports across bluesky (single platform — not corroborating), z=+2.3σ vs the cell baseline. Official notice confirms it, 9m 08s after the crowd.