NPM outages and problems
In the past 24 hours, 15 user reports came in for NPM. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 5 reports, about 20 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
NPM in October 2026
- Problem reports in October (since 28 October)
- 15
Monthly report for October 2026
What people said was wrong in recent problem reports for NPM, as a share of those reports:
- 86% Website
- 14% Login
Where NPM problem reports come from
Recent reports came from 9 areas. The most came from around Greensboro, NC, Seattle, WA and Portland, OR. Share of recent reports by area, named after its biggest town:
- 13% Greensboro, NC
- 13% Seattle, WA
- 13% Portland, OR
- 13% Dallas, TX
- 7% Cleveland, OH
- 7% St. Petersburg, FL
From 15 recent problem reports. Big cities always send the most, so reports from many places point to a widespread problem, and one area far ahead of the rest can mean a regional one. Town names: GeoNames.
NPM problem spikes, last 30 days
Since 28 October, NPM had no outage spikes or periods of elevated reports.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 28 October 2026. Monthly reports for all services
How to fix NPM not working
NPM is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach npmjs.com over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not NPM.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
While NPM is down: what to use instead
- Local cache Reuse the local cache for packages you installed before; it can carry a reinstall while registry requests time out.
- Existing node_modules Keep the dependencies already in node_modules and skip a fresh install, so builds and tests keep running until you need to add or update a package.
- Official status page Check the official status page first; an incident message there saves you from chasing a config problem that is not there.
- Help centre Use the help centre for account or publish problems that remain after the registry recovers; support can proceed without a working install.
NPM IP address, servers and network
Checking npmjs.com from our server…
Service updates from @npmjs
No posts about problems from @npmjs in the last 14 days. The latest is from .
Put the NPM status badge on your site
Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.
<a href="https://isitdownrightnow.app/services/npm/"><img src="https://isitdownrightnow.app/badge/npm.svg" alt="NPM status" height="20"></a>[](https://isitdownrightnow.app/services/npm/)The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.
How we track NPM
The status on this page comes from user-submitted problem reports for NPM, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for NPM, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from NPM's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.