Temporal had 65 outages in the last 2 years totaling 121h 3m of downtime — averaging 2.7 incidents per month.
There were 65 Temporal outages since August 16, 2025 totaling 121h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.
A small number of customers in AWS experienced API timeouts. We are monitoring the issue.
This incident has been resolved.
Some customers in GCP us-east4 experienced elevated API latencies from approximately 2026-03-18 16:00 to 2026-03-18 18:00 UTC.
From approximately 2026-03-17 00:24:00 to 2026-03-17 00:41:00 UTC, a small number of customers in AWS us-east-1 experienced elevated latencies.
Some customers using cloud ops API may experience higher latency and elevated rate of API errors
A fix has been deployed and we will continue to monitor
This incident is resolved
Customers using external observability may experience elevated rate of API errors
Errors have subsided for last 20 minutes and we will continue to monitor
This incident is resolved
Some customers in us-west-2 may have experienced elevated API latencies & error from 7:15 - 7:40 UTC on March 6th.
Some users may experience delays in updates to their authorization settings. Authorization continues to work normally, however propagation of changes is being delayed.
A fix has been deployed
Some customers may experience unauthorized errors in fetching the count of Schedules, which causes the "Create Schedule" button to be hidden. Visit https://cloud.temporal.io/namespaces/\.\/schedules/create if you need to create a Schedule via the UI
We are continuing to investigate this issue.
Error fetching Schedules count Some customers may experience unauthorized errors in fetching the count of Schedules, which also causes the "Create Schedule" button to be hidden in Cloud UI. Visit https://cloud.temporal.io/namespaces/namespace.account/schedules/create if you need to create a Schedule via the UI
We've deployed a fix that makes the 'Create Schedule' button visible again. Users will still see 'Unauthorized' errors when fetching the schedule count, and we're actively working on that as well.
The UI is working as expected now. We've deployed a fix, and the schedules count API is working as expected.
Customers in us-east4 may have experienced elevated API latencies between 13:34:00 and 13:49:00 UTC
We are currently investigating this issue.
A fix has been implemented and calls to the Cloud OPS Read-only API call success rate has recovered
Some customers in GCP us-central1 may experience elevated API latencies.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Underlying network issues have resolved and latencies have returned to normal levels
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Small number of customers in us-west-2 may experience elevated API latencies.
We are continuing to investigate this issue.
We are still investigating the root cause. Performance is recovering. Some customers may still see elevated API latencies.
Investigation ongoing.
A fix has been implemented and we are monitoring the results.
Monitoring
Retroactive update: Latencies in us-west-2 returned to normal levels after the fix was applied, and the incident was considered resolved at 23:30 UTC on Jan 26. No additional customer impact was observed.
Search attribute queries are degraded for some customers
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers may experience unavailability of namespace admin services, specifically Namespace Failover.
The issue has been identified and a fix is in progress.
This incident has been resolved.
We are currently investigating the issue
This incident is resolved; the region has recovered. This occurred due to a significant accumulation of timer tasks in the system, which required processing to clear. The backlog has since been resolved, and normal operations have resumed.
Some customers in us-west-2 may have seen resource exhausted errors on poll RPCs and increased schedule-to-start latency, task backlogs for a short period 20:35 UTC Investigating 21:05 UTC Resolved A small number of customers experienced intermittent ResourceExhausted errors when polling for tasks, along with brief increases in schedule-to-start latency and task backlogs. This occurred due to elevated load on one of our core services (the part of the system that manages task queues and delivers tasks to workers). The issue was short-lived, and system performance has since returned to normal.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This is a metrics issue and no actual impact to sync match rates for customers. Still investigating possible fixes.
We are continuing to work on a fix for this issue.
We are actively working on a fix for this issue.
We are deploying a fix for this.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers in us-west-2 may have experienced service unavailability for approximately 8 minutes between 06:10:15 UTC to 06:18:00 UTC. We’ve identified and resolved the issue caused by a spike in activity affecting one of our networking services. The source has been isolated and will not recur. As a precaution, we’re doubling capacity in the affected region and will complete a full analysis to further strengthen our protections.
Customers are not able to log in to cloud.temporal.io. We are investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating the issue.
We scaled worker pods and pollers, which reduced the latencies back to normal.
This incident has been resolved.
We are currently investigating this issue
Latencies appear to have recovered