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.
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
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
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.
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.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | 100% | 2,014 of 2,014 | 0 |
| 30 days | 100% | 8,863 of 8,863 | 0 |
| 90 days | Not 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.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 474 ms | 513 ms | 485 ms | 420 |
| Helsinki, Finland | 509 ms | 624 ms | 527 ms | 43 |
| Ashburn, USA | 254 ms | 363 ms | 253 ms | 504 |
| Copenhagen, Denmark | 451 ms | 470 ms | 453 ms | 42 |
| Singapore | 1,212 ms | 1,528 ms | 1,241 ms | 504 |
| Sydney, Australia | 1,058 ms | 1,298 ms | 1,065 ms | 502 |
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.