Live / Netlify / Incident
Netlify: Error accessing Netlify-hosted sites
Netlify · netlify.appMinor incidentResolved2026-10-05 13:34 UTC
Public — what happened
Summary
Netlify said it was looking into reports that visitors were running into errors when trying to reach sites served through its High-Performance Edge Network, beginning at 12:44 UTC on October 5, 2026. The company posted a follow-up at 13:00 UTC saying its investigation was still underway. By 13:17 UTC, Netlify reported it had found the problem and was rolling out a fix, though it did not describe the cause publicly. The incident, which Netlify rated as minor, was marked resolved at 13:34.
Affected
High-Performance Edge Network
Timeline
- Started — 2026-10-05 12:44 UTC
- Investigating — 2026-10-05 12:44 UTC (2 updates)
- Identified — 2026-10-05 13:17 UTC
- Resolved — 2026-10-05 13:34 UTC · 50 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Netlify against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Netlify: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Netlify report →
More from Netlify
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.