Vendor record
npm Registry
Checked
Front door check counts and npm Registry’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented npm Registry endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- registry.npmjs.org
- Scope
- registryNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every npm Registry product, region or your app worked.
How we count front door checksnpm Registry says
Incident posts from npm Registry’s status page, with its titles, impact levels and times. They say what npm Registry chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
14
incidents npm Registry posted, last 180 days
Median recorded duration: 1h 48m. From 14 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Issues with login and viewing packages
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(2h 21m)
Issues with npm package publish and private install
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(5h 59m)
Package Publish Degradation
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(1h 5m)
Publishing Packages Degraded Performance
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(26m)
npm audits endpoint is having issues
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(2h 21m)
14 older records
Intermittent Failures Impacting npm Publish
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(1h 48m)
intermittent Publish Failures
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(4h 33m)
Publish and Install failures
Majornpm Registry’s postStarted, per npm Registry
Closed in our record(31m)
intermittent Publish and Install Failures
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(3h 50m)
intermittent Publish Failures
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(51m)
npm website issues
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(43m)
Degraded Performance in View Package and Login on npmjs.com
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(2h 51m)
npm website degraded service
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(2h 35m)
npm Website is unavailable
Criticalnpm Registry’s postStarted, per npm Registry
Closed in our record(1h 34m)
Increased errors in viewing packages and authentication on npmjs.com
Not specifiednpm Registry’s postStarted, per npm Registry
Closed in our record(3h 14m)
Degraded Performance in View Package and Login on npmjs.com
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(2h 44m)
delay and errors viewing packages and submitting web based authentication
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(2h 45m)
delay and errors viewing packages and submitting web based authentication
Minornpm Registry’s postStarted, per npm Registry
Closed in our record(1h 10m)
Issue with npm website and login.
Majornpm Registry’s postStarted, per npm Registry
Closed in our record(50m)
Your code, your dependencies
See which of your code paths call npm Registry
Connect GitHub or GitLab to find where your public or private repository uses npm Registry. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add npm Registry status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is npm Registry currently down?
npm Registry's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did npm Registry last have an outage?
The most recent closed incident record began 2 days ago and spans 2h 21m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for npm Registry?
No. CheckUpstream checks npm Registry’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor npm Registry in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track npm Registry?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.