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 resolvedMar <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 monitorMar <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 resolvedMar <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 monitorMar <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 deployedMar <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 UIFeb <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 recoveredFeb <var data-var='date'>20</var>, <var data-var='time'>21:05</var> UTC Investigating - We are currently investigating this issue.

Cloud OPS Read-only APIs are experiencing errors

Feb <var data-var='date'>11</var>, <var data-var='time'>01:01</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'>11</var>, <var data-var='time'>00:28</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Feb <var data-var='date'>10</var>, <var data-var='time'>22:34</var> UTC Identified - The issue has been identified and a fix is being implemented.Feb <var data-var='date'>10</var>, <var data-var='time'>21:51</var> UTC Investigating - Some customers in GCP us-central1 may experience elevated API latencies.

Some customers in GCP us-central1 may experience elevated API latencies

Feb <var data-var='date'> 7</var>, <var data-var='time'>15:54</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'> 7</var>, <var data-var='time'>15:15</var> UTC Monitoring - Underlying network issues have resolved and latencies have returned to normal levelsFeb <var data-var='date'> 7</var>, <var data-var='time'>15:05</var> UTC Investigating - We are currently investigating this issue.

Some customers in AWS sa-east-1 are experiencing elevated latencies

Feb <var data-var='date'> 2</var>, <var data-var='time'>10:31</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'> 2</var>, <var data-var='time'>09:58</var> UTC Update - We are continuing to monitor for any further issues.Feb <var data-var='date'> 2</var>, <var data-var='time'>09:57</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Feb <var data-var='date'> 2</var>, <var data-var='time'>09:47</var> UTC Update - We are continuing to work on a fix for this issue.Feb <var data-var='date'> 2</var>, <var data-var='time'>09:06</var> UTC Identified - The issue has been identified and a fix is being implemented.

OpenMetrics missing metrics

Jan <var data-var='date'>31</var>, <var data-var='time'>11:56</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>31</var>, <var data-var='time'>11:34</var> UTC Update - System has recovered.Jan <var data-var='date'>31</var>, <var data-var='time'>11:04</var> UTC Update - Remediation is being applied and system is recovering.Jan <var data-var='date'>31</var>, <var data-var='time'>10:33</var> UTC Update - We are continuing to investigate this issue.Jan <var data-var='date'>31</var>, <var data-var='time'>10:07</var> UTC Update - We are continuing to investigate this issue.Jan <var data-var='date'>31</var>, <var data-var='time'>09:43</var> UTC Update - We are continuing to investigate this issue.Jan <var data-var='date'>31</var>, <var data-var='time'>09:02</var> UTC Investigating - We are currently investigating this issue.

Jan <var data-var='date'>27</var>, <var data-var='time'>14:28</var> UTC Resolved - Retroactive update: Latencies in us-west-2 returned to normal levels after the fix was applied, and the incident was considered resolved at 23:30 UTC on Jan 26. No additional customer impact was observed.Jan <var data-var='date'>26</var>, <var data-var='time'>23:31</var> UTC Update - MonitoringJan <var data-var='date'>26</var>, <var data-var='time'>23:29</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Jan <var data-var='date'>26</var>, <var data-var='time'>22:37</var> UTC Update - Investigation ongoing.Jan <var data-var='date'>26</var>, <var data-var='time'>21:53</var> UTC Update - We are still investigating the root cause. Performance is recovering. Some customers may still see elevated API latencies.Jan <var data-var='date'>26</var>, <var data-var='time'>21:44</var> UTC Update - We are continuing to investigate this issue.Jan <var data-var='date'>26</var>, <var data-var='time'>21:17</var> UTC Investigating - Small number of customers in us-west-2 may experience elevated API latencies.

Small number of customers in us-west-2 may experience elevated API latencies

Jan <var data-var='date'>16</var>, <var data-var='time'>02:54</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>16</var>, <var data-var='time'>01:58</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Jan <var data-var='date'>16</var>, <var data-var='time'>00:52</var> UTC Investigating - Search attribute queries are degraded for some customers

Search attribute queries are degraded for some customers

Jan <var data-var='date'>14</var>, <var data-var='time'>12:37</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>14</var>, <var data-var='time'>12:34</var> UTC Identified - The issue has been identified and a fix is in progress.Jan <var data-var='date'>14</var>, <var data-var='time'>12:08</var> UTC Investigating - Customers may experience unavailability of namespace admin services, specifically Namespace Failover.

Customers may experience unavailability of namespace admin services.

Jan <var data-var='date'>13</var>, <var data-var='time'>12:57</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>13</var>, <var data-var='time'>11:15</var> UTC Investigating - Customers may experience unavailability of namespace admin services.

Dec <var data-var='date'>18</var>, <var data-var='time'>22:53</var> UTC Resolved - This incident is resolved; the region has recovered. This occurred due to a significant accumulation of timer tasks in the system, which required processing to clear. The backlog has since been resolved, and normal operations have resumed.Dec <var data-var='date'>18</var>, <var data-var='time'>20:53</var> UTC Investigating - We are currently investigating the issue

High latencies for some customers in GCP us-east4 region

Dec <var data-var='date'>18</var>, <var data-var='time'>20:35</var> UTC Resolved - Some customers in us-west-2 may have seen resource exhausted errors on poll RPCs and increased schedule-to-start latency, task backlogs for a short period 20:35 UTC Investigating 21:05 UTC Resolved A small number of customers experienced intermittent ResourceExhausted errors when polling for tasks, along with brief increases in schedule-to-start latency and task backlogs. This occurred due to elevated load on one of our core services (the part of the system that manages task queues and delivers tasks to workers). The issue was short-lived, and system performance has since returned to normal.

Some customers in us-west-2 may experience elevated rate of errors

Dec <var data-var='date'>18</var>, <var data-var='time'>01:05</var> UTC Resolved - This incident has been resolved.Dec <var data-var='date'>17</var>, <var data-var='time'>23:58</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Dec <var data-var='date'>17</var>, <var data-var='time'>18:39</var> UTC Update - We are deploying a fix for this.Dec <var data-var='date'>17</var>, <var data-var='time'>11:04</var> UTC Update - We are actively working on a fix for this issue.Dec <var data-var='date'>16</var>, <var data-var='time'>19:11</var> UTC Update - We are continuing to work on a fix for this issue.Dec <var data-var='date'>16</var>, <var data-var='time'>17:02</var> UTC Update - This is a metrics issue and no actual impact to sync match rates for customers. Still investigating possible fixes.Dec <var data-var='date'>16</var>, <var data-var='time'>16:57</var> UTC Identified - The issue has been identified and a fix is being implemented.Dec <var data-var='date'>16</var>, <var data-var='time'>15:29</var> UTC Investigating - We are currently investigating this issue.

Drop in sync match rates for Activity/Workflow Processing for some customers

Dec <var data-var='date'>10</var>, <var data-var='time'>23:04</var> UTC Resolved - This incident has been resolved.Dec <var data-var='date'>10</var>, <var data-var='time'>22:38</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Dec <var data-var='date'>10</var>, <var data-var='time'>22:29</var> UTC Identified - The issue has been identified and a fix is being implemented.

Is Temporal down?

Temporal status is UP

Lastest published events

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

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

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

Temporal Services, Components and Regions

Recent Temporal events

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

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

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

A small number of customers in AWS experienced API timeouts.

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

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

Get your FREE account now,
5 monitors included!

Is Temporal down?

Temporal status is UP

Lastest published events

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

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

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

Temporal Services, Components and Regions

Recent Temporal events

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

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

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

A small number of customers in AWS experienced API timeouts.

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

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

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!