Is Netlify Down?

No — Netlify is up

Reachable from all 18 checked regions

Average response time: 235ms

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

263ms

Avg response, 30 days

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

30-day history

29-day clean streak

Aug 14 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

152ms

DNS 33ms TCP 2ms TLS 16ms TTFB 118ms

arn

312ms

DNS 51ms TCP 1ms TLS 44ms TTFB 210ms

bom

236ms

DNS 129ms TCP 2ms TLS 4ms TTFB 217ms

cdg

271ms

DNS 86ms TCP 8ms TLS 19ms TTFB 231ms

dfw

409ms

DNS 109ms TCP 1ms TLS 50ms TTFB 287ms

ewr

162ms

DNS 24ms TCP 1ms TLS 14ms TTFB 128ms

fra

128ms

DNS 53ms TCP 1ms TLS 6ms TTFB 118ms

gru

213ms

DNS 136ms TCP 1ms TLS 5ms TTFB 205ms

iad

97ms

DNS 11ms TCP 1ms TLS 5ms TTFB 81ms

jnb

565ms

DNS 177ms TCP 0ms TLS 59ms TTFB 420ms

lax

161ms

DNS 28ms TCP 1ms TLS 18ms TTFB 118ms

lhr

157ms

DNS 45ms TCP 2ms TLS 9ms TTFB 143ms

nrt

264ms

DNS 177ms TCP 2ms TLS 4ms TTFB 255ms

ord

256ms

DNS 89ms TCP 1ms TLS 19ms TTFB 215ms

sin

104ms

DNS 59ms TCP 1ms TLS 2ms TTFB 96ms

sjc

77ms

DNS 6ms TCP 1ms TLS 3ms TTFB 66ms

syd

419ms

DNS 336ms TCP 0ms TLS 3ms TTFB 413ms

yyz

264ms

DNS 43ms TCP 16ms TLS 20ms TTFB 215ms

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 up to 18 cities across three 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 — the most recent check ran from 18 of them.
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 up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required