Rewindex

CompaniesTemporal CloudIncidents

Temporal Cloud: Cloud APIs impacted because of AWS us-east-1 incident

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

AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents

Temporal Cloud’s incident blames AWS as the cause. (hop 1, posted +17 min vs the first vendor naming AWS)

“…Cloud APIs impacted because of AWS us-east-1 incident This incident has been resolved.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, Temporal Cloud +101 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana +4Temporal Cloud (this incident)posted +17 min
AWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, TemporalCloud +101 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana +4Temporal Cloud (this incident)posted +17 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<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
  root --> h4
  me["Temporal Cloud (this incident)<br/>posted +17 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

    This incident has been resolved.

From Temporal Cloud’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 status.temporal.io (opens in new tab).

Temporal Cloud profileRecent Temporal Cloud incidentsMarkdownJSON