CheckUpstream does not yet run an independent probe against GCP BigQuery, so no availability figure is published for it — only GCP BigQuery's own disclosure record below. 3 incidents were recorded in the past 12 months; the most recent resolved 11 days ago after 27 minutes. Status signals are polled from GCP BigQuery's official status feed, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against GCP BigQuery yet, so we publish no availability figure for it. What follows is GCP BigQuery's own disclosure record, which is a different thing.
Vendor disclosed: 3 incidents · 29 of 30 days with none posted · 4h 10m of declared impact
Fewer incidents in the last 30 days than 25% of 232 tracked services.
Share of each window with no impact declared by GCP BigQuery
7d
100.000%
30d
99.421%
90d
99.807%
180d
99.904%
1y
99.952%
Downtime like this can be refundable
If you're a paying GCP BigQuery customer, outages in these windows may count against GCP BigQuery's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your GCP BigQuery entitlement →Does GCP BigQuery actually matter to you?
A GCP BigQuery outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 20, 18:53 UTC · resolved in 26m · Resolved
Aug 20, 16:44 UTC · resolved in 15m · Resolved
Aug 20, 15:40 UTC · resolved in 3h 40m · Resolved
Live GCP BigQuery status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/gcp-bigquery)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
GCP BigQuery is currently Operational. CheckUpstream tracks GCP BigQuery in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is GCP BigQuery down" view? See the GCP BigQuery Live status page.
Jul 18, 14:42 UTC · resolved in 2h 5m · Resolved
GCP BigQuery's last resolved incident started 11 days ago and lasted 26 minutes (a partial outage).
We don't publish one. CheckUpstream runs no independent probe against GCP BigQuery yet, and the only other figure available would be derived from GCP BigQuery's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add GCP BigQuery to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll GCP BigQuery's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.