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.
A language model wrote this summary from the updates of Temporal Cloud.
State
Monitoring
Started
16 d ago
2026-10-15 17:12 UTC
Ongoing for
16 days
Worst impact
Degraded
Timeline
1 updateMonitoring
16 days 100%
Updates
Times in UTCAs posted by Temporal Cloud
We have temporarily restricted new Temporal Cloud namespace creation across few GCP regions due to compute capacity constraints. Impacted regions are us-central1, us-east4 and europe-west3. Existing namespaces continue to operate normally. For details, available alternatives, and how to request an exception, see https://docs.temporal.io/evaluate/cloud/regions#gcp-capacity-restriction
Affected components
2Temporal Cloud in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
18
Median duration
Not enough data
This incident
Not comparable
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