Daily provider-status observations and published incident history for Temporal.
Component incident
Temporal has an active component incident; no global outage is indicated. Verified .
Official provider source.
Looking for an update now? Check the current status, or follow Temporal for future changes.
72.4%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
76.7%
30
7
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
New namespace creation restricted across all GCP regions
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
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.
investigating
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.
investigating
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.
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.
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.
monitoring
We are continuing to monitor for any further issues.
monitoring
While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.
monitoring
We are continuing to monitor for any further issues.
monitoring
The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.
identified
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.
As of 9/4 00:07 UTC, AWS has confirmed the incident impacting us-west-2 is resolved. After a further period of monitoring, we have confirmed service is stable and have begun failing back the affected MRN namespaces.
monitoring
We are starting to see recovery as of 23:01 UTC.
investigating
We are investigating connectivity errors affecting some customers with namespaces in the us-west-2 region relating to an AWS outage in this region. Our team is actively assessing impact and working on mitigation. Affected MRN namespaces have been failed over. We will provide updates as more information becomes available.
https://health.aws.amazon.com/health/status
Low Rate of Namespace Create/Update Failures Across All Regions
We have identified an issue where some customers may receive failures when creating or updating namespaces. We are currently rolling back the affected service. Temporal Cloud will ensure failures are manually retried.
We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev
investigating
We are currently investigating elevated error rates in GCP us-central1, and have failed over MRN namespaces in this region.
Legacy Incident Archive
39 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Some customers may experience a loss in metrics (v0 and v1) starting 19:00 UTC
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Mitigation is complete and global metrics are restored. We are currently monitoring.
identified
Mitigation is still in progress and metrics are slowly being restored across namespaces.
identified
We're in the process of mitigating impact and metrics are slowly being restored across some namespaces.
investigating
Global metrics service has been impacted by this incident. We're working on mitigation.
investigating
We are currently investigating, additional details to come shortly. Impact is limited to metrics only.
Customers in us-east-2 may experience some visibility related errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing full recovery on our end, we are continuing to monitor.
monitoring
Mitigation is in effect, we are seeing some recovery. Please submit a support ticket if you are seeing service degradation.
identified
Mitigation is still in progress. We are scaling up service to help with mitigation efforts.
identified
All MRN-enabled namespaces have been failed over as of 17:53 UTC. Mitigation continues to progress.
identified
We are working on a fix, if your namespace are MRN enabled please fail over to your passive regions for faster recovery.
investigating
Customers with namespaces in us-east-2 may experience errors with visibility queries. We are currently investigating.
Elevated latencies in us-east-1
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Some customers in AWS us-east-1 may experience elevated latencies and errors on their namespaces
Broken Temporal skipping test server link
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are investigating a broken link for the latest version of the Temporal skipping test server
Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The service has remained stable since 15:00 UTC.
We continue to investigate the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are monitoring for any further occurrences.
investigating
We are currently investigating the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are working to mitigate any recurring impact.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.
Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.
Some customers in AWS us-east-1 may experience elevated rate of transient API errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Some customers in AWS us-east-1 may experience elevated rate of transient API errors.
Customers in GCP us-east4 may experience elevated API latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We have rolled out a change and have paused further investigation overnight pending validation under daytime traffic.
identified
We are continuing to work on the investigation and remediation of the elevated API latencies in GCP us-east4.
We will provide further updates within one hour.
identified
We are currently working to remediate the elevated API latencies that were observed in GCP us-east4.
investigating
We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available.
investigating
Customers in GCP us-east4 may experience elevated API latencies.
Some customers in GCP europe-west3 may experience elevated API latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
Some customers in GCP europe-west3 may experience elevated API latencies from 05:54 to 06:05 UTC
Some customers in AWS us-east-2 may have experienced elevated API latencies and errors
Source not attested
Last archived state: resolved
View archived record details
monitoring
Some customers in AWS us-east-2 may have experienced elevated API latencies and errors between 17:57 and 18:16 UTC
