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 | 245 of 590 (42%) |
Incidents, newest first
Minor February 2, 2026 OpenMetrics missing metrics 1h 25m ap-northeast-1, ap-northeast-2, ap-south-1, ap-south-2 and 4 more
Started Feb 02, 2026, 09:06 AM UTC· resolved Feb 02, 2026, 10:31 AM UTC
- identified Feb 02, 2026, 09:37 AM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 02, 2026, 09:47 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 02, 2026, 10:01 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Feb 02, 2026, 10:02 AM UTC
We are continuing to monitor for any further issues.
- resolved Feb 02, 2026, 10:31 AM UTC
This incident has been resolved.
Minor January 26, 2026 Small number of customers in us-west-2 may experience elevated API latencies 17h 10m us-west-2
Started Jan 26, 2026, 09:17 PM UTC· resolved Jan 27, 2026, 02:28 PM UTC
- investigating Jan 26, 2026, 09:17 PM UTC
Small number of customers in us-west-2 may experience elevated API latencies.
- investigating Jan 26, 2026, 09:44 PM UTC
We are continuing to investigate this issue.
- investigating Jan 26, 2026, 09:53 PM UTC
We are still investigating the root cause. Performance is recovering. Some customers may still see elevated API latencies.
- investigating Jan 26, 2026, 10:37 PM UTC
Investigation ongoing.
- monitoring Jan 26, 2026, 11:29 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jan 26, 2026, 11:31 PM UTC
Monitoring
- resolved Jan 27, 2026, 02:28 PM UTC
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.
Minor January 16, 2026 Search attribute queries are degraded for some customers 2h 1m Web UI
Started Jan 16, 2026, 12:52 AM UTC· resolved Jan 16, 2026, 02:54 AM UTC
- investigating Jan 16, 2026, 12:52 AM UTC
Search attribute queries are degraded for some customers
- monitoring Jan 16, 2026, 01:58 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 16, 2026, 02:54 AM UTC
This incident has been resolved.
Minor January 14, 2026 Customers may experience unavailability of namespace admin services. 29m Web UI
Started Jan 14, 2026, 12:08 PM UTC· resolved Jan 14, 2026, 12:37 PM UTC
- investigating Jan 14, 2026, 12:08 PM UTC
Customers may experience unavailability of namespace admin services, specifically Namespace Failover.
- identified Jan 14, 2026, 12:34 PM UTC
The issue has been identified and a fix is in progress.
- resolved Jan 14, 2026, 12:37 PM UTC
This incident has been resolved.
Minor December 18, 2025 High latencies for some customers in GCP us-east4 region 2h us-east4
Started Dec 18, 2025, 08:53 PM UTC· resolved Dec 18, 2025, 10:53 PM UTC
- investigating Dec 18, 2025, 08:53 PM UTC
We are currently investigating the issue
- resolved Dec 18, 2025, 10:53 PM UTC
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.
Minor December 18, 2025 Some customers in us-west-2 may experience elevated rate of errors –
Started Dec 18, 2025, 08:35 PM UTC· resolved Dec 18, 2025, 08:35 PM UTC
- resolved Dec 18, 2025, 11:42 PM UTC
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.
Minor December 16, 2025 Drop in sync match rates for Activity/Workflow Processing for some customers 1d 9h us-west1, eu-central-1
Started Dec 16, 2025, 03:29 PM UTC· resolved Dec 18, 2025, 01:05 AM UTC
- investigating Dec 16, 2025, 03:29 PM UTC
We are currently investigating this issue.
- identified Dec 16, 2025, 04:57 PM UTC
The issue has been identified and a fix is being implemented.
- identified Dec 16, 2025, 05:02 PM UTC
This is a metrics issue and no actual impact to sync match rates for customers. Still investigating possible fixes.
- identified Dec 16, 2025, 07:11 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 17, 2025, 11:04 AM UTC
We are actively working on a fix for this issue.
- identified Dec 17, 2025, 06:39 PM UTC
We are deploying a fix for this.
- monitoring Dec 17, 2025, 11:58 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 18, 2025, 01:05 AM UTC
This incident has been resolved.
Minor December 10, 2025 OpenMetrics data updates are delayed 35m Metrics
Started Dec 10, 2025, 10:29 PM UTC· resolved Dec 10, 2025, 11:04 PM UTC
- identified Dec 10, 2025, 10:29 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Dec 10, 2025, 10:38 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 10, 2025, 11:04 PM UTC
This incident has been resolved.
Notice November 18, 2025 Customers in us-west-2 may experience unavailability of service –
Started Nov 18, 2025, 06:15 AM UTC· resolved Nov 18, 2025, 06:15 AM UTC
- resolved Nov 18, 2025, 06:40 AM UTC
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.
Major November 16, 2025 Customers are not able to log in to cloud.temporal.io. 30m Web UI
Started Nov 16, 2025, 07:47 PM UTC· resolved Nov 16, 2025, 08:18 PM UTC
- investigating Nov 16, 2025, 07:47 PM UTC
Customers are not able to log in to cloud.temporal.io. We are investigating this issue.
- resolved Nov 16, 2025, 08:18 PM UTC
This incident has been resolved.
Minor November 4, 2025 Task processing delay for certain customers in AWS ap-southeast-1 region 1d 7h
Started Nov 04, 2025, 07:30 PM UTC· resolved Nov 06, 2025, 03:00 AM UTC
- identified Nov 04, 2025, 10:19 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Nov 07, 2025, 11:43 PM UTC
This incident has been resolved.
Minor October 23, 2025 Increased latencies for schedules, batches and versioning APIs in us-east-1 1h 29m us-east-1
Started Oct 23, 2025, 07:13 PM UTC· resolved Oct 23, 2025, 08:43 PM UTC
- investigating Oct 23, 2025, 07:13 PM UTC
We are currently investigating the issue.
- investigating Oct 23, 2025, 08:42 PM UTC
We scaled worker pods and pollers, which reduced the latencies back to normal.
- resolved Oct 23, 2025, 08:43 PM UTC
This incident has been resolved.
Minor October 22, 2025 Namespaces in aws us-west-2 experiencing increased latencies 24m us-west-2
Started Oct 22, 2025, 01:51 AM UTC· resolved Oct 22, 2025, 02:15 AM UTC
- investigating Oct 22, 2025, 01:51 AM UTC
We are currently investigating this issue
- resolved Oct 22, 2025, 02:49 AM UTC
Latencies appear to have recovered
Minor October 21, 2025 Intermittent failures attempting to add us-east-2 replicas to existing namespaces –
Started Oct 21, 2025, 03:00 AM UTC· resolved Oct 21, 2025, 03:00 AM UTC
- resolved Oct 21, 2025, 10:14 PM UTC
At around 2025-10-20 UTC 23:00, some customer requests to add an aws us-east-2 replica to an existing namespace failed. We successfully retried these failed requests around 2025-10-21 UTC 05:00
Major October 20, 2025 Service disruptions in AWS us-east-1 11h 18m us-east-1
Started Oct 20, 2025, 08:11 AM UTC· resolved Oct 20, 2025, 07:30 PM UTC
- investigating Oct 20, 2025, 07:42 AM UTC
Investigating increased latency in control-plane operations for some customers in AWS US-EAST-1 due to ongoing cloud operational issue. Workflow operations are not impacted.
- investigating Oct 20, 2025, 08:07 AM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status Workflow operations are currently not affected.
- identified Oct 20, 2025, 08:11 AM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status There is a loss of OpenMetrics endpoint data for namespaces in us-east-1 Workflow operations are currently not affected.
- monitoring Oct 20, 2025, 10:22 AM UTC
AWS is observing services recovering, see: https://health.aws.amazon.com/health/status Workflow operations are currently not affected.
- monitoring Oct 20, 2025, 03:36 PM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status We are currently seeing network instability in us-east-1. Some customers may see increased latency and error rates in this region.
- monitoring Oct 20, 2025, 04:35 PM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status We are currently seeing network instability in us-east-1. Some customers may see increased latency and error rates in this region.
- monitoring Oct 20, 2025, 04:50 PM UTC
Investigating service disruptions due to ongoing AWS outage in US-East-1. See: https://health.aws.amazon.com/health/status We are experiencing network instability in us-east-1. Some customers may see increased latency and error rates in this region. We are currently failing over pre-existing multi-region and multi-cloud namespaces to unaffected regions.
- monitoring Oct 20, 2025, 07:34 PM UTC
All pre-existing multi-region and multicloud namespaces to unaffected regions have been failed-over. We are seeing major improvements in networking in the region. We will continue monitoring the situation until full recovery.
- monitoring Oct 20, 2025, 08:40 PM UTC
We continue to see recovery and are actively monitoring stability in the affected region
- resolved Oct 20, 2025, 09:28 PM UTC
Update: Our systems are showing full recovery across all previously impacted namespaces. Namespaces that failed over during the incident have not yet been failed back. We are working directly with a small number of customers on follow-up recovery steps for issues indirectly related to this incident. Update [ 10/22/2025 - 21:00:00Z ] - All multi-region namespaces have been failed back to their preferred region (excluding any namespaces that were specifically requested to not fail back on)