← Back to the carnage
GRAFANA

🟡 Grafana Cloud decided visibility is optional—some instances have achieved true invisibility. Engineers are squinting at logs trying to find what walked out the door. The irony of a monitoring tool being invisible to its own users is not lost on anyone. (Auto-resolved: no updates in 24h)

⏰ Jan 27, 2026 Fixed (for now) spotted via status_rss

// The official story

Grafana Cloud instances unavailable

// Status page says

Jan 27 , 10:17 UTC Investigating - Some users experience their Grafana Cloud instances as unavailable.

🔗 Official status page (for the PR-approved version)

https://status.grafana.com/incidents/1t4plkgbp05s

Grafana's Greatest Hits

🟢 GRAFANA Jul 23, 2026
🟠 Grafana's write endpoints played peek-a-boo between 21:20-22:23 UTC, dropping in and out like a flaky WiFi connection at a coffee shop. They're monitoring now, which is either reassuring or means they're as confused as we are. (Auto-resolved: no updates in 24h)
🟢 GRAFANA Jul 21, 2026
🟡 Grafana's Cloud Log Exporter ghosted several regions and nobody knows why. The logs that monitor your logs are now unmonitorable—peak recursion energy. Engineers are frantically checking the couch cushions for clues. (Auto-resolved: no updates in 24h)
🟢 GRAFANA Jul 15, 2026
🟠 Grafana's prod-eu-west-2 decided to do the Schrödinger's outage thing—some dashboards work, others don't, nobody knows which. Third-party provider apparently forgot to pay their bills. Investigators are doing that classic 'we're looking into it' dance while engineers stress-refresh Slack. (Auto-resolved: no updates in 24h)
🟢 GRAFANA Jul 14, 2026
🟠 Grafana's metrics backend decided partial outages were the new feature release. Writes are limping along, reads are confused, and rule evaluation is just vibing offline. Engineers are performing emergency CPR in the datacenter. (Auto-resolved: no updates in 24h)