← Back to the carnage
GRAFANA

🟡 Grafana's 429 errors are doing their best impression of a bouncer who read the door policy wrong. Metrics queries getting rejected faster than spam applications. Engineering team is caffeinating heavily across multiple regions. (Auto-resolved: no updates in 24h)

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

// The official story

Elevated 429 Errors Impacting Metrics Querying Across Multiple Regions

// Status page says

Apr 20 , 14:09 UTC Investigating - We are currently experiencing a major incident causing elevated 429 (rate limit) errors across multiple regions, primarily impacting metrics querying. This is a high-priority issue, and our engineering team is actively engaged and working urgently to identify the root cause and restore full service as quickly as possible. Customers may experience widespread failures or delays when querying

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

https://status.grafana.com/incidents/71xkpmw5c372

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)