Skip to content
Back to NetlifyIncident Postmortem
Netlify logo

Netlify

Tracked by PulseWatch

Auto-drafted postmortem

Netlify outage on May 3 — 102d 14h disruption

May 3, 04:14 PM → Aug 14, 07:00 AM · 102d 14h · high

A service disruption affecting Netlify was detected due to an elevated volume of user reports. The incident, which lasted 102 days and 14 hours, was resolved on August 14, 2026.

Peak reports
12
in 15 min
Total reports
488
during the incident
Duration
102d 14h
tracked by PulseWatch

Impact

The incident led to a significant increase in user reports, totaling 488 during the disruption. The most frequently reported issue type was 'Website down' (310 reports), followed by 'Slow / unresponsive' (151 reports) and 'API issues' (18 reports). No specific top impacted regions were recorded.

Top reported issues

  • Website down310
  • Slow / unresponsive151
  • API issues18
  • Cloud provider issues9

Incident timeline

  1. May 3, 04:14 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 04:28 PM

    Status updated: major issue

  3. May 3, 04:48 PM

    Status updated: possible issue

  4. May 3, 05:28 PM

    Status updated: major issue

  5. May 3, 05:48 PM

    Status updated: possible issue

  6. May 3, 06:28 PM

    Status updated: major issue

  7. May 3, 06:48 PM

    Status updated: possible issue

  8. May 3, 07:28 PM

    Status updated: major issue

  9. May 3, 07:48 PM

    Status updated: possible issue

  10. May 3, 08:28 PM

    Status updated: major issue

  11. May 3, 08:48 PM

    Status updated: possible issue

  12. May 3, 09:28 PM

    Status updated: major issue

  13. May 5, 08:45 PM

    Peak of 15 reports in 15 minutes (baseline 1.3)

  14. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 04:14 PM

    Netlify status page acknowledged the incident.

    View official source
  2. Aug 14, 07:00 AM

    Slow / unresponsive clustered from 2 sources across 12 signals. Suppressed 11 redundant alerts and flagged flapping behavior.

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