← Back to the carnage
GRAFANA
🟡 Grafana's k6 extension-based test runs decided to ghost everyone—local and cloud deployments equally affected. Regular tests are fine, which is like saying your car works great except when you try to drive it. Engineering team is presumably refreshing their status page every 30 seconds. (Auto-resolved: no updates in 24h)
// The official story
Partial K6 Test Run Outage
// Status page says
Apr 3 , 15:29 UTC Investigating - We're experiencing an outage affecting test runs that use k6 extensions. The issue prevents users from executing these types of test runs both locally and in Grafana Cloud. Test runs that do not use extensions are not affected by this incident.
🔗 Official status page (for the PR-approved version)
https://status.grafana.com/incidents/07mjd7ggxs1sGrafana'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)