Temporal Outage History

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.

Temporal experienced degraded performance with higher than normal latencies in the AWS us-west-2 region for 37 minutes. The service team actively investigated the issue and observed recovery with stabilizing latencies. The incident was classified as minor and has been resolved.

Temporal experienced a 48-minute incident where some users encountered delays when updating their authorization settings, though existing authorization functionality continued to work normally. The issue was identified and a fix was successfully deployed to resolve the propagation delays.

Temporal Cloud experienced an 18.4-hour incident where some customers encountered unauthorized errors when fetching Schedule counts, which caused the "Create Schedule" button to be hidden from the UI. The team deployed an initial fix to restore the button visibility while continuing to work on the underlying unauthorized errors. The incident was fully resolved with a complete fix that restored both the UI functionality and the schedules count API.