npm RegistryStatus record
Latest recorded vendor status
Source checked
A recorded report, not a live test of your application.
Open official status pageCheck the product, region and time against your own logs.
Check counts and incident historyComponent records
Vendor products and regions, with issue records listed first.
| Product / region | Recorded status | Record last seen |
|---|---|---|
Package installation | Operational | |
Package publishing | Operational | |
Package search | Operational | |
Replication Feed | Operational | |
Security Audit | Operational | |
www.npmjs.com website | Operational |
- Operational
Package installation
Record last seen - Operational
Package publishing
Record last seen - Operational
Package search
Record last seen - Operational
Replication Feed
Record last seen - Operational
Security Audit
Record last seen - Operational
www.npmjs.com website
Record last seen
6 components
“Last seen” is saved when a component changes or its record is refreshed. It is not the time of every status check. These records can differ from the vendor’s overall report.
Recent incidents
Past 30 days
Started or first observed in this window. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not confirm an ongoing outage.
Issues with login and viewing packages
Started
Closed in record
Issues with npm package publish and private install
Started
Closed in record
Recorded impact: Minor
Components: Package publishing · Package installation · Replication Feed
Read vendor report
Maintenance and future scheduled work are excluded.
Explore reliability history