Live  /  Providers  /  Netlify

Netlify

netlify.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Netlify. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Cloud & hosting · SquidGrid tracks Netlify’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Netlify is reporting

Current & recent incidents

Resolved

Error accessing Netlify-hosted sites

Major impact · 2026-09-24 19:25 UTC

Resolved

Elevated CDN Errors

Minor impact · 2026-09-24 00:00 UTC

Resolved

Errors accessing Netlify-hosted sites

Major impact · 2026-09-21 16:37 UTC

Resolved

Elevated Image CDN Errors

Minor impact · 2026-09-16 13:19 UTC

Resolved

Increased Latency in IAD Region on Global Network

Minor impact · 2026-08-31 20:56 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Netlify has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Netlify runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Netlify is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Netlify.