Grafana outage on May 2 — 1d 5h disruption
May 2, 04:00 PM → May 3, 09:03 PM · 1d 5h · high
On May 2, 2026, Grafana experienced a service disruption that was detected through user reports. The incident resulted in approximately 1 day and 5 hours of degraded service. The issue was resolved on May 3, 2026, at 21:03 UTC.
Impact
During the incident, users reported experiencing issues with Grafana, leading to a total of 1000 reports. The primary reported issue type was slow or unresponsive service, accounting for 982 reports. Additionally, 18 reports indicated API-related problems. No specific regional impact was recorded, suggesting a widespread disruption. The service disruption was initially detected via these user reports.
Top reported issues
- Slow / unresponsive982
- API issues18
Incident timeline
- May 2, 04:00 PM
PulseWatch detected elevated report volume (high severity)
- May 2, 10:37 PM
Status updated: major issue
- May 2, 10:42 PM
Status updated: major issue
- May 2, 10:52 PM
Status updated: major issue
- May 2, 10:57 PM
Status updated: major issue
- May 2, 11:07 PM
Status updated: major issue
- May 2, 11:12 PM
Status updated: major issue
- May 2, 11:22 PM
Status updated: major issue
- May 2, 11:27 PM
Status updated: major issue
- May 2, 11:37 PM
Status updated: major issue
- May 2, 11:42 PM
Status updated: major issue
- May 2, 11:52 PM
Status updated: major issue
- May 2, 11:57 PM
Status updated: major issue
- May 3, 12:07 AM
Status updated: major issue
- May 3, 12:12 AM
Status updated: major issue
- May 3, 12:22 AM
Status updated: major issue
- May 3, 12:27 AM
Status updated: major issue
- May 3, 12:37 AM
Status updated: major issue
- May 3, 12:42 AM
Status updated: major issue
- May 3, 12:52 AM
Status updated: major issue
- May 3, 12:57 AM
Status updated: major issue
- May 3, 01:07 AM
Status updated: major issue
- May 3, 01:12 AM
Status updated: major issue
- May 3, 01:22 AM
Status updated: major issue
- May 3, 01:27 AM
Status updated: major issue
- May 3, 01:37 AM
Status updated: major issue
- May 3, 01:42 AM
Status updated: major issue
- May 3, 01:52 AM
Status updated: major issue
- May 3, 01:57 AM
Status updated: major issue
- May 3, 02:07 AM
Status updated: major issue
- May 3, 02:12 AM
Status updated: major issue
- May 3, 02:22 AM
Status updated: major issue
- May 3, 02:27 AM
Status updated: major issue
- May 3, 02:37 AM
Status updated: major issue
- May 3, 02:42 AM
Status updated: major issue
- May 3, 02:52 AM
Status updated: major issue
- May 3, 02:57 AM
Status updated: major issue
- May 3, 03:07 AM
Status updated: major issue
- May 3, 03:12 AM
Status updated: major issue
- May 3, 03:22 AM
Status updated: major issue
- May 3, 03:27 AM
Status updated: major issue
- May 3, 03:37 AM
Status updated: major issue
- May 3, 03:42 AM
Status updated: major issue
- May 3, 03:52 AM
Status updated: major issue
- May 3, 03:57 AM
Status updated: major issue
- May 3, 04:07 AM
Status updated: major issue
- May 3, 04:12 AM
Status updated: major issue
- May 3, 04:22 AM
Status updated: major issue
- May 3, 04:27 AM
Status updated: major issue
- May 3, 02:30 PM
Peak of 17 reports in 15 minutes (baseline 1.3)
- May 3, 08:52 PM
Status updated: major issue
- May 3, 08:57 PM
Status updated: major issue
- May 3, 09:03 PM
Report volume returned to baseline — incident resolved
Official updates
- May 2, 04:00 PM
Grafana status page acknowledged the incident.
View official source