Vendor reports: operationalResolved · vendor status “resolved”Official status API

Customers in us-east4 may have experienced elevated API latencies and resource exhausted errors

Reported by Temporal Cloud · Developer Tools & CI/CD · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Oct 1, 2026, 14:52 UTC
Vendor's clock
Resolved
Oct 1, 2026, 14:00 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Affected scope

us-east4

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Temporal Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Oct 1, 2026, 14:00 UTCVendor-reported resolutionVendor time
  2. Oct 1, 2026, 14:52 UTCVendor-reported startVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.