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.

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

Apr <var data-var='date'>21</var>, <var data-var='time'>23:37</var> UTC Resolved - We identified and resolved an issue that caused some Child Workflows to fail to start under certain conditions. Affected Workflows have been reprocessed and are now operating normally as of 23:26 UTC. Apr <var data-var='date'>21</var>, <var data-var='time'>23:15</var> UTC Investigating - We are investigating an issue where child workflows started with the TerminateIfRunning conflict policy may fail to start. The issue began approximately 2026-04-21 19:39 UTC.A fix is in progress and we will provide updates shortly.

Degraded Child Workflow Execution

Apr <var data-var='date'>15</var>, <var data-var='time'>11:15</var> UTC Resolved - Visibility system and APIs have recovered. Apr <var data-var='date'>15</var>, <var data-var='time'>10:36</var> UTC Monitoring - Remediation has been applied and the visibility system is recovering. We are continuing to monitor. Apr <var data-var='date'>15</var>, <var data-var='time'>09:41</var> UTC Update - We are continuing to investigate the increased visibility API latencies. Apr <var data-var='date'>15</var>, <var data-var='time'>09:12</var> UTC Update - We are continuing to investigate this issue. Apr <var data-var='date'>15</var>, <var data-var='time'>08:58</var> UTC Investigating - Workspace operations are functioning normally. Some customers experiencing increased visibility api latency.

Some customers in us-west-2 experiencing increased visibility API latencies

Apr <var data-var='date'>10</var>, <var data-var='time'>14:00</var> UTC Resolved - Billing data freshness in the Billing API was delayed between 2026-04-09 08:00 UTC and 2026-04-10 14:00 UTC. During this period, recently generated billing data was not immediately reflected in API responses. This issue did not affect API availability. The delay has been resolved, and billing data is now updating within normal freshness expectations.

Billing API Data Freshness Delay

Apr <var data-var='date'> 9</var>, <var data-var='time'>00:47</var> UTC Resolved - From 2026-04-09 00:23:00 UTC to 2026-04-09 00:47:15 UTC, some customers using GCP private service connect in us-central1 may have had client connection issues or UNAVAILABLE responses

Some customers connecting over PrivateServiceConnect in uscentral1 experienced elevated errors

Apr <var data-var='date'> 9</var>, <var data-var='time'>00:41</var> UTC Resolved - Between 23:52:49 and 00:13:52 UTC on Apr 8–9, some customers saw intermittent 500 errors in parts of the Temporal Cloud Control Plane, affecting access to certain web pages and APIs. We identified the issue as shared rate limiting that caused temporary impact to other requests. The issue is resolved, and we are making targeted improvements for better isolation and resilience.

Some customers briefly experienced elevated errors for Web UI and Cloud Ops API

Apr <var data-var='date'> 1</var>, <var data-var='time'>07:27</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'> 1</var>, <var data-var='time'>07:11</var> UTC Monitoring - Impacted Schedules have been refreshed and backlogs have been cleared. Resources have been scaled out to mitigate. Apr <var data-var='date'> 1</var>, <var data-var='time'>06:38</var> UTC Update - We have identified a backlog of workflow tasks and are currently refreshing Workflows to unblock the stuck schedules. Mar <var data-var='date'>31</var>, <var data-var='time'>20:00</var> UTC Identified - Small number of customers in AWS us-west-2 may experience delayed execution of schedules

Small number of customers in AWS us-west-2 may experience delayed execution of schedules

Mar <var data-var='date'>31</var>, <var data-var='time'>01:09</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>31</var>, <var data-var='time'>00:35</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>30</var>, <var data-var='time'>22:10</var> UTC Identified - Small number of customers in GCP europe-west3 may experience delayed firing of timers.

Small number of customers in GCP europe-west3 may experience delayed firing of timers

Mar <var data-var='date'>27</var>, <var data-var='time'>22:08</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>27</var>, <var data-var='time'>19:30</var> UTC Monitoring - A fix has been implemented and we are monitoring results. Mar <var data-var='date'>27</var>, <var data-var='time'>18:37</var> UTC Investigating - We are currently investigating this issue.

Elevated latencies and errors in certain namespaces in AWS us-east-1 region

Mar <var data-var='date'>19</var>, <var data-var='time'>01:30</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>19</var>, <var data-var='time'>00:47</var> UTC Monitoring - A small number of customers in AWS experienced API timeouts. We are monitoring the issue.

A small number of customers in AWS experienced API timeouts.

Mar <var data-var='date'>18</var>, <var data-var='time'>16:00</var> UTC Resolved - Some customers in GCP us-east4 experienced elevated API latencies from approximately 2026-03-18 16:00 to 2026-03-18 18:00 UTC.

Some customers in GCP us-east4 experienced elevated API latencies.

Mar <var data-var='date'>17</var>, <var data-var='time'>01:36</var> UTC Resolved - From approximately 2026-03-17 00:24:00 to 2026-03-17 00:41:00 UTC, a small number of customers in AWS us-east-1 experienced elevated latencies.

A small number of customers in AWS us-east-1 experienced elevated latencies.

Mar <var data-var='date'>11</var>, <var data-var='time'>23:53</var> UTC Resolved - This incident is resolved Mar <var data-var='date'>11</var>, <var data-var='time'>23:27</var> UTC Monitoring - A fix has been deployed and we will continue to monitor Mar <var data-var='date'>11</var>, <var data-var='time'>23:23</var> UTC Identified - Some customers using cloud ops API may experience higher latency and elevated rate of API errors

Some customers using cloud ops API may experience higher latency and elevated rate of API errors

Mar <var data-var='date'> 9</var>, <var data-var='time'>17:23</var> UTC Resolved - This incident is resolved Mar <var data-var='date'> 9</var>, <var data-var='time'>12:29</var> UTC Monitoring - Errors have subsided for last 20 minutes and we will continue to monitor Mar <var data-var='date'> 9</var>, <var data-var='time'>12:11</var> UTC Identified - Customers using external observability may experience elevated rate of API errors

Customers using external observability may experience elevated rate of API errors

Mar <var data-var='date'> 6</var>, <var data-var='time'>07:00</var> UTC Resolved - Some customers in us-west-2 may have experienced elevated API latencies & error from 7:15 - 7:40 UTC on March 6th.

Some customers in us-west-2 may have experienced elevated API latencies & error

Mar <var data-var='date'> 2</var>, <var data-var='time'>06:39</var> UTC Resolved - A fix has been deployed Mar <var data-var='date'> 2</var>, <var data-var='time'>05:53</var> UTC Identified - Some users may experience delays in updates to their authorization settings. Authorization continues to work normally, however propagation of changes is being delayed.

Delay in modifications of Authorization settings

Feb <var data-var='date'>27</var>, <var data-var='time'>22:40</var> UTC Resolved - The UI is working as expected now. We've deployed a fix, and the schedules count API is working as expected. Feb <var data-var='date'>27</var>, <var data-var='time'>19:40</var> UTC Identified - We've deployed a fix that makes the 'Create Schedule' button visible again. Users will still see 'Unauthorized' errors when fetching the schedule count, and we're actively working on that as well. Feb <var data-var='date'>27</var>, <var data-var='time'>04:20</var> UTC Update - Error fetching Schedules count Some customers may experience unauthorized errors in fetching the count of Schedules, which also causes the "Create Schedule" button to be hidden in Cloud UI. Visit https://cloud.temporal.io/namespaces/namespace.account/schedules/create if you need to create a Schedule via the UI Feb <var data-var='date'>27</var>, <var data-var='time'>04:19</var> UTC Update - We are continuing to investigate this issue. Feb <var data-var='date'>27</var>, <var data-var='time'>04:18</var> UTC Investigating - Some customers may experience unauthorized errors in fetching the count of Schedules, which causes the "Create Schedule" button to be hidden. Visit https://cloud.temporal.io/namespaces/\<namespace\>.\<account\>/schedules/create if you need to create a Schedule via the UI

Error fetching Schedules count

Feb <var data-var='date'>26</var>, <var data-var='time'>14:44</var> UTC Resolved - Customers in us-east4 may have experienced elevated API latencies between 13:34:00 and 13:49:00 UTC

Customers in us-east4 may experience elevated API latencies

Feb <var data-var='date'>20</var>, <var data-var='time'>21:24</var> UTC Resolved - A fix has been implemented and calls to the Cloud OPS Read-only API call success rate has recovered Feb <var data-var='date'>20</var>, <var data-var='time'>21:05</var> UTC Investigating - We are currently investigating this issue.

Is Temporal down?

Temporal status is UP

Lastest published events

Namespace creation and modification availablity degraded

Temporal UI was unable to display human readable execution details

Some customers in GCP us-east4 experienced elevated API latencies

Temporal Services, Components and Regions

Recent Temporal events

Namespace creation and modification availablity degraded

Temporal UI was unable to display human readable execution details

Some customers in GCP us-east4 experienced elevated API latencies

Some customers in GCP us-east4 experienced elevated API latencies

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

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

Get your FREE account now,
5 monitors included!

Is Temporal down?

Temporal status is UP

Lastest published events

Namespace creation and modification availablity degraded

Temporal UI was unable to display human readable execution details

Some customers in GCP us-east4 experienced elevated API latencies

Temporal Services, Components and Regions

Recent Temporal events

Namespace creation and modification availablity degraded

Temporal UI was unable to display human readable execution details

Some customers in GCP us-east4 experienced elevated API latencies

Some customers in GCP us-east4 experienced elevated API latencies

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

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

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!