Live  /  Temporal  /  Incident

Temporal: New namespace creation restricted across few GCP regions. Impacted regions are us-central1 and europe-west3

Temporal · temporal.ioMinor incidentmonitoring2026-11-09 20:04 UTC
Public — what happened

Summary

Temporal said it has temporarily limited the creation of new Temporal Cloud namespaces in two Google Cloud regions, us-central1 and europe-west3, starting at 17:12 UTC on 2026-10-15. The company attributed the restriction to limits on available computing capacity. It said namespaces that already exist continue to work normally, and it pointed customers to documentation on alternatives and on requesting an exception. A later update on 2026-11-09 said Temporal is still monitoring, and the incident is not marked as resolved.

Affected

Capacity

As listed on Temporal’s status page.

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 43, 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.