Minor impactResolvedDevOps

npm incident: Degraded Package Install Experience

npm reported this minor-impact incident on its official status page on Aug 26, 2025, 12:40 UTC. It was resolved after 3h 9m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Aug 26, 2025, 12:40 UTC
started
Aug 26, 2025, 15:49 UTC
resolved
3h 9m
duration
Minor
impact

Affected components

  • Package installation
  1. resolvedAug 26, 2025, 15:49 UTC

    This incident has been resolved.

  2. monitoringAug 26, 2025, 15:16 UTC

    We are continuing to monitor for any further issues.

  3. monitoringAug 26, 2025, 15:15 UTC

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

  4. identifiedAug 26, 2025, 14:27 UTC

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

  5. investigatingAug 26, 2025, 12:41 UTC

    We are continuing to investigate this issue.

  6. investigatingAug 26, 2025, 12:40 UTC

    We are investigating an issue where users are experiencing failures during npm install. Errors observed include 429 Too Many Requests and 403 Forbidden for GitHub Actions.

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

npm incident on Aug 26, 2025: Degraded Package Install Experience · APIStatus.watch