Space for ads
Checked every 5 minutes · How we measure this
As of 15:10 EDT on 8 Sep 2026, npmjs.com responded to our check in 219 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 9 minutes ago
The line is response time measured from our probe to npmjs.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by npm on its own status page. Verify on their status page.
The ability for users to navigate to or interact with the npm website.
The ability for users to read from the registry so that they can install packages.
The ability for users to search for a package
The ability for users to get output from running npm audit
Allows users to replicate public registry
0 problem reports
No incidents recorded since monitoring began. Monitoring for npm records every incident lasting ten minutes or more.
npm is responding normally. Our last automated check of npmjs.com completed 9 minutes ago and succeeded in 219 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, npm has been available 100.00% over 24 hours, 100.00% over 7 days, 100.00% over 30 days. We have recorded no incidents in the last 30 days.
npm has averaged 180 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to npmjs.com and does not include rendering time in your browser.
Our probe is reaching npmjs.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://npmjs.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than npm. On Windows run ping npmjs.com and nslookup npmjs.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load npmjs.com in a private or incognito window. If it works there, clear cookies and site data for npmjs.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
