StatOSS

Netlify uptime

Netlify, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

api.netlify.com/api/v1/sitesEvery 5 minutes

Netlify is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:53 UTC from Singapore: 401 in 1,219 ms.

Last 24 hours

Up for 51 d 10 h100% passed

287 checks, median 471 ms from Falkenstein, all passed

95% under 485 ms

Response time by region
EuropeEurope471 ms
N. AmericaNorth America253 ms
AsiaAsia1,209 ms
OceaniaOceania1,111 ms

Medians over this range, on one scale up to 1,500 ms.

Last 90 days

Up for 51 d 10 h99.97% passed

14,805 checks, median 475 ms from Falkenstein, 3 timeouts

95% under 631 ms

Response time by region
EuropeEurope475 ms
N. AmericaNorth America262 ms
AsiaAsia1,184 ms
OceaniaOceania1,049 ms

Medians over this range, on one scale up to 1,500 ms. Europe's places are scaled to Falkenstein, its fastest shared place.

Failures older than 15 days show on the bars only.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:56 UTC.

In the last 30 days Netlify passed 8,863 of 8,863 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,014 of 2,0140
30 days100%8,863 of 8,8630
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany474 ms513 ms485 ms420
Helsinki, Finland509 ms624 ms527 ms43
Ashburn, USA254 ms363 ms253 ms504
Copenhagen, Denmark451 ms470 ms453 ms42
Singapore1,212 ms1,528 ms1,241 ms504
Sydney, Australia1,058 ms1,298 ms1,065 ms502

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Hosting for static sites and front ends, with builds, functions and forms.

StatOSS sends GET https://api.netlify.com/api/v1/sites and counts the check as passed on status 401 within 10 seconds. The REST API's list of sites, which the CLI and deploys use. Without a token it answers 401.

It checks Netlify's API, not the sites Netlify serves from its CDN or the builds.

Netlify reports its own incidents at www.netlifystatus.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 401.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.