npm registry uptime
npm registry, 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.
npm registry is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:37 UTC from Ashburn, USA: 200 in 149 ms.
Last 24 hours
Up for 6 d 3 h100% passed
288 checks, median 204 ms from Copenhagen, all passed
95% under 234 ms
Response time by region
Medians over this range, on one scale up to 300 ms. Europe's places are scaled to Copenhagen, its fastest shared place.
Last 90 days
Up for 6 d 3 h100% passed
1,764 checks, median 201 ms from Copenhagen, all passed
95% under 233 ms
Response time by region
Medians over this range, on one scale up to 300 ms. Europe's places are scaled to Copenhagen, its fastest shared place.
In the last 24 hours npm registry passed 288 of 288 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 | 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 | 211 ms | 242 ms | 215 ms | 192 |
| Ashburn, USA | 115 ms | 203 ms | 137 ms | 563 |
| Copenhagen, Denmark | 204 ms | 245 ms | 211 ms | 170 |
| Singapore | 216 ms | 295 ms | 227 ms | 561 |
| Sydney, Australia | 179 ms | 211 ms | 185 ms | 83 |
| Aarhus, Denmark | 208 ms | 254 ms | 218 ms | 195 |
Outages
None detected since checks began on 30 Sep 2026.
What is checked
The public registry behind npm, pnpm, Yarn and Bun installs: package metadata and tarballs for JavaScript and TypeScript.
StatOSS sends GET https://registry.npmjs.org/-/ping and counts the check as passed on status 200 within 10 seconds. The registry's own health endpoint, the one `npm ping` calls. It answers 200 with an empty JSON object.
Package tarballs and npmjs.com, the website, are not checked; either can fail while the ping answers. So can publishing.
npm registry reports its own incidents at status.npmjs.org. 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 200.
- 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.