Is npm (npm Registry) down?
Partially degradedchecked 3 minutes ago
npm (npm Registry) is answering our probes, but running at least 5.1x its 7-day median from Southeast Asia. The rest of the regions we check answered at their usual speed.
As of Sep 23, 2026, 9:07 AM UTC, npm (npm Registry) answered RealUptime's probes in all 10 regions that returned a reading.
No outage recorded in the 46 days we have measured npm (npm Registry) (since Aug 8, 2026).
npm (npm Registry) reports: All systems operational (“All Systems Operational”)
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
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.
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 224msstatus code: 200checked: Sep 23, 2026, 9:05 AM UTC0 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-WestOperationallatency: 427msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC0 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-CentralOperationallatency: 169msstatus code: 200checked: Sep 23, 2026, 9:04 AM UTC0 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.
- CanadaOperationallatency: 38msstatus code: 200checked: Sep 23, 2026, 9:05 AM UTC0 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 AmericaOperationallatency: 374msstatus code: 200checked: Sep 23, 2026, 9:06 AM UTC0 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.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 481msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC0 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.
- UKOperationallatency: 159msstatus code: 200checked: Sep 23, 2026, 9:04 AM UTC0 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 PacificDegradedAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 631msstatus code: 200checked: Sep 23, 2026, 9:07 AM UTC0 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 AsiaDegradedlatency: 1048msstatus code: 200checked: Sep 23, 2026, 8:51 AM UTC0 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.
- AustraliaOperationallatency: 495msstatus code: 200checked: Sep 23, 2026, 9:04 AM UTC0 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
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 serversTell me when this goes down
Get told when we measure this
We will tell you when our probes stop reaching npm (npm Registry), and again when they can reach it again. That is our own measurement from ten regions, not npm (npm Registry)'s status page. No account, no card.
Put this badge in your README
Live, from this page's own readings.[](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
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.