Temporal Outage History
Uptime record, past incidents, and downtime history for Temporal.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| July 2026 | 33.3% | 9 | 6 |
| June 2026 | 50% | 30 | 15 |
| May 2026 | 74.2% | 31 | 8 |
| April 2026 | 90.5% | 21 | 2 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Apr 10
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
July 2026
Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies
Started: Jul 8, 2:26 PM
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 8, 7:07 PM
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 8, 4:46 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 8, 4:19 PM
identified
The issue has been identified and a fix is being implemented.
Jul 8, 4:19 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 8, 3:36 PM
investigating
Some customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.
Jul 8, 3:25 PM
Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies
Started: Jul 8, 2:40 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 8, 3:27 AM
investigating
Customers in AWS us-east-1 may experience elevated rate of API errors and elevated latencies.
Jul 8, 3:26 AM
Some customers in AWS us-east-1 may experience elevated rate of transient API errors
Started: Jul 7, 11:25 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 8, 12:59 AM
investigating
Some customers in AWS us-east-1 may experience elevated rate of transient API errors.
Jul 8, 12:03 AM
Customers in GCP us-east4 may experience elevated API latencies
Started: Jul 7, 1:00 PM
monitoring
We are continuing to monitor for any further issues.
Jul 8, 12:05 AM
monitoring
We have rolled out a change and have paused further investigation overnight pending validation under daytime traffic.
Jul 7, 11:53 PM
identified
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 7, 10:20 PM
identified
We are currently working to remediate the elevated API latencies that were observed in GCP us-east4.
Jul 7, 7:14 PM
investigating
We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available.
Jul 7, 6:21 PM
investigating
Customers in GCP us-east4 may experience elevated API latencies.
Jul 7, 5:48 PM
Some customers in GCP europe-west3 may experience elevated API latencies
Started: Jul 7, 5:54 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 7, 6:18 AM
identified
Some customers in GCP europe-west3 may experience elevated API latencies from 05:54 to 06:05 UTC
Jul 7, 6:17 AM
Some customers in AWS us-east-2 may have experienced elevated API latencies and errors
Started: Jul 5, 6:41 PM
monitoring
Some customers in AWS us-east-2 may have experienced elevated API latencies and errors between 17:57 and 18:16 UTC
Jul 5, 6:41 PM
Errors on GetSystemInfo and healthcheck endpoints for latest SDK versions
Started: Jul 1, 6:02 PM
monitoring
The fix has been rolled out across all regions, and we are actively monitoring.
Jul 2, 1:55 PM
identified
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 1, 10:12 PM
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)
Jul 1, 6:02 PM
June 2026
GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls
Started: Jun 17, 9:18 PM
investigating
A fix has been implemented. The visibility is coming back and we are monitoring.
Jun 17, 9:34 PM
investigating
We are currently investigating this issue.
Jun 17, 9:18 PM
Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses.
Started: Jun 12, 7:09 PM
monitoring
This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.
Jun 12, 11:16 PM
monitoring
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 12, 8:44 PM
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.
Jun 12, 7:09 PM
Audit logs temporarily delayed for a few hours — no data loss.
Started: Jun 11, 7:58 PM
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.
Jun 11, 7:58 PM
Customers might observe Usage API returning missing or delayed data
Started: Jun 11, 2:34 PM
investigating
We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.
Jun 11, 2:34 PM
GCP customers in us-east4 are experiencing elevated errors for Visibility API calls
Started: Jun 8, 10:06 PM
monitoring
The region has recovered — visibility calls are succeeding without errors. We are failing namespaces back in.
Jun 8, 11:18 PM
monitoring
Multi Region Namespaces were failed over at 10:23 PM UTC
Jun 8, 10:42 PM
monitoring
A fix has been implemented and we are monitoring
Jun 8, 10:38 PM
investigating
We are currently investigating this issue.
Jun 8, 10:06 PM
Some customers in AWS sa-east-1 may experience elevated API latencies
Started: Jun 6, 2:15 AM
monitoring
The issue appears to have been transient network latency that has resolved. We are monitoring the situation.
Jun 6, 2:29 AM
investigating
Some customers in AWS sa-east-1 may experience elevated API latencies. We are currently investigating the issue.
Jun 6, 2:15 AM
Some customers may be experiencing stuck workflows or activities
Started: Jun 3, 12:45 AM
monitoring
Refresh across all executions is nearing completion with no additional impact observed. Incident is fully mitigated and resolved.
Jun 16, 9:00 PM
monitoring
The last few namespaces are still refreshing. We are starting to patch the code, and are monitoring the situation.
Jun 16, 3:56 PM
monitoring
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 11, 8:25 PM
monitoring
Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved.
Jun 8, 7:02 PM
monitoring
Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete.
Jun 5, 10:02 PM
monitoring
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 4, 10:35 PM
monitoring
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 4, 5:40 PM
monitoring
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
Jun 4, 7:08 AM
identified
Workflows will continue to be refreshed overnight, and we are monitoring the situation.
Jun 4, 6:45 AM
identified
Refreshes are still in progress and we are monitoring the situation.
Jun 4, 6:14 AM
identified
Rollback is complete; refresh of open workflows is underway to unblock impacted workflows.
Jun 4, 4:27 AM
identified
The rollback is making progress across impacted cells, and we are continuing to monitor the situation.
Jun 4, 1:40 AM
identified
Rollback is still in progress and we are continuing to monitor the situation.
Jun 3, 11:36 PM
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...
Jun 3, 9:35 PM
investigating
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 3, 8:41 PM
investigating
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 3, 7:51 PM
investigating
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 3, 6:30 PM
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.
Jun 3, 5:55 PM
May 2026
Some customers in us-west-2 may experience elevated rate of API errors & higher latencies
Started: May 29, 1:31 PM
monitoring
Latencies and error rates are stable after remediation and we are continuing to monitoring it.
May 29, 3:15 PM
identified
Error rates remain stable, and we continue to implement remediation measures while monitoring service performance closely.
May 29, 2:50 PM
identified
We continue to investigate the root cause while implementing remediation measures. Error rates have recovered.
May 29, 2:03 PM
identified
Failover was initiated for the affected HA namespaces while we keep investigating the root cause.
May 29, 1:43 PM
identified
Some customers in us-west-2 may experience elevated rate of API errors & higher latencies
May 29, 1:31 PM
Some customers in AWS us-east-1 experienced a small number of gRPC UNIMPLEMENTED errors
Started: May 28, 8:22 PM
monitoring
The service continues to operate normally. We will provide additional updates as they become available.
May 29, 10:48 AM
monitoring
The service remains stable. We are continuing to monitor closely while work progresses on a permanent fix to prevent recurrence.
May 29, 2:11 AM
monitoring
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 28, 11:17 PM
monitoring
Service has remained stable and we are continuing to monitor the situation.
We will continue to provide updates as they become available.
May 28, 10:14 PM
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 28, 9:00 PM
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.
May 28, 8:22 PM
Namespace creation and modification availablity degredaed
Started: May 22, 11:40 PM
investigating
Namespace creation, modification and deletion were unable to be completed from 23:10 to 23:35 UTC.
There is no impact to workflow operations
May 22, 11:40 PM
Customers using OpenMetric for external observability may see gaps in some metrics
Started: May 22, 1:30 AM
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)
May 26, 9:47 PM
Some customers in AWS us-east-1 may experience elevated API latencies
Started: May 8, 1:50 AM
monitoring
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 8, 5:37 PM
monitoring
We continue to monitor the situation and the service stability has been maintained.
May 8, 12:29 PM
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 8, 9:27 AM
identified
We continue to stay closely aligned with AWS and are actively monitoring the environment to ensure ongoing stability.
May 8, 7:43 AM
identified
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 8, 3:40 AM
identified
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 8, 2:55 AM
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 8, 1:50 AM
investigating
Some customers in AWS us-east-1 may experience elevated API latencies.
May 8, 1:14 AM
Some customers in us-west-2 may experience elevated rate of API errors and high latency
Started: May 5, 5:43 AM
monitoring
Some customers may have experienced additional latencies and errors during this period (17:40 - 18:01 UTC) when we applied additional mitigation.
May 5, 8:09 PM
monitoring
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 res...
May 5, 4:47 PM
monitoring
API latencies and error rates have remained stable after a fix in history service and we continue to monitor the situation.
May 5, 9:24 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 5, 7:50 AM
identified
We continue working to mitigate the issue.
May 5, 7:39 AM
identified
We are working to mitigate the issue. Error rates are recovering.
May 5, 7:12 AM
investigating
This is still in investigation
May 5, 6:22 AM
investigating
We are currently investigating the issue.
May 5, 5:43 AM
Some customers in AWS us-east-1 may be seeing a small number of gRPC UNIMPLEMENTED errors
Started: May 4, 10:50 PM
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 4, 11:23 PM
investigating
We are currently investigating a small number of gRPC UNIMPLEMENTED errors being returned in the AWS us-east-1 region.
May 4, 10:50 PM
April 2026
Degraded Child Workflow Execution
Started: Apr 21, 11:15 PM
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.
Apr 21, 11:15 PM
Some customers in us-west-2 experiencing increased visibility API latencies
Started: Apr 15, 8:58 AM
monitoring
Remediation has been applied and the visibility system is recovering. We are continuing to monitor.
Apr 15, 10:36 AM
investigating
We are continuing to investigate the increased visibility API latencies.
Apr 15, 9:41 AM
investigating
We are continuing to investigate this issue.
Apr 15, 9:12 AM
investigating
Workspace operations are functioning normally. Some customers experiencing increased visibility api latency.
Apr 15, 8:58 AM
March 2026
Small number of customers in AWS us-west-2 may experience delayed execution of schedules
Started: Mar 31, 8:00 PM
identified
We have identified a backlog of workflow tasks and are currently refreshing Workflows to unblock the stuck schedules.
Apr 1, 6:38 AM
identified
Small number of customers in AWS us-west-2 may experience delayed execution of schedules
Apr 1, 5:47 AM
Elevated latencies and errors in certain namespaces in AWS us-east-1 region
Started: Mar 27, 6:37 PM
monitoring
A fix has been implemented and we are monitoring results.
Mar 27, 7:30 PM
investigating
We are currently investigating this issue.
Mar 27, 6:50 PM
A small number of customers in AWS experienced API timeouts.
Started: Mar 19, 12:47 AM
monitoring
A small number of customers in AWS experienced API timeouts. We are monitoring the issue.
Mar 19, 12:47 AM