Rewindex

RewindexOutage eventsOct 9, 2026

AWS us-east-1 outage, Oct 9, 2026

17 vendors posted 17 incidents between 21:00 on Oct 9 and 10:00 on Oct 10 UTC, against about 21 incidents from 17 vendors in the same hours on an ordinary week. 6 vendors named AWS in 6 incidents (3 of them blamed it). Vendors reported an AWS outage; AWS’s own incident for this date is not in the archive.

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 the first vendor named AWS.

    27. first vendor named AWS 22:33
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.

AWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud, JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebee
AWS us-east-1own incident not archivedWithin an hour5 vendors, 2 blamed AWSConvex, Temporal Cloud,JFrog, PlanetScale +1Later1 vendor, 1 blamed AWSChargebee
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 us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
  root --> later

Vendors that named AWS

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

5 vendors

  • +0 min

    Names AWS

    Major incident

    ConvexFailing function calls

    …On 2026-10-09, between 22:11 and 22:52 UTC, some query and mutation executions running in us-east-1 failed to run. This outage was caused by a network issue at an upstream provider. The problem is now…

  • +1 min

    Names AWS

    Minor incident

    Temporal CloudElevated latency and errors in AWS us-east-1

    …Elevated latency and errors in AWS us-east-1 This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back. Latency and error rates in AWS us-ea…

  • +18 min

    Names AWS

    Incident, no impact listed

    JFrogJFrog Cloud Platform outage affecting subset of customers in AWS US East region

    …JFrog Cloud Platform outage affecting subset of customers in AWS US East region This incident has been resolved. A fix has been implemented and we are monitoring the results. This incident has been re…

  • +20 min

    Blames AWS

    Major incident

    PlanetScaleAWS us-east-1 connectivity failures

    …AWS us-east-1 connectivity failures AWS us-east-1 cross-zone networking has fully recovered. A small number of database branches in AWS us-east-1 were impacted by cross-zone networking issues, for whi…

  • +54 min

    Blames AWS

    Major incident

    ConfluentPossible outage in AWS us-east-1

    …Possible outage in AWS us-east-1 This incident has been resolved. All affected services have fully recovered. The observed elevated error rates seen in AWS us-east-1 have subsided and all services hav…

Later

1 vendor

  • +11 h 1 min

    Blames AWS

    Minor incident

    ChargebeeAPI Service Degradation

    …ervice Degradation We experienced a brief service interruption in the US region due to an AWS platform issue, which resulted in intermittent API failures for some merchants. All services have complete…

Same window, did not name anyone

11 incidents started during the event without naming AWS or another vendor. Some are part of it, some are a normal day’s background (about 21 in these hours).

Show all 11

Detected automatically from 12 status pages opening incidents in the peak hour (normally at most 8). 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.