Skip to content
Back to NetlifyIncident Postmortem
Netlify logo

Netlify

Tracked by PulseWatch

Auto-drafted postmortem

Netlify outage on May 3 — 102d 7h disruption

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

A service disruption affecting Netlify was detected on May 3, 2026, following an elevated volume of user reports. The incident was resolved on August 14, 2026.

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

Impact

Users experienced a high severity disruption to Netlify services. The incident was characterized by a peak of 16 reports within a 15-minute period, with a total of 488 reports received throughout the outage. The most frequently reported issues included websites being down, slow or unresponsive service, and API-related problems. No specific regional impact was recorded during this period.

Top reported issues

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

Incident timeline

  1. May 3, 11:24 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 11:53 PM

    Status updated: possible issue

  3. May 4, 12:28 AM

    Status updated: major issue

  4. May 4, 12:48 AM

    Status updated: possible issue

  5. May 4, 12:58 AM

    Status updated: major issue

  6. May 5, 08:45 PM

    Peak of 15 reports in 15 minutes (baseline 1.3)

  7. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 11:24 PM

    Netlify status page acknowledged the incident.

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

    Slow / unresponsive clustered from 2 sources across 6 signals. Suppressed 5 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