Skip to content
Back to NetlifyIncident Postmortem
Netlify logo

Netlify

Tracked by PulseWatch

Auto-drafted postmortem

Netlify outage on May 3 — 102d 9h disruption

May 3, 09:24 PM → Aug 14, 07:00 AM · 102d 9h · medium

A service disruption affecting Netlify was detected on May 3, 2026, following an elevated volume of user reports. The incident impacted users for approximately 102 days and 9 hours. Service was fully restored on August 14, 2026.

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

Impact

The disruption was characterized by a significant increase in user reports, totaling 488 over the incident's duration, with a peak of 8 reports in a 15-minute period. The most frequently reported issues included websites being down, slow or unresponsive service, and API-related problems. While no specific regional impact was recorded, the incident was correlated across support forums, indicating a broad user impact across various service functionalities.

Top reported issues

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

Incident timeline

  1. May 3, 09:24 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 3, 09:53 PM

    Status updated: possible issue

  3. May 3, 10:28 PM

    Status updated: major issue

  4. May 3, 10:53 PM

    Status updated: possible issue

  5. May 3, 11:28 PM

    Status updated: major issue

  6. May 3, 11:48 PM

    Status updated: possible issue

  7. May 5, 08:45 PM

    Peak of 15 reports in 15 minutes (baseline 1.3)

  8. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 09:24 PM

    Netlify status page acknowledged the incident.

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

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