Netlify incident: Increase in DNS Resolution Errors

Affected components

• Hosted DNS
• Standard Edge Network

1. resolvedMay 10, 2026, 08:56 UTC

   This incident has been resolved.

2. monitoringMay 10, 2026, 08:55 UTC

   We are continuing to monitor for any further issues.

3. monitoringMay 10, 2026, 08:32 UTC

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

4. identifiedMay 10, 2026, 08:07 UTC

   We're experiencing an increase in DNS resolution errors impacting domains on our Standard Edge Network. A fix has been deployed, and we're monitoring the results.

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Short Codes to Google Voice United StatesMinor · May 4, 2026, 20:40 UTC
• Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Twilio: SMS Delivery Delays from Twilio to Multiple Networks in Multiple Countries in EuropeMinor · May 7, 2026, 08:07 UTC
• Twilio: SMS Delivery Failures from Twilio to Orange MadagascarMinor · May 7, 2026, 13:15 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC

How often does Netlify have incidents?

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