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 |
|---|---|---|---|
| May 2026 | 80% | 25 | 5 |
| April 2026 | 90% | 30 | 3 |
| March 2026 | 80.6% | 31 | 6 |
| February 2026 | 100% | 5 | 0 |
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)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
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
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