RewindexOutage eventsJul 16, 2026
AWS outage, Jul 16, 2026
26 vendors posted 24 incidents between 08:00 and 22:00 UTC, against about 57 incidents from 35 vendors in the same hours on an ordinary week. 4 vendors named AWS in 4 incidents (3 of them blamed it), and 2 did so before AWS’s own status page. AWS posted “Increased 5xx Errors (global)” at 08:44 UTC.
Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.
Times are UTC; lags are from when AWS posted (08:44).
- AWS posted 08:44first vendor named AWS 08:29
How it spread
Vendors that named AWS, grouped by when they posted, and vendors that blamed one of the vendors AWS took down. Solid lines: the vendor named the other. Dashed: same window, not named.
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>posted 08:44 UTC"]:::root
before["Posted before AWS did<br/>2 vendors, 1 blamed AWS<br/>FusionAuth, Upstash"]:::blames
root --> before
h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Coda, Grammarly"]:::blames
root --> h1
p0["Anthropic<br/>posted −5 min, did not name AWS"]:::timing
root -.-> p0
k0["GitHub, GitHub Copilot<br/>+12 h 21 min"]:::hop2
p0 -->|"blamed Anthropic"| k0Vendors that named AWS
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Posted before AWS did
2 vendors
- Critical incident
−14 min
Blames AWS
FusionAuthInvestigating outage affecting multiple regions
…Investigating outage affecting multiple regions The AWS issue is still ongoing, but we have restored traffic by modifying our routing to avoid the impacted AWS services. All FusionAuth services should…
- Incident, no impact listed
−9 min
Names AWS
UpstashQStash us-east-1 - URL Publish Errors
…QStash us-east-1 - URL Publish Errors Partial outage due to http parsing errors. Problem was resolved couple minutes later. If problem continues, refreshing the DNS cache is recommended. Partial outag…
Within an hour
2 vendors
- Minor incident
+13 min
Blames AWS
CodaIssue affecting access to coda.io
…Issue affecting access to coda.io Amazon has resolved the CloudFront service outage, and our services are back to normal. Amazon has resolved the CloudFront service outage, and our services are back t…
- Minor incident
+15 min
Blames AWS
GrammarlyLogin to Grammarly via superhuman.com may be temporarily unavailable
…in to Grammarly via superhuman.com may be temporarily unavailable Amazon has resolved the CloudFront service outage, and our services are back to normal. Amazon has resolved the CloudFront service out…
Second hop: vendors that named another vendor
These incidents name a vendor other than AWS, for example a messaging or CDN provider that was itself affected.
- Minor incident
+12 h 21 min
Blames Anthropic
GitHuband GitHub CopilotClaude Fable 5 experiencing degraded performance
…Claude Fable 5 experiencing degraded performance On July 16, 2026, GitHub Copilot users experienced elevated errors when using Claude Fable 5 from 17:33 UTC until mitigation at 22:04 UTC. The average…
Same window, did not name anyone
19 incidents started during the event without naming AWS or another vendor. Some are part of it, some are a normal day’s background (about 57 in these hours).
Show all 19
- −41 minMinor incident
- −38 minMinor incident
- −17 minMajor incident
- −16 minMajor incident
- −12 minMajor incident
- −5 minCritical incident
- −5 minMinor incident
- −4 minMajor incident
- −4 minMajor incident
- +16 minIncident
- +16 minCritical incident
- +20 minMinor incident
- +22 minMinor incident
- +29 minCritical incident
- +29 minMajor incident
- +35 minMinor incident
- +44 minCritical incident
- +55 minMajor incident
- +1 h 1 minCritical incident
Detected automatically from 16 status pages opening incidents in the peak hour (normally at most 7). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.