WhatBrokeToday
GTA 6FAQ
Is npm down right now?

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
npm incidents per month
MonthIncidents
2026-118
2026-105
2026-095
2026-080
2026-070
2026-060
2026-050
2026-040
2026-030
2026-020
2026-010
2025-120
2025-110

Every npm incident in the last 12 months

Every npm incident in the last 12 months, newest first
DateIncidentSeverityTime to fixStatus 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.

criticalongoingnot yet
npm Package ai@7.0.176 Hotfix Released Following 7.0.175minorongoingnot yet
Multiple NPM Packages Contain Malicious Code

Cause: Publication of malicious package versions containing malware.

criticalongoingnot yet
Mongoose sanitizeFilter Vulnerability in countDocuments

Cause: The sanitizeFilter protection mechanism was not applied during countDocuments() queries in affected versions.

criticalongoingnot 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.

criticalongoingnot yet
node-opcua Namespace-Level RBAC Fail-Open Vulnerability

Cause: Namespace-level RBAC fail-open via unbound DefaultRolePermissions allowing anonymous write and call bypasses.

criticalongoingnot 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.

criticalongoingnot yet
npm: Minor issues impacting package publishmedium37 minfirst
npm: View package and auth outage on npmjs.comhigh1 minfirst
Prisma CLI 7.10.x Missing Provenance

Cause: Missing npm provenance for the latest 7.x releases of prisma CLI

minorongoingnot yet
npm: Degraded Publish, Install, and View Packagemedium1 minfirst
npm: Degraded Package Install and Publishinghigh1 h+1 h
npm: Issues with login and viewing packagesmedium1 minfirst
npm: Issues with npm package publish and private installmedium1 minfirst
npm: Package Publish Degradationmedium1 minfirst
npm: Publishing Packages Degraded Performancemedium1 minfirst
npm audits endpoint is having issuesmedium1 minfirst
npm: Intermittent Failures Impacting npm Publishmedium1 minfirst

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.