Minor impactResolvedDevOps

npm incident: Degraded performance with package installation

npm reported this minor-impact incident on its official status page on Feb 25, 2026, 18:43 UTC. It was resolved after 1h 20m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Feb 25, 2026, 18:43 UTC
started
Feb 25, 2026, 20:03 UTC
resolved
1h 20m
duration
Minor
impact

Affected components

  • Package installation

Timeline

updates from npm's status page ↗
  1. resolvedFeb 25, 2026, 20:03 UTC

    This incident has been resolved.

  2. monitoringFeb 25, 2026, 19:28 UTC

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

  3. identifiedFeb 25, 2026, 19:24 UTC

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

  4. investigatingFeb 25, 2026, 18:43 UTC

    We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in npm's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does npm have incidents?

npm reported 8 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 59m. See npm's uptime and incident history

← Previous: npm publishing impacted (Feb 17, 2026)Next: Degraded performance for package publish (Mar 5, 2026) →
npm incident on Feb 25, 2026: Degraded performance with package installation · APIStatus.watch