rewindex

RewindexOutage eventsNov 6, 2026

AWS outage, Nov 6, 2026

8 linked vendors posted 8 incidents between and . 5 vendors named AWS in 5 incidents (3 of them blamed it), and 1 did so before AWS’s own status page; 3 more are tied in by a known dependency. AWS posted “Elevated Launch Failures (us-west-2)” at 22:51 UTC. 8 other vendors had incidents in the same window; nothing links them to AWS (listed below).

Observed, not verified. A line means a vendor’s incident named another vendor, or a known dependency (declared by the vendor and named as a cause before). It is not a proven cause. Incidents that only share the time window are listed apart.

Times are in UTC; lags are from when AWS posted ().

    9. AWS posted first vendor named AWS
Named AWSNamed another vendor or depends on oneEach 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: a known dependency, not named in the incident.

Swipe sideways to see the whole diagram.

depends on AWSAWSposted 22:51 UTCPosted before AWS did1 vendorHightouchWithin an hour3 vendors, 2 blamed AWSDagster, Databricks, Semgrep1 to 4 hours later1 vendor, 1 blamed AWSStarburstKnown dependency3 vendorsBandwidth, Sigma Computing, Segment
depends on AWSAWSposted 22:51 UTCPosted before AWS did1 vendorHightouchWithin an hour3 vendors, 2 blamed AWSDagster, Databricks, Semgrep1 to 4 hours later1 vendor, 1 blamed AWSStarburstKnown dependency3 vendorsBandwidth, Sigma Computing,Segment
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 22:51 UTC"]:::root
  before["Posted before AWS did<br/>1 vendor<br/>Hightouch"]:::names
  root --> before
  h1["Within an hour<br/>3 vendors, 2 blamed AWS<br/>Dagster, Databricks, Semgrep"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Starburst"]:::blames
  root --> h4
  dr["Known dependency<br/>3 vendors<br/>Bandwidth, Sigma Computing, Segment"]:::hop2
  root -.->|"depends on AWS"| dr

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

1 vendor

  • −1 h 51 min

    Names AWS

    Incident, no impact listed

    HightouchProcessing delay for subset of Events

    …etween 3:45 PM and 4:40 PM ET, a small portion of events sent to Event Streaming syncs in us-east-1 were delayed by up to 55 minutes. The underlying problem has been addressed and all impacted Events…

Within an hour

3 vendors

  • +22 min

    Blames AWS

    Major incident

    DagsterElevated errors in launching serverless runs

    …Elevated errors in launching serverless runs AWS resolved the outage on their end, ECS tasks are being placed An upstream issue in AWS was causing errors in Dagster+, which was preventing Dagster+ Ser…

  • +30 min

    Names AWS

    Critical incident

    DatabricksES-2342108

    …ute, Databricks SQL, and Lakeflow Jobs were unavailable for customers using Databricks on AWS in the us-west-2 region. Affected customers may have encountered cluster launch failures, delays starting…

  • +55 min

    Blames AWS

    Minor incident

    SemgrepPossibly Delayed Scans

    …bly Delayed Scans We have observed full recovery of affected systems. We are observing an AWS EC2 failure in at least one region. We are observing that we have sufficient capacity to handle current lo…

1 to 4 hours later

1 vendor

Linked by a known dependency

These incidents did not name AWS, but the vendor declares the vendors shown as a dependency and has named it as a cause before.

Also happening at the same time (not linked)

8 incidents from 8 vendors started in this window without naming AWS or a linked vendor, and with no known dependency on them. Listed for context only; they are not counted as part of the event (an ordinary week has about 12 incidents in these hours).

Show all 8

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