Amazon Web Services outage — July 17, 2026

AWS Billing Console: Inaccurate Estimated Billing Data

Amazon Web Services’s Multiple services was disrupted for 20h 20m 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

Timeline

1. 00:18Z

   Detected · Signal

   5 crowd signals for Multiple services on AWS crossed the signal threshold.
2. 08:38Z

   Confirmed · Official

   An official AWS status-page notice corroborated the event — 8h 19m after detection.
3. 20:39Z

   Resolved

   Signal volume fell back below the threshold; the event was closed.

What people reported

“🟠 Flexera is reporting a Partial Outage since 10:24 UTC "Flexera- Spot- All regions - Incorrect AWS billing data" Affects: Spot UI Live timeline → https://pi”bluesky_jetstream · 10:30 UTC

“We know data centers would be primary targets in future hybrid wars. We saw the huge crash in companies when the Amazon cloud went down.”bluesky_jetstream · 10:33 UTC

“I panicked this morning. I am 3 days into my first and new home, with a mortgage, and then AWS slap this to me. I have a dead AWS account that has historically ”bluesky_jetstream · 11:21 UTC

“This seems like one of those days where you reboot six times to try to fix your network connection and then find out there's an AWS outage”bluesky_jetstream · 15:53 UTC

“You're not working hard enough if your AWS bill isn't $1.7B.”news.yc · 18:27 UTC

How this was detected

1 independent evidence class for Multiple services on AWS. 5 crowd reports across bluesky, hn_comments (below the anomaly threshold), z=+0.4σ vs the cell baseline. Official notice confirms it, 8h 19m after the crowd.