Temporal Incident History

This incident has been resolved. Visibility performance has been restored.

The issue has been identified and mitigations have been put in place. We are continuing to monitor.

We are currently investigating this issue.

API latencies have recovered and remained stable since the observed periods of elevated latency.

We are investigating short periods of elevated API latency that occurred between 11:58–11:59 UTC and 12:17–12:19 UTC. We will provide an update as soon as it becomes available.

We are currently investigating elevated API latencies in GCP us-east4

We have continued to see normal activity in this region with latencies holding at pre-incident levels. This incident is now resolved.

Our engineering has implemented a fix and we are seeing normal service return to this region. We are continuing to monitor.

As of 17:53 UTC our engineering team has identified the issue and is actively working to restore normal service. We will provide another update as more information becomes available.

We are continuing to investigate this issue.

Some customers in AWS eu-west-1 may experience elevated latencies starting 13:47 UTC time.

This incident has been resolved.

The affected infrastructure has recovered. Latencies and error rates have returned to normal, and workloads have resumed.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are continuing to monitor.

We have mitigated the primary impact, and service has been restored for most affected customers. Recovery efforts continue for the remaining infrastructure, with a small number of customer namespaces still affected. Our engineering team is actively working to complete restoration and will provide another update as progress is made.

We are currently investigating this issue

We're seeing recovery on our end and errors and latencies on Visibility APIs have dropped. We will continue to monitor this but the incident is mitigated and resolved.

We have identified the issue and implemented mitigation efforts. We are currently monitoring.

We are currently investigating this issue.

Some customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1), starting from 12:45 UTC to 13:25 UTC. Metrics lag have since recovered back to nominal.

A spike in workload caused resource contention in the underlying infrastructure, resulting in elevated latency for critical APIs. We scaled up the underlying resources to handle the increased load, and latencies have returned to normal. We will continue to monitor the system, but the mitigation is complete and the incident has been resolved.

Latencies are back to normal levels, we’re monitoring.

The failover has been completed.

We are failing over MRN namespaces

Customers in AWS eu-west-1 may experience elevated API latencies.

A configuration error caused a partial loss of metrics (v0 and v1) for some customers between 2026-07-16 19:00 UTC and 2026-07-17 02:12 UTC. We have updated the config and mitigated impact across impacted regions. All global metrics are now restored and the incident is resolved.

Mitigation is complete and global metrics are restored. We are currently monitoring.

Mitigation is still in progress and metrics are slowly being restored across namespaces.

We're in the process of mitigating impact and metrics are slowly being restored across some namespaces.

Global metrics service has been impacted by this incident. We're working on mitigation.

We are currently investigating, additional details to come shortly. Impact is limited to metrics only.

All MRN-enabled namespaces failed over by Temporal have been failed back. This incident has been fully mitigated and is now resolved.

We are seeing full recovery on our end, we are continuing to monitor.

Mitigation is in effect, we are seeing some recovery. Please submit a support ticket if you are seeing service degradation.

Mitigation is still in progress. We are scaling up service to help with mitigation efforts.

All MRN-enabled namespaces have been failed over as of 17:53 UTC. Mitigation continues to progress.

We are working on a fix, if your namespace are MRN enabled please fail over to your passive regions for faster recovery.

Customers with namespaces in us-east-2 may experience errors with visibility queries. We are currently investigating.

Errors and latencies have recovered, incident has been resolved.

Some customers in AWS us-east-1 may experience elevated latencies and errors on their namespaces

The latencies were caused by issues with a downstream service which resolved after we scaled up. We've been monitoring for errors and latencies and have not seen any further issues. This issue is now considered resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We have rolled out a change and have paused further investigation overnight pending validation under daytime traffic.

We are continuing to work on the investigation and remediation of the elevated API latencies in GCP us-east4. We will provide further updates within one hour.

We are currently working to remediate the elevated API latencies that were observed in GCP us-east4.

We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available.

Customers in GCP us-east4 may experience elevated API latencies.

A Java SDK release was incorrectly tagged, preventing the time-skipping test server from being published. After correcting the tag, rerunning the release workflow, and clearing the temporal.download cache, downloads were restored.

A fix has been implemented and we are monitoring the results.

We are investigating a broken link for the latest version of the Temporal skipping test server