npm incident: Degraded performance of package publish and install

Affected components

• Package installation
• Package publishing

1. resolvedOct 20, 2025, 13:32 UTC

   This incident has been resolved.

2. monitoringOct 20, 2025, 10:50 UTC

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

3. investigatingOct 20, 2025, 09:31 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.

• Vimeo: AI and Create services unavailableCritical · Oct 20, 2025, 07:55 UTC
• Convex: Many Convex backends are downMajor · Oct 20, 2025, 07:22 UTC
• Airtable: Airtable is partially unavailableMajor · Oct 20, 2025, 07:25 UTC
• 1Password: Intermittent performance issues with 1Password.comMajor · Oct 20, 2025, 09:05 UTC
• GitBook: Public content not loading or taking longer to loadMajor · Oct 20, 2025, 09:16 UTC
• Mux: Mux Player embeds increased error ratesMajor · Oct 20, 2025, 09:39 UTC
• Cloudinary: Degraded Performance in US DatacenterMinor · Oct 20, 2025, 07:51 UTC
• Pusher: MT1 cluster - increased latency and webhook delivery failuresMinor · Oct 20, 2025, 08:10 UTC
• New Relic: Data Irregularities - US and EU regionMinor · Oct 20, 2025, 08:40 UTC
• Miro: Potential Service Disruptions (External Incident)Minor · Oct 20, 2025, 08:49 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