Live check
Is npm down right now?
Observed from npm’s public feed by our independent monitor. Always confirm operational decisions on the official status page.
While you wait: the npm incident checklist
- Scope registry vs publish vs site. npm's status page separates package downloads, publishing, the website, search and audit. Installs failing is a very different incident from the website or search being down — confirm which component before you touch CI.
- Lean on your cache and lockfile. npm ci with a committed lockfile plus a warm cache or an internal proxy/mirror (Verdaccio, Artifactory, GitHub Packages) rides out a registry incident. If you have no mirror, that's your first postmortem action item.
- Freeze publishes. Don't cut releases or bump versions while publishing is degraded — a half-published package or a failed dist-tag update is worse than waiting. Hold the release train until the component is green.
- Neutralize audit-driven failures. npm audit and funding checks call the registry and can fail your install step even when packages resolve. Temporarily add --no-audit --no-fund in CI so a metadata endpoint doesn't block a deploy.
- Stop the retry storm. Parallel CI jobs retrying against a degraded registry make it worse for everyone and for you. Pin a single mirror, reduce concurrency, and let queued builds wait rather than hammer.
What breaks when npm has issues
An npm incident is a supply-chain and CI outage, not a production one: fresh installs fail, Docker image builds that run npm install break, and deploys that reinstall dependencies stall — including the hotfix you need for some other fire. Publishing new packages blocks, and audit/metadata endpoints can fail installs on their own. Anything with a warm cache, a committed lockfile or an internal mirror keeps building; clean-checkout CI is what hurts.
FAQ
Is it npm or my network/registry?
Check status.npmjs.org. If it's green, look at your own registry config (.npmrc), proxy, corporate mirror or DNS — a single machine failing while npm is healthy is usually local.
Can I still deploy while npm is down?
Often yes, if your artifacts are already built or your dependencies are cached and pinned by a lockfile. Deploys that require a clean npm install from the public registry are the ones that block.
Why does CI fail only on the install step?
Because that's the step that talks to the registry. A registry or audit incident surfaces exactly there. --no-audit and a mirror often get installs through a partial incident.
Does npm being down affect packages I already installed?
No. Already-installed and cached packages keep working; running apps don't call the registry. The impact is on installing, publishing and metadata lookups, not on code that's already resolved.
Put npm’s status in your toolbar
Is it you — or your vendor? You checked once. The extension watches npm and the rest of your stack continuously — badge, popup and Side Panel, free for 5 vendors, no account.
Add to Chrome — free, no accountNot an outage? Track API changes before they become incidents.
VendorStatus shows when a dependency is failing now. Breakwater watches official developer changelogs and migration deadlines locally in your browser, so your team can plan the change before the next deploy.
Also on your stack?
Not affiliated with npm. Status data comes from their public status page.