Temporal incident

Some customers in us-west-2 may experience elevated rate of API errors & higher latencies

Resolved after 2 hours 18 minutes, affecting us-west-2, on May 29, 2026.

resolved May 29, 2026, 03:49 PM UTC

Remediation has been completed at this time and we have confirmed the recovery of all affected namespaces.

Started
May 29, 2026, 01:31 PM UTC
Resolved
May 29, 2026, 03:49 PM UTC
Duration
2h 18m
Detected by Pingoru
May 29, 2026, 01:31 PM UTC

Affected components

us-west-2

Update timeline

  1. identified May 29, 2026, 01:31 PM UTC

    Some customers in us-west-2 may experience elevated rate of API errors & higher latencies

  2. identified May 29, 2026, 01:43 PM UTC

    Failover was initiated for the affected HA namespaces while we keep investigating the root cause.

  3. identified May 29, 2026, 02:03 PM UTC

    We continue to investigate the root cause while implementing remediation measures. Error rates have recovered.

  4. identified May 29, 2026, 02:50 PM UTC

    Error rates remain stable, and we continue to implement remediation measures while monitoring service performance closely.

  5. monitoring May 29, 2026, 03:15 PM UTC

    Latencies and error rates are stable after remediation and we are continuing to monitoring it.

  6. resolved May 29, 2026, 03:49 PM UTC

    Remediation has been completed at this time and we have confirmed the recovery of all affected namespaces.

Your product runs on more than Temporal

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →