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.
August 2026
Customers in (GCP) us-west1 may experience elevated API latencies
minorSource not attested
Last archived state: resolved
View archived record details
us-west1
monitoring
A fix has been implemented and we are seeing recovery. We will be continuing to monitor the results.
identified
Downstream cloud provider (GCP) is reporting issues. We are working with them to resolve this issue.
investigating
Customers in (GCP) us-west1 may experience elevated API latencies.
Customers in AWS us-west-2 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
The incident has been mitigated, and we are monitoring
investigating
Customers in AWS us-west-2 may experience elevated API latencies
Some customers in AWS eu-west-1 may experience elevated latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Remediation remains in effect, and latency and error rates continue to improve. We are actively monitoring the system to ensure continued stability.
identified
Remediation has improved overall latency. We continue to monitor while the remaining work completes.
identified
The remediation work is still in progress. Next update will be posted once this completes.
identified
The issue has been identified and remediation work is ongoing. API latencies might remain elevated while work completes.
investigating
Customers in AWS eu-west-1 might have experienced degraded API latencies starting 07:00 UTC.
July 2026
Usage API and UI are experiencing an outage
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
Some customers in AWS us-west-2 may experience degraded visibility performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been identified and mitigations have been put in place. We are continuing to monitor.
investigating
We are currently investigating this issue.
Some customers in GCP us-east4 may experience elevated latencies
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating short periods of elevated API latency that occurred between 11:58–11:59 UTC and 12:17–12:19 UTC.
We will provide an update as soon as it becomes available.
investigating
We are currently investigating elevated API latencies in GCP us-east4
Some customers in AWS us-west-2 may experience degraded visibility performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the issue and implemented mitigation efforts. We are currently monitoring.
investigating
We are currently investigating this issue.
Some customers in GCP us-east4 may experience elevated latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
A fix has been implemented and we are continuing to monitor.
identified
We have mitigated the primary impact, and service has been restored for most affected customers. Recovery efforts continue for the remaining infrastructure, with a small number of customer namespaces still affected. Our engineering team is actively working to complete restoration and will provide another update as progress is made.
investigating
We are currently investigating this issue
Some customers in AWS eu-west-1 may experience elevated latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our engineering has implemented a fix and we are seeing normal service return to this region. We are continuing to monitor.
identified
As of 17:53 UTC our engineering team has identified the issue and is actively working to restore normal service. We will provide another update as more information becomes available.
investigating
We are continuing to investigate this issue.
investigating
Some customers in AWS eu-west-1 may experience elevated latencies starting 13:47 UTC time.
Customers in AWS eu-west-1 may experience elevated API latencies
Source not attested
Last archived state: resolved
View archived record details
monitoring
Latencies are back to normal levels, we’re monitoring.
investigating
The failover has been completed.
investigating
We are failing over MRN namespaces
investigating
Customers in AWS eu-west-1 may experience elevated API latencies.
