Skip to service list
IU
npm

Is npm down?

npm status · Developer Tools · checked (7s ago)

Also searched as npmjs, npm registry.

Operational

No — npm is not down. All npm systems are reported operational.

According to npm's official status page, npm was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, npm's feed reported no outage in 100.00% of our checks.

No outage reported (30d)
100.00%
Share of our checks where npm's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
562 ms
How long the last status check took
Reported by
Operational
All Systems Operational

Is npm down for you right now?

Everything above is read from npm's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.

Nobody has reported npm in the last 24 hours. Yours would be the first.

Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.

What npm is

npm is the registry behind the JavaScript ecosystem — the source almost every `npm install`, `yarn install` and `pnpm install` reads from, along with the website and the publishing API. It is owned by GitHub, but has its own status page and fails independently.

What npm's status feed covers

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.

isuptime reads this feed on a schedule and reports what it says — how that works, in detail.

npm uptime, last 30 days

One bar per day. Each shows the share of that day's checks where npm's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days npm was down.

2026-10-0913 of 30 days recordedToday
  • No outage reported (99%+)
  • 95–99%
  • 80–95%
  • Under 80%
  • No data

Other services reporting problems right now

9 other services isuptime tracks were also reporting a problem as of the same check, 7s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.

1 more service is reporting problems — see all →

npm response time trend

Each point is one check of npm's status endpoint.

npm outage history

npm has published 29 incidents in the last 12 months, the 20 most recent shown here. Only what npm posted itself — not every problem users hit.

npm status — frequently asked

Is npm down right now?
No — npm is not down. All npm systems are reported operational. Checked (7s ago).
What is npm's status right now?
npm is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 562 ms. isuptime reads this from npm's own published feed and does not test npm independently.
When did npm last go down?
The most recent incident npm published was “Minor issues impacting package publish”, opened Nov 7, 02:28 PM UTC (7h ago) and marked resolved Nov 7, 03:05 PM UTC. That is the latest entry in npm's own incident feed, not every problem users experienced.
What is npm's uptime?
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.
Is it just me, or is npm down for everyone?
npm reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.

npm says operational but it is not working for me

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.

Open npm's official status page

Alternatives to npm

npm is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.

If npm goes down

Status shown for each is read from that provider's own feed, on the same schedule as this page.

Other Developer Tools services

← See live status for all 102 services