npm reported "Issues with login and viewing packages" on its status page at 2026-10-14 09:29 UTC.

npm lists these components: www.npmjs.com website.

When did the incident start and end?

It started at 2026-10-14 09:29 UTC and ended at 2026-10-14 11:44 UTC. It lasted 2 h 15 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.

npmIncident · 2026-10-14 09:29 UTC

Issues with login and viewing packages

ResolvedOfficial update

This incident has been resolved.

The latest update from npm.

State

Resolved

Started

18 d ago

2026-10-14 09:29 UTC

Lasted

2 h 15 min

until 2026-10-14 11:44 UTC

Worst impact

Degraded

Timeline

5 updates

09:2910:0210:3611:1011:44

DegradedUpdate postedTimes in UTC

Investigating

1 h 51 min 82%

Identified

13 min 10%

Monitoring

11 min 8%

Updates

Times in UTC

As posted by npm

Resolved2026-10-14 11:44 UTC

This incident has been resolved.

Monitoring2026-10-14 11:33 UTC

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

Identified2026-10-14 11:20 UTC

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

Investigating2026-10-14 11:06 UTC

We are continuing to investigate the issue. We also observe increased errors in accessing package settings.

Investigating2026-10-14 09:29 UTC

We observed increased errors and latency in login and viewing packages. We are investigating the issue.

Affected components

www.npmjs.com website

npm in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 51 min

This incident

1.2× 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·Degraded Package Install and Publishing

This incident has been resolved.

Resolvedresolved 10 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