GRAFANA

⚪ Grafana's k6 Cloud went dark for 45 minutes after someone shipped a Friday-night-special API update. The fix? Ctrl+Z. Service is back, dignity is not. (Auto-resolved: no updates in 24h)

⏰ Apr 14, 2026 Fixed (for now) spotted via status_rss

// The official story

k6 Cloud Service Disruption

// Status page says

Apr 14 , 11:30 UTC Resolved - Between approximately 12:30 UTC and 13:15 UTC, k6 Cloud experienced a service disruption due to issues introduced in a recent API release. During this time, users were unable to access the k6 Cloud application. The issue was mitigated by reverting the release, and service has since been fully restored.

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

https://status.grafana.com/incidents/v9b12ncr9ftp

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)