Live  /  Temporal  /  Incident

Temporal: UI Disruptions in GCP us-central1

Temporal · temporal.ioMinor incidentResolved2026-10-01 21:47 UTC
Public — what happened

Summary

Temporal reported a minor problem on October 1, 2026, starting at 21:06 UTC, in which some users in its GCP us-central1 region had trouble with the web interface. The company said workflows themselves kept running normally and only the interface was affected for impacted namespaces in that region. By 21:21 UTC Temporal said it had found the cause and fixed the issue, though it did not describe what the cause was, and it marked the incident resolved at 21:47.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 41, 2026, our weekly internet health report.

The full archive is on the Temporal status & history page.

Related: Temporal status & history. SquidGrid is not affiliated with Temporal.