Live  /  Providers  /  npm

npm

npmjs.comNo open incidents

Independent assessment — SquidGrid is not affiliated with npm. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks npm’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what npm is reporting

Current & recent incidents

Resolved

Issues with npm package publish and private install

Minor impact · 2026-09-27 06:47 UTC

Resolved

Package Publish Degradation

Minor impact · 2026-09-15 17:20 UTC

Resolved

Publishing Packages Degraded Performance

Minor impact · 2026-09-15 16:13 UTC

Resolved

npm audits endpoint is having issues

Minor impact · 2026-09-04 11:29 UTC

Resolved

Intermittent Failures Impacting npm Publish

Minor impact · 2026-09-03 22:41 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what npm has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

npm runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of npm is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with npm.