Live / Temporal / Incident
Temporal: Intermittent request failures for some namespaces in GCP us-east4
Temporal · temporal.ioMinor incidentResolved2026-10-31 14:16 UTC
Public — what happened
Summary
Temporal said that starting at 13:31 UTC on 2026-10-31, some customers in its GCP us-east4 region saw intermittent request failures affecting a subset of namespaces. The company said affected users could see slower responses and more errors on API calls, including worker polling, which could reduce how many tasks were processed. Temporal reported at 13:48 UTC that a fix had been put in place and it was monitoring, and it marked the incident resolved at 14:16 UTC. No cause was given in the text provided.
Affected
us-east4
Timeline
- Started — 2026-10-31 13:31 UTC
- Investigating — 2026-10-31 13:31 UTC
- Monitoring — 2026-10-31 13:48 UTC (2 updates)
- Resolved — 2026-10-31 14:16 UTC · 45 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Temporal against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Temporal: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Temporal report →
More from Temporal
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.