Temporal Cloud outage, 31 October 2026
Intermittent request failures for some namespaces in GCP us-east4
- Started
- Resolved
- 31 Oct 2026, 14:16 UTC (after 45 min)
- Impact
- Minor
- Affected
- us-east4
Is this still happening?
No. Temporal Cloud marked this incident resolved on 31 Oct 2026, 14:16 UTC, 45 min after it began.
Right now: Temporal Cloud reports degraded performance on some systems. (as of 31 Oct, 14:54 UTC) Live Temporal Cloud status
Last update from Temporal Cloud
This incident has been resolved.
Read the full incident on the official Temporal Cloud status page
Similar Temporal Cloud incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved
-
, resolved after 29 min
Some customers in GCP us-east4 may experience elevated latencies
-
, resolved after 2 h 10 min
Some customers in GCP us-east4 may experience elevated latencies
-
, still open
-
, resolved after 4 h 24 min
Elevated GCP storage latency in us-central1 - precautionary namespace failover
Other recent Temporal Cloud incidents
-
Elevated error rates for cross-region traffic between US AWS regions
-
Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI
-
Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors
-
Some customers may have incorrectly received a "credit expiry notification"