Skip to content
Back to GrafanaIncident Postmortem
Grafana logo

Grafana

Tracked by PulseWatch

Auto-drafted postmortem

Grafana outage on May 3 — 16h 45m disruption

May 3, 04:03 AM → May 3, 08:48 PM · 16h 45m · high

On May 3, 2026, Grafana experienced a service disruption that was detected through user reports. The incident began at 04:03 UTC and was resolved at 20:48 UTC on the same day.

Peak reports
22
in 15 min
Total reports
593
during the incident
Duration
16h 45m
tracked by PulseWatch

Impact

During the incident, users reported experiencing issues with Grafana. A total of 593 reports were received, with the majority indicating slow or unresponsive service. A smaller number of reports cited API-related problems. No specific regional impact was identified from the reports.

Top reported issues

  • Slow / unresponsive584
  • API issues9

Incident timeline

  1. May 3, 04:03 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 08:53 AM

    Status updated: major issue

  3. May 3, 08:57 AM

    Status updated: major issue

  4. May 3, 09:07 AM

    Status updated: major issue

  5. May 3, 09:12 AM

    Status updated: major issue

  6. May 3, 09:22 AM

    Status updated: major issue

  7. May 3, 09:27 AM

    Status updated: major issue

  8. May 3, 09:37 AM

    Status updated: major issue

  9. May 3, 09:42 AM

    Status updated: major issue

  10. May 3, 09:52 AM

    Status updated: major issue

  11. May 3, 09:57 AM

    Status updated: major issue

  12. May 3, 10:07 AM

    Status updated: major issue

  13. May 3, 10:12 AM

    Status updated: major issue

  14. May 3, 10:22 AM

    Status updated: major issue

  15. May 3, 10:27 AM

    Status updated: major issue

  16. May 3, 10:37 AM

    Status updated: major issue

  17. May 3, 10:42 AM

    Status updated: major issue

  18. May 3, 10:52 AM

    Status updated: major issue

  19. May 3, 10:57 AM

    Status updated: major issue

  20. May 3, 11:07 AM

    Status updated: major issue

  21. May 3, 11:12 AM

    Status updated: major issue

  22. May 3, 11:22 AM

    Status updated: major issue

  23. May 3, 11:27 AM

    Status updated: major issue

  24. May 3, 11:37 AM

    Status updated: major issue

  25. May 3, 11:42 AM

    Status updated: major issue

  26. May 3, 11:52 AM

    Status updated: major issue

  27. May 3, 11:57 AM

    Status updated: major issue

  28. May 3, 12:07 PM

    Status updated: major issue

  29. May 3, 12:12 PM

    Status updated: major issue

  30. May 3, 12:22 PM

    Status updated: major issue

  31. May 3, 12:27 PM

    Status updated: major issue

  32. May 3, 12:37 PM

    Status updated: major issue

  33. May 3, 12:42 PM

    Status updated: major issue

  34. May 3, 12:52 PM

    Status updated: major issue

  35. May 3, 12:57 PM

    Status updated: major issue

  36. May 3, 01:07 PM

    Status updated: major issue

  37. May 3, 01:12 PM

    Status updated: major issue

  38. May 3, 01:22 PM

    Status updated: major issue

  39. May 3, 01:27 PM

    Status updated: major issue

  40. May 3, 01:37 PM

    Status updated: major issue

  41. May 3, 01:42 PM

    Status updated: major issue

  42. May 3, 01:52 PM

    Status updated: major issue

  43. May 3, 01:57 PM

    Status updated: major issue

  44. May 3, 02:07 PM

    Status updated: major issue

  45. May 3, 02:12 PM

    Status updated: major issue

  46. May 3, 02:22 PM

    Status updated: major issue

  47. May 3, 02:27 PM

    Status updated: major issue

  48. May 3, 02:30 PM

    Peak of 17 reports in 15 minutes (baseline 1.3)

  49. May 3, 02:37 PM

    Status updated: major issue

  50. May 3, 02:42 PM

    Status updated: major issue

  51. May 3, 08:37 PM

    Status updated: major issue

  52. May 3, 08:42 PM

    Status updated: major issue

  53. May 3, 08:48 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 04:03 AM

    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