Is npm (npm Registry) down right now?

Operational. We reached npm (npm Registry) from all 10 regions we check.

How does RealUptime check if npm (npm Registry) is down?

RealUptime checks npm (npm Registry) with scheduled HTTP probes against its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra confirmation probe whenever a signal suggests a problem. This verifies that the functional endpoints we probe actually answer, not that every feature of npm (npm Registry) works end to end.

What does "degraded" mean for npm (npm Registry)?

Degraded means npm (npm Registry) answered our probe but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that is down, or one that refused our probe, is reported as down or awaiting data instead, never softened into "degraded".

What is npm (npm Registry)'s current response time?

RealUptime's most recent measured response time for npm (npm Registry), by region: US-East: 299 ms, US-West: 442 ms, Europe: 264 ms, Asia-Pacific: 311 ms, US-Central: 686 ms, Canada: 304 ms, UK: 396 ms, Southeast Asia: 140 ms, Australia: 144 ms, South America: 262 ms. This is the latest single probe reading per region, not an average.

When did RealUptime last check npm (npm Registry)?

RealUptime's probes last checked npm (npm Registry) at 2026-10-05T20:15:20.095Z.

Is npm (npm Registry) down?

Short linkrlup.io/down/npm

I'm having a problem

Operationalchecked 2 minutes ago

We reached npm (npm Registry) from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, npm (npm Registry) answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured npm (npm Registry) (since Aug 8, 2026).

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC

US-East299 msOperational

US-West442 msOperational

Europe264 msOperational

Asia-Pacific311 msOperational

US-Central686 msOperational

Canada304 msOperational

UK396 msOperational

Southeast Asia140 msOperational

Australia144 msOperational

South America262 msOperational

their status pagetheir claim, not our reading

npm (npm Registry) reports: All systems operational (“All Systems Operational”)

from npm (npm Registry)'s own status page, checked Oct 5, 2026, 7:58 PM UTC

Our probes and npm (npm Registry)'s own status page agree: both show npm (npm Registry) as reachable right now.

npm (npm Registry)'s own component breakdown, as they publish it

www.npmjs.com websiteOperational
Package installationOperational
Package publishingOperational
Package searchOperational
Security AuditOperational
Replication FeedOperational

These are npm (npm Registry)'s components, named and scored by npm (npm Registry). We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is npm (npm Registry)'s own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

npm (npm Registry) response time, by region

US-East

437msp95 · latest

1s500ms0ms

Sep 6Sep 20Oct 5

US-West

326msp95 · latest

1s500ms0ms

Sep 6Sep 20Oct 5

Europe

500msp95 · latest

1s500ms0ms

Sep 6Sep 20Oct 5

Asia-Pacific

612msp95 · latest

1s500ms0ms

Sep 6Sep 20Oct 5

US-Central

735msp95 · latest

2s1s0ms

Sep 6Sep 20Oct 5

Canada

474msp95 · latest

1s500ms0ms

Sep 6Sep 20Oct 5

442msp95 · latest

500ms250ms0ms

Sep 6Sep 20Oct 5

Southeast Asia

481msp95 · latest

2s1s0ms

Sep 6Sep 20Oct 5

Australia

413msp95 · latest

2s1s0ms

Sep 6Sep 20Oct 5

South America

526msp95 · latest

1s500ms0ms

Sep 6Sep 20Oct 5

Is it npm (npm Registry), or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not npm (npm Registry) -- it cannot diagnose npm (npm Registry)'s own systems.

Get an email when we see npm (npm Registry) go down, and when it is back

What we measured, and what people reported

North America
OperationalUS-East, US-West, US-Central, Canada
- US-East
  Operationallatency: 299msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach npm (npm Registry) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-West
  Operationallatency: 442msstatus code: 200checked: Oct 5, 2026, 8:13 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach npm (npm Registry) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-Central
  Operationallatency: 686msstatus code: 200checked: Oct 5, 2026, 8:04 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach npm (npm Registry) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- Canada
  Operationallatency: 304msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach npm (npm Registry) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
South America
Operationallatency: 262msstatus code: 200checked: Oct 5, 2026, 8:05 PM UTC
0 people in the last 5 minutesNot enough reports to sayOur South America probes reach npm (npm Registry) normally. We do not have enough reports from South America to say anything about what people there are seeing.
Europe
OperationalEurope, UK
- Europe
  Operationallatency: 264msstatus code: 200checked: Oct 5, 2026, 8:13 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach npm (npm Registry) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UK
  Operationallatency: 396msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur UK probes reach npm (npm Registry) normally. We do not have enough reports from UK to say anything about what people there are seeing.
Asia Pacific
OperationalAsia-Pacific, Southeast Asia, Australia
- Asia-Pacific
  Operationallatency: 311msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach npm (npm Registry) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast Asia
  Operationallatency: 140msstatus code: 200checked: Oct 5, 2026, 8:05 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach npm (npm Registry) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- Australia
  Operationallatency: 144msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
  0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach npm (npm Registry) normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using npm (npm Registry), counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for npm (npm Registry) yet, which is not evidence that nothing is wrong.

Recent outages

Issues with npm package publish and private install, 5h 57mdeclared on their status page2026-09-27

Package Publish Degradation, 1hdeclared on their status page2026-09-15

Publishing Packages Degraded Performance, 22mdeclared on their status page2026-09-15

npm audits endpoint is having issues, 2h 20mdeclared on their status page2026-09-04

Intermittent Failures Impacting npm Publish, 1h 39mdeclared on their status page2026-09-03

intermittent Publish Failures, 4h 24mdeclared on their status page2026-07-30

Publish and Install failures, 31mdeclared on their status page2026-07-24

intermittent Publish and Install Failures, 3h 43mdeclared on their status page2026-07-23

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring npm (npm Registry) since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for npm (npm Registry) covering any window you pick, with our measurements and npm (npm Registry)'s own claim at the time, side by side.

Full availability history for npm (npm Registry): 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

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

Put this badge in your README

npm (npm Registry) uptime measured by RealUptime

Live, from this page's own readings.

[![npm (npm Registry) uptime measured by RealUptime](https://realuptime.io/outages/npm/badge.svg?days=30)](https://realuptime.io/outages/npm)

<a href="https://realuptime.io/outages/npm"><img src="https://realuptime.io/outages/npm/badge.svg?days=30" alt="npm (npm Registry) uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What npm (npm Registry)'s SLA implies, from our measurement

Window

What you pay per month

Uptime target in your contract

Include outages only one region saw (none)

At or above your target

We measured none of downtime for npm (npm Registry) over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from npm (npm Registry)'s SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional

https://registry.npmjs.org/npm

secondaryfunctional

https://registry.npmjs.org/

RealUptime is not affiliated with npm (npm Registry); the name identifies what we measured, and nothing here speaks for npm (npm Registry)'s own team. We send a single web request to npm (npm Registry) from 10 regions on our own schedule and time the response. We do not see inside npm (npm Registry)'s systems, do not use an account or real transaction, and are not the same signal npm (npm Registry)'s own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for npm (npm Registry) is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.

Related services

AWS (Amazon Web Services)Akamai Amplitude Anthropic Auth0