Vendor reports: partial outageResolved · vendor status “resolved”Official status API
Multiple Products: Multiple products in us-central1-b are experiencing network service degradation.
Reported by Google Cloud · Cloud & Infrastructure · source last read just now
- Vendor start
- Sep 1, 2026, 14:42 UTC
- Vendor's clock
- Resolved
- Sep 1, 2026, 18:52 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 4 h 10 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Regions: nam5, us-central1.[E5]
What is unknown
- Which components are affected: the vendor did not say.[E6]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-09-01 18:52 UTC · summary s1, evidence 5f7677a4d5b0bb05
Evidence (7)
- E1Google Cloud reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "Multiple Products: Multiple products in us-central1-b are experiencing network service degradation.". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-09-01 14:42 UTC. (vendor) source (opens in a new tab)
- E5Regions stated by the vendor: nam5, us-central1. (vendor) source (opens in a new tab)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-09-01 18:52 UTC. (vendor) source (opens in a new tab)
Affected scope
nam5, us-central1 (Iowa)
Components: not stated by the vendor
From the vendor's structured data.
Potential relevance
Google 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.
- Sep 1, 2026, 14:42 UTCVendor-reported startVendor time
- Sep 1, 2026, 18:52 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.