Is Netlify Down?

No — Netlify is up

Reachable from all 18 checked regions

Average response time: 240ms

Last checked 1 minute ago · checks run every 30 minutes

Official status page: https://www.netlifystatus.com

Netlify uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

267ms

Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 30 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

10-day clean streak

Jul 26 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

126ms

DNS 13ms TCP 1ms TLS 16ms TTFB 88ms

arn

313ms

DNS 46ms TCP 1ms TLS 42ms TTFB 213ms

bom

271ms

DNS 204ms TCP 1ms TLS 3ms TTFB 262ms

cdg

202ms

DNS 25ms TCP 8ms TLS 18ms TTFB 161ms

dfw

352ms

DNS 8ms TCP 30ms TLS 26ms TTFB 223ms

ewr

179ms

DNS 39ms TCP 0ms TLS 15ms TTFB 144ms

fra

233ms

DNS 150ms TCP 1ms TLS 6ms TTFB 215ms

gru

213ms

DNS 139ms TCP 3ms TLS 5ms TTFB 200ms

iad

93ms

DNS 17ms TCP 2ms TLS 7ms TTFB 84ms

jnb

552ms

DNS 190ms TCP 0ms TLS 59ms TTFB 407ms

lax

209ms

DNS 67ms TCP 1ms TLS 19ms TTFB 164ms

lhr

185ms

DNS 56ms TCP 2ms TLS 4ms TTFB 163ms

nrt

218ms

DNS 144ms TCP 2ms TLS 5ms TTFB 202ms

ord

201ms

DNS 44ms TCP 2ms TLS 21ms TTFB 148ms

sin

315ms

DNS 255ms TCP 2ms TLS 3ms TTFB 301ms

sjc

80ms

DNS 11ms TCP 1ms TLS 3ms TTFB 75ms

syd

406ms

DNS 330ms TCP 1ms TLS 3ms TTFB 397ms

yyz

172ms

DNS 41ms TCP 0ms TLS 16ms TTFB 135ms

What Netlify does

Netlify is a web hosting and automation platform for modern web projects. It provides continuous deployment from Git, serverless functions, form handling, and a global CDN. Netlify is popular among developers building JAMstack sites with frameworks like Gatsby, Hugo, and Eleventy.

What an outage looks like

Netlify outages may cause deployed sites to return error pages or load very slowly. Build and deploy pipelines may stall, with builds stuck in the queue indefinitely. Netlify Forms submissions may fail, and serverless Netlify Functions may return 500 errors or time out.

What to do about it

Check www.netlifystatus.com for real-time incident updates. If your site is critical, consider having a backup deployment on another platform. For build failures, check the deploy log in the Netlify dashboard once it's accessible again to see if a retry is needed.

Is it down for everyone, or just you?

If this page says Netlify is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Netlify outage FAQ

Will my Netlify site stay online during a Netlify outage?

Static sites hosted on Netlify's CDN often remain accessible during partial outages because the content is cached across multiple edge nodes. If the CDN itself is impacted, your site may go down. Sites with serverless functions are more likely to be affected since those require Netlify's compute infrastructure.

How long do Netlify outages usually last?

Most Netlify incidents are resolved within 30 minutes to a few hours. CDN-related issues are typically resolved faster than build system problems. You can check historical incidents on netlifystatus.com to see typical resolution times.

Can I deploy my site elsewhere if Netlify is down?

If you need an emergency fallback, you can deploy your static site to another platform like Vercel or Cloudflare Pages and update your DNS to point to the new host. However, this requires DNS propagation time and is only practical if you have a pre-configured backup deployment.

Does Netlify's build system affect my site's availability?

No, Netlify's build system and hosting CDN are separate. If the build system is down, your current live deployment continues serving traffic normally. You just won't be able to deploy new versions until the build system recovers.

How we measure this

We request Netlify's public endpoint every 30 minutes from Fly.io regions across six continents — 18 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Netlify publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Netlify goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required