Live  /  npm  /  Incident

npm: Issues with login and viewing packages

npm · npmjs.comMinor incidentResolved2026-10-14 11:44 UTC
Public — what happened

Summary

npm reported a minor incident beginning at 09:29 UTC on October 14, 2026, in which signing in and browsing packages were producing more errors and running slower than usual. By 11:06 UTC the company said problems had also spread to opening package settings pages. npm said it found the source of the trouble at 11:20 UTC but did not describe what it was, then rolled out a fix at 11:33 UTC and marked the incident resolved at 11:44.

Affected

www.npmjs.com website

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 43, 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.