Rewindex

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).

  1. AWS posted 08:44first vendor named AWS 08:29
Named AWSNamed another vendorDid not name anyoneEach column is 30 minutes

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.

blamed AnthropicAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not name AWSGitHub, GitHub Copilot+12 h 21 min
blamed AnthropicAWSposted 08:44 UTCPosted before AWS did2 vendors, 1 blamed AWSFusionAuth, UpstashWithin an hour2 vendors, 2 blamed AWSCoda, GrammarlyAnthropicposted −5 min, did not nameAWSGitHub, GitHub Copilot+12 h 21 min
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
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"| k0

Vendors 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

  • −14 min

    Blames AWS

    Critical incident

    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…

  • −9 min

    Names AWS

    Incident, no impact listed

    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

  • +13 min

    Blames AWS

    Minor incident

    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…

  • +15 min

    Blames AWS

    Minor incident

    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.

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

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.