Temporal Cloud outage, 19 October 2026
Elevated connection resets for some GCP namespaces
- Started
- Resolved
- 19 Oct 2026, 22:13 UTC
- Impact
- Not stated
- Affected
- us-east4, us-central1
Is this still happening?
No. Temporal Cloud marked this incident resolved on 19 Oct 2026, 22:13 UTC.
Right now: Temporal Cloud reports degraded performance on some systems. (as of 26 Oct, 03:45 UTC) Live Temporal Cloud status
Last update from Temporal Cloud
Between October 6 and October 15, 2026, some clients connected to GCP-hosted namespaces may have seen intermittent TCP connection resets. SDK retries limited the impact and there is no ongoing impact.
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 after 5 h 55 min
-
, 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"