Status updated
NPM down?
Npmjs.org is a domain operated by npm, the JavaScript package registry owned by GitHub. It is primarily associated with registry infrastructure, most notably registry.npmjs.org, the endpoint the npm command-line tool uses to download and publish packages. Developers worldwide rely on this service every time they install Node.js dependencies. The registry hosts millions of open source JavaScript packages, making it critical infrastructure for web and server-side development. Browsing and account management happen on the related npmjs.com website.
I have a problem with NPM
Select the type of problem you're facing to help us and other users.
Recent User Report Trends for NPM
Aggregated reports in the last 48 hours.
What is NPM's current status?
All systems are operational
No active incidents reported.
Incident history: past 7 days
times in UTCToday
Yesterday
Oct 30, 2026
Oct 29, 2026
Oct 28, 2026
Oct 27, 2026
User Reports for NPM
Recent issues reported by users from around the world.
Experiencing an issue? Add your report:
Stop refreshing this page
We'll email you the moment NPM goes down — and again when it's back.
How to fix NPM not working
npm is the package registry for JavaScript. Developers install packages from it and publish their own, using the npm command-line tool and the npmjs.com website. The registry address is registry.npmjs.org. Find your symptom below. Most problems come from the registry itself, your network or proxy, a sign-in or access token, or a package setting. Check the status page before you change your project.
Jump to what you are seeing
Registry Down
Installing or downloading packages fails for everyone.
- Try the install once more after a short wait.
- Check status.npmjs.com for an incident.
- If the status page shows an outage, wait for it to clear rather than changing your project.
Website Down
The npm website does not load for you.
- Open the page in a private window and on another network.
- Check status.npmjs.com.
- If only your network is affected, check any proxy or firewall settings.
Publishing Failed
A package will not publish.
- Read the error. An access error usually means the token or permission is wrong, and a version conflict usually means that version already exists.
- Check the version number in your package file has been raised since your last publish.
- Check you are signed in with a token that is allowed to publish this package.
Search Issues
Package search returns nothing, or it is slow.
- Try the exact package name rather than a description.
- Reload in a private window.
- If search is down but the package name works, install by name and check the status page.
API Errors
Calls to the registry or the npm API fail with an error.
- Check the status code. An access error usually means the token is wrong or has expired, too many calls means you should slow down, and a server error means a service-side problem.
- Confirm the token has not been revoked and is for the right account.
- Retry with a growing delay, and check status.npmjs.com if several calls fail together.
Slow Downloads
Packages download slowly, or they time out during an install.
- Check your network, and any proxy or VPN, since they can slow large downloads.
- Try again at a quieter time, or on another network.
- If it is slow for everyone, check the status page.
Login Issues
Signing in to the npm website or the command line fails.
- Check your username and password, and the second sign-in step if you use one.
- If a saved token has expired, create a new one and replace it in your tools.
- Check the status page for a sign-in incident.
Still not working?
If it still does not work, contact your team's npm administrator first, since they manage the organisation and its packages. For a registry-wide problem, contact npm support through the help option on npmjs.com. Have the package name, the exact error text, your organisation name, and the time it started with your time zone. Never send tokens or passwords in a support message. Live incident updates are on status.npmjs.com.
Most package problems come from a network setting, an expired token or a version number, and they usually clear once that one item is checked. The status page shows live registry incidents, so you can see whether the problem is on npm's side.
Frequently asked questions about NPM
Is NPM down right now?
No. Based on the latest status data on this page, NPM (npmjs.org) is up and running normally. The most recent incident, "View package and auth outage on npmjs.com", was resolved (last update Oct 26, 2026).
What should I do if NPM is not working for me?
First rule out your side: reload the page, try another browser or device, clear the cache and cookies for npmjs.org, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.
What was the most recent NPM incident?
The most recent incident on record is "View package and auth outage on npmjs.com", last updated on Oct 26, 2026. It has been resolved.
How do I report a problem with NPM?
Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.
Where is the official NPM status page?
The official status page for NPM is status.npmjs.com.
Advanced Domain Info Unavailable
We couldn't load advanced domain and security information for npmjs.org at this time. Please try again later.