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
Errors on GetSystemInfo and healthcheck endpoints for latest SDK versions
Source not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been rolled out across all regions, and we are actively monitoring.
identified
Fix is being rolled out across all regions, current impact is limited to us-west-2 and us-east-1 regions. All systems stable and we're actively monitoring this. Next update will be posted once rollouts completed.
identified
Customers on the latest SDK versions may see decompression errors when calling the GetSystemInfo and gRPC health check endpoints, and in rare cases, some workflows may hit a non-determinism error (NDE) during replay. A fix for this is rolling out.
Affected versions -
Java 1.36.0
Go 1.45.0
TypeScript 1.19.0
Rust 0.5.0
Python 1.29.0
Workaround - Disable gzip compression in the SDK client (set gRPC compression to none)
June 2026
GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls
Source not attested
Last archived state: resolved
View archived record details
investigating
A fix has been implemented. The visibility is coming back and we are monitoring.
investigating
We are currently investigating this issue.
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.
Source not attested
Last archived state: resolved
View archived record details
monitoring
This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.
monitoring
This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.
monitoring
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved.
We failed namespaces with MRN out of the cell.
We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.
Audit logs temporarily delayed for a few hours — no data loss.
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified that audit logs have been temporarily delayed since approximately 2026-06-11 18:00:00 UTC. We are implementing a fix, and we expect no data loss and a completed backfill within hours.
Customers might observe Usage API returning missing or delayed data
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.
GCP customers in us-east4 are experiencing elevated errors for Visibility API calls
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in.
monitoring
Multi Region Namespaces were failed over at 10:23 PM UTC
monitoring
A fix has been implemented and we are monitoring
investigating
We are currently investigating this issue.
Some customers in AWS sa-east-1 may experience elevated API latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue appears to have been transient network latency that has resolved. We are monitoring the situation.
investigating
Some customers in AWS sa-east-1 may experience elevated API latencies. We are currently investigating the issue.
Some customers may be experiencing stuck workflows or activities
Source not attested
Last archived state: resolved
View archived record details
monitoring
Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
monitoring
The last few namespaces are still refreshing. We are starting to patch the code, and are monitoring the situation.
monitoring
Refresh operations across both open and closed workflows are complete in most regions; we continue to make steady progress across the remaining few namespaces in the us-east-1, us-west-2, us-east4, us-west1, us-central1, asia-south1, europe-west3. No additional impact has been observed since mitigation was implemented, and we continue to closely monitor the environment. The next update will be provided once the refresh process has completed.
monitoring
Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved.
monitoring
Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete.
monitoring
As refresh of closed workflows progresses, some users may see unblocked stuck parent workflows from closed child workflows; this is happening because the missed task for closed child workflows is refreshed and delivered to parent. It could also happen on other stuck workflows that are waiting for task updates which were missed due to this incident.
monitoring
We are continuing to monitor the ongoing refresh process for all open workflows. We are also considering options for refreshing closed workflows. We will continue to share more updates as this progresses.
monitoring
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
identified
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
identified
Refreshes are still in progress and we are monitoring the situation.
identified
Rollback is complete; refresh of open workflows is underway to unblock impacted workflows.
identified
The rollback is making progress across impacted cells, and we are continuing to monitor the situation.
identified
Rollback is still in progress and we are continuing to monitor the situation.
identified
A bug in the recent update in History pagination caused a rare edge case where an extra task could be added before the response was returned. This incorrectly advanced the read level, causing some tasks to be skipped. We’ve identified the issue, and are currently rolling back the update to stop this from happening again.
We will be refreshing all executions in cells where the update was deployed and will monitor these closely. This will progress any stuck workflows, but will not impact any...
investigating
We're rolling back the recent update as a possible mitigation to avoid any further occurrences of this issue. We are however still in the process of investigating root cause and will post updates as we have them.
investigating
We are investigating a recent update that could have caused intermittent missed task dispatches, resulting in some tasks being stuck. Impact identified as of now is limited to a handful of workflows that were caught in a rare edge case. We will continue to share more updates as investigation progresses.
investigating
We are continuing to investigate this issue. Please report any stuck workflows or activities to support so we can help unblock them as we work on root cause investigation and resolution.
investigating
We are investigating a few reports where a workflow or activity is becoming stuck and not making progress when it should. Please report any such issues you see to support.
May 2026
Some customers in us-west-2 may experience elevated rate of API errors & higher latencies
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Latencies and error rates are stable after remediation and we are continuing to monitoring it.
identified
Error rates remain stable, and we continue to implement remediation measures while monitoring service performance closely.
identified
We continue to investigate the root cause while implementing remediation measures. Error rates have recovered.
identified
Failover was initiated for the affected HA namespaces while we keep investigating the root cause.
identified
Some customers in us-west-2 may experience elevated rate of API errors & higher latencies
Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors
Source not attested
Last archived state: resolved
View archived record details
monitoring
The service continues to operate normally. We will provide additional updates as they become available.
monitoring
The service remains stable. We are continuing to monitor closely while work progresses on a permanent fix to prevent recurrence.
monitoring
We have confirmed the service is now stable and are now working to ensure a permanent fix is in place to prevent any recurrence.
We will continue to monitor for errors until the fix is deployed.
monitoring
Service has remained stable and we are continuing to monitor the situation.
We will continue to provide updates as they become available.
monitoring
The gRPC UNIMPLEMENTED errors previously observed have been mitigated.
We are continuing to monitor the situation and are working towards a permanent fix at this time.
identified
Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors today from 19:40 to 20:05 UTC.
We have identified a root cause and are currently working towards a permanent fix.
