Netlify incident: Increased errors on the CDN

Affected components

• High-Performance Edge Network
• Standard Edge Network

1. resolvedApr 2, 2026, 17:59 UTC

   This incident has been resolved.

2. monitoringApr 2, 2026, 15:34 UTC

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

3. investigatingApr 2, 2026, 14:19 UTC

   We are continuing to investigate this issue.

4. investigatingApr 2, 2026, 14:19 UTC

   We're also experiencing errors on the High Performance Edge Network. We're investigating the issue.

5. investigatingApr 2, 2026, 12:26 UTC

   We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be unaffected.

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.

• Inngest: Dashboard downCritical · Apr 2, 2026, 17:07 UTC
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• 1Password: Teams accounts are unable to access Developer EnvironmentsMinor · Apr 1, 2026, 14:13 UTC

How often does Netlify have incidents?

Netlify reported 15 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 1h 3m. See Netlify's uptime and incident history