Vendor reports: degradedOpen · vendor status “monitoring”Official status API

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

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

Official source (opens in a new tab)
Vendor start
Oct 15, 2026, 17:12 UTC
Vendor's clock
Resolved
Not yet
Still open
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Affected scope

us-central1, europe-west3

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.

What to check on your side

Verification steps only. Statuswall cannot see your systems.

  • Check CI pipelines, builds, git operations and package installs that rely on Temporal Cloud.
  • Hold deploys that depend on it until the vendor reports recovery, if your process allows.
  • Check error rates, latency and timeouts in your own monitoring for requests that depend on Temporal Cloud.
  • Look at synthetic checks and alerts that exercise Temporal Cloud.
  • Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
  • Follow the vendor's official incident page for scope changes and resolution.

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 15, 2026, 17:12 UTCVendor-reported startVendor time

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