Viewing packages and signing in on npmjs.com broke for 36 minutes on 26 October 2026. The npm status page attributes the fault to its own website component, not to anything in your build pipeline.
Started
05:54 UTC
Duration
Lasted 36m
Source
IsDown
Next time
npm is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: www.npmjs.com website
What happened?
npm's own status page logged one incident on 26 October 2026, affecting the www.npmjs.com website component. It started at 05:54 UTC under the title "View package and auth outage on npmjs.com", meaning package detail pages and authentication were both affected. At 06:11 npm said the issue had been identified and a fix was being implemented. By 06:21 a fix was in place and being monitored, and the incident was marked resolved at 06:30, 36 minutes after it began. That is the full record: four updates, no root cause given at any stage, and no post-mortem published since. No user reports were filed during the window, which is plausible given how short the incident was and that it affected the website rather than package installs themselves. Over the past 90 days npm has logged 10 incidents with a median duration of 2 hours 5 minutes, so this one resolved far faster than typical for this provider. Across its history npm averages 2.5 incidents a month, 191 in total, which puts this outage in line with a provider that has frequent but usually short website-layer problems. The scope stayed narrow: one component, one incident, no mention of the registry itself failing.
Learning
UptimeRobot's own probes watched the npm registry, not the website, and recorded 100% uptime over 24 hours and 99.989% over 30 days, with no outage registered against this incident. Both readings are correct at once: the registry that serves package installs stayed reachable throughout, while the separate website component that handles viewing a package page or logging in broke for 36 minutes. This is a common split in npm's architecture, where install traffic and browser traffic on npmjs.com run through different paths that can fail independently. If your own monitoring only checks whether `npm install` succeeds, it would have shown green the whole time, correctly, because that path never broke. If your product links out to npmjs.com for package pages or relies on npm auth flows, your users could have hit failures your own checks never caught. The lesson is to watch the specific layer you depend on rather than assuming one green check covers the whole provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.