← Back to the carnage
NPM
⚪ npmjs.com had a brief identity crisis this afternoon but found itself again by evening. The package registry went dark for a few hours—apparently even the left-pad of the internet needs bathroom breaks. All systems are now pretending nothing happened. (Auto-resolved: no updates in 24h)
// The official story
npmjs.com - Service Disruption
// Status page says
Nov 18 , 19:11 UTC Resolved - We have confirmed that all systems are now fully operational and the connectivity issues have been completely resolved. Nov 18 , 19:09 UTC Update - This incident has been resolved. All services are now operating normally. We apologize for the disruption and appreciate your patience. Nov 18 , 15:23 UTC <
🔗 Official status page (for the PR-approved version)
https://status.npmjs.org/incidents/67q3d5th9kccNpm's Greatest Hits
🟢 NPM
Apr 27, 2026
🟡 npm's web interface decided to ghost everyone at 21:06 UTC. Thousands of devs now learning that `npm search` doesn't work offline. The registry itself is probably fine, but good luck proving it when you can't reach the status page. (Auto-resolved: no updates in 24h)