outages.live
Live

npm

npm is operational

Checked 15 s ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

7

Median duration

1 h 51 min

Longest incident

5 h 57 min

Components

6
www.npmjs.com website Operational
90 days ago3 days with an incidentToday
Package installation Operational
90 days ago3 days with an incidentToday
Package publishing Operational
90 days ago4 days with an incidentToday
Package search Operational
90 days agoNo incidentsToday
Security Audit Operational
90 days ago1 day with an incidentToday
Replication Feed Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 26, 2026

Duration36 min05:54 to 06:30View package and auth outage on npmjs.comPartial outage

This incident has been resolved.

Oct 22, 2026

Duration5 h 16 min06:43 to 11:59Degraded Publish, Install, and View PackageDegraded

This incident has been resolved.

Duration1 h 51 min02:33 to 04:24Degraded Package Install and PublishingPartial outage

This incident has been resolved.

Oct 14, 2026

Duration2 h 15 min09:29 to 11:44Issues with login and viewing packagesDegraded

This incident has been resolved.

Sep 27, 2026

Duration5 h 57 min00:50 to 06:47Issues with npm package publish and private installDegraded

This incident has been resolved.

Sep 15, 2026

Duration1 h17:20 to 18:19Package Publish DegradationDegraded

This incident has been resolved.

Duration22 min16:13 to 16:35Publishing Packages Degraded PerformanceDegraded

This incident has been resolved.

Sep 4, 2026

Duration2 h 20 min11:29 to 13:48npm audits endpoint is having issuesDegraded

This incident has been resolved.

Sep 3, 2026

Duration1 h 39 min21:42 to 23:21Intermittent Failures Impacting npm PublishDegraded

This incident has been resolved.

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.live/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.live/feed.xml?providers=npm
Slack
/feed subscribe https://outages.live/feed.xml?providers=npm

Go from tracking outages to fixing production issues with Polylane.

Try Polylane