Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
The environment has been validated and all residual issues have been cleared. This incident is now resolved.
The latest update from Temporal Cloud.
State
Resolved
Started
52 d ago
2026-09-10 20:51 UTC
Lasted
10 h 30 min
until 2026-09-11 07:21 UTC
Worst impact
Partial outage
Timeline
7 updatesIdentified
1 h 36 min 15%
Monitoring
8 h 54 min 85%
Updates
Times in UTCAs posted by Temporal Cloud
The environment has been validated and all residual issues have been cleared. This incident is now resolved.
A configuration change affecting namespaces in the us-central1 and asia-southeast2 regions resulted in some workflow requests not being processed as expected. The change was rolled back and workflow processing resumed. We are continuing to validate the environment and clear any residual issues, and will provide further updates as that work completes.
We are continuing to monitor for any further issues.
While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.
We are continuing to monitor for any further issues.
The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.
Some customers with namespaces in the us-central1 and asia-southeast2 regions may experience errors and blocked progress on their workflows. We are currently rolling out a fix.
Affected components
4Temporal Cloud in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
36
Median duration
45 min
This incident
14× 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