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.
May 2026
Namespace creation and modification availablity degredaed
majorSource not attested
Last archived state: resolved
View archived record details
investigating
Namespace creation, modification and deletion were unable to be completed from 23:10 to 23:35 UTC.
There is no impact to workflow operations
Customers using OpenMetric for external observability may see gaps in some metrics
Source not attested
Last archived state: resolved
View archived record details
monitoring
Customers using OpenMetrics to scrape their Temporal Cloud metrics may see gaps in their data for metrics ending with _limit mentioned here (https://docs.temporal.io/cloud/metrics/openmetrics/metrics-reference#limit-metrics)
Some customers in us-west-2 may experience elevated rate of API errors and high latency
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.
monitoring
We are continuing to monitor the affected cell and have kept our status page in a monitoring state while we validate stability.
As a precaution, Multi-region Namespace traffic has been failed over to secondary regions, where it continues to be served normally.
While we complete stabilization work, Multi-region Namespaces will continue running from secondary regions.
Our current priority is to ensure the affected cell is stable and operating normally. Once confirmed, and the incident is res...
monitoring
API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We continue working to mitigate the issue.
identified
We are working to mitigate the issue. Error rates are recovering.
investigating
This is still in investigation
investigating
We are currently investigating the issue.
Some customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errors
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been identified as being related to a proxy node replacement rollout which has been halted. We are currently monitoring the region but do not anticipate any new errors at this point.
investigating
We are currently investigating a small number of gRPC UNIMPLEMENTED errors being returned in the AWS us-east-1 region.
April 2026
Degraded Child Workflow Execution
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue where child workflows started with the TerminateIfRunning conflict policy may fail to start. The issue began approximately 2026-04-21 19:39 UTC.A fix is in progress and we will provide updates shortly.
Some customers in us-west-2 experiencing increased visibility API latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Remediation has been applied and the visibility system is recovering. We are continuing to monitor.
investigating
We are continuing to investigate the increased visibility API latencies.
investigating
We are continuing to investigate this issue.
investigating
Workspace operations are functioning normally. Some customers experiencing increased visibility api latency.
March 2026
Small number of customers in AWS us-west-2 may experience delayed execution of schedules
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified a backlog of workflow tasks and are currently refreshing Workflows to unblock the stuck schedules.
identified
Small number of customers in AWS us-west-2 may experience delayed execution of schedules
Elevated latencies and errors in certain namespaces in AWS us-east-1 region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring results.
investigating
We are currently investigating this issue.
A small number of customers in AWS experienced API timeouts.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A small number of customers in AWS experienced API timeouts. We are monitoring the issue.
