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.

Some customers may experience a loss in metrics (v0 and v1) starting 19:00 UTC

Jul <var data-var='date'>15</var>, <var data-var='time'>21:15</var> UTC Resolved - All MRN-enabled namespaces failed over by Temporal have been failed back. This incident has been fully mitigated and is now resolved. Jul <var data-var='date'>15</var>, <var data-var='time'>20:29</var> UTC Update - We are seeing full recovery on our end, we are continuing to monitor. Jul <var data-var='date'>15</var>, <var data-var='time'>19:58</var> UTC Monitoring - Mitigation is in effect, we are seeing some recovery. Please submit a support ticket if you are seeing service degradation. Jul <var data-var='date'>15</var>, <var data-var='time'>19:12</var> UTC Update - Mitigation is still in progress. We are scaling up service to help with mitigation efforts. Jul <var data-var='date'>15</var>, <var data-var='time'>18:33</var> UTC Update - All MRN-enabled namespaces have been failed over as of 17:53 UTC. Mitigation continues to progress. Jul <var data-var='date'>15</var>, <var data-var='time'>17:52</var> UTC Identified - We are working on a fix, if your namespace are MRN enabled please fail over to your passive regions for faster recovery. Jul <var data-var='date'>15</var>, <var data-var='time'>16:55</var> UTC Investigating - Customers with namespaces in us-east-2 may experience errors with visibility queries. We are currently investigating.

Customers in us-east-2 may experience some visibility related errors

Jul <var data-var='date'>14</var>, <var data-var='time'>19:57</var> UTC Resolved - Errors and latencies have recovered, incident has been resolved. Jul <var data-var='date'>14</var>, <var data-var='time'>18:47</var> UTC Investigating - Some customers in AWS us-east-1 may experience elevated latencies and errors on their namespaces

Elevated latencies in us-east-1

Jul <var data-var='date'>14</var>, <var data-var='time'>00:42</var> UTC Resolved - 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. Jul <var data-var='date'> 9</var>, <var data-var='time'>18:56</var> UTC Update - We are continuing to monitor for any further issues. Jul <var data-var='date'> 8</var>, <var data-var='time'>00:05</var> UTC Update - We are continuing to monitor for any further issues. Jul <var data-var='date'> 7</var>, <var data-var='time'>23:53</var> UTC Monitoring - We have rolled out a change and have paused further investigation overnight pending validation under daytime traffic. Jul <var data-var='date'> 7</var>, <var data-var='time'>22:20</var> UTC Update - 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. Jul <var data-var='date'> 7</var>, <var data-var='time'>19:14</var> UTC Identified - We are currently working to remediate the elevated API latencies that were observed in GCP us-east4. Jul <var data-var='date'> 7</var>, <var data-var='time'>18:21</var> UTC Update - We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available. Jul <var data-var='date'> 7</var>, <var data-var='time'>13:00</var> UTC Investigating - Customers in GCP us-east4 may experience elevated API latencies.

Customers in GCP us-east4 may experience elevated API latencies

Jul <var data-var='date'>14</var>, <var data-var='time'>00:20</var> UTC Resolved - 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. Jul <var data-var='date'>14</var>, <var data-var='time'>00:05</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>14</var>, <var data-var='time'>00:03</var> UTC Investigating - We are investigating a broken link for the latest version of the Temporal skipping test server

Broken Temporal skipping test server link

Jul <var data-var='date'> 9</var>, <var data-var='time'>16:25</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 9</var>, <var data-var='time'>16:08</var> UTC Investigating - Some customers in AWS us-west-2 may experience unjustified throttling errors.

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

Jul <var data-var='date'> 8</var>, <var data-var='time'>21:47</var> UTC Resolved - 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. Jul <var data-var='date'> 8</var>, <var data-var='time'>19:07</var> UTC Monitoring - 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. Jul <var data-var='date'> 8</var>, <var data-var='time'>16:46</var> UTC Investigating - 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. Jul <var data-var='date'> 8</var>, <var data-var='time'>16:00</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 8</var>, <var data-var='time'>15:44</var> UTC Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'> 8</var>, <var data-var='time'>15:28</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 8</var>, <var data-var='time'>14:26</var> UTC Investigating - Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.

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

Jul <var data-var='date'> 8</var>, <var data-var='time'>10:14</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 8</var>, <var data-var='time'>02:45</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 8</var>, <var data-var='time'>02:40</var> UTC Investigating - Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.

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

Jul <var data-var='date'> 8</var>, <var data-var='time'>10:04</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 8</var>, <var data-var='time'>00:59</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 7</var>, <var data-var='time'>23:25</var> UTC Investigating - Some customers in AWS us-east-1 may experience elevated rate of transient API errors.

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

Jul <var data-var='date'> 7</var>, <var data-var='time'>07:29</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 7</var>, <var data-var='time'>06:05</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 7</var>, <var data-var='time'>05:54</var> UTC Identified - Some customers in GCP europe-west3 may experience elevated API latencies from 05:54 to 06:05 UTC

Some customers in GCP europe-west3 may experience elevated API latencies

Jul <var data-var='date'> 5</var>, <var data-var='time'>19:38</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 5</var>, <var data-var='time'>18:41</var> UTC Monitoring - Some customers in AWS us-east-2 may have experienced elevated API latencies and errors between 17:57 and 18:16 UTC

Is Temporal down?

Temporal status is UP

Lastest published events

Self-Signup Onboarding Access Restriction

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

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

Temporal Services, Components and Regions

Recent Temporal events

Self-Signup Onboarding Access Restriction

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

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

Cloud Ops API — Elevated Error Rates and Latencies

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

Usage API and UI are experiencing an outage