Is Netlify down right now?

Netlify reports no incident on its status page. Our regional reading: Checks passing. Our checks of Netlify pass from all 10 regions we check.

How does RealUptime check Netlify?

RealUptime checks Netlify with scheduled HTTP requests to its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra check whenever a signal suggests a problem. A passing check shows that the functional endpoints we check answered our request, not that every feature of Netlify works for users.

What does "degraded" mean for Netlify?

Degraded means Netlify answered our check but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that fails our check, or one that refused it, is shown as a failed check or as awaiting data instead, never softened into "degraded".

What is Netlify's current response time?

RealUptime's most recent response time for Netlify, by region: US-East: 314 ms, US-West: 307 ms, Europe: 436 ms, Asia-Pacific: 1327 ms, US-Central: 217 ms, Canada: 1177 ms, UK: 415 ms, Southeast Asia: 2522 ms, Australia: 1969 ms, South America: 733 ms. This is the latest single check reading per region, not an average.

Has Netlify had a recent outage?

Netlify's last published incident: "Elevated Build Errors", Oct 17, 2026, 52 min.

When did RealUptime last check Netlify?

RealUptime's checks last ran against Netlify at 2026-10-19T20:46:53.323Z.

Is Netlify down?

Short linkrlup.io/down/netlify

I'm having a problem

Vendor reports no incidentWhat Netlify reports

Netlify reports no incident on its status page.

As of the last successful poll, 2026-10-19 20:46 UTC.

Netlify's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 8 minutes ago

Our checks of Netlify pass from all 10 regions we check.

As of Oct 19, 2026, 8:46 PM UTC, RealUptime's checks of Netlify passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 19, 2026, 8:46 PM UTC

US-East314 msChecks passing

US-West307 msChecks passing

Europe436 msChecks passing

Asia-Pacific1327 msChecks passing

US-Central217 msChecks passing

Canada1177 msChecks passing

UK415 msChecks passing

Southeast Asia2522 msChecks passing

Australia1969 msChecks passing

South America733 msChecks passing

their status pagetheir claim, not our reading

Netlify reports: All systems operational (“All Systems Operational”)

from Netlify's own status page, checked Oct 19, 2026, 8:23 PM UTC

Netlify's own component breakdown, as they publish it

Atlassian Bitbucket APIOperational
High-Performance Edge NetworkOperational
Atlassian Bitbucket WebhooksOperational
Standard Edge NetworkOperational
Atlassian Bitbucket SSHOperational
Origin ServersOperational
Build PipelineOperational
npm, Inc. Registry ReadsOperational
GitHub API RequestsOperational
Netlify Application UIOperational
APIOperational
GitHub WebhooksOperational
GitHub Git OperationsOperational
Hosted DNSOperational
NS1 APIOperational
PrerenderingOperational
IdentityOperational
NS1 Management PortalOperational
Name.comOperational
Netlify FunctionsOperational
AnalyticsOperational
Log DrainsOperational
Collaborative Deploy PreviewsOperational
Git GatewayOperational
Edge FunctionsOperational
Netlify Image CDNOperational
Netlify BlobsOperational
Netlify ObservabilityOperational
Netlify ConnectOperational
Netlify Create APIOperational
Visual EditorOperational
Netlify FormsOperational
Netlify Support ForumsOperational
Netlify HelpdeskOperational
Domain PurchasingOperational
BillingOperational
Agent RunnersOperational
AI GatewayOperational
Live TunnelOperational
Netlify DatabaseOperational

These are Netlify's components, named and scored by Netlify. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Netlify's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Netlify response time, by region

US-East

1.6sp95 · latest

2s1s0ms

Sep 20Oct 4Oct 19

US-West

1.2sp95 · latest

2.5s1.3s0ms

Sep 20Oct 4Oct 19

Europe

1.2sp95 · latest

2s1s0ms

Sep 20Oct 4Oct 19

Asia-Pacific

2.3sp95 · latest

5s2.5s0ms

Sep 20Oct 4Oct 19

US-Central

1.2sp95 · latest

2s1s0ms

Sep 20Oct 4Oct 19

Canada

1.6sp95 · latest

2s1s0ms

Sep 20Oct 4Oct 19

912msp95 · latest

2s1s0ms

Sep 20Oct 4Oct 19

Southeast Asia

2.5sp95 · latest

5s2.5s0ms

Sep 20Oct 4Oct 19

Australia

2.4sp95 · latest

2.5s1.3s0ms

Sep 20Oct 4Oct 19

South America

2.3sp95 · latest

2.5s1.3s0ms

Sep 20Oct 4Oct 19

Why some readings show as awaiting data. 1 of 20 readings for Netlify came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Netlify's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Netlify

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Netlify. It cannot diagnose Netlify's own systems.

Email me when Netlify reports an incident on its status page, and again when it reports it resolved.

What our checks show, and what people reported

North America
Checks passingUS-East, US-West, US-Central, Canada
- US-East
  Checks passinglatency: 314msstatus code: 401checked: Oct 19, 2026, 8:46 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Netlify normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-West
  Checks passinglatency: 307msstatus code: 401checked: Oct 19, 2026, 8:46 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Netlify normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-Central
  Checks passinglatency: 217msstatus code: 401checked: Oct 19, 2026, 8:36 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Netlify normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- Canada
  Checks passinglatency: 1177msstatus code: 401checked: Oct 19, 2026, 8:36 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Netlify normally. We do not have enough reports from Canada to say anything about what people there are seeing.
South America
Checks passinglatency: 733msstatus code: 401checked: Oct 19, 2026, 8:36 PM UTC
0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Netlify normally. We do not have enough reports from South America to say anything about what people there are seeing.
Europe
Checks passingEurope, UK
- Europe
  Checks passinglatency: 436msstatus code: 401checked: Oct 19, 2026, 8:46 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Netlify normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UK
  Checks passinglatency: 415msstatus code: 401checked: Oct 19, 2026, 8:36 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Netlify normally. We do not have enough reports from UK to say anything about what people there are seeing.
Asia Pacific
Checks passingAsia-Pacific, Southeast Asia, Australia
- Asia-Pacific
  Checks passinglatency: 1327msstatus code: 401checked: Oct 19, 2026, 8:46 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Netlify normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast Asia
  Checks passinglatency: 2522msstatus code: 401checked: Oct 19, 2026, 8:36 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Netlify normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- Australia
  Checks passinglatency: 1969msstatus code: 401checked: Oct 19, 2026, 8:41 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Netlify normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Netlify, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Netlify yet, which is not evidence that nothing is wrong.

Recent probe events

Elevated Build Errors, 52mdeclared on their status page2026-10-17

Elevated Edge Function Errors, 1mdeclared on their status page2026-10-08

Elevated error rates for AI Gateway, 1mdeclared on their status page2026-10-06

Error accessing Netlify-hosted sites, 50mdeclared on their status page2026-10-05

Error accessing Netlify-hosted sites, 1mdeclared on their status page2026-09-29

Error accessing Netlify-hosted sites, 24mdeclared on their status page2026-09-24

Elevated CDN Errors, 34mdeclared on their status page2026-09-23

Errors accessing Netlify-hosted sites, 1h 25mdeclared on their status page2026-09-21

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Netlify since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Netlify covering any window you pick, with our check readings and Netlify's own claim at the time, side by side.

Full check history for Netlify: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Live, from this page's own readings.

[![Netlify uptime by RealUptime's checks](https://realuptime.io/outages/netlify/badge.svg?days=30)](https://realuptime.io/outages/netlify)

<a href="https://realuptime.io/outages/netlify"><img src="https://realuptime.io/outages/netlify/badge.svg?days=30" alt="Netlify uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Netlify down?", https://realuptime.io/outages/netlify. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional

https://api.netlify.com/api/v1/user

secondary

https://www.netlifystatus.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.netlify.com

RealUptime is not affiliated with Netlify; the name identifies what we checked, and nothing here speaks for Netlify's own team. We send a single web request to Netlify from 10 regions on our own schedule and time the response. We do not see inside Netlify's systems, do not use an account or real transaction, and are not the same signal Netlify's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Netlify is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.

Related services

AWS (Amazon Web Services)Akamai Amplitude Anthropic Auth0