Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures
Temporal Cloud reports that some customers connecting over AWS PrivateLink in us-west-2 can have connection failures. The components are us-west-2 and AWS us-west-2. Temporal Cloud applied a mitigation and monitors the results.
State
Monitoring
Started
Ongoing for
1 h 20 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
43 min 54%
Identified
6 min 7%
Monitoring
31 min 39%
Updates
Times in UTCAs posted by Temporal Cloud
We applied a mitigation and are monitoring the results.
We've identified the issue, and mitigation is in progress.
Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures We are investigating
Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures We are investigating
Affected components
2Temporal Cloud in the last 90 days
Full historyIncidents in 90 days
20
Days with an incident
40
Median duration
49 min
This incident
1.6× 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