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
Timeline
- Started — 2026-10-14 09:29 UTC
- Investigating — 2026-10-14 09:29 UTC (2 updates)
- Identified — 2026-10-14 11:20 UTC
- Monitoring — 2026-10-14 11:33 UTC
- Resolved — 2026-10-14 11:44 UTC · 2h 15m 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 43, 2026, our weekly internet health report.