Is npm down?

NO · npm is up

checked 19:00 UTC …[official ↗][post on x]

90 days ok7d 100% · 30d 100% · 90d 100%

components6

  • www.npmjs.com websiteok
  • Package installationok
  • Package publishingok
  • Package searchok
  • Security Auditok
  • Replication Feedok

incident historylast 10

› 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.

embed thisREADME, docs or internal wiki

npm status
[![npm status](https://devhunt.org/api/status/npm/badge)](https://devhunt.org/status/npm)

more

is github down?is gitlab down?is bitbucket down?is docker hub down?is pypi down?is rubygems.org down?is snyk down?all 92 tools →

FAQ

Is npm down right now?+

When this page was last built (19:00 UTC on Nov 16, 2026), npm’s official status page reported: "All Systems Operational". The status box at the top of this page re-checks every few minutes while you have it open.

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.