Temporal Cloud

Affected: us-east4, us-central1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. resolved 2026-10-19 22:13 UTC

   Between October 6 and October 15, 2026, some clients connected to GCP-hosted namespaces may have seen intermittent TCP connection resets. SDK retries limited the impact and there is no ongoing impact.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Capacity

Names an upstream provider: Google Cloud.

1. monitoring 2026-10-15 17:12 UTC

   We have temporarily restricted new Temporal Cloud namespace creation across all GCP regions due to compute capacity constraints. Existing namespaces continue to operate normally. For details, available alternatives, and how to request an exception, see...

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. monitoring 2026-10-14 13:20 UTC

   Between 12:21:15 UTC and 12:22:00 UTC, some users may have experienced elevated latency and error rates in GCP us-west1. The issue has been identified and mitigated. We are continuing to monitor the region. MRN namespaces have been failed over and will be failed back once...

2. resolved 2026-10-14 13:36 UTC

   This incident has been resolved. The GCP us-west1 region is stable and all affected namespaces have been failed back.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-10-09 22:33 UTC

   We are investigating elevated latency and increased deadline exceeded errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.

2. investigating 2026-10-09 22:38 UTC

   We have identified the cause of elevated latency affecting a subset of namespaces in AWS us-east-1. Namespaces with Multi-Region Replication enabled are being failed over to their replica region to restore service. We will provide another update within 30 minutes.

3. investigating 2026-10-09 22:50 UTC

   Mitigation remains in progress. We are continuing to fail over affected namespaces with Multi-Region Replication enabled to their replica regions. Some customers may continue to experience elevated latency while this work is underway. We will provide another update within 30...

4. monitoring 2026-10-09 23:11 UTC

   Latency and error rates in AWS us-east-1 have returned to normal levels and affected namespaces have recovered. We are continuing to monitor the region. We will provide another update once failback is complete.

5. resolved 2026-10-10 00:51 UTC

   This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-10-09 22:25 UTC

   Between 18:41 and 18:54 UTC on October 9, 2026, cross-region traffic to and from AWS us-east-1, us-east-2, and us-west-2 may have seen increased error rates. The issue has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations..

1. investigating 2026-10-08 21:53 UTC

   We are monitoring elevated Cloud Storage latency from GCP in us-central1. As a precaution, multi-region namespaces in this region have been failed over to their replica regions. No impact to workflow execution has been observed. We will fail back once GCP confirms recovery.

2. monitoring 2026-10-09 01:04 UTC

   Cloud Storage latency in GCP us-central1 has returned to normal levels. We are continuing to monitor the region and will begin failing multi-region namespaces back to us-central1 shortly.

3. resolved 2026-10-09 02:17 UTC

   This incident is now resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 20:23 UTC

   We are investigating increased errors and timeouts affecting the Temporal Cloud control plane, Cloud Ops API, and Temporal UI. Next update in 30 minutes.

2. monitoring 2026-10-05 20:39 UTC

   A fix has been implemented and we are seeing recovery for the Temporal Cloud control plane, Cloud Ops API, and Temporal UI. We are continuing to monitor.

3. resolved 2026-10-05 20:52 UTC

   This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Web UI

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-10-01 21:06 UTC

   We are currently investigating an issue where some users in us-central1 GCP are experiencing UI service disruptions.

2. investigating 2026-10-01 21:07 UTC

   There are no current workflow disruptions, only UI components affected for impacted namespaces within the region.

3. monitoring 2026-10-01 21:21 UTC

   Identified cause and resolved regional UI issue, monitoring for any continued impact.

4. resolved 2026-10-01 21:47 UTC

   Between 20:40 and 21:12 UTC, some users in GCP us-central1 experienced disruptions to the UI. We continued monitoring through the affected period and have seen no further reports since. This incident is now resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-01 14:00 UTC

   Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors between 13:26 and 13:56 UTC

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-27 01:01 UTC

   We are investigating increased latency and errors for namespaces in AWS us-west-2. We will share another update within 30 minutes.

2. monitoring 2026-09-27 01:22 UTC

   Between 00:32 and 01:03 UTC, some namespaces in AWS us-west-2 saw increased API latency and errors. This has now recovered and we are monitoring.

3. resolved 2026-09-27 01:53 UTC

   The issue is resolved and service is operating normally.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Billing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 15:54 UTC

   We are currently investigating this issue.

2. identified 2026-09-18 16:00 UTC

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

3. monitoring 2026-09-18 17:21 UTC

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

4. resolved 2026-09-18 22:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Metrics

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 10:10 UTC

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

2. monitoring 2026-09-11 13:31 UTC

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

3. resolved 2026-09-11 14:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-central1, asia-southeast2

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-10 20:51 UTC

   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.

2. monitoring 2026-09-10 22:27 UTC

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

3. monitoring 2026-09-10 22:29 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-09-10 22:59 UTC

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

5. monitoring 2026-09-10 23:29 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2026-09-11 00:17 UTC

   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...

7. resolved 2026-09-11 07:21 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-03 21:12 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...

2. monitoring 2026-09-03 23:25 UTC

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

3. monitoring 2026-09-04 02:13 UTC

   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.

4. resolved 2026-09-04 05:28 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Namespace Management

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-02 15:26 UTC

   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.

2. resolved 2026-09-02 15:49 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-central1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 15:47 UTC

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

2. identified 2026-09-01 16:07 UTC

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

3. resolved 2026-09-01 21:43 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-21 13:30 UTC

   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...

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. investigating 2026-08-20 15:20 UTC

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

2. identified 2026-08-20 16:05 UTC

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

3. monitoring 2026-08-20 18:10 UTC

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

4. resolved 2026-08-20 19:00 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-13 12:00 UTC

   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...

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-08-13 11:47 UTC

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

2. monitoring 2026-08-13 12:09 UTC

   The incident has been mitigated, and we are monitoring

3. monitoring 2026-08-13 12:09 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-08-13 12:27 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: eu-west-1

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-08-05 13:17 UTC

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

2. identified 2026-08-05 13:24 UTC

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

3. identified 2026-08-05 16:05 UTC

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

4. identified 2026-08-05 17:29 UTC

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

5. monitoring 2026-08-06 02:52 UTC

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

6. resolved 2026-08-07 18:26 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Billing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-31 23:46 UTC

   We are currently investigating this issue.

2. investigating 2026-08-01 00:24 UTC

   We are continuing to investigate this issue.

3. identified 2026-08-01 00:26 UTC

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

4. monitoring 2026-08-01 00:30 UTC

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

5. resolved 2026-08-01 01:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-23 19:11 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-23 19:32 UTC

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

3. resolved 2026-07-23 19:59 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east4

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-07-22 12:35 UTC

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

2. investigating 2026-07-22 12:48 UTC

   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.

3. resolved 2026-07-22 13:04 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-20 18:29 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-20 18:45 UTC

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

3. resolved 2026-07-20 19:14 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east4

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-07-20 17:44 UTC

   We are currently investigating this issue

2. identified 2026-07-20 18:57 UTC

   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...

3. identified 2026-07-20 19:03 UTC

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

4. monitoring 2026-07-20 19:04 UTC

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

5. monitoring 2026-07-20 19:33 UTC

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

6. resolved 2026-07-20 19:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Metrics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-20 13:55 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: eu-west-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-20 13:47 UTC

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

2. investigating 2026-07-20 14:18 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-20 19:11 UTC

   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.

4. monitoring 2026-07-20 19:50 UTC

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

5. resolved 2026-07-20 20:50 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: eu-west-1

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-17 14:30 UTC

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

2. investigating 2026-07-17 14:38 UTC

   We are failing over MRN namespaces

3. investigating 2026-07-17 14:49 UTC

   The failover has been completed.

4. monitoring 2026-07-17 15:22 UTC

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

5. resolved 2026-07-17 15:56 UTC

   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,...

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-16 22:26 UTC

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

2. investigating 2026-07-16 22:42 UTC

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

3. identified 2026-07-16 23:21 UTC

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

4. identified 2026-07-17 00:00 UTC

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

5. monitoring 2026-07-17 00:24 UTC

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

6. resolved 2026-07-17 02:14 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-15 16:55 UTC

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

2. identified 2026-07-15 17:52 UTC

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

3. identified 2026-07-15 18:33 UTC

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

4. identified 2026-07-15 19:12 UTC

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

5. monitoring 2026-07-15 19:58 UTC

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

6. monitoring 2026-07-15 20:29 UTC

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

7. resolved 2026-07-15 21:15 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-14 18:47 UTC

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

2. resolved 2026-07-14 19:57 UTC

   Errors and latencies have recovered, incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-14 00:03 UTC

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

2. monitoring 2026-07-14 00:05 UTC

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

3. resolved 2026-07-14 00:20 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-09 16:08 UTC

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

2. resolved 2026-07-09 16:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-08 14:26 UTC

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

2. monitoring 2026-07-08 15:28 UTC

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

3. identified 2026-07-08 15:44 UTC

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

4. monitoring 2026-07-08 16:00 UTC

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

5. investigating 2026-07-08 16:46 UTC

   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.

6. monitoring 2026-07-08 19:07 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.

7. resolved 2026-07-08 21:47 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-08 02:40 UTC

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

2. monitoring 2026-07-08 02:45 UTC

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

3. resolved 2026-07-08 10:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-07 23:25 UTC

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

2. monitoring 2026-07-08 00:59 UTC

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

3. resolved 2026-07-08 10:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east4

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-07-07 13:00 UTC

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

2. investigating 2026-07-07 18:21 UTC

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

3. identified 2026-07-07 19:14 UTC

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

4. identified 2026-07-07 22:20 UTC

   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.

5. monitoring 2026-07-07 23:53 UTC

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

6. monitoring 2026-07-08 00:05 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2026-07-09 18:56 UTC

   We are continuing to monitor for any further issues.

8. resolved 2026-07-14 00:42 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: europe-west3

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2026-07-07 05:54 UTC

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

2. monitoring 2026-07-07 06:05 UTC

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

3. resolved 2026-07-07 07:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-07-05 18:41 UTC

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

2. resolved 2026-07-05 19:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-west1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. resolved 2026-07-05 18:31 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-07-01 18:02 UTC

   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...

2. identified 2026-07-01 22:12 UTC

   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.

3. monitoring 2026-07-02 13:55 UTC

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

4. resolved 2026-07-02 16:26 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-17 21:18 UTC

   We are currently investigating this issue.

2. investigating 2026-06-17 21:34 UTC

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

3. resolved 2026-06-17 22:04 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-06-12 19:09 UTC

   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...

2. monitoring 2026-06-12 20:44 UTC

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

3. monitoring 2026-06-12 23:16 UTC

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

4. resolved 2026-06-14 16:06 UTC

   Incident Resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Audit Logging

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-11 19:58 UTC

   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.

2. resolved 2026-06-11 20:45 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: Billing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-11 14:34 UTC

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

2. resolved 2026-06-11 15:32 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east4

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-08 22:06 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-08 22:38 UTC

   A fix has been implemented and we are monitoring

3. monitoring 2026-06-08 22:42 UTC

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

4. monitoring 2026-06-08 23:18 UTC

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

5. resolved 2026-06-09 00:59 UTC

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

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: sa-east-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-06 02:15 UTC

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

2. monitoring 2026-06-06 02:29 UTC

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

3. resolved 2026-06-06 04:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-03 00:45 UTC

   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.

2. investigating 2026-06-03 18:30 UTC

   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.

3. investigating 2026-06-03 19:51 UTC

   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...

4. investigating 2026-06-03 20:41 UTC

   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.

5. identified 2026-06-03 21:35 UTC

   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...

6. identified 2026-06-03 23:36 UTC

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

7. identified 2026-06-04 01:40 UTC

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

8. identified 2026-06-04 04:27 UTC

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

9. identified 2026-06-04 06:14 UTC

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

10. identified 2026-06-04 06:45 UTC

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

11. monitoring 2026-06-04 07:08 UTC

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

12. monitoring 2026-06-04 17:40 UTC

    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.

13. monitoring 2026-06-04 22:35 UTC

    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...

14. monitoring 2026-06-05 22:02 UTC

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

15. monitoring 2026-06-08 19:02 UTC

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

16. monitoring 2026-06-11 20:25 UTC

    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...

17. monitoring 2026-06-16 15:56 UTC

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

18. monitoring 2026-06-16 21:00 UTC

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

19. monitoring 2026-06-16 21:07 UTC

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

20. resolved 2026-06-16 21:08 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.

Affected: us-east-1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-28 20:22 UTC

   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.

2. monitoring 2026-05-28 21:00 UTC

   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.

3. monitoring 2026-05-28 22:14 UTC

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

4. monitoring 2026-05-28 23:17 UTC

   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.

5. monitoring 2026-05-29 02:11 UTC

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

6. monitoring 2026-05-29 10:48 UTC

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

7. resolved 2026-05-29 22:14 UTC

   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.

Excerpts are shortened. Read the full incident on Temporal Cloud's status page.