Minor impactResolvedDevOps

npm incident: Degraded performance on npmjs.com

npm reported this minor-impact incident on its official status page on Oct 3, 2025, 18:07 UTC. It was resolved after 7h 35m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Oct 3, 2025, 18:07 UTC
started
Oct 4, 2025, 01:42 UTC
resolved
7h 35m
duration
Minor
impact

Affected components

  • www.npmjs.com website

Timeline

updates from npm's status page ↗
  1. resolvedOct 4, 2025, 01:42 UTC

    This incident has been resolved.

  2. investigatingOct 3, 2025, 18:07 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: Degraded Package Install Experience (Aug 26, 2025)Next: Degraded performance of package publish and install (Oct 20, 2025) →
npm incident on Oct 3, 2025: Degraded performance on npmjs.com · APIStatus.watch