Issues with login and viewing packages
DegradedThis incident has been resolved.
Is npm down?
npm is up and running. npm is the registry JavaScript packages are published to and installed from.
Last 90 days
99.49%
Estimated uptime
Estimated uptime
90 days agoToday
Worked out from the incidents npm reported, so it is an estimate and not a measurement.
npm reliability, last 90 days
9Incidents reported
0Full outages
2 h 15 minTypical duration
5 h 57 minLongest incident
Last incident: “Issues with login and viewing packages”, 3 days ago.
Components
www.npmjs.com websiteOperational
Package installationOperational
Package publishingOperational
Package searchOperational
Security AuditOperational
Replication FeedOperational
Recent incidents
Issues with npm package publish and private install
DegradedThis incident has been resolved.
Package Publish Degradation
DegradedThis incident has been resolved.
Publishing Packages Degraded Performance
DegradedThis incident has been resolved.
npm audits endpoint is having issues
DegradedThis incident has been resolved.
Questions
Is npm down right now?
npm’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
When was npm last down?
The most recent incident npm reported was “Issues with login and viewing packages”, 3 days ago (2026-10-14 09:29 UTC). None of its incidents in the last 90 days were a full outage.
Which parts of npm are tracked here?
npm reports 6 components on its status page, including www.npmjs.com website, Package installation, Package publishing, Package search, Security Audit. Each is checked again whenever this page refreshes.
What should I do if npm is down?
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
npm install fails but npmjs.com loads?
Package installation (the registry) and the website are separate components. The registry can fail while the site is fine, and yarn/pnpm hit the same registry — switching the client won't help.
npm publish fails while installs still work?
Publishing is its own component ('Package publishing'). Check that row — it can fail independently of installation.
How do I tell if npm is down for everyone or only for me?
If the status above is operational but npm still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
How can I get alerted when my own site goes down?
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.