Temporal Outage History
Temporal degraded · 1 active incident View live status →Pingoru has recorded 97 incidents for Temporal: 93 in the last 12 months and 22 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 10 of 720 (1%) |
| May 2026 | 11 | 188 of 744 (25%) |
| June 2026 | 7 | 333 of 720 (46%) |
| July 2026 | 21 | 202 of 744 (27%) |
| August 2026 | 5 | 82 of 744 (11%) |
| September 2026 | 7 | 37 of 720 (5%) |
| October 2026 | 9 | 231 of 575 (40%) |
Incidents, newest first
Notice May 15, 2026 Temporal UI was unable to display human readable execution details –
Started May 15, 2026, 06:30 PM UTC· resolved May 15, 2026, 06:30 PM UTC
- resolved May 15, 2026, 09:00 PM UTC
A change to the Cloud UI caused a breaking change to the codec server endpoint. This impacted the UI for roughly 1.5 hours between May 15, 2026, 11:42:57 AM PDT and May 15, 2026 1:14:53 PM PDT. The change was rolled back and the UI is back to normal operating conditions.
Minor May 13, 2026 Some customers in GCP us-east4 experienced elevated API latencies –
Started May 13, 2026, 04:43 PM UTC· resolved May 13, 2026, 04:43 PM UTC
- resolved May 13, 2026, 04:44 PM UTC
Some customers in GCP us-east4 experienced elevated API latencies for two minutes between 13:03:30 and 13:05:30 UTC. The issue is currently resolved with latencies back to baseline.
Minor May 8, 2026 Some customers in AWS us-east-1 may experience elevated API latencies 1d 2h us-east-1
Started May 08, 2026, 01:50 AM UTC· resolved May 09, 2026, 03:56 AM UTC
- investigating May 08, 2026, 01:14 AM UTC
Some customers in AWS us-east-1 may experience elevated API latencies.
- identified May 08, 2026, 01:50 AM UTC
We are proactively failing all AWS us-east-1 multi‑region replication enabled primary namespaces due to ongoing AWS incident https://health.aws.amazon.com/health/status?path=open-issues
- identified May 08, 2026, 02:55 AM UTC
We are continuing to work closely with AWS as they address the underlying issue. We are also actively monitoring the health of impacted namespaces.
- identified May 08, 2026, 03:40 AM UTC
We are continuing to work closely with AWS as they address the underlying issue and are actively monitoring impacted multi-region replication-enabled namespaces for stability. We have also confirmed those namespaces are in their expected replication configuration.
- identified May 08, 2026, 07:43 AM UTC
We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.
- monitoring May 08, 2026, 09:27 AM UTC
We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable.
- monitoring May 08, 2026, 12:29 PM UTC
We continue to monitor the situation and the service stability has been maintained.
- monitoring May 08, 2026, 05:37 PM UTC
AWS continues to work to resolve the underlying infrastructure issues in us-east-1. We continue to monitor our service closely, and we have not observed any new impact.
- resolved May 09, 2026, 03:56 AM UTC
AWS has resolved the underlying infrastructure issues in us-east-1. We have marked the region as healthy and are failing our AWS us-east-1 primary multi-region replication customers back and resolving.
Major May 5, 2026 Some customers in us-west-2 may experience elevated rate of API errors and high latency 16h 2m us-west-2
Started May 05, 2026, 05:43 AM UTC· resolved May 05, 2026, 09:46 PM UTC
- investigating May 05, 2026, 05:43 AM UTC
We are currently investigating the issue.
- investigating May 05, 2026, 06:22 AM UTC
This is still in investigation
- identified May 05, 2026, 07:12 AM UTC
We are working to mitigate the issue. Error rates are recovering.
- identified May 05, 2026, 07:39 AM UTC
We continue working to mitigate the issue.
- monitoring May 05, 2026, 07:50 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 05, 2026, 09:24 AM UTC
API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.
- monitoring May 05, 2026, 04:47 PM UTC
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 resolved, we will restore Multi-region Namespace traffic to primary regions. For Multi-region Namespaces failed over by Temporal, we will manage fail back. For manually failed over namespaces, customers can initiate fail back once the incident is resolved.
- monitoring May 05, 2026, 08:09 PM UTC
Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.
- resolved May 05, 2026, 09:46 PM UTC
This incident has been resolved.
Major May 4, 2026 Some customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errors 1h 45m us-east-1
Started May 04, 2026, 10:50 PM UTC· resolved May 05, 2026, 12:36 AM UTC
- investigating May 04, 2026, 10:50 PM UTC
We are currently investigating a small number of gRPC UNIMPLEMENTED errors being returned in the AWS us-east-1 region.
- monitoring May 04, 2026, 11:23 PM UTC
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.
- resolved May 05, 2026, 12:36 AM UTC
This incident has been resolved.
Minor April 21, 2026 Degraded Child Workflow Execution 21m europe-west3
Started Apr 21, 2026, 11:15 PM UTC· resolved Apr 21, 2026, 11:37 PM UTC
- investigating Apr 21, 2026, 11:15 PM UTC
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.
- resolved Apr 21, 2026, 11:37 PM UTC
We identified and resolved an issue that caused some Child Workflows to fail to start under certain conditions. Affected Workflows have been reprocessed and are now operating normally as of 23:26 UTC.
Minor April 15, 2026 Some customers in us-west-2 experiencing increased visibility API latencies 2h 17m us-west-2
Started Apr 15, 2026, 08:58 AM UTC· resolved Apr 15, 2026, 11:15 AM UTC
- investigating Apr 15, 2026, 08:58 AM UTC
Workspace operations are functioning normally. Some customers experiencing increased visibility api latency.
- investigating Apr 15, 2026, 09:12 AM UTC
We are continuing to investigate this issue.
- investigating Apr 15, 2026, 09:41 AM UTC
We are continuing to investigate the increased visibility API latencies.
- monitoring Apr 15, 2026, 10:36 AM UTC
Remediation has been applied and the visibility system is recovering. We are continuing to monitor.
- resolved Apr 15, 2026, 11:15 AM UTC
Visibility system and APIs have recovered.
Notice April 10, 2026 Billing API Data Freshness Delay –
Started Apr 10, 2026, 02:00 PM UTC· resolved Apr 10, 2026, 02:00 PM UTC
- resolved Apr 10, 2026, 02:39 PM UTC
Billing data freshness in the Billing API was delayed between 2026-04-09 08:00 UTC and 2026-04-10 14:00 UTC. During this period, recently generated billing data was not immediately reflected in API responses. This issue did not affect API availability. The delay has been resolved, and billing data is now updating within normal freshness expectations.
Minor April 9, 2026 Some customers briefly experienced elevated errors for Web UI and Cloud Ops API –
Started Apr 09, 2026, 12:41 AM UTC· resolved Apr 09, 2026, 12:41 AM UTC
- resolved Apr 09, 2026, 12:41 AM UTC
Between 23:52:49 and 00:13:52 UTC on Apr 8–9, some customers saw intermittent 500 errors in parts of the Temporal Cloud Control Plane, affecting access to certain web pages and APIs. We identified the issue as shared rate limiting that caused temporary impact to other requests. The issue is resolved, and we are making targeted improvements for better isolation and resilience.
Minor April 9, 2026 Some customers connecting over PrivateServiceConnect in uscentral1 experienced elevated errors 17m
Started Apr 09, 2026, 12:30 AM UTC· resolved Apr 09, 2026, 12:47 AM UTC
- resolved Apr 09, 2026, 01:02 AM UTC
From 2026-04-09 00:23:00 UTC to 2026-04-09 00:47:15 UTC, some customers using GCP private service connect in us-central1 may have had client connection issues or UNAVAILABLE responses
Minor March 31, 2026 Small number of customers in AWS us-west-2 may experience delayed execution of schedules 11h 27m us-west-2
Started Mar 31, 2026, 08:00 PM UTC· resolved Apr 01, 2026, 07:27 AM UTC
- identified Apr 01, 2026, 05:47 AM UTC
Small number of customers in AWS us-west-2 may experience delayed execution of schedules
- identified Apr 01, 2026, 06:38 AM UTC
We have identified a backlog of workflow tasks and are currently refreshing Workflows to unblock the stuck schedules.
- monitoring Apr 01, 2026, 07:11 AM UTC
Impacted Schedules have been refreshed and backlogs have been cleared. Resources have been scaled out to mitigate.
- resolved Apr 01, 2026, 07:27 AM UTC
This incident has been resolved.
Minor March 30, 2026 Small number of customers in GCP europe-west3 may experience delayed firing of timers 2h 58m europe-west3
Started Mar 30, 2026, 10:10 PM UTC· resolved Mar 31, 2026, 01:09 AM UTC
- identified Mar 31, 2026, 01:07 AM UTC
Small number of customers in GCP europe-west3 may experience delayed firing of timers.
- monitoring Mar 31, 2026, 01:08 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 31, 2026, 01:09 AM UTC
This incident has been resolved.
Minor March 27, 2026 Elevated latencies and errors in certain namespaces in AWS us-east-1 region 3h 31m us-east-1
Started Mar 27, 2026, 06:37 PM UTC· resolved Mar 27, 2026, 10:08 PM UTC
- investigating Mar 27, 2026, 06:50 PM UTC
We are currently investigating this issue.
- monitoring Mar 27, 2026, 07:30 PM UTC
A fix has been implemented and we are monitoring results.
- resolved Mar 27, 2026, 10:08 PM UTC
This incident has been resolved.
Minor March 19, 2026 A small number of customers in AWS experienced API timeouts. 42m ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-2 and 10 more
Started Mar 19, 2026, 12:47 AM UTC· resolved Mar 19, 2026, 01:30 AM UTC
- monitoring Mar 19, 2026, 12:47 AM UTC
A small number of customers in AWS experienced API timeouts. We are monitoring the issue.
- resolved Mar 19, 2026, 01:30 AM UTC
This incident has been resolved.
Notice March 18, 2026 Some customers in GCP us-east4 experienced elevated API latencies. –
Started Mar 18, 2026, 04:00 PM UTC· resolved Mar 18, 2026, 04:00 PM UTC
- resolved Mar 18, 2026, 07:16 PM UTC
Some customers in GCP us-east4 experienced elevated API latencies from approximately 2026-03-18 16:00 to 2026-03-18 18:00 UTC.
Minor March 17, 2026 A small number of customers in AWS us-east-1 experienced elevated latencies. – us-east-1
Started Mar 17, 2026, 01:36 AM UTC· resolved Mar 17, 2026, 01:36 AM UTC
- resolved Mar 17, 2026, 01:36 AM 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.
Minor March 11, 2026 Some customers using cloud ops API may experience higher latency and elevated rate of API errors 30m Cloud Ops API
Started Mar 11, 2026, 11:23 PM UTC· resolved Mar 11, 2026, 11:53 PM UTC
- identified Mar 11, 2026, 11:23 PM UTC
Some customers using cloud ops API may experience higher latency and elevated rate of API errors
- monitoring Mar 11, 2026, 11:27 PM UTC
A fix has been deployed and we will continue to monitor
- resolved Mar 11, 2026, 11:53 PM UTC
This incident is resolved
Minor March 9, 2026 Customers using external observability may experience elevated rate of API errors 5h 12m Metrics
Started Mar 09, 2026, 12:11 PM UTC· resolved Mar 09, 2026, 05:23 PM UTC
- identified Mar 09, 2026, 12:11 PM UTC
Customers using external observability may experience elevated rate of API errors
- monitoring Mar 09, 2026, 12:29 PM UTC
Errors have subsided for last 20 minutes and we will continue to monitor
- resolved Mar 09, 2026, 05:23 PM UTC
This incident is resolved
Notice March 6, 2026 Some customers in us-west-2 may have experienced elevated API latencies & error –
Started Mar 06, 2026, 07:00 AM UTC· resolved Mar 06, 2026, 07:00 AM UTC
- resolved Mar 06, 2026, 07:14 PM UTC
Some customers in us-west-2 may have experienced elevated API latencies & error from 7:15 - 7:40 UTC on March 6th.
Minor March 2, 2026 Delay in modifications of Authorization settings 45m Auth(n)/Auth(z)
Started Mar 02, 2026, 05:53 AM UTC· resolved Mar 02, 2026, 06:39 AM UTC
- identified Mar 02, 2026, 05:53 AM UTC
Some users may experience delays in updates to their authorization settings. Authorization continues to work normally, however propagation of changes is being delayed.
- resolved Mar 02, 2026, 06:39 AM UTC
A fix has been deployed
Notice February 27, 2026 Error fetching Schedules count 18h 21m
Started Feb 27, 2026, 04:18 AM UTC· resolved Feb 27, 2026, 10:40 PM UTC
- investigating Feb 27, 2026, 04:18 AM UTC
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
- investigating Feb 27, 2026, 04:19 AM UTC
We are continuing to investigate this issue.
- investigating Feb 27, 2026, 04:20 AM UTC
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
- identified Feb 27, 2026, 07:40 PM UTC
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.
- resolved Feb 27, 2026, 10:40 PM UTC
The UI is working as expected now. We've deployed a fix, and the schedules count API is working as expected.
Notice February 26, 2026 Customers in us-east4 may experience elevated API latencies – us-east4
Started Feb 26, 2026, 02:44 PM UTC· resolved Feb 26, 2026, 02:44 PM UTC
- resolved Feb 26, 2026, 02:44 PM UTC
Customers in us-east4 may have experienced elevated API latencies between 13:34:00 and 13:49:00 UTC
Major February 20, 2026 Cloud OPS Read-only APIs are experiencing errors 18m Cloud Ops API
Started Feb 20, 2026, 09:05 PM UTC· resolved Feb 20, 2026, 09:24 PM UTC
- investigating Feb 20, 2026, 09:20 PM UTC
We are currently investigating this issue.
- resolved Feb 20, 2026, 09:29 PM UTC
A fix has been implemented and calls to the Cloud OPS Read-only API call success rate has recovered
Minor February 10, 2026 Some customers in GCP us-central1 may experience elevated API latencies 3h 10m us-central1
Started Feb 10, 2026, 09:51 PM UTC· resolved Feb 11, 2026, 01:01 AM UTC
- investigating Feb 10, 2026, 09:51 PM UTC
Some customers in GCP us-central1 may experience elevated API latencies.
- identified Feb 10, 2026, 10:34 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 11, 2026, 12:28 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 11, 2026, 01:01 AM UTC
This incident has been resolved.
Minor February 7, 2026 Some customers in AWS sa-east-1 are experiencing elevated latencies 49m sa-east-1
Started Feb 07, 2026, 03:05 PM UTC· resolved Feb 07, 2026, 03:54 PM UTC
- investigating Feb 07, 2026, 03:05 PM UTC
We are currently investigating this issue.
- monitoring Feb 07, 2026, 03:15 PM UTC
Underlying network issues have resolved and latencies have returned to normal levels
- resolved Feb 07, 2026, 03:54 PM UTC
This incident has been resolved.