Live  /  npm  /  Incident

npm: Minor issues impacting package publish

npm · npmjs.comMinor incidentResolved2026-11-07 15:05 UTC
Public — what happened

Summary

npm reported a minor problem affecting the publishing of packages, which it began investigating at 14:28 UTC on 2026-11-07. About nine minutes later, at 14:37 UTC, npm said it had put a fix in place and was watching to see how it held up. The company did not state a cause or say who was affected, and it marked the incident resolved at 15:05.

Affected

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