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

Some customers in AWS us-east-2 may have experienced elevated API latencies and errors

Jul <var data-var='date'> 5</var>, <var data-var='time'>18:31</var> UTC Resolved - Some customers in GCP us-west1 may have experienced elevated API latencies between 17:50 and 17:57 UTC.

Some customers in GCP us-west1 may have experienced elevated API latencies

Jul <var data-var='date'> 2</var>, <var data-var='time'>16:26</var> UTC Resolved - The rollout is complete and resolves the compression issues. All listed affected versions should no longer experience any compression-related errors. Jul <var data-var='date'> 2</var>, <var data-var='time'>13:55</var> UTC Monitoring - The fix has been rolled out across all regions, and we are actively monitoring. Jul <var data-var='date'> 1</var>, <var data-var='time'>22:12</var> UTC Update - 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. Jul <var data-var='date'> 1</var>, <var data-var='time'>18:02</var> UTC Identified - 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)

Errors on GetSystemInfo and healthcheck endpoints for latest SDK versions

Jun <var data-var='date'>17</var>, <var data-var='time'>22:04</var> UTC Resolved - The region has recovered — visibility calls are succeeding without errors. The incident is resolved. Jun <var data-var='date'>17</var>, <var data-var='time'>21:34</var> UTC Update - A fix has been implemented. The visibility is coming back and we are monitoring. Jun <var data-var='date'>17</var>, <var data-var='time'>21:18</var> UTC Investigating - We are currently investigating this issue.

GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls

Jun <var data-var='date'>16</var>, <var data-var='time'>21:08</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>16</var>, <var data-var='time'>21:07</var> UTC Update - Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved. Jun <var data-var='date'>16</var>, <var data-var='time'>21:00</var> UTC Update - Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved. Jun <var data-var='date'>16</var>, <var data-var='time'>15:56</var> UTC Update - The last few namespaces are still refreshing. We are starting to patch the code, and are monitoring the situation. Jun <var data-var='date'>11</var>, <var data-var='time'>20:25</var> UTC Update - 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. Jun <var data-var='date'> 8</var>, <var data-var='time'>19:02</var> UTC Update - Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved. Jun <var data-var='date'> 5</var>, <var data-var='time'>22:02</var> UTC Update - Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete. Jun <var data-var='date'> 4</var>, <var data-var='time'>22:35</var> UTC Update - 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. Jun <var data-var='date'> 4</var>, <var data-var='time'>17:40</var> UTC Update - 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. Jun <var data-var='date'> 4</var>, <var data-var='time'>07:08</var> UTC Monitoring - Workflows will continue to be refreshed overnight, and we are monitoring the situation. Jun <var data-var='date'> 4</var>, <var data-var='time'>06:45</var> UTC Update - Workflows will continue to be refreshed overnight, and we are monitoring the situation. Jun <var data-var='date'> 4</var>, <var data-var='time'>06:14</var> UTC Update - Refreshes are still in progress and we are monitoring the situation. Jun <var data-var='date'> 4</var>, <var data-var='time'>04:27</var> UTC Update - Rollback is complete; refresh of open workflows is underway to unblock impacted workflows. Jun <var data-var='date'> 4</var>, <var data-var='time'>01:40</var> UTC Update - The rollback is making progress across impacted cells, and we are continuing to monitor the situation. Jun <var data-var='date'> 3</var>, <var data-var='time'>23:36</var> UTC Update - Rollback is still in progress and we are continuing to monitor the situation. Jun <var data-var='date'> 3</var>, <var data-var='time'>21:35</var> UTC Identified - 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. Jun <var data-var='date'> 3</var>, <var data-var='time'>20:41</var> UTC Update - 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. Jun <var data-var='date'> 3</var>, <var data-var='time'>19:51</var> UTC Update - 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. Jun <var data-var='date'> 3</var>, <var data-var='time'>18:30</var> UTC Update - 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. Jun <var data-var='date'> 3</var>, <var data-var='time'>00:45</var> UTC Investigating - 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.

Some customers may be experiencing stuck workflows or activities

Jun <var data-var='date'>14</var>, <var data-var='time'>16:06</var> UTC Resolved - Incident Resolved. Jun <var data-var='date'>12</var>, <var data-var='time'>23:16</var> UTC Update - This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location. Jun <var data-var='date'>12</var>, <var data-var='time'>20:44</var> UTC Update - This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy. Jun <var data-var='date'>12</var>, <var data-var='time'>19:09</var> UTC Monitoring - 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.

Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.

Jun <var data-var='date'>11</var>, <var data-var='time'>20:45</var> UTC Resolved - This has been fixed, and the audit logs have been backfilled. Jun <var data-var='date'>11</var>, <var data-var='time'>19:58</var> UTC Identified - 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.

Audit logs temporarily delayed for a few hours — no data loss.

Jun <var data-var='date'>11</var>, <var data-var='time'>15:32</var> UTC Resolved - We have identified the root cause and confirmed that no customer impact occurred. Jun <var data-var='date'>11</var>, <var data-var='time'>14:34</var> UTC Investigating - We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.

Customers might observe Usage API returning missing or delayed data

Jun <var data-var='date'> 9</var>, <var data-var='time'>00:59</var> UTC Resolved - Namespaces have been failed back to their primary region. This incident has been resolved Jun <var data-var='date'> 8</var>, <var data-var='time'>23:18</var> UTC Update - The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in. Jun <var data-var='date'> 8</var>, <var data-var='time'>22:42</var> UTC Update - Multi Region Namespaces were failed over at 10:23 PM UTC Jun <var data-var='date'> 8</var>, <var data-var='time'>22:38</var> UTC Monitoring - A fix has been implemented and we are monitoring Jun <var data-var='date'> 8</var>, <var data-var='time'>22:06</var> UTC Investigating - We are currently investigating this issue.

GCP customers in us-east4 are experiencing elevated errors for Visibility API calls

Jun <var data-var='date'> 6</var>, <var data-var='time'>04:26</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 6</var>, <var data-var='time'>02:29</var> UTC Monitoring - The issue appears to have been transient network latency that has resolved. We are monitoring the situation. Jun <var data-var='date'> 6</var>, <var data-var='time'>02:15</var> UTC Investigating - Some customers in AWS sa-east-1 may experience elevated API latencies. We are currently investigating the issue.

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

May <var data-var='date'>29</var>, <var data-var='time'>22:14</var> UTC Resolved - 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. May <var data-var='date'>29</var>, <var data-var='time'>10:48</var> UTC Update - The service continues to operate normally. We will provide additional updates as they become available. May <var data-var='date'>29</var>, <var data-var='time'>02:11</var> UTC Update - The service remains stable. We are continuing to monitor closely while work progresses on a permanent fix to prevent recurrence. May <var data-var='date'>28</var>, <var data-var='time'>23:17</var> UTC Update - 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. May <var data-var='date'>28</var>, <var data-var='time'>22:14</var> UTC Update - Service has remained stable and we are continuing to monitor the situation. We will continue to provide updates as they become available. May <var data-var='date'>28</var>, <var data-var='time'>21:00</var> UTC Monitoring - 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. May <var data-var='date'>28</var>, <var data-var='time'>20:22</var> UTC Identified - 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.

Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors

May <var data-var='date'>29</var>, <var data-var='time'>15:49</var> UTC Resolved - Remediation has been completed at this time and we have confirmed the recovery of all affected namespaces. May <var data-var='date'>29</var>, <var data-var='time'>15:00</var> UTC Monitoring - Latencies and error rates are stable after remediation and we are continuing to monitoring it. May <var data-var='date'>29</var>, <var data-var='time'>14:50</var> UTC Update - Error rates remain stable, and we continue to implement remediation measures while monitoring service performance closely. May <var data-var='date'>29</var>, <var data-var='time'>14:03</var> UTC Update - We continue to investigate the root cause while implementing remediation measures. Error rates have recovered. May <var data-var='date'>29</var>, <var data-var='time'>13:43</var> UTC Update - Failover was initiated for the affected HA namespaces while we keep investigating the root cause. May <var data-var='date'>29</var>, <var data-var='time'>13:31</var> UTC Identified - Some customers in us-west-2 may experience elevated rate of API errors & higher latencies

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

May <var data-var='date'>27</var>, <var data-var='time'>15:00</var> UTC Resolved - 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.

Some customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors

May <var data-var='date'>26</var>, <var data-var='time'>23:15</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>22</var>, <var data-var='time'>01:30</var> UTC Monitoring - 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)

Customers using OpenMetric for external observability may see gaps in some metrics

May <var data-var='date'>22</var>, <var data-var='time'>23:43</var> UTC Resolved - This incident has been resolved. Analysis shows the error was from our domain management vendor. May <var data-var='date'>22</var>, <var data-var='time'>23:40</var> UTC Investigating - Namespace creation, modification and deletion had increased latencies from 23:10 to 23:35 UTC. There is no impact to workflow operations

Namespace creation and modification availablity degraded

May <var data-var='date'>15</var>, <var data-var='time'>18:30</var> UTC Resolved - 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.

Temporal UI was unable to display human readable execution details

May <var data-var='date'>13</var>, <var data-var='time'>16:43</var> UTC Resolved - 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

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

May <var data-var='date'> 9</var>, <var data-var='time'>03:56</var> UTC Resolved - 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. May <var data-var='date'> 8</var>, <var data-var='time'>17:37</var> UTC Update - 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. May <var data-var='date'> 8</var>, <var data-var='time'>12:29</var> UTC Update - We continue to monitor the situation and the service stability has been maintained. May <var data-var='date'> 8</var>, <var data-var='time'>09:27</var> UTC Monitoring - We continue to work closely with AWS and monitor the situation. There are no new developments at this time, and service remains stable. May <var data-var='date'> 8</var>, <var data-var='time'>07:43</var> UTC Update - We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability. May <var data-var='date'> 8</var>, <var data-var='time'>03:40</var> UTC Update - 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. May <var data-var='date'> 8</var>, <var data-var='time'>02:55</var> UTC Update - We are continuing to work closely with AWS as they address the underlying issue. We are also actively monitoring the health of impacted namespaces. May <var data-var='date'> 8</var>, <var data-var='time'>01:50</var> UTC Identified - 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 May <var data-var='date'> 8</var>, <var data-var='time'>01:14</var> UTC Investigating - Some customers in AWS us-east-1 may experience elevated API latencies.

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

May <var data-var='date'> 5</var>, <var data-var='time'>21:46</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>20:09</var> UTC Update - Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation. May <var data-var='date'> 5</var>, <var data-var='time'>16:47</var> UTC Update - 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. May <var data-var='date'> 5</var>, <var data-var='time'>09:24</var> UTC Update - API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation. May <var data-var='date'> 5</var>, <var data-var='time'>07:50</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 5</var>, <var data-var='time'>07:39</var> UTC Update - We continue working to mitigate the issue. May <var data-var='date'> 5</var>, <var data-var='time'>07:12</var> UTC Identified - We are working to mitigate the issue. Error rates are recovering. May <var data-var='date'> 5</var>, <var data-var='time'>06:22</var> UTC Update - This is still in investigation May <var data-var='date'> 5</var>, <var data-var='time'>05:43</var> UTC Investigating - We are currently investigating the issue.

Some customers in us-west-2 may experience elevated rate of API errors and high latency

May <var data-var='date'> 5</var>, <var data-var='time'>00:36</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 4</var>, <var data-var='time'>23:23</var> UTC Monitoring - 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. May <var data-var='date'> 4</var>, <var data-var='time'>22:50</var> UTC Investigating - We are currently investigating a small number of gRPC UNIMPLEMENTED errors being returned in the AWS us-east-1 region.

Is Temporal down?

Temporal status is UP

Lastest published events

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 transient API errors

Customers in GCP us-east4 may experience elevated API latencies

Temporal Services, Components and Regions

Recent Temporal events

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 transient API errors

Customers in GCP us-east4 may experience elevated API latencies

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

Some customers in AWS us-east-2 may have experienced elevated API latencies and errors

Some customers in GCP us-west1 may have experienced elevated API latencies

Get your FREE account now,
5 monitors included!

Is Temporal down?

Temporal status is UP

Lastest published events

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 transient API errors

Customers in GCP us-east4 may experience elevated API latencies

Temporal Services, Components and Regions

Recent Temporal events

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 transient API errors

Customers in GCP us-east4 may experience elevated API latencies

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

Some customers in AWS us-east-2 may have experienced elevated API latencies and errors

Some customers in GCP us-west1 may have experienced elevated API latencies

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!