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

GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls

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

Official source (opens in a new tab)
Vendor start
Jun 17, 2026, 21:18 UTC
Vendor's clock
Resolved
Jun 17, 2026, 22:04 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
46 min
From vendor start and resolution

Affected scope

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.

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. Jun 17, 2026, 21:18 UTCVendor-reported startVendor time
  2. Jun 17, 2026, 22:04 UTCVendor-reported resolutionVendor time

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

Temporal Cloud: GCP customers in europe-west3 are experiencing elevated errors for Visibility API calls — statuswall