outages.live
Live
npmIncident · 2026-10-22 02:33 UTC

Degraded Package Install and Publishing

ResolvedOfficial update

This incident has been resolved.

The latest update from npm.

State

Resolved

Started

10 d ago

2026-10-22 02:33 UTC

Lasted

1 h 51 min

until 2026-10-22 04:24 UTC

Worst impact

Partial outage

Timeline

5 updates
02:3303:0103:2803:5604:24
Partial outageUpdate postedTimes in UTC

Investigating

34 min 31%

Identified

1 h 3 min 57%

Monitoring

13 min 12%

Updates

Times in UTC

As posted by npm

Resolved2026-10-22 04:24 UTC

This incident has been resolved.

Monitoring2026-10-22 04:10 UTC

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

Identified2026-10-22 03:07 UTC

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

Investigating2026-10-22 02:37 UTC

We are continuing to investigate this issue.

Investigating2026-10-22 02:33 UTC

We are currently investigating this issue.

Affected components

3
www.npmjs.com websitePackage installationPackage publishing

npm in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

7

Median duration

1 h 51 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 h 57 min
median 1 h 51 min
90 days agoToday

Other npm incidents

All incidents

npm·View package and auth outage on npmjs.com

This incident has been resolved.

Resolvedresolved 6 d ago

npm·Degraded Publish, Install, and View Package

This incident has been resolved.

Resolvedresolved 10 d ago

npm·Issues with login and viewing packages

This incident has been resolved.

Resolvedresolved 18 d ago

npm·Issues with npm package publish and private install

This incident has been resolved.

Resolvedresolved 35 d ago

npm·Package Publish Degradation

This incident has been resolved.

Resolvedresolved 47 d ago

Follow npm

Your coding agent knows when npm is down, and tells you when a failure is theirs, not yours. You can also get npm incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "npm" and tell me if npm has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=npm
Slack
/feed subscribe https://outages.cc/feed.xml?providers=npm

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane