npm favicon

NPM outage on 2026-11-07

npmjs.org
November 2026 7 Minor incident

Package publishing on NPM broke for 40 minutes on 7 November 2026. The fault sat with NPM's registry, not with your build pipeline.

Started

14:28 UTC

Duration

Lasted 40m

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: Package publishing

What happened?

NPM's status page logged one incident that day, starting at 14:28 UTC under the title "Minor issues impacting package publish". The affected component was package publishing only, nothing else on NPM's component list was marked down. NPM posted three updates in total. At 14:28 they said they were investigating. By 14:37 they reported a fix had been implemented and they were monitoring results. At 15:05 the incident was marked resolved, which puts the total length at 40 minutes. No user reports were filed during the window, so there is no first-hand account of what publishing attempts actually did during that stretch, whether they failed outright, hung, or queued and went through late. NPM's status page gives no further detail on what the fix was or what caused the publishing path to break. One filing from a vendor, with no root cause note and no post-mortem, is what the record contains, so this is what can be said: package publishing was impaired, a fix went in nine minutes after the start, and the rest resolved within another half hour. Over the past 90 days NPM has logged 10 incidents with a median duration of 1 hour 47 minutes, so this one ran shorter than NPM's own recent median. Across all time NPM has logged 192 incidents, averaging 2.5 a month.

Learning

UptimeRobot's own probes against NPM's registry, run from EU and NA regions every 60 seconds, show 100% uptime over the past 24 hours and the past 7 days, and 99.989% over 30 days, with this incident not registered against that monitoring at all. That is not a contradiction. Package publishing is a write path, a specific action you take against the registry, and a probe that checks whether the registry responds to a read or a simple ping will not exercise that path the same way a real publish does. This is the general shape of registry outages: the service can look healthy from outside while the one operation you actually need, pushing a new package version, fails or stalls. Watching your own CI logs for failed publishes tells you something broke, but not whether the fault is yours or NPM's. Your own monitoring covers your half of that question, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.