Rewindex

Companiesv0Incidents

v0: Elevated errors across multiple services in IAD1 (Washington, D.C., USA)

MinorStatus: resolvedStarted Resolved (5.3 h)1 updatewww.vercel-status.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, May 8, 2026 · 38 vendors, 43 incidents

v0’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +53 min vs AWS’s own post)

Swipe sideways to see the whole diagram.

same windowAWS 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, SingleStorev0 (this incident)posted +53 min
same windowAWS 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, SingleStorev0 (this incident)posted +53 min
v0 is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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
  me["v0 (this incident)<br/>posted +53 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    We've deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in the IAD1 region.

From v0’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on www.vercel-status.com (opens in new tab).

v0 profileRecent v0 incidentsMarkdownJSON