Grafana status · Observability · checked (21s ago)
Also searched as Grafana Cloud.
Operational
No — Grafana is not down. All Grafana systems are reported operational.
According to Grafana's official status page, Grafana was reporting “Service Under Maintenance” when isuptime last checked at . Over the last 30 days, Grafana's feed reported no outage in 100.00% of our checks.
No outage reported (30d)
100.00%
Share of our checks where Grafana's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
400 ms
How long the last status check took
Reported by
Operational
Service Under Maintenance
Is Grafana down for you right now?
Everything above is read from Grafana's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Grafana in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What Grafana is
Grafana Cloud is the hosted version of Grafana: dashboards, plus managed Loki for logs, Mimir for metrics, Tempo for traces and Grafana OnCall for alerting. It is monitoring infrastructure, so its outages have a particular sting.
What Grafana's status feed covers
Grafana's status page separates the hosted backends — metrics, logs, traces — from the dashboard front end and from alerting, and reports by region. Alerting is the component to watch: dashboards being unavailable is an inconvenience, whereas an alerting incident means notifications for your own systems may not fire.
One bar per day. Each shows the share of that day's checks where Grafana's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Grafana was down.
2026-08-2530 of 30 days recordedToday
No outage reported (99%+)
95–99%
80–95%
Under 80%
No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 22s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
AWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration API — under_maintenance
AWS Germany - prod-eu-west-2: API — under_maintenance
Grafana outage history
Grafana has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Grafana posted itself — not every problem users hit.
No — Grafana is not down. All Grafana systems are reported operational. Checked (21s ago).
What is Grafana's status right now?
Grafana is reporting “Service Under Maintenance” on its official status page — Operational — as of . That status feed answered our last check in 400 ms. isuptime reads this from Grafana's own published feed and does not test Grafana independently.
When did Grafana last go down?
The most recent incident Grafana published was “Kubernetes Observability Billing & Usage Incorrect”, opened Sep 22, 09:27 PM UTC (19h ago) and marked resolved Sep 23, 02:06 PM UTC. That is the latest entry in Grafana's own incident feed, not every problem users experienced.
What is Grafana's uptime?
isuptime does not measure Grafana's uptime directly — it reads Grafana's own published status feed. Over the last 30 days, Grafana's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is Grafana down for everyone?
Grafana reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
Grafana says operational but it is not working for me
A dashboard showing no data is usually the data source rather than Grafana — check that the underlying Prometheus, Loki or database is reachable and that the query's time range covers actual data. Expired data source credentials produce empty panels rather than errors. Ingestion rate limits on your plan silently drop series.
