Amazon Web Services outage — July 16, 2026
Amazon CloudFront: Increased 5xx Errors
Amazon Web Services’s Networking & CDN has a confirmed disruption, detected on July 16, 2026. 503Radar’s sensors raised the first signal at 08:43 UTC, 4m 17s before the official status page acknowledged impact.
Key facts
| Detected | July 16, 2026 · 08:43 UTC |
| Confirmed | 08:48 UTC · lead time 4m 17s |
| Service | Networking & CDN |
| Official record | https://health.aws.amazon.com/health/status |
Timeline
- 08:43Z
Detected · Signal
16 crowd signals for Networking & CDN on AWS crossed the signal threshold. - 08:48Z
Confirmed · Official
An official AWS status-page notice corroborated the event — 4m 17s after detection.
What people reported
“Is AWS Amazon CloudFront down for you? Users are reporting problems with AWS Amazon CloudFront. Repost if you are having issues. #awsdown”@isdown.app · 08:34 UTC
“It looks it affects many services, e.g. I'm not able to re-auth many of the MCPs in claude code as all requests to WorkOS timeout with 504 Gateway Timeout,”news.yc · 08:39 UTC
“oh, up early to get stuff done? well # AWS Cloudfront # outage seems to have come to the rescue. :-\”#outage · 08:46 UTC
“🟠 Amazon Web Services is reporting a Partial Outage since 08:44 UTC "Amazon CloudFront: Increased 5xx Errors" Affects: Amazon CloudFront Live timeline → http”@pingoru.bsky.social · 08:50 UTC
“# AmazonWebServices # Cloudfront is broken. Expect half the internet to be down”#mastodon · 08:50 UTC
“AWS VPC is down. All my apps went down out of the blue. Customers started calling me all at once. Codex fixed it in 4 minutes and 38 seconds by temporarily rero”bluesky_jetstream · 08:51 UTC
How this was detected
2 independent evidence classes for networking on AWS. 13 crowd reports across bluesky, hn_comments, mastodon (independent class), z=+5.8σ vs the cell baseline; 3 press mentions (corroboration). Official notice confirms it, 4m 17s after the crowd.