Is npm down?
npmjs.com is reachable but answered 403 to our probes. It is probably up and blocking automated or regional traffic — not an outage.
- Website
- npmjs.com
- Response time
- 94 ms (median)
- Uptime (24 h)
- 100%
- Last down
- no outage in 90 days
Official status page ↗Report a problemNo problem reports in 24 h
Response time — last 24 checks
Median across 4 regions, one point every 2 minutes. Red markers = round failed.
Last 24 hours
One bar per hour · colour = success rate · height = median response.
Latest check by region
| Region | Result | Response | DNS | TLS expires | Server |
|---|---|---|---|---|---|
| Dallas, US | HTTP 403 | 4462 ms | 11 ms | — | cloudflare |
| Washington DC, US | HTTP 403 | 103 ms | 5 ms | — | cloudflare |
| Frankfurt, DE | HTTP 403 | 82 ms | 4 ms | — | cloudflare |
| Singapore, SG | HTTP 403 | 85 ms | 4 ms | — | cloudflare |
Resolves to: 104.17.135.117, 104.17.134.117, 2606:4700::6811:8675, 2606:4700::6811:8775
Service status history
| Time (UTC) | Regions OK | Response |
|---|---|---|
| 26 Oct 2026 17:00 UTC | 4/4 | 94 ms |
| 26 Oct 2026 16:58 UTC | 4/4 | 76 ms |
| 26 Oct 2026 16:56 UTC | 4/4 | 96 ms |
| 26 Oct 2026 16:54 UTC | 4/4 | 76 ms |
| 26 Oct 2026 16:52 UTC | 4/4 | 88 ms |
| 26 Oct 2026 16:50 UTC | 4/4 | 92 ms |
| 26 Oct 2026 16:48 UTC | 4/4 | 94 ms |
| 26 Oct 2026 16:46 UTC | 4/4 | 84 ms |
| 26 Oct 2026 16:44 UTC | 4/4 | 75 ms |
| 26 Oct 2026 16:42 UTC | 4/4 | 74 ms |
| 26 Oct 2026 16:40 UTC | 4/4 | 91 ms |
| 26 Oct 2026 16:38 UTC | 4/4 | 88 ms |
| Time (UTC) | Regions OK | Response |
|---|---|---|
| 26 Oct 2026 16:36 UTC | 4/4 | 104 ms |
| 26 Oct 2026 16:34 UTC | 4/4 | 82 ms |
| 26 Oct 2026 16:32 UTC | 4/4 | 84 ms |
| 26 Oct 2026 16:30 UTC | 4/4 | 153 ms |
| 26 Oct 2026 16:28 UTC | 4/4 | 82 ms |
| 26 Oct 2026 16:26 UTC | 4/4 | 80 ms |
| 26 Oct 2026 16:24 UTC | 4/4 | 92 ms |
| 26 Oct 2026 16:22 UTC | 4/4 | 92 ms |
| 26 Oct 2026 16:20 UTC | 4/4 | 78 ms |
| 26 Oct 2026 16:18 UTC | 4/4 | 154 ms |
| 26 Oct 2026 16:16 UTC | 4/4 | 110 ms |
| 26 Oct 2026 16:14 UTC | 4/4 | 82 ms |
Problems with npm? Report it
No user reports in the last 24 hours. Anonymous, no account needed.
Recent comments
No comments yet. If something is broken for you, say so above — it helps everyone else.
What this result means
The server answered HTTP 403 to automated requests from every region. That is a security policy (bot protection or geo-blocking), not an outage — the site is most likely fine in a normal browser.
1 · Browser
- Hard-refresh: Ctrl+F5 (Mac: ⌘+Shift+R).
- Try a private/incognito window — rules out extensions and stale cookies.
- Clear cache & cookies for npmjs.com.
2 · DNS
- Flush DNS: Windows
ipconfig /flushdns, macOSsudo dscacheutil -flushcache. - Switch to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) DNS.
- Works on mobile data but not Wi-Fi? Your ISP's DNS or filtering is the culprit.
3 · Network
- Disable VPN/proxy, or turn one on if your region blocks the site.
- Check firewall, antivirus web-shield and parental controls.
- Restart your router; ask a friend elsewhere to open this page.
More in For Developers
Outages happening right now
Verdict rule: DOWN when most regions fail, DEGRADED when some fail or the median exceeds 3 s, RESTRICTED when the site answers 401/403/429 to our probes. Checks come from Dallas, Washington DC, Frankfurt and Singapore. Share: https://isitdownorme.com/npm