CompaniesTemporal CloudIncidents
Temporal Cloud: Elevated error rates for cross-region traffic between US AWS regions
AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents
Temporal Cloud’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted −7 min vs the first vendor naming AWS)
“…Elevated error rates for cross-region traffic between US AWS regions Between 18:41 and 18:54 UTC on October 9, 2026, cross-region traffic to and from AWS us-east-1, us-east-2, and us-west-2 may have s…”
Swipe sideways to see the whole diagram.
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
me["Temporal Cloud (this incident)<br/>posted −7 min"]:::me
root -.->|"same window"| meFull 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
- resolved
Between 18:41 and 18:54 UTC on October 9, 2026, cross-region traffic to and from AWS us-east-1, us-east-2, and us-west-2 may have seen increased error rates. The issue has been resolved.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Temporal Cloud profileRecent Temporal Cloud incidentsMarkdownJSON