Is Netlify Down?

No — Netlify is up

Reachable from all 17 checked regions

Average response time: 295ms

Last checked 27 minutes 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

334ms

Avg response, 30 days

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

30-day history

80-day clean streak

Sep 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

413ms

DNS 36ms TCP 8ms TLS 17ms TTFB 378ms

arn

378ms

DNS 6ms TCP 1ms TLS 50ms TTFB 258ms

cdg

256ms

DNS 15ms TCP 9ms TLS 19ms TTFB 214ms

dfw

521ms

DNS 116ms TCP 0ms TLS 49ms TTFB 403ms

ewr

168ms

DNS 22ms TCP 1ms TLS 14ms TTFB 135ms

fra

130ms

DNS 34ms TCP 1ms TLS 5ms TTFB 117ms

gru

335ms

DNS 239ms TCP 1ms TLS 2ms TTFB 328ms

iad

171ms

DNS 55ms TCP 2ms TLS 6ms TTFB 160ms

jnb

647ms

DNS 172ms TCP 0ms TLS 53ms TTFB 520ms

lax

192ms

DNS 12ms TCP 1ms TLS 18ms TTFB 151ms

lhr

168ms

DNS 29ms TCP 2ms TLS 5ms TTFB 150ms

nrt

210ms

DNS 9ms TCP 1ms TLS 4ms TTFB 201ms

ord

271ms

DNS 23ms TCP 11ms TLS 11ms TTFB 216ms

sin

123ms

DNS 10ms TCP 1ms TLS 3ms TTFB 116ms

sjc

247ms

DNS 44ms TCP 2ms TLS 3ms TTFB 236ms

syd

534ms

DNS 293ms TCP 1ms TLS 3ms TTFB 526ms

yyz

254ms

DNS 21ms TCP 12ms TLS 20ms TTFB 206ms

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 17 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 17 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 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required