npm status
Is npm down?
Couldn’t reach the npm status page
The status page didn’t answer in time (checked at 01:09 UTC). That can mean a wider outage or just a slow response; open the official page directly. Official npm status page ↗
Recent incidents
See past incidents on the official npm status page.
What to do if npm is down
- Install from your lockfile and cache with `npm ci --prefer-offline`; packages you already downloaded don’t need the registry.
- Git is distributed: keep committing locally and push when the service is back.
- Use your lockfile and local cache for installs, and avoid deleting caches or node_modules during an outage.
- Pin CI to cached dependencies or a mirror so builds don’t all fail on the same registry.
FAQ
Is npm down right now?+
The official status page didn’t answer when this page was last built. The status box at the top re-checks while you have it open, or open https://status.npmjs.org directly.
Where is the official npm status page?+
https://status.npmjs.org. It’s run by npm itself and lists each component, open incidents and past incidents (it also covers npm registry). DevHunt reads its public status API; nothing here is added or guessed.
npm isn’t working for me, but the status page says it’s up. Why?+
Status pages update a few minutes after a problem starts, and small or regional issues sometimes never show up. Check your own network, VPN and API keys, try another browser or region, and look at the components list: one feature can fail while the rest works.
Does DevHunt collect outage reports from users?+
No. This page only shows what npm’s official status page says, with the time it was checked. It does not count user reports, so it can lag behind an outage that npm hasn’t acknowledged yet.
More status pages: Is GitHub down? · Is GitLab down? · Is Bitbucket down? · Is Docker Hub down? · all 66 dev tools