npm works for others but not for me. What can I do?

1. Check whether it is only this device: Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service. 2. Test from the command line: Check name resolution and the route, to see where the connection stops. 3. Check your tokens and rate limits: An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down. 4. Restart the router and the device: Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service. 5. Flush the DNS cache: Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again. 6. Turn off VPN and proxy for a moment: VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set. 7. Change the DNS server: If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.

Is npm down?

Q: Is npm down right now?

Operational. Both signals agree: the official status feed and our own check.

No, npm is up right now

Both signals agree: the official status feed and our own check.

Official status

All Systems Operational

From status.npmjs.org, read 3 min ago.

Our check, from Germany

Answered in 106 ms

Request to registry.npmjs.org, 3 min ago. 258 of 288 checks in the last 24 hours succeeded, median 163 ms.

Is npm working for you?

One click, no account. It helps others see whether the problem is widespread.

We are still collecting reports. The numbers appear once 20 people have answered within 24 hours.

Response time, last 24 hours

measured from our server in Germany

Time to first responseFailed check

One request every 5 minutes from a single location (Falkenstein, Germany). It shows how the answer time changes; it is not the speed you will see on your own connection.

Works for everyone else? Fix it on your side

Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
Test from the command line. Check name resolution and the route, to see where the connection stops.
nslookup npmjs.com tracert npmjs.com
Check your tokens and rate limits. An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down.
Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
ipconfig /flushdns
Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.

Still stuck? Search our guides for npm, browse all fix guides, or describe your case.

Recent incidents

from the official feed, read 21 min ago

Issues with npm package publish and private install

ResolvedStarted Sep 27, 00:50 UTCResolved Sep 27, 06:47 UTC

Package Publish Degradation

ResolvedStarted Sep 15, 17:20 UTCResolved Sep 15, 18:19 UTC

Publishing Packages Degraded Performance

ResolvedStarted Sep 15, 16:13 UTCResolved Sep 15, 16:35 UTC

npm audits endpoint is having issues

ResolvedStarted Sep 4, 11:29 UTCResolved Sep 4, 13:48 UTC

Intermittent Failures Impacting npm Publish

ResolvedStarted Sep 3, 21:42 UTCResolved Sep 3, 23:21 UTC

intermittent Publish Failures

ResolvedStarted Jul 30, 12:06 UTCResolved Jul 30, 16:30 UTC

Publish and Install failures

ResolvedStarted Jul 24, 11:08 UTCResolved Jul 24, 11:38 UTC

intermittent Publish and Install Failures

ResolvedStarted Jul 23, 16:09 UTCResolved Jul 23, 19:52 UTC

Questions and experiences

Ask about this page: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…