Netlify uptime
Netlify, checked by StatOSS every 5 minutes from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Measured from outside, with every outage dated in UTC.
Netlify is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:37 UTC from Sydney, Australia: 401 in 851 ms.
Last 24 hours
Up for 6 d 3 h99.65% passed
288 checks, median 466 ms from Falkenstein, 1 timeout
95% under 524 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.
- Timed out, from Sydney, Australia5 min, 1 check
Last 90 days
Up for 6 d 3 h99.88% passed
1,764 checks, median 462 ms from Falkenstein, 2 timeouts
95% under 550 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.
In the last 24 hours Netlify passed 287 of 288 checks, 99.65%.
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 | 99.65% | 287 of 288 | 0 |
| 7 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 30 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 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 | 466 ms | 626 ms | 485 ms | 198 |
| Ashburn, USA | 264 ms | 382 ms | 276 ms | 559 |
| Copenhagen, Denmark | 477 ms | 518 ms | 482 ms | 170 |
| Singapore | 1,186 ms | 1,401 ms | 1,208 ms | 557 |
| Sydney, Australia | 1,059 ms | 1,489 ms | 1,164 ms | 83 |
| Aarhus, Denmark | 523 ms | 628 ms | 541 ms | 195 |
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: Aarhus and Copenhagen in Denmark, Falkenstein in Germany, 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.