Netlify outage: Elevated HTTP 500 errors serving sites and the Netlify UI

1. resolvedAug 18, 2026, 20:00 UTC

   On August 18 between 20:02 and 20:08 UTC, some visitors to Netlify-hosted sites and people using the Netlify dashboard received error pages instead of the content they requested. Normal service was restored at 20:08 UTC. We apologize for the disruption

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.

• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio Phone Numbers to Claro BrazilMinor · Aug 18, 2026, 14:30 UTC
• Expo: iOS Submissions hanging on App Store Connect build uploadsMinor · Aug 18, 2026, 16:25 UTC
• Twilio: Flex login errors with SSOv2Minor · Aug 18, 2026, 17:10 UTC
• Twilio: 1Console Login UnavailableMinor · Aug 18, 2026, 17:13 UTC
• Cursor: Grok Bot connector delaysMinor · Aug 18, 2026, 18:46 UTC
• Cursor: GitHub-connected Cloud Agent workflows degradedMinor · Aug 18, 2026, 19:47 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