Live  /  npm  /  Incident

npm: Degraded Publish, Install, and View Package

npm · npmjs.comMinor incidentResolved2026-10-22 11:59 UTC
Public — what happened

Summary

npm reported a minor incident affecting its ability to publish packages, install them, and view package pages, beginning at 06:43 UTC on October 22, 2026. The company said it was investigating at first and did not name a cause in its updates. By 09:00 UTC it said a fix was in place and it was watching the results, and the incident was marked resolved at 11:59 UTC.

Affected

www.npmjs.com website, Package installation, Package publishing

As listed on npm’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the npm status & history page.

Related: npm status & history. SquidGrid is not affiliated with npm.