Is Netlify down right now?

Live status of netlify.com, checked every 5 minutes.

Netlify is up

Last checked: 22 Oct 2026, 19:23 UTC

Answered in 150 ms

Short answer: No. Netlify is up. Our last check of netlify.com was on 22 Oct 2026, 19:23 UTC. It answered in 150 ms with HTTP status 301.

Netlify uptime and response time

Uptime today
100%
Uptime, 7 days
100%
Uptime, 30 days
100%
Average response
275 ms
30 days agoToday

Based on 2,861 checks of netlify.com since 12 Oct 2026. Each bar is one day: green means every check got an answer, amber means some failed, red means most failed, grey means no checks that day.

Recent Netlify problems we saw

None. Every check of netlify.com since 12 Oct 2026 got an answer.

A failed check means our server got no answer or a server error. It does not show which part of Netlify broke.

Netlify's own status page

Netlify is a cloud and hosting platform. It reports incidents itself, and that report says which part is affected. Check it next to the result above.

netlifystatus.com

Up here but not working for you?

Work down this list. Stop at the first step that fixes it.

  1. Reload the page with the cache skipped: Ctrl + F5 on Windows, Cmd + Shift + R on a Mac.
  2. Open netlify.com in a private window. If it works there, an extension or a stored cookie is the cause.
  3. Try another network, for example your phone with wifi turned off. If it works, the fault is in your connection or your provider.
  4. Look up the address with our DNS lookup. If it finds records but your computer does not, restart your router or switch DNS server.
  5. Check if only one part is broken (sign-in, payments, uploads). Netlify's status page lists each part.
  6. Wait 10 minutes and try again. Short faults often clear before anyone announces them.

For your own site, the full method is in our website down checklist.

How this check works

  • Every 5 minutes our server sends one request to https://netlify.com and waits up to 8 seconds.
  • Any answer below HTTP status 500 counts as up. No answer, or a status of 500 or above, counts as failed.
  • A failed check is tried once more after 3 seconds before it is recorded.
  • We check from one location. A fault that only affects another region will not show here.
  • We check one address. Netlify can have a broken feature while this address still answers.

Questions about Netlify status

Is Netlify down right now?+
No. Netlify is up. Our last check of netlify.com was on 22 Oct 2026, 19:23 UTC. It answered in 150 ms with HTTP status 301.
How often do you check Netlify?+
Every 5 minutes, with one request to https://netlify.com from our server. A check that fails is tried once more after 3 seconds before it counts as failed. Opening this page also runs one fresh check.
Netlify is up here but it does not work for me. Why?+
Our check only proves that netlify.com answers a request from our server. The fault can still be on your side (your connection, your DNS, your browser, an ad blocker), in your region only, or in one part of Netlify such as sign-in or payments while the front page still loads.
Where does Netlify announce outages?+
On its own status page: https://www.netlifystatus.com. That page is written by Netlify and says which part is affected. Ours is an outside check of one address, so the two can disagree for a few minutes at the start of an incident.
What counts as down on this page?+
No answer within 8 seconds, a failed connection, or an HTTP status of 500 or above. Any other answer counts as up, including redirects and a 403, because it shows the server is running.
Can I get this kind of check for my own website?+
Yes. PULSX checks your own site every 60 seconds and sends an alert by email, Slack, Discord, webhook or phone push when it stops answering. It is free for 20 monitors, with no card.

This page watches Netlify. Who watches your site?

PULSX checks your own website, API, cron jobs and SSL certificate every 60 seconds and tells you the minute something fails. Free for 20 monitors, with no card.