Live / npm / Incident
npm: Degraded Package Install and Publishing
npm · npmjs.comMajor incidentResolved2026-10-22 04:24 UTC
Public — what happened
Summary
npm reported a major incident titled Degraded Package Install and Publishing, which began at 02:33 UTC on 2026-10-22. The company said it was investigating at first, and by 03:07 UTC it said the problem had been identified and a fix was being put in place. npm said a fix was in place by 04:10 UTC and it was watching the results, and it marked the incident resolved at 04:24 UTC. The company did not say in its updates what caused the problem or who was affected.
Affected
www.npmjs.com website, Package installation, Package publishing
Timeline
- Started — 2026-10-22 02:33 UTC
- Investigating — 2026-10-22 02:33 UTC (2 updates)
- Identified — 2026-10-22 03:07 UTC
- Monitoring — 2026-10-22 04:10 UTC
- Resolved — 2026-10-22 04:24 UTC · 1h 51m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach npm against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for npm: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the npm report →
More from npm
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.