npm outage on 22 October 2026
Major outageAn email when it goes down, and when it’s back.
“Degraded Package Install and Publishing”
On 22 October, npm had a major outage affecting package installation, package publishing and the www.npmjs.com website, with the incident open from 02:33 to 04:24 UTC (1 h 51 min). The status page showed the affected components in major outage from 02:33 (02:37 for the website) until 04:10, when it reported a fix was in place and began monitoring before marking the incident resolved at 04:24. OpenAI, Musixmatch, Notion, Asana, Claude and Supabase also reported problems during the same period.
npm’s own incident page ↗- When
- 02:33–04:24 UTC
- How long
- 1 h 51 min
- Incident open on its page
- 02:33–04:24 UTC
- Components affected
- 3
- npm, 30 days before
- No other outages
What broke when
From npm’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 117 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Package installation: degraded performance
- Package publishing: degraded performance
- Package installation: partial outage
- Package publishing: partial outage
- www.npmjs.com website: partial outage
- Cause identified
- Fix in place, monitoring
- Package installation: back to normal
- Package publishing: back to normal
- www.npmjs.com website: back to normal
- Resolved
Where this comes from
Stackpulse reads npm’s official status page at status.npmjs.org every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with npm. Names and logos belong to their owners.