Skip to content
Back to GrafanaIncident Postmortem
Grafana logo

Grafana

Tracked by PulseWatch

Auto-drafted postmortem

Grafana outage on May 3 — 6h 2m disruption

May 3, 02:31 PM → May 3, 08:33 PM · 6h 2m · high

On May 3, 2026, the Grafana service experienced a high-severity outage, which was detected through user reports. The disruption began at approximately 14:31 UTC. Service functionality was fully restored by 20:33 UTC on the same day.

Peak reports
12
in 15 min
Total reports
221
during the incident
Duration
6h 2m
tracked by PulseWatch

Impact

Users reported a high-severity disruption to the Grafana service. A total of 221 reports were received during the incident, with a peak of 12 reports in a 15-minute period. The primary issues reported by users included slow or unresponsive service, accounting for 212 reports, and API-related problems, with 9 reports. No specific regional impact was recorded during this period.

Top reported issues

  • Slow / unresponsive212
  • API issues9

Incident timeline

  1. May 3, 02:31 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 02:52 PM

    Status updated: major issue

  3. May 3, 02:57 PM

    Status updated: major issue

  4. May 3, 03:07 PM

    Status updated: major issue

  5. May 3, 03:12 PM

    Status updated: major issue

  6. May 3, 03:22 PM

    Status updated: major issue

  7. May 3, 03:27 PM

    Status updated: major issue

  8. May 3, 03:37 PM

    Status updated: major issue

  9. May 3, 03:42 PM

    Status updated: major issue

  10. May 3, 03:52 PM

    Status updated: major issue

  11. May 3, 03:57 PM

    Status updated: major issue

  12. May 3, 04:08 PM

    Status updated: major issue

  13. May 3, 04:13 PM

    Status updated: major issue

  14. May 3, 04:27 PM

    Status updated: major issue

  15. May 3, 04:37 PM

    Status updated: major issue

  16. May 3, 04:42 PM

    Status updated: major issue

  17. May 3, 04:52 PM

    Status updated: major issue

  18. May 3, 04:57 PM

    Status updated: major issue

  19. May 3, 05:07 PM

    Status updated: major issue

  20. May 3, 05:12 PM

    Status updated: major issue

  21. May 3, 05:22 PM

    Status updated: major issue

  22. May 3, 05:27 PM

    Status updated: major issue

  23. May 3, 05:30 PM

    Peak of 12 reports in 15 minutes (baseline 1.3)

  24. May 3, 05:37 PM

    Status updated: major issue

  25. May 3, 05:42 PM

    Status updated: major issue

  26. May 3, 05:52 PM

    Status updated: major issue

  27. May 3, 05:57 PM

    Status updated: major issue

  28. May 3, 06:07 PM

    Status updated: major issue

  29. May 3, 06:12 PM

    Status updated: major issue

  30. May 3, 06:22 PM

    Status updated: major issue

  31. May 3, 06:27 PM

    Status updated: major issue

  32. May 3, 06:37 PM

    Status updated: major issue

  33. May 3, 06:42 PM

    Status updated: major issue

  34. May 3, 06:52 PM

    Status updated: major issue

  35. May 3, 06:57 PM

    Status updated: major issue

  36. May 3, 07:07 PM

    Status updated: major issue

  37. May 3, 07:12 PM

    Status updated: major issue

  38. May 3, 07:22 PM

    Status updated: major issue

  39. May 3, 07:27 PM

    Status updated: major issue

  40. May 3, 07:37 PM

    Status updated: major issue

  41. May 3, 07:42 PM

    Status updated: major issue

  42. May 3, 07:52 PM

    Status updated: major issue

  43. May 3, 07:57 PM

    Status updated: major issue

  44. May 3, 08:07 PM

    Status updated: major issue

  45. May 3, 08:12 PM

    Status updated: major issue

  46. May 3, 08:22 PM

    Status updated: major issue

  47. May 3, 08:27 PM

    Status updated: major issue

  48. May 3, 08:33 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 02:31 PM

    Grafana status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash