npm reported "Minor issues impacting package publish" on its status page at 2026-11-07 14:28 UTC. npm reports minor issues with package publishing. The incident is resolved. It lasted 37 minutes.

npm lists these components: Package publishing.

When did the incident start and end?

It started at 2026-11-07 14:28 UTC and ended at 2026-11-07 15:05 UTC. It lasted 37 min.

How do I get alerts for npm?

Subscribe to the npm live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of npm. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

npmIncident ·

Minor issues impacting package publish

ResolvedOfficial update

npm reports minor issues with package publishing. The incident is resolved. It lasted 37 minutes.

State

Resolved

Started

Lasted

37 min

Worst impact

Degraded

Timeline

3 updates

14:2814:3714:4614:5515:05

DegradedUpdate postedTimes in UTC

Investigating

11 min 29%

Monitoring

26 min 71%

Updates

Times in UTC

As posted by npm

Resolved

This incident has been resolved.

Monitoring

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

Investigating

We are currently investigating this issue.

Affected components

Package publishing

npm in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 45 min

This incident

65% shorter than 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 45 min

90 days agoToday

Other npm incidents

All incidents

npm·View package and auth outage on npmjs.com

This incident has been resolved.

Resolved

npm·Degraded Publish, Install, and View Package

This incident has been resolved.

Resolved

npm·Degraded Package Install and Publishing

This incident has been resolved.

Resolved

npm·Issues with login and viewing packages

This incident has been resolved.

Resolved

npm·Issues with npm package publish and private install

This incident has been resolved.

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.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