Skip to content

Outage tracker / npm (npm Registry) / In the US

Is npm (npm Registry) down in the US?

Vendor reports no incidentWhat npm (npm Registry) reports

npm (npm Registry) reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:34 UTC.

npm (npm Registry)'s status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn, San Jose, and Chicago

All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked npm (npm Registry) at Nov 5, 2026, 2:34 PM UTC.

Over the last 24 hours we completed 326 checks from Ashburn, San Jose, and Chicago and 325 answered cleanly, 99.69% availability.

Of the 7 other regions we check npm (npm Registry) from, all 7 read checks passing right now.

Email me when npm (npm Registry) reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is npm (npm Registry)'s own statement from its status page, with our regional reading beside it.

What our Ashburn, San Jose, and Chicago probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing112 checks in 24h, 100.00%
ChicagoChecks passing72 checks in 24h, 98.61%

Last checked Nov 5, 2026, 2:34 PM UTC.

npm (npm Registry) from Ashburn, San Jose, and Chicago over the last 30 days

Over the last 30 days, npm (npm Registry) answered our Chicago probe in 584 ms on average, and 1 check in 20 took longer than 898 ms.

Over the last 30 days, npm (npm Registry) answered our San Jose probe in 606 ms on average, and 1 check in 20 took longer than 873 ms.

Over the last 30 days, npm (npm Registry) answered our Ashburn probe in 684 ms on average, and 1 check in 20 took longer than 997 ms.

Ranked by average response time across the 10 cities we check npm (npm Registry) from, Chicago 4th, San Jose 5th, Ashburn 7th; London was fastest at 445 ms and São Paulo slowest at 1,085 ms.

From Ashburn, San Jose, and Chicago we ran 10,542 checks of npm (npm Registry) in 30 days, and 10,537 answered cleanly: 99.95% availability.

5 of the 30 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.68% across 318 checks.

In Ashburn local time (EST), npm (npm Registry) was slowest around 8 PM, at 973 ms on average over the last 14 days, and quickest around 7 PM, at 793 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5198100.00%824 ms
Wed, Nov 432599.69%692 ms
Tue, Nov 331899.68%714 ms
Mon, Nov 2343100.00%1,008 ms
Sun, Nov 1360100.00%922 ms
Sat, Oct 31359100.00%894 ms
Fri, Oct 30359100.00%906 ms
Thu, Oct 29360100.00%934 ms
Wed, Oct 28358100.00%852 ms
Tue, Oct 27360100.00%766 ms
Mon, Oct 2636299.72%702 ms
Sun, Oct 2535999.72%932 ms
Sat, Oct 24360100.00%833 ms
Fri, Oct 23360100.00%623 ms

npm (npm Registry) outages measured from the US

Our Ashburn, San Jose, and Chicago probes measured no confirmed npm (npm Registry) outage in the last 90 days.

How the other regions read right now

Of the 7 other regions we check npm (npm Registry) from, all 7 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 99 checks
TokyoChecks passing100.00% of 60 checks
TorontoChecks passing100.00% of 72 checks
LondonChecks passing100.00% of 72 checks
SingaporeChecks passing100.00% of 71 checks
SydneyChecks passing100.00% of 71 checks
São PauloChecks passing100.00% of 72 checks

Other countries we check npm (npm Registry) from

How we measured this

The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against npm (npm Registry)'s public endpoints. They are not user reports, and they are not npm (npm Registry)'s own status page.

See npm (npm Registry)'s full check readings, the 90-day history by region, or the outage tracker methodology.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter