Rewindex

RewindexOutage eventsMay 8, 2026

AWS us-east-1 outage, May 8, 2026

37 vendors posted 38 incidents between 22:00 on May 7 and 10:00 on May 8 UTC, against about 22 incidents from 19 vendors in the same hours on an ordinary week. 25 vendors named AWS in 27 incidents (23 of them blamed it), and 3 did so before AWS’s own status page. AWS posted “Increased Error Rate and Latency (us-east-1)” at 00:25 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 (00:25).

    25. AWS posted 00:25first vendor named AWS 22:55
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-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack, Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign, Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStore
AWS us-east-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack,Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign,Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStore
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/>posted 00:25 UTC"]:::root
  before["Posted before AWS did<br/>3 vendors, 2 blamed AWS<br/>Neon, Datadog, Convex"]:::blames
  root --> before
  h1["Within an hour<br/>11 vendors, 11 blamed AWS<br/>Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>10 vendors, 9 blamed AWS<br/>Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed AWS<br/>Wiz, SingleStore"]:::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”…).

Posted before AWS did

3 vendors

  • −1 h 30 min

    Names AWS

    Incident, no impact listed

    NeonES-1900190

    …een 20:03 UTC and 22:13 UTC on May 7, 2026, a subset of customers using Neon databases in AWS us-east-1 may have experienced issues with compute endpoints not scaling down to zero after periods of ina…

  • −19 min

    Blames AWS

    Critical incident

    DatadogDelayed Monitors Notifications

    …ovider issues, we are also continuing to see unavailability of telemetry data coming from AWS into Datadog. https://health.aws.amazon.com/health/status This incident has been resolved. We are investig…

  • −9 min

    Blames AWS

    Major incident

    ConvexIntermittent Impact from AWS Outage

    …Intermittent Impact from AWS Outage We’ve mitigated the impact from AWS’s Availability Zone issue, and service has remained stable. We have not observed further node failures or customer impact, so we…

Within an hour

11 vendors

1 to 4 hours later

11 vendors

Later

2 vendors

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 22 in these hours).

Show all 11

Detected automatically from 17 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.