outages.live
Live

Temporal Cloud

Temporal Cloud is reporting degraded

Checked 58 s ago Degraded

Partially Degraded Service

New namespace creation restricted across few GCP regions. Impacted regions are us-central1, us-east4 and europe-west3

New Temporal Cloud namespace creation does not work in the GCP regions us-central1, us-east4, and europe-west3. Existing namespaces continue to operate normally. Temporal Cloud reports the status as monitoring, and the restriction is still in place after 23973 minutes.

Degradedupdated 10 d ago

History

90 days agoToday

Incidents in 90 days

20

Days with an incident

37

Median duration

45 min

Longest incident

10 h 30 min

Components

30

Amazon Web Services (AWS)

ap-northeast-1 Operational
90 days agoNo incidentsToday
ap-northeast-2 Operational
90 days agoNo incidentsToday
ap-south-1 Operational
90 days agoNo incidentsToday
ap-south-2 Operational
90 days agoNo incidentsToday
ap-southeast-1 Operational
90 days agoNo incidentsToday
ap-southeast-2 Operational
90 days agoNo incidentsToday
ca-central-1 Operational
90 days agoNo incidentsToday
eu-central-1 Operational
90 days agoNo incidentsToday
eu-west-1 Operational
90 days ago1 day with an incidentToday
eu-west-2 Operational
90 days agoNo incidentsToday
sa-east-1 Operational
90 days agoNo incidentsToday
us-east-1 Operational
90 days ago2 days with an incidentToday
us-east-2 Operational
90 days agoNo incidentsToday
us-west-2 Operational
90 days ago4 days with an incidentToday
Capacity Operational
90 days agoNo incidentsToday

Google Cloud Platform (GCP)

asia-south1 Operational
90 days agoNo incidentsToday
europe-west3 Operational
90 days agoNo incidentsToday
us-east4 Operational
90 days ago2 days with an incidentToday
us-central1 Operational
90 days ago4 days with an incidentToday
us-west1 Operational
90 days ago2 days with an incidentToday
asia-southeast2 Operational
90 days ago2 days with an incidentToday
Capacity Degraded
90 days ago19 days with an incidentToday

Global Services

Web UI Operational
90 days ago1 day with an incidentToday
Cloud Ops API Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 31, 2026

Duration45 min13:31 to 14:16Intermittent request failures for some namespaces in GCP us-east4Degraded

This incident has been resolved.

Oct 19, 2026

Duration1 min22:13 to 22:13Elevated connection resets for some GCP namespacesNotice

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.

Oct 14, 2026

Duration17 min13:20 to 13:36Elevated latency and errors in GCP us-west1Notice

This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.

Oct 9, 2026

Duration2 h 17 min22:33 to 00:51Elevated latency and errors in AWS us-east-1Degraded

This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.

Duration1 min22:25 to 22:25Elevated error rates for cross-region traffic between US AWS regionsNotice

Between 18:41 and 18:54 UTC on October 9, 2026, cross-region traffic to and from AWS us-east-1, us-east-2, and us-west-2 may have seen increased error rates. The issue has been resolved.

Oct 8, 2026

Duration4 h 25 min21:53 to 02:17Elevated GCP storage latency in us-central1 – precautionary namespace failoverNotice

This incident is now resolved.

Oct 5, 2026

Duration29 min20:23 to 20:52Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIMajor outage

This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally.

Oct 1, 2026

Duration40 min21:07 to 21:47UI Disruptions in GCP us-central1Degraded

Between 20:40 and 21:12 UTC, some users in GCP us-central1 experienced disruptions to the UI. We continued monitoring through the affected period and have seen no further reports since. This incident is now resolved.

Sep 27, 2026

Duration53 min01:01 to 01:53Increased latency in region us-west-2Degraded

The issue is resolved and service is operating normally.

Sep 18, 2026

Duration6 h 29 min15:54 to 22:23Some customers may have incorrectly received a "credit expiry notification"Degraded

This incident has been resolved.

Sep 11, 2026

Duration4 h 19 min10:10 to 14:29Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)Notice

This incident has been resolved.

Sep 10, 2026

Duration10 h 30 min20:51 to 07:21Customers in us-central1 and asia-southeast2 may experience a delay in workflow progressPartial outage

The environment has been validated and all residual issues have been cleared. This incident is now resolved.

Sep 3, 2026

Duration8 h 16 min21:12 to 05:28Elevated Errors in us-west-2 RegionDegraded

As of 9/4 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved.

Affected components

1
  • CapacityGoogle Cloud Platform (GCP)Degraded

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=temporal
Slack
/feed subscribe https://outages.live/feed.xml?providers=temporal

Go from tracking outages to fixing production issues with Polylane.

Try Polylane