← Back to the carnage
GRAFANA
🟡 Tempo stopped accepting writes in prod-us-east-3 since 18:50 UTC. Users getting the full error experience while engineers play forensics with their infrastructure. Nothing says 'observability platform' like being unable to observe your own metrics. (Auto-resolved: no updates in 24h)
// The official story
Tempo Write Outage
// Status page says
Apr 10 , 19:42 UTC Investigating - We are currently investigating a write outage affecting prod-us-east-3. The issue began at 18:50 UTC. Users may experience errors, timeouts, or unavailability while we work to identify the cause and restore service.
🔗 Official status page (for the PR-approved version)
https://status.grafana.com/incidents/80yc5t3fwf8cGrafana'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)