npm outage history
npm had 18 incidents in the last 12 months, fixed in 1 min on median. 8 never appeared on its status page.
- Incidents, 12 months
- 18
- 8 critical or high
- Median time to fix
- 1 min
- 10 resolved
- Longest
- 1 h
- Never on the status page
- 8
- posted after 1 min (median)
npm incidents per month
View as table
| Month | Incidents |
|---|---|
| 2026-11 | 8 |
| 2026-10 | 5 |
| 2026-09 | 5 |
| 2026-08 | 0 |
| 2026-07 | 0 |
| 2026-06 | 0 |
| 2026-05 | 0 |
| 2026-04 | 0 |
| 2026-03 | 0 |
| 2026-02 | 0 |
| 2026-01 | 0 |
| 2025-12 | 0 |
| 2025-11 | 0 |
Every npm incident in the last 12 months
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Vant NPM Package Malicious Versions Published Cause: Malicious code and install hooks ('postinstall': 'node lib/utils/support.js') were added to multiple versions of the vant package. | critical | ongoing | not yet | |
| npm Package ai@7.0.176 Hotfix Released Following 7.0.175 | minor | ongoing | not yet | |
| Multiple NPM Packages Contain Malicious Code Cause: Publication of malicious package versions containing malware. | critical | ongoing | not yet | |
| Mongoose sanitizeFilter Vulnerability in countDocuments Cause: The sanitizeFilter protection mechanism was not applied during countDocuments() queries in affected versions. | critical | ongoing | not yet | |
| bitcoinjs-lib Undetected Merkle Node Duplication Vulnerability Cause: `fastMerkleRoot` pads an odd level by hashing the last node with itself without reporting it, and `checkTxRoots` fails to look for repeated transactions. | critical | ongoing | not yet | |
| node-opcua Namespace-Level RBAC Fail-Open Vulnerability Cause: Namespace-level RBAC fail-open via unbound DefaultRolePermissions allowing anonymous write and call bypasses. | critical | ongoing | not yet | |
| @injectivelabs/sdk-ts Malware Published in NPM Version 1.20.21 Cause: Malicious code injected into npm package @injectivelabs/sdk-ts version 1.20.21. | critical | ongoing | not yet | |
| npm: Minor issues impacting package publish | medium | 37 min | first | |
| npm: View package and auth outage on npmjs.com | high | 1 min | first | |
| Prisma CLI 7.10.x Missing Provenance Cause: Missing npm provenance for the latest 7.x releases of prisma CLI | minor | ongoing | not yet | |
| npm: Degraded Publish, Install, and View Package | medium | 1 min | first | |
| npm: Degraded Package Install and Publishing | high | 1 h | +1 h | |
| npm: Issues with login and viewing packages | medium | 1 min | first | |
| npm: Issues with npm package publish and private install | medium | 1 min | first | |
| npm: Package Publish Degradation | medium | 1 min | first | |
| npm: Publishing Packages Degraded Performance | medium | 1 min | first | |
| npm audits endpoint is having issues | medium | 1 min | first | |
| npm: Intermittent Failures Impacting npm Publish | medium | 1 min | first |
Compare npm's reliability
Questions
- How often does npm go down?
- npm had 18 incidents in the last 12 months, fixed in 1 min on median. 8 never appeared on its status page.
- How long do npm outages last?
- Half of npm's resolved incidents in the last 12 months were fixed within 1 min; the longest took 1 h.
- Does npm report every outage on its status page?
- No. 8 of 18 npm incidents in the last 12 months never appeared on its status page.