Question 1

Is npm down right now?

Accepted Answer

No — npm is not down. All npm systems are reported operational. Checked at 2026-09-23T17:23:27.474Z.

Question 2

What is npm's status right now?

Accepted Answer

npm is reporting "All Systems Operational" on its official status page — Operational — as of 2026-09-23T17:23:27.474Z. That status feed answered isuptime's last check in 945 ms. isuptime reads this from npm's own published feed and does not test npm independently.

Question 3

When did npm last go down?

Accepted Answer

The most recent incident npm published was "Package Publish Degradation", opened 2026-09-15T17:20:05.454Z and marked resolved 2026-09-15T18:19:35.922Z. This is the latest entry in npm's own incident feed, not every problem users experienced.

Question 4

What is npm's uptime?

Accepted Answer

isuptime does not measure npm's uptime directly — it reads npm's own published status feed. Over the last 30 days, npm's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.

Question 5

Is it just me, or is npm down for everyone?

Accepted Answer

npm reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.

Question 6

npm says operational but it is not working for me — why?

Accepted Answer

A failing install is usually local. Try a different registry mirror or clear the cache with `npm cache clean --force`. Corporate proxies and self-signed certificates produce SSL errors that look like registry failures. `ETARGET` and `ERESOLVE` are dependency-resolution problems in your own tree, and a 404 on a private package is authentication, not an outage.

Question 7

What does npm's status page actually cover?

Accepted Answer

npm's status page separates package downloads from publishing, search and the website. Downloads are the component that matters: publishing can be broken all day without anyone's CI noticing, whereas a downloads incident stops builds worldwide within minutes.

Question 8

What can I use instead of npm while it is down?

Accepted Answer

GitHub (operational). Each state was read from that provider's own status feed at 2026-09-23T17:23:27.474Z, in the same round as npm's, so the readings are comparable in time. Check the substitute is up before moving work to it.

Question 9

Is anything else down right now, or is it just npm?

Accepted Answer

As of 2026-09-23T17:23:27.474Z, 9 other services isuptime tracks were also reporting a problem: Cloudflare (Minor Service Outage); Twilio (Partially Degraded Service); Supabase (Partially Degraded Service); Elastic (Partial System Outage); Cursor (Partially Degraded Service); Scaleway (Partially Degraded Service); Snowflake (Partially Degraded Service); Salesforce (Degraded Performance: 1 active incident); PlayStation Network (PlayStation Store affected in Russia). All are checked on one schedule, so the timing is directly comparable — but overlapping in time does not establish a shared cause.

Is npm down?

Is npm down for you right now?

What npm is

What npm's status feed covers

npm uptime, last 30 days

Other services reporting problems right now

npm response time trend

npm outage history

npm status — frequently asked

npm says operational but it is not working for me

Alternatives to npm

If npm goes down

Other Developer Tools services