Temporal Cloud: Errors and higher latencies observed in us-west-2 & us-east-1 (Related to AWS network errors)

MinorStatus: resolvedStarted 2023-09-18 19:18 UTCResolved 2023-09-18 23:15 UTC (4.0 h)1 updatestatus.temporal.io

Part of an outage event

AWS outage, Sep 18, 2023 · 29 vendors, 29 incidents

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

“…Errors and higher latencies observed in us-west-2 & us-east-1 (Related to AWS network errors) This incident has been resolved.…”

Swipe sideways to see the whole diagram.

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/>3 vendors, 1 blamed AWS<br/>Dagster, Snowflake, Vanta"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 5 blamed AWS<br/>Amplitude, Temporal Cloud, Coralogix, Confluent +3"]:::blames
  root --> h4
  me["Temporal Cloud (this incident)<br/>posted +1 h 11 min"]:::me
  h4 --- 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

resolved2023-09-18 23:15 UTC
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.

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

Temporal Cloud profile Recent Temporal Cloud incidents Markdown JSON