Temporal

This incident has been resolved.

A fix has been implemented and we are currently working on sending out correction emails to affected customers.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

OpenMetrics incomplete responses have recovered and remain stable. We continue to monitor the situation.

We are currently investigating a degradation in OpenMetrics endpoint causing incomplete responses for customers in APSE region starting 10:10 UTC.

The environment has been validated and all residual issues have been cleared. This incident is now resolved.

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.

We are continuing to monitor for any further issues.

While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.

We are continuing to monitor for any further issues.

The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.

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 05:03 UTC, all affected MRN namespaces have been failed back to us-west-2. No further issues have been observed and this incident is resolved.

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.

We are starting to see recovery as of 23:01 UTC.

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

The rollback of the affected service has completed. Namespace configuration changes will resume as expected.

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.

GCP is reporting that mitigations are in place, and that all services in this region are operational. MRN namespaces have been failed back to their primary regions.

We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev

We are currently investigating elevated error rates in GCP us-central1, and have failed over MRN namespaces in this region.

Self-Signup onboarding was inadvertently restricted after a rollout, preventing users from completing Self-Signup onboarding. The configuration change occurred on August 20 at 21:21 UTC, and the issue was noticed at approximately 12:40 UTC on August 21. The issue was mitigated at 13:01 UTC by correcting the onboarding configuration. The onboarding configuration was corrected, and Self-Signup onboarding functionality has returned to normal.

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

A fix has been implemented and we are seeing recovery. We will be continuing to monitor the results.

Downstream cloud provider (GCP) is reporting issues. We are working with them to resolve this issue.

Customers in (GCP) us-west1 may experience elevated API latencies.

We experienced a brief period of elevated error rates and latency on the Cloud Ops API, lasting approximately 5 minutes (from 11.41 UTC to 11.46 UTC). The incident has been resolved, and the Cloud Ops API is operating normally. We are investigating the cause. We apologize for the disruption.

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

We are continuing to monitor for any further issues.

The incident has been mitigated, and we are monitoring

Customers in AWS us-west-2 may experience elevated API latencies

No further errors and latencies have been observed and systems remain stable. The issue was capacity related and caused elevated database latencies. The service was scaled up and closely monitored until all latencies resolved.

Remediation remains in effect, and latency and error rates continue to improve. We are actively monitoring the system to ensure continued stability.

Remediation has improved overall latency. We continue to monitor while the remaining work completes.

The remediation work is still in progress. Next update will be posted once this completes.

The issue has been identified and remediation work is ongoing. API latencies might remain elevated while work completes.

Customers in AWS eu-west-1 might have experienced degraded API latencies starting 07:00 UTC.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating this issue.

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

This incident has been resolved.

Some customers in AWS us-west-2 may experience unjustified throttling errors.

A set of fixes have been implemented and no further latency or failures have been observed in AWS us-east-1 since 17:00 UTC.

The service has remained stable since 15:00 UTC. We continue to investigate the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are monitoring for any further occurrences.

We are currently investigating the root cause of the elevated latencies and API errors observed in AWS us-east-1 and are working to mitigate any recurring impact.

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

The issue has been identified and a fix is being implemented.

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

Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.

This incident has been resolved.

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

Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.

This incident has been resolved.

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

Some customers in AWS us-east-1 may experience elevated rate of transient API errors.

This incident has been resolved.

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

Some customers in GCP europe-west3 may experience elevated API latencies from 05:54 to 06:05 UTC

This incident has been resolved.

Some customers in AWS us-east-2 may have experienced elevated API latencies and errors between 17:57 and 18:16 UTC

Some customers in GCP us-west1 may have experienced elevated API latencies between 17:50 and 17:57 UTC.

The rollout is complete and resolves the compression issues. All listed affected versions should no longer experience any compression-related errors.

The fix has been rolled out across all regions, and we are actively monitoring.

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.

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)

The region has recovered — visibility calls are succeeding without errors. The incident is resolved.

A fix has been implemented. The visibility is coming back and we are monitoring.

We are currently investigating this issue.

This incident has been resolved.

Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.

Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.

The last few namespaces are still refreshing. We are starting to patch the code, and are monitoring the situation.

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.

Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved.

Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete.

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.

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.

Workflows will continue to be refreshed overnight, and we are monitoring the situation.

Workflows will continue to be refreshed overnight, and we are monitoring the situation.

Refreshes are still in progress and we are monitoring the situation.

Rollback is complete; refresh of open workflows is underway to unblock impacted workflows.

The rollback is making progress across impacted cells, and we are continuing to monitor the situation.

Rollback is still in progress and we are continuing to monitor the situation.

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 of the closed ones.

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.

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.

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.

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.

Incident Resolved.

This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.

This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.

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.

This has been fixed, and the audit logs have been backfilled.

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.

We have identified the root cause and confirmed that no customer impact occurred.

We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.

Namespaces have been failed back to their primary region. This incident has been resolved

The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in.

Multi Region Namespaces were failed over at 10:23 PM UTC

A fix has been implemented and we are monitoring

We are currently investigating this issue.

This incident has been resolved.

The issue appears to have been transient network latency that has resolved. We are monitoring the situation.

Some customers in AWS sa-east-1 may experience elevated API latencies. We are currently investigating the issue.

The service has remained stable since the initial behavior was observed 5/28 19:40 to 20:05 UTC. A permanent fix for the region is now in-progress.

The service continues to operate normally. We will provide additional updates as they become available.

The service remains stable. We are continuing to monitor closely while work progresses on a permanent fix to prevent recurrence.

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.

Service has remained stable and we are continuing to monitor the situation. We will continue to provide updates as they become available.

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.

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.

Remediation has been completed at this time and we have confirmed the recovery of all affected namespaces.

Latencies and error rates are stable after remediation and we are continuing to monitoring it.

Error rates remain stable, and we continue to implement remediation measures while monitoring service performance closely.

We continue to investigate the root cause while implementing remediation measures. Error rates have recovered.

Failover was initiated for the affected HA namespaces while we keep investigating the root cause.

Some customers in us-west-2 may experience elevated rate of API errors & higher latencies

Some customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors returned during the time period 15:00-15:30:00 UTC. This issue was investigated and identified as being related to a deployment in the affected region that has been rolled back - no further impact is expected.

This incident has been resolved.

Customers using OpenMetrics to scrape their Temporal Cloud metrics may see gaps in their data for metrics ending with _limit mentioned here (https://docs.temporal.io/cloud/metrics/openmetrics/metrics-reference#limit-metrics)

This incident has been resolved. Analysis shows the error was from our domain management vendor.

Namespace creation, modification and deletion had increased latencies from 23:10 to 23:35 UTC. There is no impact to workflow operations

A change to the Cloud UI caused a breaking change to the codec server endpoint. This impacted the UI for some customers 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.

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.

Some customers in GCP us-east4 experienced elevated API latencies for two minutes between 12:38 and 12:40 UTC. The issue is currently resolved with latencies back to baseline.

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 into this region.

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.

We continue to monitor the situation and the service stability has been maintained.

We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable.

We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.

We are continuing to work closely with AWS as they address the underlying issue and are actively monitoring impacted namespaces for stability. We have also confirmed multi-region replication-enabled namespaces are in their expected replication configuration.

We are continuing to work closely with AWS as they address the underlying issue. We are also actively monitoring the health of impacted namespaces.

We have proactively failed over all impacted 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

Some customers in AWS us-east-1 may experience elevated API latencies.

This incident has been resolved.

Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.

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.

API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.

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

We continue working to mitigate the issue.

We are working to mitigate the issue. Error rates are recovering.

This is still in investigation

We are currently investigating the issue.

This incident has been resolved.

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.

We are currently investigating a small number of gRPC UNIMPLEMENTED errors being returned in the AWS us-east-1 region.