New namespace creation restricted across all GCP regions
Monitoring - We have temporarily restricted new Temporal Cloud namespace creation across all GCP regions due to compute capacity constraints. 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
Oct 15, 2026 - 17:12 UTC
Amazon Web Services (AWS) Operational
ap-northeast-1 Operational
ap-northeast-2 Operational
ap-south-1 Operational
ap-south-2 Operational
ap-southeast-1 Operational
ap-southeast-2 Operational
ca-central-1 Operational
eu-central-1 Operational
eu-west-1 Operational
eu-west-2 Operational
sa-east-1 Operational
us-east-1 Operational
us-east-2 Operational
us-west-2 Operational
Capacity Operational
Google Cloud Platform (GCP) Degraded Performance
asia-south1 Operational
europe-west3 Operational
us-east4 Operational
us-central1 Operational
us-west1 Operational
asia-southeast2 Operational
Capacity Degraded Performance
Global Services Operational
Web UI Operational
Cloud Ops API Operational
Metrics Operational
Namespace Management Operational
Auth(n)/Auth(z) Operational
Audit Logging Operational
Export History Operational
Billing Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Oct 15, 2026

Unresolved incident: New namespace creation restricted across all GCP regions.

Oct 14, 2026

Elevated latency and errors in GCP us-west1
Resolved - This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.
Oct 14, 13:36 UTC
Monitoring - Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once monitoring confirms the region is stable.
Oct 14, 13:20 UTC

Oct 13, 2026

No incidents reported.

Oct 12, 2026

No incidents reported.

Oct 11, 2026

No incidents reported.

Oct 10, 2026

Elevated latency and errors in AWS us-east-1
Resolved - This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.
Oct 10, 00:51 UTC
Monitoring - Latency and error rates in AWS us-east-1 have returned to normal levels and affected namespaces have recovered. We are continuing to monitor the region. We will provide another update once failback is complete.
Oct 9, 23:11 UTC
Update - Mitigation remains in progress. We are continuing to fail over affected namespaces with Multi-Region Replication enabled to their replica regions. Some customers may continue to experience elevated latency while this work is underway. We will provide another update within 30 minutes.
Oct 9, 22:50 UTC
Update - We have identified the cause of elevated latency affecting a subset of namespaces in AWS us-east-1. Namespaces with Multi-Region Replication enabled are being failed over to their replica region to restore service. We will provide another update within 30 minutes.
Oct 9, 22:38 UTC
Investigating - We are investigating elevated latency and increased deadline exceeded errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.
Oct 9, 22:33 UTC

Oct 9, 2026

Elevated error rates for cross-region traffic between US AWS regions
Resolved - 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 9, 22:25 UTC
Elevated GCP storage latency in us-central1 – precautionary namespace failover
Resolved - This incident is now resolved.
Oct 9, 02:17 UTC
Monitoring - Cloud Storage latency in GCP us-central1 has returned to normal levels. We are continuing to monitor the region and will begin failing multi-region namespaces back to us-central1 shortly.
Oct 9, 01:04 UTC
Investigating - We are monitoring elevated Cloud Storage latency from GCP in us-central1. As a precaution, multi-region namespaces in this region have been failed over to their replica regions. No impact to workflow execution has been observed. We will fail back once GCP confirms recovery.
Oct 8, 21:53 UTC

Oct 8, 2026

Oct 7, 2026

No incidents reported.

Oct 6, 2026

No incidents reported.

Oct 5, 2026

Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI
Resolved - This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally.
Oct 5, 20:52 UTC
Monitoring - A fix has been implemented and we are seeing recovery for the Temporal Cloud control plane, Cloud Ops API, and Temporal UI. We are continuing to monitor.
Oct 5, 20:39 UTC
Investigating - We are investigating increased errors and timeouts affecting the Temporal Cloud control plane, Cloud Ops API, and Temporal UI. Next update in 30 minutes.
Oct 5, 20:23 UTC

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

No incidents reported.

Oct 1, 2026

UI Disruptions in GCP us-central1
Resolved - 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.
Oct 1, 21:47 UTC
Monitoring - Identified cause and resolved regional UI issue, monitoring for any continued impact.
Oct 1, 21:21 UTC
Update - There are no current workflow disruptions, only UI components affected for impacted namespaces within the region.
Oct 1, 21:07 UTC
Investigating - We are currently investigating an issue where some users in us-central1 GCP are experiencing UI service disruptions.
Oct 1, 21:06 UTC
Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors
Resolved - Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors between 13:26 and 13:56 UTC
Oct 1, 14:00 UTC
Incident History Powered by Atlassian Statuspage