Is npm down?

What works right now

• ●UpRegistry pingYes: registry.npmjs.org answers.200 in 224 ms
• ●UpPackage metadataYes: npm can resolve a real package.200 in 179 ms

Failing for you? Check whether it is you

1. Is it you?

   Check which registry you are using and whether npm can reach it.

   npm config get registry
   npm ping

   Copy

What to do while npm is down

When npm is down, npm install cannot fetch packages you do not have cached, and publishing may fail. Anything already in your npm cache installs offline.

1. Install from your cache

   --prefer-offline uses cached tarballs and only goes to the network for misses; --offline never touches the network.

   npm ci --prefer-offline
   # pnpm
   pnpm install --offline

   Copy

2. Use a mirror for now

   npm swaps the registry host in your lockfile's URLs for the one you configure, and still checks every tarball against the lockfile's integrity hash. Switch back afterwards.

   npm ci --registry=https://registry.npmmirror.com
   # afterwards
   npm config delete registry

   Copy

3. Publishing is a separate system

   If only "Package publishing" is down on the official page, installs work; wait before npm publish.

Last 24 hours

Last 30 days

Incident timeline

Outages our checks saw, and incidents from the official status page, newest first.

1. OfficialOct 22, 6:43 UTC · 5.3 hDegraded Publish, Install, and View Package

   This incident has been resolved.

2. OfficialOct 22, 2:33 UTC · 1.8 hDegraded Package Install and Publishing

   This incident has been resolved.

3. OfficialOct 14, 9:29 UTC · 2.3 hIssues with login and viewing packages

   This incident has been resolved.

4. OfficialSep 27, 0:50 UTC · 6 hIssues with npm package publish and private install

   This incident has been resolved.

5. OfficialSep 15, 17:20 UTC · 60 minPackage Publish Degradation

   This incident has been resolved.

6. OfficialSep 15, 16:13 UTC · 22 minPublishing Packages Degraded Performance

   This incident has been resolved.

7. OfficialSep 3, 21:42 UTC · 1.7 hIntermittent Failures Impacting npm Publish

   This incident has been resolved.

8. OfficialJul 30, 12:06 UTC · 4.4 hintermittent Publish Failures

   This incident has been resolved.

9. OfficialJul 24, 11:08 UTC · 31 minPublish and Install failures

   This incident has been resolved.

10. OfficialJul 23, 16:09 UTC · 3.7 hintermittent Publish and Install Failures

    This incident has been resolved.

Official status

The official page: https://status.npmjs.org/.

Get alerts, or show it in your README

Follow the RSS feed of npm incidents in any reader, or paste this badge into a README; it updates itself.

[![npm status](https://tensorust-status.vercel.app/api/badge?id=npm)](https://tensorust.com/status/npm/)

How we check npm

Every 5 minutes, from Washington, D.C., with no API key. A failed check is retried once after 2 seconds before it counts; npm is down when every critical check fails, and degraded when some do or the official page reports a problem.

• https://registry.npmjs.org/-/ping: The registry npm install talks to.
• https://registry.npmjs.org/react/latest: Resolving a real package.

Other services