Is Grafana Cloud Down?

No — Grafana Cloud is up

Reachable from all 8 checked regions

Average response time: 241ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.grafana.com

Phone call notifications to numbers in Russia and Kazakhstan are blocked

minor investigating

Phone call notifications to numbers in Russia and Kazakhstan are currently blocked. We are working to resolve the issue. As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative. We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.

Components the vendor reports as affected: Incident Management and Response (IRM) Degraded Performance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Grafana Cloud fail from enough regions to rule out probe noise.

Grafana Cloud uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

385ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 77 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

77-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

94ms

DNS 30ms TCP 5ms TLS 8ms TTFB 62ms

arn

151ms

DNS 64ms TCP 5ms TLS 8ms TTFB 116ms

cdg

68ms

DNS 28ms TCP 2ms TLS 5ms TTFB 53ms

dfw

108ms

DNS 48ms TCP 2ms TLS 5ms TTFB 80ms

ewr

189ms

DNS 72ms TCP 7ms TLS 10ms TTFB 128ms

sjc

210ms

DNS 48ms TCP 11ms TLS 15ms TTFB 139ms

syd

973ms

DNS 0ms TCP 1ms TLS 5ms TTFB 223ms

yyz

135ms

DNS 18ms TCP 1ms TLS 4ms TTFB 51ms

What Grafana Cloud does

Grafana Cloud is the hosted version of Grafana, bundling dashboards with managed backends for metrics, logs, traces and profiles, plus alerting, synthetic monitoring and k6 load testing. Engineering teams point their telemetry at it and run on-call alerting from it, so an incident affects how they see their own systems rather than the systems themselves.

What an outage looks like

Dashboards load but panels show no data or stop at a gap, and queries time out or return partial results. Metric, log and trace ingestion may be rejected, so the missing window is permanent rather than merely delayed in appearing. Most seriously, alert rule evaluation and notifications can stop, which means genuine problems in your own infrastructure go unannounced while everything looks quiet.

What to do about it

Check status.grafana.com, which separates Grafana itself from Metrics, Logs, Traces, Alerting and SLO, Synthetic Monitoring and Incident Management, and reports them across the AWS, GCP and Azure regions. Treat an Alerting incident as a monitoring blackout and watch critical systems by other means until it clears. Do not read empty dashboards as evidence that your services are healthy.

Is it down for everyone, or just you?

If this page says Grafana Cloud is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Grafana Cloud outage FAQ

Are my alerts still firing if Grafana Cloud is down?

Not necessarily, and this is the risk that matters most. Alerting and SLO is a separate component covering rule evaluation and the alertmanager, and when it is degraded conditions that should page someone may go unevaluated or unnotified. Assume you are flying blind for the duration and arrange another way to watch anything critical rather than trusting the silence.

Is my data lost if Grafana Cloud ingestion fails?

Data that could not be ingested is generally gone rather than delayed. Agents and collectors buffer for a limited window and then drop what they cannot send, so a long incident leaves a permanent gap in the metrics, logs or traces for that period. Note the window, because a gap in a dashboard six months from now is very hard to explain otherwise.

Is Grafana Cloud down or is my data source broken?

Check which component is flagged, since the symptom is the same either way. An empty panel can mean Grafana cannot query the backend, or that nothing is being ingested, or that your own exporter stopped. If Grafana, Metrics and Logs are all operational, look at whether the agent on your infrastructure is still running before investigating anything on the Grafana side.

Does a Grafana Cloud outage affect self-hosted Grafana?

No. Self-hosted Grafana runs on your own infrastructure and is independent of the hosted service, so an incident on status.grafana.com does not affect it. The exception is a self-hosted instance querying Grafana Cloud backends as a data source, or using Private Datasource Connect, where the dashboards are yours but the data behind them is not.

Why does synthetic monitoring stop reporting during an incident?

Synthetic Monitoring is its own component, covering both the API and the public probes that run checks from Grafana's locations. When it is degraded, checks may not run or their results may not arrive, which looks identical to the checked service being unreachable. Confirm against the status page before treating a synthetic failure as evidence that your own endpoint is down.

How we measure this

We request Grafana Cloud's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Grafana Cloud publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Grafana Cloud goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required