← Back to the carnage
GRAFANA
⚪ Grafana's synthetic monitoring public probe in Calgary decided to take an unscheduled siesta from 12:09-12:35 UTC. Your tests that relied on it? Yeah, they failed spectacularly. At least it's back now and nobody's still waiting for results from February.
// The official story
Degradation of service on Synthetic Monitoring Public Probe AWS Canada (Calgary)
// Status page says
Feb 17 , 12:47 UTC Resolved - There was a service degradation today from ~12:09 UTC until ~12:35 UTC on the Public Probe of Calgary for Synthetic Monitoring. Impact may include SM check fails where the probe was used.
🔗 Official status page (for the PR-approved version)
https://status.grafana.com/incidents/n0q9zdwc447dGrafana'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)