Oct <var data-var='date'> 5</var>, <var data-var='time'>20:52</var> UTC Resolved - This incident has been resolved. The Temporal Cloud control plane, Cloud Ops API, and Temporal UI are operating normally. Oct <var data-var='date'> 5</var>, <var data-var='time'>20:39</var> UTC Monitoring - 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. Oct <var data-var='date'> 5</var>, <var data-var='time'>20:23</var> UTC Investigating - We are investigating increased errors and timeouts affecting the Temporal Cloud control plane, Cloud Ops API, and Temporal UI. Next update in 30 minutes.

Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI

Oct <var data-var='date'> 1</var>, <var data-var='time'>21:47</var> UTC Resolved - 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. Oct <var data-var='date'> 1</var>, <var data-var='time'>21:21</var> UTC Monitoring - Identified cause and resolved regional UI issue, monitoring for any continued impact. Oct <var data-var='date'> 1</var>, <var data-var='time'>21:07</var> UTC Update - There are no current workflow disruptions, only UI components affected for impacted namespaces within the region. Oct <var data-var='date'> 1</var>, <var data-var='time'>21:06</var> UTC Investigating - We are currently investigating an issue where some users in us-central1 GCP are experiencing UI service disruptions.

UI Disruptions in GCP us-central1

Oct <var data-var='date'> 1</var>, <var data-var='time'>14:00</var> UTC Resolved - Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors between 13:26 and 13:56 UTC

Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors

Sep <var data-var='date'>27</var>, <var data-var='time'>01:53</var> UTC Resolved - The issue is resolved and service is operating normally. Sep <var data-var='date'>27</var>, <var data-var='time'>01:22</var> UTC Monitoring - 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. Sep <var data-var='date'>27</var>, <var data-var='time'>01:01</var> UTC Investigating - We are investigating increased latency and errors for namespaces in AWS us-west-2. We will share another update within 30 minutes.

Increased latency in region us-west-2

Sep <var data-var='date'>18</var>, <var data-var='time'>22:23</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>18</var>, <var data-var='time'>17:21</var> UTC Monitoring - A fix has been implemented and we are currently working on sending out correction emails to affected customers. Sep <var data-var='date'>18</var>, <var data-var='time'>16:00</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>18</var>, <var data-var='time'>15:54</var> UTC Investigating - We are currently investigating this issue.

Some customers may have incorrectly received a "credit expiry notification"

Sep <var data-var='date'>11</var>, <var data-var='time'>14:29</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>11</var>, <var data-var='time'>13:31</var> UTC Monitoring - OpenMetrics incomplete responses have recovered and remain stable. We continue to monitor the situation. Sep <var data-var='date'>11</var>, <var data-var='time'>10:10</var> UTC Investigating - We are currently investigating a degradation in OpenMetrics endpoint causing incomplete responses for customers in APSE region starting 10:10 UTC.

Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)

Sep <var data-var='date'>11</var>, <var data-var='time'>07:21</var> UTC Resolved - The environment has been validated and all residual issues have been cleared. This incident is now resolved. Sep <var data-var='date'>11</var>, <var data-var='time'>00:17</var> UTC Update - 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. Sep <var data-var='date'>10</var>, <var data-var='time'>23:29</var> UTC Update - We are continuing to monitor for any further issues. Sep <var data-var='date'>10</var>, <var data-var='time'>22:59</var> UTC Update - While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor. Sep <var data-var='date'>10</var>, <var data-var='time'>22:29</var> UTC Update - We are continuing to monitor for any further issues. Sep <var data-var='date'>10</var>, <var data-var='time'>22:27</var> UTC Monitoring - The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments. Sep <var data-var='date'>10</var>, <var data-var='time'>20:51</var> UTC Identified - 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.

Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress

Sep <var data-var='date'> 4</var>, <var data-var='time'>05:28</var> UTC Resolved - 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. Sep <var data-var='date'> 4</var>, <var data-var='time'>02:13</var> UTC Update - 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. Sep <var data-var='date'> 3</var>, <var data-var='time'>23:25</var> UTC Monitoring - We are starting to see recovery as of 23:01 UTC. Sep <var data-var='date'> 3</var>, <var data-var='time'>21:12</var> UTC Investigating - 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

Elevated Errors in us-west-2 Region

Sep <var data-var='date'> 2</var>, <var data-var='time'>15:49</var> UTC Resolved - The rollback of the affected service has completed. Namespace configuration changes will resume as expected. Sep <var data-var='date'> 2</var>, <var data-var='time'>15:26</var> UTC Identified - 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.

Low Rate of Namespace Create/Update Failures Across All Regions

Sep <var data-var='date'> 1</var>, <var data-var='time'>21:43</var> UTC Resolved - 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. Sep <var data-var='date'> 1</var>, <var data-var='time'>16:07</var> UTC Identified - We have identified this as an upstream network issue with GCP: https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev Sep <var data-var='date'> 1</var>, <var data-var='time'>15:47</var> UTC Investigating - We are currently investigating elevated error rates in GCP us-central1, and have failed over MRN namespaces in this region.

Elevated error rates in GCP us-central1

Aug <var data-var='date'>21</var>, <var data-var='time'>13:30</var> UTC Resolved - 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.

Self-Signup Onboarding Access Restriction

Aug <var data-var='date'>20</var>, <var data-var='time'>19:00</var> UTC Resolved - We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>18:10</var> UTC Monitoring - A fix has been implemented and we are seeing recovery. We will be continuing to monitor the results. Aug <var data-var='date'>20</var>, <var data-var='time'>16:05</var> UTC Identified - Downstream cloud provider (GCP) is reporting issues. We are working with them to resolve this issue. Aug <var data-var='date'>20</var>, <var data-var='time'>15:20</var> UTC Investigating - Customers in (GCP) us-west1 may experience elevated API latencies.

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

Aug <var data-var='date'>13</var>, <var data-var='time'>12:27</var> UTC Resolved - We have continued to see normal activity in this region, with latencies holding at pre-incident levels. This incident is now resolved. Aug <var data-var='date'>13</var>, <var data-var='time'>12:09</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>13</var>, <var data-var='time'>12:09</var> UTC Monitoring - The incident has been mitigated, and we are monitoring Aug <var data-var='date'>13</var>, <var data-var='time'>11:47</var> UTC Investigating - Customers in AWS us-west-2 may experience elevated API latencies

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

Aug <var data-var='date'>13</var>, <var data-var='time'>12:00</var> UTC Resolved - 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.

Cloud Ops API — Elevated Error Rates and Latencies

Aug <var data-var='date'> 7</var>, <var data-var='time'>18:26</var> UTC Resolved - 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. Aug <var data-var='date'> 6</var>, <var data-var='time'>02:52</var> UTC Monitoring - Remediation remains in effect, and latency and error rates continue to improve. We are actively monitoring the system to ensure continued stability. Aug <var data-var='date'> 5</var>, <var data-var='time'>17:29</var> UTC Update - Remediation has improved overall latency. We continue to monitor while the remaining work completes. Aug <var data-var='date'> 5</var>, <var data-var='time'>16:05</var> UTC Update - The remediation work is still in progress. Next update will be posted once this completes. Aug <var data-var='date'> 5</var>, <var data-var='time'>13:24</var> UTC Identified - The issue has been identified and remediation work is ongoing. API latencies might remain elevated while work completes. Aug <var data-var='date'> 5</var>, <var data-var='time'>13:17</var> UTC Investigating - Customers in AWS eu-west-1 might have experienced degraded API latencies starting 07:00 UTC.

Some customers in AWS eu-west-1 may experience elevated latencies

Aug <var data-var='date'> 1</var>, <var data-var='time'>01:00</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'> 1</var>, <var data-var='time'>00:30</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'> 1</var>, <var data-var='time'>00:26</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'> 1</var>, <var data-var='time'>00:24</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>31</var>, <var data-var='time'>23:46</var> UTC Investigating - We are currently investigating this issue.

Usage API and UI are experiencing an outage

Jul <var data-var='date'>23</var>, <var data-var='time'>19:59</var> UTC Resolved - This incident has been resolved. Visibility performance has been restored. Jul <var data-var='date'>23</var>, <var data-var='time'>19:32</var> UTC Monitoring - The issue has been identified and mitigations have been put in place. We are continuing to monitor. Jul <var data-var='date'>23</var>, <var data-var='time'>19:11</var> UTC Investigating - We are currently investigating this issue.

Some customers in AWS us-west-2 may experience degraded visibility performance

Jul <var data-var='date'>22</var>, <var data-var='time'>13:04</var> UTC Resolved - API latencies have recovered and remained stable since the observed periods of elevated latency. Jul <var data-var='date'>22</var>, <var data-var='time'>12:48</var> UTC Update - 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. Jul <var data-var='date'>22</var>, <var data-var='time'>12:35</var> UTC Investigating - We are currently investigating elevated API latencies in GCP us-east4

Some customers in GCP us-east4 may experience elevated latencies

Jul <var data-var='date'>21</var>, <var data-var='time'>12:30</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'>21</var>, <var data-var='time'>12:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'>20</var>, <var data-var='time'>23:53</var> UTC Scheduled - An upstream AWS service used by Audit Logs will undergo required maintenance on July 21, 2026, from 12:00 to 12:30 UTC. During this maintenance window, Audit Logs will be temporarily unavailable through both the Audit Logs page and the GetAuditLogs API. Once the maintenance is complete, Audit Logs will become available again. Any delayed audit log data will be processed and become available as normal. No audit log data will be lost.

Audit Log Maintenance

Jul <var data-var='date'>20</var>, <var data-var='time'>20:50</var> UTC Resolved - We have continued to see normal activity in this region with latencies holding at pre-incident levels. This incident is now resolved. Jul <var data-var='date'>20</var>, <var data-var='time'>19:50</var> UTC Monitoring - Our engineering has implemented a fix and we are seeing normal service return to this region. We are continuing to monitor. Jul <var data-var='date'>20</var>, <var data-var='time'>19:11</var> UTC Identified - 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. Jul <var data-var='date'>20</var>, <var data-var='time'>14:18</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>20</var>, <var data-var='time'>13:47</var> UTC Investigating - Some customers in AWS eu-west-1 may experience elevated latencies starting 13:47 UTC time.

Jul <var data-var='date'>20</var>, <var data-var='time'>19:55</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>20</var>, <var data-var='time'>19:33</var> UTC Update - The affected infrastructure has recovered. Latencies and error rates have returned to normal, and workloads have resumed. Jul <var data-var='date'>20</var>, <var data-var='time'>19:04</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>20</var>, <var data-var='time'>19:03</var> UTC Update - A fix has been implemented and we are continuing to monitor. Jul <var data-var='date'>20</var>, <var data-var='time'>18:57</var> UTC Identified - 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. Jul <var data-var='date'>20</var>, <var data-var='time'>17:44</var> UTC Investigating - We are currently investigating this issue

Jul <var data-var='date'>20</var>, <var data-var='time'>19:14</var> UTC Resolved - 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. Jul <var data-var='date'>20</var>, <var data-var='time'>18:45</var> UTC Monitoring - We have identified the issue and implemented mitigation efforts. We are currently monitoring. Jul <var data-var='date'>20</var>, <var data-var='time'>18:29</var> UTC Investigating - We are currently investigating this issue.

Jul <var data-var='date'>20</var>, <var data-var='time'>13:55</var> UTC Resolved - 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.

Some customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1) from 12:45 to 13:25 UTC

Jul <var data-var='date'>17</var>, <var data-var='time'>15:56</var> UTC Resolved - 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. Jul <var data-var='date'>17</var>, <var data-var='time'>15:22</var> UTC Monitoring - Latencies are back to normal levels, we’re monitoring. Jul <var data-var='date'>17</var>, <var data-var='time'>14:49</var> UTC Update - The failover has been completed. Jul <var data-var='date'>17</var>, <var data-var='time'>14:38</var> UTC Update - We are failing over MRN namespaces Jul <var data-var='date'>17</var>, <var data-var='time'>14:30</var> UTC Investigating - Customers in AWS eu-west-1 may experience elevated API latencies.

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

Jul <var data-var='date'>17</var>, <var data-var='time'>02:14</var> UTC Resolved - 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. Jul <var data-var='date'>17</var>, <var data-var='time'>00:24</var> UTC Monitoring - Mitigation is complete and global metrics are restored. We are currently monitoring. Jul <var data-var='date'>17</var>, <var data-var='time'>00:00</var> UTC Update - Mitigation is still in progress and metrics are slowly being restored across namespaces. Jul <var data-var='date'>16</var>, <var data-var='time'>23:21</var> UTC Identified - We're in the process of mitigating impact and metrics are slowly being restored across some namespaces. Jul <var data-var='date'>16</var>, <var data-var='time'>22:42</var> UTC Update - Global metrics service has been impacted by this incident. We're working on mitigation. Jul <var data-var='date'>16</var>, <var data-var='time'>22:26</var> UTC Investigating - We are currently investigating, additional details to come shortly. Impact is limited to metrics only.

Is Temporal down?

Temporal status is UP

Lastest published events

Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI

UI Disruptions in GCP us-central1

Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors

Temporal Services, Components and Regions

Recent Temporal events

Increased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UI

UI Disruptions in GCP us-central1

Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors

Increased latency in region us-west-2

Some customers may have incorrectly received a "credit expiry notification"

Some customers in APSE region may experience incomplete responses from Temporal Cloud metrics (OpenMetrics)