Rewindex

CompaniesTemporal CloudIncidents

Temporal Cloud: Some customers in AWS us-east-1 may experience elevated API latencies

MinorStatus: resolvedStarted Resolved (27 h)1 updatestatus.temporal.io (opens in new tab)
Part of an outage event

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

Temporal Cloud’s incident blames AWS as the cause. (hop 1, posted +49 min vs AWS’s own post)

“…Some customers in AWS us-east-1 may experience elevated API latencies AWS has resolved the underlying infrastructure issues in us-east-1. We have marked the region as healthy and are failing our AWS u…”

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, SingleStoreTemporal Cloud (this incident)posted +49 min
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, SingleStoreTemporal Cloud (this incident)posted +49 min
Temporal Cloud 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["Temporal Cloud (this incident)<br/>posted +49 min"]:::me
  h1 --- 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

    AWS has resolved the underlying infrastructure issues in us-east-1. We have marked the region as healthy and are failing our AWS us-east-1 primary multi-region replication customers back into this region.

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

Impact, status and times are the vendor’s own, as last archived. View on status.temporal.io (opens in new tab).

Temporal Cloud profileRecent Temporal Cloud incidentsMarkdownJSON