Elevated error rates in GCP us-central1
GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.
The latest update from Temporal Cloud.
State
Resolved
Started
61 d ago
2026-09-01 15:47 UTC
Lasted
5 h 56 min
until 2026-09-01 21:43 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
20 min 6%
Identified
5 h 36 min 94%
Updates
Times in UTCAs posted by Temporal Cloud
GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.
We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
We are currently investigating elevated error rates in GCP us-central1, and have failed over MRN namespaces in this region.
Affected components
2Temporal Cloud in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
36
Median duration
45 min
This incident
8.0× the median
Other Temporal Cloud incidents
All incidentsTemporal Cloud·Intermittent request failures for some namespaces in GCP us-east4
This incident has been resolved.
Temporal Cloud·Elevated connection resets for some GCP namespaces
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.
Temporal Cloud·New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3
New namespace creation does not work in Temporal Cloud GCP regions us-central1, us-east4 and europe-west3. Capacity components are affected. Existing namespaces continue to operate normally. The provider reports the state as monitoring. A workaround and alternatives are at the provided documentation link.
Temporal Cloud·Elevated latency and errors in GCP us-west1
This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.
Temporal Cloud·Elevated latency and errors in AWS us-east-1
This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.
Follow Temporal Cloud
Your coding agent knows when Temporal Cloud is down, and tells you when a failure is theirs, not yours. You can also get Temporal Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "temporal" and tell me if Temporal Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=temporal/feed subscribe https://outages.cc/feed.xml?providers=temporalFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane