Rewindex

CompaniesTemporal CloudIncidents

Temporal Cloud: Customers in GCP us-central1 may experience elevated API latencies

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

Google Cloud outage, Aug 6, 2025 · 12 vendors, 12 incidents

Temporal Cloud’s incident names Google Cloud (location or integration). (hop 1, posted +0 min vs the first vendor naming Google Cloud)

“…Customers in GCP us-central1 may experience elevated API latencies This incident has been resolved.…”

Swipe sideways to see the whole diagram.

blamed TwilioGoogle Cloudown incident not archivedWithin an hour4 vendors, 2 blamed Google CloudTemporal Cloud, Confluent, Grafana Cloud, JFrog1 to 4 hours later1 vendor, 1 blamed Google CloudBasetenTwilioposted +42 min, did not name Google CloudBrex, Close+2 h 3 min to +5 h 16 minTemporal Cloud (this incident)posted +0 min
blamed TwilioGoogle Cloudown incident not archivedWithin an hour4 vendors, 2 blamed GoogleCloudTemporal Cloud, Confluent,Grafana Cloud, JFrog1 to 4 hours later1 vendor, 1 blamed GoogleCloudBasetenTwilioposted +42 min, did not nameGoogle CloudBrex, Close+2 h 3 min to +5 h 16 minTemporal Cloud (this incident)posted +0 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["Google Cloud<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>4 vendors, 2 blamed Google Cloud<br/>Temporal Cloud, Confluent, Grafana Cloud, JFrog"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Google Cloud<br/>Baseten"]:::blames
  root --> h4
  p0["Twilio<br/>posted +42 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Brex, Close<br/>+2 h 3 min to +5 h 16 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  me["Temporal Cloud (this incident)<br/>posted +0 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