CheckUpstream measured Grafana Cloud at 100.000% availability across 2820 independent checks (global · api). 97 incidents were recorded in the past 12 months; the most recent resolved 4 days ago after 16 hours. Status signals are polled from Grafana Cloud's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2820 · p95 321ms (30d)
Share of our own checks against Grafana Cloud endpoints that returned Grafana Cloud's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 8 incidents · 30 of 30 days with none posted · 5m of declared impact
Fewer incidents in the last 30 days than 12% of 232 tracked services.
Share of each window with no impact declared by Grafana Cloud
7d
99.946%
30d
99.987%
90d
99.996%
180d
80.673%
1y
84.082%
Downtime like this can be refundable
If you're a paying Grafana Cloud customer, outages in these windows may count against Grafana Cloud'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 Grafana Cloud entitlement →Does Grafana Cloud actually matter to you?
A Grafana Cloud 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 →Predicted resolution
n=39~156m (p25 111m – p75 397m)
Based on 39 historical Major incidents · currently 5110m elapsed.
From 7 incidents Grafana Cloud published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Grafana Cloud takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 1 still open.
Aug 28, 17:12 UTC · resolved in 7m · Resolved
Aug 28, 17:12 UTC · in progress · Monitoring
Aug 28, 00:58 UTC · resolved in 16h 22m · Resolved
Live Grafana Cloud status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/grafana-cloud)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Grafana Cloud is currently Degraded. CheckUpstream tracks Grafana Cloud 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 Grafana Cloud down" view? See the Grafana Cloud Live status page.
Aug 27, 12:09 UTC · resolved in 7h 55m · Resolved
Jul 30, 14:45 UTC · resolved in 3h · Resolved
Jul 30, 13:15 UTC · resolved in 2h 9m · Resolved
Jul 29, 21:46 UTC · resolved in 9h 48m · Resolved
Jul 24, 17:02 UTC · resolved in 1h 28m · Resolved
Jul 24, 09:17 UTC · resolved in 4h 52m · Resolved
Jul 23, 23:00 UTC · resolved in 6h 34m · Resolved
Jul 23, 17:14 UTC · resolved in 2h 35m · Resolved
Jul 23, 10:13 UTC · resolved in 5h 28m · Resolved
Jul 22, 10:27 UTC · resolved in 1h 2m · Resolved
Jul 21, 18:43 UTC · resolved in 2h 31m · Resolved
Grafana Cloud's last resolved incident started 4 days ago and lasted 16h 22m (degraded performance).
Grafana Cloud's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Grafana Cloud endpoints. It is the share of checks that returned the expected response, not a figure taken from Grafana Cloud's status page.
Sign up to CheckUpstream and add Grafana Cloud 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 Grafana Cloud'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.