Home
Services
Netlify

Netlify netlify.com

Is Netlify down right now? Live status and outage tracker

No, Netlify is up.

No outage detected, and no user reports in the last hour.

Netlify's own status page: www.netlifystatus.com

Live Updated 4 min ago Data refreshes every 5 minutes

Not working for you? Official status pageStatus page

User reports, last 24 hours, 15 minutes a segment: 96 flowing 0 slow (elevated) 0 jammed (outage)

User reports, last 24 hours

2 reports in total, counted in 15-minute windows

No problem reports came in for Netlify in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 2 reports. Worldwide, most recent reports were about hosting (50%) and domains (25%). There has been no spike in reports since 29 October. These are user reports from the US, where most people report Netlify problems.

Around the world right now: normal in 71 other countries. By country

NormalClose to the usual level24 h · 2 reports
ElevatedMore than 1.5 times the usual levelNone in this chart
OutageMore than twice the usual level and far above the day's averageNone in this chart
Usual levelWhat a usual day sees at that timeAlmost none at this time of day

Reports, last hour

Quiet

Uptime, 24 h

100.00%

No outage windows

Last outage

None

In the last 24 hours

Busiest 15 minutes

1 report, 21 h ago

Last 24 hours

Netlify outages and problems

In the past 24 hours, 2 user reports came in for Netlify. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 1 report, about 21 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Netlify stayed at their usual level the whole time.

Official status

What Netlify's status page says

Checking www.netlifystatus.com…

This month

Netlify in November 2026

Problem reports in November: 1

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for Netlify worldwide.

Hosting50%
Domains25%
DNS25%

Share of 4 recent reports that said what was wrong, from every country listed below.

World map

Netlify reports around the world

In the last 24 hours, 15 problem reports about Netlify came in from 10 countries. Right now reports are at the usual level in every country.

Outage now
Problems now
Normal

Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Country	Now	24 hours
Italy	Normal	3
The US numbers above	Normal	2
Turkey	Normal	2
Nigeria	Normal	2
Belgium	Normal	1
Canada	Normal	1
Finland	Normal	1
Greece	Normal	1
Thailand	Normal	1
Costa Rica	Normal	1
The UK	Normal	0
Mexico	Normal	0

Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Netlify problem spikes, last 30 days

Since 29 October, Netlify had no outage spikes or periods of elevated reports.

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

The US11
Italy5
Chile2
The UK2
India2
Nigeria2
Turkey2
South Africa2

Country history starts on 29 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 29 October 2026. Monthly reports for all services

Troubleshooting

How to fix Netlify not working

Netlify is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach netlify.com over your own connection, right now. Nothing is sent to us or stored.

Check the Deploys tab for failures
Open Deploys for failures. If the latest deploy shows Failed, click it to read the build log where you can spot a bad build command or missing environment variable.
Trigger a clean retry deploy
Use Trigger deploy for stuck builds. Pick Clear cache and deploy site when your page sticks on old content because cached dependencies block the fresh build from finishing.
Verify domain and HTTPS settings
Visit Site settings for domains. When your custom domain shows a certificate error, check Domain management for DNS records and allow TLS to renew after you fix them.
Re-link Git and rebuild locally
Run netlify build in your repo clone because a failure on your laptop often explains a failed deploy, and you can catch missing packages before you push again. Reconnect Git if needed.

While Netlify is down: what to use instead

Vercel Move a Git-based static or Next.js site here when you need a deploy to go out and the usual build pipeline will not finish.
Cloudflare Pages Use it for a static site or JAMstack build if you want to connect the same repo and get a live URL without waiting on the main host.
GitHub Pages Push a plain static site from a GitHub repo when you only need HTML, CSS and client-side JavaScript online.
Render Point a repo at it for a web service or static site when you need builds and a custom domain while your usual host is unavailable.

Your device

Fix Netlify on Windows, Mac, Android and iPhone

Netlify on Windows

Fix: Clear your browser cache and flush your Windows DNS cache via the Command Prompt to resolve local connection blocks to Netlify. You can also try temporarily disabling Windows Defender Firewall to see if it is blocking Netlify's deployment traffic.
Check: Check if you can access the Netlify status page or test the connection to the Netlify API endpoint using the command line. If other websites load but the Netlify dashboard does not, the service might be experiencing an outage.

Command Prompt

ping netlify.comTest whether Netlify's servers reply

nslookup netlify.comCheck that Netlify's DNS resolves

tracert netlify.comTrace where the connection drops

ipconfig /flushdnsClear the DNS cache, then reload

Netlify on Mac

Fix: Clear your browser data and flush the directory service cache in macOS Terminal to restore your connection to Netlify. Ensure that any active VPNs or iCloud Private Relay settings are temporarily disabled, as they can interfere with Netlify routes.
Check: Try accessing Netlify's official status page or use diagnostic tools to check your connection path to Netlify's servers. If the site fails to load across multiple browsers on your Mac, Netlify may be down.

Terminal

ping -c 4 netlify.comTest whether Netlify's servers reply

nslookup netlify.comCheck that Netlify's DNS resolves

traceroute netlify.comTrace where the connection drops

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Netlify on Android

Fix: Clear the storage and cache of your mobile browser, or switch from Wi-Fi to mobile data to bypass local DNS issues routing to Netlify. Ensure that any active VPN or custom DNS setting on your Android device is disabled.
Check: Attempt to load the Netlify dashboard or a Netlify-hosted site on a different network to see if the issue is isolated. If you receive a server error on both Wi-Fi and mobile data, Netlify is likely experiencing an outage.

Netlify on iPhone and iPad

Fix: Clear your Safari history and website data, and toggle Airplane Mode on and off to reset your network connection to Netlify. You should also temporarily disable iCloud Private Relay in your iCloud settings if Netlify sites fail to load.
Check: Use a mobile browser to visit Netlify's status page or test if other websites load normally on your iPhone or iPad. If only Netlify-hosted pages fail to load, the platform is likely down.

About

What happens when Netlify goes down

Netlify hosts static sites. You link a GitHub repo to ship marketing pages and docs with Forms and Functions, so when the service fails your builds stick in the queue and visitors see blank screens or missing pages.

Builds tend to stall first while the dashboard spins or shows failed deploys although live pages still open because the build queue backs up before the edge cache fails. Your build never finishes. When domains drop you face certificate warnings and Forms stop saving submissions. Outages stay partial in most cases, so your live site can fail in one region while deploys work elsewhere and rollbacks through the dashboard bring back the last good version.

Servers and network

Netlify IP address, servers and network

IPv4 addresses: 15.197.167.90
Show all 2
3.33.186.135
IPv6 addresses: 2a05:d014:58f:6200::1f5
Show all 2
2a05:d014:58f:6200::1f6
Network: AS16509 · Amazon.com, Inc., registered in the United States
Served through: Netlify
DNS hosted by: NS1
HTTPS certificate: Issued by DigiCert Inc, valid until 6 Feb 2027 (96 days)
HTTP/3: Not advertised
Our check: Answered in 795 ms

Checked from our server in Frankfurt, Germany, 2 days ago, for www.netlify.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from www.netlify.com. Fastest from Singapore (128 ms), slowest from Madrid (389 ms). Every location connected through Amazon.com, Inc. (AS16509), using 2 different addresses.

Location	Result	Time	Address reached
FrankfurtGermany	Up	231 ms	3.33.186.135
ViennaAustria	Up	308 ms	3.33.186.135
MilanItaly	Up	347 ms	3.33.186.135
ParisFrance	Up	252 ms	3.33.186.135
AmsterdamNetherlands	Up	294 ms	3.33.186.135
MadridSpain	Up	389 ms	3.33.186.135
WarsawPoland	Up	346 ms	3.33.186.135
Los AngelesUSA	Up	335 ms	3.33.186.135
São PauloBrazil	Up	166 ms	15.197.167.90
SingaporeSingapore	Up	128 ms	15.197.167.90
TokyoJapan	Up	200 ms	3.33.186.135

Checked with check-host.net from its servers in these cities 2 days ago, for www.netlify.com. Time is how long each server took to load the page.

Questions

Netlify FAQ

Is Netlify down right now?

The status at the top of this page shows whether user problem reports are above their usual level, counted in 15-minute windows over the last 24 hours. If that looks calm, check the official status page for deploy or build issues, then test your site in an incognito window on another connection because cache or DNS often breaks for you alone. Clear cache and retry.

Why does my deploy fail or stay stuck on building?

You pushed code but the deploy hangs on building or drops with a failed build message in the log. Open the deploy log in your dashboard and read the first red error since wrong Node version or failed dependency install stops it before it publishes. Fix that line first.

My site shows Page Not Found after deploy, how do I fix the publish settings?

Your build shows published yet the URL shows that blank Page Not Found message with a broken link tip. You lack an index.html at the root or your publish directory points to the wrong folder, so add the file or correct the setting in site settings under build and deploy. Push and test again.

How do I fix custom domain certificate and DNS errors?

Custom domains fail when your Netlify address works yet the browser flags a certificate warning or DNS error. You pointed the DNS to the servers yet propagation or a missing SSL certificate blocks secure load, so verify the DNS records in your registrar match the values shown in domain settings and wait for TLS to issue. Wait then reload it.

What should I check when Forms or serverless Functions stop working after deploy?

Forms break when you test your contact form but you see zero submissions, or your function path returns a missing page after deploy. You missed the data attribute on the form or you placed functions outside the folder set in site settings, so check the help centre docs for Forms setup and Functions path and redeploy with the fix. Retest in private mode.

For your site

Put the Netlify status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

HTML

<a href="https://isitdownrightnow.app/services/netlify/"><img src="https://isitdownrightnow.app/badge/netlify.svg" alt="Netlify status" height="20"></a>

Markdown, for README files

[![Netlify status](https://isitdownrightnow.app/badge/netlify.svg)](https://isitdownrightnow.app/services/netlify/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Netlify

The status on this page comes from user-submitted problem reports for Netlify, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Netlify, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Netlify's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.