StatOSS

npm registry uptime

npm registry, 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.

registry.npmjs.org/-/pingEvery 5 minutes

npm registry is up.

Up for 51 d 9 h. Last checked 2026-11-20 18:08 UTC from Sydney, Australia: 200 in 176 ms.

Last 24 hours

Up for 51 d 9 h100% passed

287 checks, median 184 ms from Copenhagen, all passed

95% under 232 ms

Response time by region
EuropeEurope184 ms
N. AmericaNorth America128 ms
AsiaAsia204 ms
OceaniaOceania179 ms

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

Last 90 days

Up for 51 d 9 h100% passed

14,795 checks, median 194 ms from Copenhagen, all passed

95% under 240 ms

Response time by region
EuropeEurope194 ms
N. AmericaNorth America128 ms
AsiaAsia209 ms
OceaniaOceania178 ms

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

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:13 UTC.

In the last 30 days npm registry passed 8,854 of 8,854 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,005 of 2,0050
30 days100%8,854 of 8,8540
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, Germany208 ms289 ms338 ms42
Helsinki, Finland193 ms259 ms204 ms42
Ashburn, USA128 ms436 ms168 ms503
Copenhagen, Denmark186 ms224 ms193 ms420
Singapore205 ms269 ms213 ms504
Sydney, Australia178 ms285 ms193 ms504

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: 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 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.