Skip to content
Back to NetlifyIncident Postmortem
Netlify logo

Netlify

Tracked by PulseWatch

Auto-drafted postmortem

Netlify outage on May 4 — 15h 2m disruption

May 4, 12:47 AM → May 4, 03:49 PM · 15h 2m · high

On May 4, 2026, a service disruption affecting Netlify was detected through user reports. The incident began at 00:47 UTC and was resolved at 15:49 UTC on the same day.

Peak reports
9
in 15 min
Total reports
230
during the incident
Duration
15h 2m
tracked by PulseWatch

Impact

Users reported a high severity disruption to Netlify services, with a total of 230 reports received during the incident. The primary issues reported included slow or unresponsive service (127 reports), websites being down (94 reports), and API-related problems (9 reports). These reports were correlated across support forums, indicating a broad impact on user experience. No specific regional concentrations of reports were identified.

Top reported issues

  • Slow / unresponsive127
  • Website down94
  • API issues9

Incident timeline

  1. May 4, 12:47 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 4, 01:18 AM

    Status updated: possible issue

  3. May 4, 01:23 AM

    Status updated: possible issue

  4. May 4, 01:28 AM

    Status updated: major issue

  5. May 4, 01:48 AM

    Status updated: possible issue

  6. May 4, 01:53 AM

    Status updated: possible issue

  7. May 4, 01:58 AM

    Status updated: possible issue

  8. May 4, 02:18 AM

    Status updated: possible issue

  9. May 4, 02:23 AM

    Status updated: possible issue

  10. May 4, 02:28 AM

    Status updated: major issue

  11. May 4, 02:48 AM

    Status updated: possible issue

  12. May 4, 02:53 AM

    Status updated: possible issue

  13. May 4, 02:58 AM

    Status updated: possible issue

  14. May 4, 03:18 AM

    Status updated: possible issue

  15. May 4, 03:23 AM

    Status updated: possible issue

  16. May 4, 03:28 AM

    Status updated: major issue

  17. May 4, 03:48 AM

    Status updated: possible issue

  18. May 4, 03:53 AM

    Status updated: possible issue

  19. May 4, 03:58 AM

    Status updated: possible issue

  20. May 4, 04:18 AM

    Status updated: possible issue

  21. May 4, 04:23 AM

    Status updated: possible issue

  22. May 4, 04:28 AM

    Status updated: major issue

  23. May 4, 04:48 AM

    Status updated: possible issue

  24. May 4, 04:53 AM

    Status updated: possible issue

  25. May 4, 04:58 AM

    Status updated: possible issue

  26. May 4, 05:18 AM

    Status updated: possible issue

  27. May 4, 05:23 AM

    Status updated: possible issue

  28. May 4, 05:28 AM

    Status updated: major issue

  29. May 4, 05:48 AM

    Status updated: possible issue

  30. May 4, 05:53 AM

    Status updated: possible issue

  31. May 4, 05:58 AM

    Status updated: possible issue

  32. May 4, 06:18 AM

    Status updated: possible issue

  33. May 4, 06:23 AM

    Status updated: possible issue

  34. May 4, 06:28 AM

    Status updated: major issue

  35. May 4, 09:15 AM

    Peak of 10 reports in 15 minutes (baseline 1.3)

  36. May 4, 03:49 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 12:47 AM

    Netlify 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