Is npm down?
Loading the latest status…
Is npm down right now? Live status from npm’s status page, our own checks and user reports, updated every minute.
- Official status
- Reachable
- Reports in the last hour
Detailed data for this service is briefly unavailable. The status above comes from our latest check.
npm’s status page
- www.npmjs.com website
- Package installation
- Package publishing
- Package search
- Security Audit
- Replication Feed
Not working for me
Pick what’s broken. Your report shows up on the chart below within a few minutes.
Last 24 hours
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (registry.npmjs.org)
By region
| Region | npm registry registry.npmjs.org |
|---|---|
| N. Virginia | |
| Oregon | |
| Frankfurt | |
| Singapore | |
| Tokyo | |
| São Paulo |
Each row shows the latest result from that region. How we check
Last 90 days
We have checked npm ourselves since Oct 28, 2026. Earlier days come from its status page.
8 days with problems in the last 90 days.
Recent incidents
Incidents: 5 in the last 30 days and 10 in the last 90, lasting a median of 1 h 44 min.
- Minor issues impacting package publishDegraded37 min
- View package and auth outage on npmjs.comPartial outage35 min
- Degraded Publish, Install, and View PackageDegraded5 h 16 min
- Degraded Package Install and PublishingPartial outage1 h 50 min
- Issues with login and viewing packagesDegraded2 h 15 min
- Issues with npm package publish and private installDegraded5 h 57 min
- Package Publish DegradationDegraded59 min
- Publishing Packages Degraded PerformanceDegraded21 min
- npm audits endpoint is having issuesDegraded2 h 19 min
- Intermittent Failures Impacting npm PublishDegraded1 h 39 min
If npm isn’t working for you
npm is the package registry and command-line tool for JavaScript, run by GitHub, that hosts millions of open-source packages.
Common npm errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
npm http 500 https://registry.npmjs.org/... | The registry returned a server error or a not found for a package that exists, which npm's docs call most likely a temporary registry glitch. | An outage | Check npm's status page and try again later. Source |
npm ERR! Error: 404 Not Found | The package or tarball could not be found; for an existing package during an incident this is a registry glitch, otherwise check the name. | Your side | Check the package name and version; if it exists, retry later. Source |
No compatible version found | Your npm is outdated. | Your side | Update to the latest stable npm. Source |
npm ERR! Error: ENOSPC, write | The drive you are installing to has no space or no write permission. | Your side | Free disk space or point npm's tmp folder somewhere with more space. Source |
SSL Error | npm is talking SSL to an unencrypted endpoint, usually because of a proxy configuration error. | Your side | Fix your proxy settings or registry URL. Source |
Is it just you?
- Run npm ping to check whether the registry answers from your machine.
- Try npm view <package> for a popular package; if it works, the problem is your package name, auth or cache.
- Check whether your project uses a private registry or proxy in .npmrc; that may be what is failing.
- Clear the cache with npm cache clean --force for random errors.
- Check status.npmjs.org for registry incidents.
Alternatives to npm
Questions
npm posts registry incidents at status.npmjs.org. If installs fail with 500 errors for packages that exist, npm's own docs say it is most likely a temporary registry glitch.
Usually the package name or version is wrong, or it is private and you are not logged in. If a known public package returns 404, the registry may be having problems.
Sources: docs.npmjs.com, status.npmjs.org
Get alerted when npm breaks your app.
If your product depends on npm, your users feel its outages too. Point a Site Qwality monitor at the npm endpoint you use and at your own site, and we alert you on Slack, email, SMS or a webhook as soon as either one stops answering.