Major impactResolvedDevOps

npm outage: Degraded Package Install and Publishing

npm reported this major-impact incident on its official status page on Oct 22, 2026, 02:33 UTC. It was resolved after 1h 51m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Oct 22, 2026, 02:33 UTC
started
Oct 22, 2026, 04:24 UTC
resolved
1h 51m
duration
Major
impact

Affected components

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

Timeline

updates from npm's status page ↗
  1. resolvedOct 22, 2026, 04:24 UTC

    This incident has been resolved.

  2. monitoringOct 22, 2026, 04:10 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedOct 22, 2026, 03:07 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingOct 22, 2026, 02:37 UTC

    We are continuing to investigate this issue.

  5. investigatingOct 22, 2026, 02:33 UTC

    We are currently investigating this issue.

What APIStatus.watch saw

  • Oct 22, 2026, 02:35 UTCoperational → degraded
  • Oct 22, 2026, 04:15 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does npm have incidents?

npm reported 9 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 2h 15m. See npm's uptime and incident history

← Previous: Issues with login and viewing packages (Oct 14, 2026)Next: Degraded Publish, Install, and View Package (Oct 22, 2026) →