Google Cloud Compute Engine & BigQuery & Cloud Run degraded Sep 01, 2026: SLA credit impact
Check your eligibility — use the checklist yourself or optionally request a free review from AllCaps Technologies.
What happened
Multiple products in us-central1-b are experiencing network service degradation. — resolved.
Started Sep 01, 2026 14:44 UTC. Duration: 4h 8m.
Affected: Compute Engine, BigQuery, Cloud Run (us-central1).
This month's ledger effect
The numbers below are month-to-date for the services this incident touched. A tier can already be open from other outages earlier in the month; this incident's own contribution is listed in the last column.
| Service | Region | Uptime | Month downtime | This incident | Status this month |
|---|---|---|---|---|---|
| Compute Engine | us-central1 | — | — | status incident only; not counted as SLA downtime | eligibility not established — customer contract and telemetry required |
| BigQuery | all regions | — | — | status incident only; not counted as SLA downtime | eligibility not established — customer contract and telemetry required |
| Cloud Run | us-central1 | — | — | status incident only; not counted as SLA downtime | eligibility not established — customer contract and telemetry required |
Eligibility is not established by the public status incident. Use the self-service checklist to compare your plan, configuration and telemetry, or optionally request a free review from AllCaps Technologies on the eligibility page. Public incident duration is not counted as contractual customer downtime.
Google Cloud eligibility is calculated per project, covered service, region or edition and often requires customer log files.
Preserve possible eligibility: open a Cloudflare support case promptly. Some standard terms require notice within five business days, but the exact notice and claim deadlines depend on the affected product and the customer's negotiated contract. No deadline is calculated here until those are validated.
Share
Google Cloud Compute Engine, BigQuery, Cloud Run: Multiple products in us-central1-b are experiencing network service degradation. Duration: 4h 8m. Compute Engine (us-central1): SLA eligibility requires customer contract and telemetry validation BigQuery: SLA eligibility requires customer contract and telemetry validation Cloud Run (us-central1): SLA eligibility requires customer contract and telemetry validation https://slacreditwatch.com/i/gcp/J5ia5t9p3g9Q5Wi7r8Ev
Google Cloud Compute Engine, BigQuery, Cloud Run: Multiple products in us-central1-b are experiencing network service degradation. Duration: 4h 8m. Compute Engine (us-central1): SLA eligibility requires customer contract and telemetry validation; BigQuery: SLA eligibility requires customer contract and telemetry validation; Cloud Run (us-central1): SLA eligibility requires customer contract and telemetry validation. https://slacreditwatch.com/i/gcp/J5ia5t9p3g9Q5Wi7r8Ev
Calculator
No credit estimate is produced from this public incident. Use the applicable product fees, qualifying customer-observed outage period, affected-customer ratio, and the SLA in the customer's contract.
Get outage alerts
When a selected vendor reports a relevant outage, we tell you what evidence to preserve and help you check eligibility. Use the checklist yourself, or optionally request a free review from AllCaps Technologies on the incident's eligibility page. Confirmed contractual alerts include the credit math and filing deadline.
Choose vendors, add your email, and confirm once. No spend or contract details required.