Minor impactResolvedCloud

Netlify incident: Purges are Delayed on Primary Load Balancer

Netlify reported this minor-impact incident on its official status page on May 15, 2026, 16:23 UTC. It was resolved after 2h 36m.

Right now Netlify is operational. Live Netlify status →

🔔 Get alerted when Netlify has issuesFree · email alerts · no credit card
May 15, 2026, 16:23 UTC
started
May 15, 2026, 18:58 UTC
resolved
2h 36m
duration
Minor
impact

Affected components

  • Standard Edge Network

Timeline

updates from Netlify's status page ↗
  1. resolvedMay 15, 2026, 18:58 UTC

    This incident has been resolved.

  2. monitoringMay 15, 2026, 17:44 UTC

    A fix has been implemented, and we are monitoring the results.

  3. identifiedMay 15, 2026, 16:23 UTC

    We are currently experiencing a delay in cache purges, and some sites on our Standard Edge Network may be serving stale content. The issue has been identified and a fix is being implemented.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Netlify's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Netlify have incidents?

Netlify reported 9 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 31 min. See Netlify's uptime and incident history

← Previous: Increased Latency in API & Builds (May 12, 2026)Next: Degraded performance with Create API (May 19, 2026) →
Netlify incident on May 15, 2026: Purges are Delayed on Primary Load Balancer · APIStatus.watch