Temporal incident

Elevated latency and errors in AWS us-east-1

Minor Resolved View vendor source →

Temporal experienced a minor incident on October 9, 2026 affecting us-east-1, lasting 2h 17m. The incident has been resolved; the full update timeline is below.

Started
Oct 09, 2026, 10:33 PM UTC
Resolved
Oct 10, 2026, 12:51 AM UTC
Duration
2h 17m
Detected by Pingoru
Oct 09, 2026, 10:33 PM UTC

Affected components

us-east-1

Update timeline

  1. investigating Oct 09, 2026, 10:33 PM UTC

    We are investigating elevated latency and increased ResourceExhausted errors affecting some namespaces in the AWS us-east-1 region. Workflows may progress more slowly than usual. Our team is actively working to identify the cause. We will provide another update within 30 minutes.

  2. investigating Oct 09, 2026, 10:38 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 09, 2026, 10:50 PM UTC

    We have identified the cause of elevated latency affecting a subset of namespaces in AWS us-east-1. Namespaces with Multi-Region Replication enabled are being failed over to their replica region to restore service. We will provide another update within 30 minutes.

  4. monitoring Oct 09, 2026, 11:11 PM UTC

    Latency and error rates in AWS us-east-1 have returned to normal levels and affected namespaces have recovered. We are continuing to monitor the region. We will provide another update once failback is complete.

  5. resolved Oct 10, 2026, 12:51 AM UTC

    This incident has been resolved. The AWS us-east-1 region is stable and all affected namespaces have been failed back.