npm outage: Publish and Install failures

Affected components

• Package installation
• Package publishing

1. resolvedJul 24, 2026, 11:38 UTC

   This incident has been resolved.

2. monitoringJul 24, 2026, 11:36 UTC

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

3. investigatingJul 24, 2026, 11:32 UTC

   We are continuing to investigate this issue.

4. investigatingJul 24, 2026, 11:08 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.

• Render: Service Disruption in OregonCritical · Jul 24, 2026, 11:16 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident NotificationMajor · Jul 23, 2026, 19:14 UTC
• Grafana Cloud: Errors creating new Slack integration for Grafana IRMMajor · Jul 24, 2026, 09:17 UTC
• Notion: Notion is downMajor · Jul 24, 2026, 11:24 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• dbt Cloud: Scheduled jobs are intermittently affected by job failures caused by 403 errorMinor · Jul 24, 2026, 07:58 UTC
• DigitalOcean: Network Connectivity from India to NYCMinor · Jul 24, 2026, 10:36 UTC

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