Is npm down right now?

No. Our checks are finding no problems with npm right now. That verdict is live, and the banner at the top of this page carries it too. We re-check npm continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are API errors, can't connect, downloads failing, upload failing, search not working, no response / timing out, can't log in and 5xx error pages. Those are the options the report button offers for npm, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With npm specifically, the registry API, the tarball CDN, the search index and the npmjs.com website are separate. Installs can fail while the site loads normally, a new version takes time to reach every edge, and one bad CDN region affects some machines and not others. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For npm, run npm ping, then install a small well-known package from a different network. npm ping succeeding while one package fails points at that package or version. Everything failing on one network and working on another points at your proxy, DNS or corporate mirror. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on npm's side. Specifically: resist deleting node_modules and package-lock.json for a clean install. A clean install has to fetch every dependency from the registry that is currently failing, which turns a partial outage into a total one. An existing node_modules keeps working. Reporting it here helps other people see they are not alone.

Continuously, around the clock. npm publishes a machine-readable status feed, so our first check reads it directly and reports what npm itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.npmjs.org, and it is linked further up this page. That is npm's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to npm or npmjs.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need npm's own support, not us.