Amazon Web Services outage — July 17, 2026
AWS Billing Console: Inaccurate Estimated Billing Data
Amazon Web Services’s Multiple services was disrupted for 9h 00m on July 17, 2026. 503Radar’s sensors raised the first signal at 00:18 UTC, 8h 19m before the official status page acknowledged impact.
Key facts
| Detected | July 17, 2026 · 00:18 UTC |
| Confirmed | 08:38 UTC · lead time 8h 19m |
| Resolved | 09:19 UTC |
| Duration | 9h 00m |
| Service | Multiple services |
| Official record | https://health.aws.amazon.com/health/status |
Timeline
- 00:18Z
Detected · Signal
5 crowd signals for Multiple services on AWS crossed the signal threshold. - 08:38Z
Confirmed · Official
An official AWS status-page notice corroborated the event — 8h 19m after detection. - 09:19Z
Resolved
Signal volume fell back below the threshold; the event was closed.
What people reported
“"Zero Downtime Deployment in AWS with Tofu/Terraform and SAM" by Jorge Tovar #serverless #python #aws-sam #terraform #disaster-recovery”bluesky_jetstream · 21:32 UTC
“AWS IS HAVING ISSUES. PROLLY ALL THOSE DANK MEMES I DROPPED ON IT.”bluesky_jetstream · 02:03 UTC
“We’re officially going cold turkey - Amazon Mechanical Turk is being slowly shut down. The foundational took for AI launched in 2005, and is now closed to new c”@jbrodley.tcp.fm.ap.brid.gy · 06:02 UTC
“P.S. We break down AWS concepts visually every week in our free newsletter. Join at awsfundamentals.com/newsletter”@tpschmidt.com · 07:02 UTC
“Cloud compute is still hugely supply-limited and the big AI companies are paying 4-10x more for compute than most people are paying AWS/Azure. Companies are bui”@tuftyindigo.bsky.social · 07:21 UTC
How this was detected
1 independent evidence class for Multiple services on AWS. 5 crowd reports across bluesky (single platform — not corroborating), z=+0.0σ vs the cell baseline. Official notice confirms it, 8h 19m after the crowd.