Temporal incident

Customers in GCP us-east4 may experience elevated API latencies

Minor Resolved View vendor source →

Temporal experienced a minor incident on July 7, 2026 affecting us-east4, lasting 6d 11h. The incident has been resolved; the full update timeline is below.

Started
Jul 07, 2026, 01:00 PM UTC
Resolved
Jul 14, 2026, 12:42 AM UTC
Duration
6d 11h
Detected by Pingoru
Jul 07, 2026, 01:00 PM UTC

Affected components

us-east4

Update timeline

  1. investigating Jul 07, 2026, 05:48 PM UTC

    Customers in GCP us-east4 may experience elevated API latencies.

  2. investigating Jul 07, 2026, 06:21 PM UTC

    We are continuing to investigate the elevated API latencies in GCP us-east4 and will provide more details as they become available.

  3. identified Jul 07, 2026, 07:14 PM UTC

    We are currently working to remediate the elevated API latencies that were observed in GCP us-east4.

  4. identified Jul 07, 2026, 10:20 PM UTC

    We are continuing to work on the investigation and remediation of the elevated API latencies in GCP us-east4. We will provide further updates within one hour.

  5. monitoring Jul 07, 2026, 11:53 PM UTC

    We have paused further investigation overnight pending validation under daytime traffic.

  6. monitoring Jul 08, 2026, 12:05 AM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Jul 09, 2026, 06:56 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Jul 14, 2026, 12:42 AM UTC

    The latencies were caused by issues with a downstream service which resolved after we scaled up. We've been monitoring for errors and latencies and have not seen any further issues. This issue is now considered resolved.