Temporal Outage History

Temporal customers in AWS us-east-1 experienced elevated API latencies for 26.8 hours due to underlying AWS infrastructure issues. Temporal proactively failed over multi-region replication enabled namespaces to maintain service stability during the incident. The issue was resolved when AWS fixed their infrastructure problems and Temporal failed customers back to the us-east-1 region.

Temporal customers in the us-west-2 region experienced elevated API error rates and high latency for 16.1 hours due to issues with the history service. Multi-region Namespace traffic was proactively failed over to secondary regions as a precautionary measure, where services continued operating normally. The incident was resolved after implementing a fix to the history service, with Multi-region Namespaces being failed back to primary regions once stability was confirmed.

Temporal customers in AWS us-east-1 experienced gRPC UNIMPLEMENTED errors for 1.8 hours due to a proxy node replacement rollout. The rollout was halted to stop new errors from occurring, and the incident was resolved after a monitoring period.

Temporal experienced an issue where child workflows using the TerminateIfRunning conflict policy failed to start, beginning at approximately 19:39 UTC on April 21, 2026. The service degradation affected workflow execution functionality for 25 minutes. The issue was resolved at 23:26 UTC with affected workflows returning to normal operation.

Temporal experienced increased visibility API latencies affecting some customers in the us-west-2 region for 2.3 hours. Workspace operations continued to function normally during the incident. The issue was resolved through remediation efforts, and the visibility system and APIs fully recovered.

A small number of Temporal customers in AWS us-west-2 experienced delayed execution of their scheduled workflows due to a backlog of workflow tasks. The engineering team identified stuck schedules, refreshed the affected workflows, cleared the backlogs, and scaled out resources to resolve the issue. The incident lasted 11.5 hours before being fully resolved.

Temporal experienced elevated latencies and errors affecting certain namespaces in the AWS us-east-1 region for 3.6 hours. The service disruption impacted workflow processing and operations for users in those specific namespaces. The issue was resolved after implementing a fix and monitoring the results.

A small number of Temporal customers experienced API timeouts across multiple AWS regions including us-east-1, us-west-2, and several others in Asia Pacific, Europe, and other regions. The incident lasted 43 minutes and has been resolved.

Temporal's cloud ops API experienced higher latency and elevated error rates, affecting some customers for 33 minutes. The issue was identified and a fix was deployed, with monitoring continuing until full resolution was confirmed.

Temporal customers using external observability experienced an elevated rate of API errors for 5.3 hours. The service team identified the issue and monitored the situation as errors subsided. The incident was fully resolved after confirmation that API error rates had returned to normal levels.