npm incident: Issue with package publishing

Affected components

• Package publishing

1. resolvedOct 20, 2025, 20:15 UTC

   This incident has been resolved.

2. monitoringOct 20, 2025, 19:20 UTC

   We are seeing recovery in package publishing. We will continue to monitor the results.

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

• 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
• Convex: Usage info on Convex dashboard is unavailableMajor · Oct 20, 2025, 14:48 UTC
• Upstash: Upstash Console issuesMajor · Oct 20, 2025, 14:52 UTC
• Pusher: MT1 cluster - increased latencyMajor · Oct 20, 2025, 17:26 UTC
• Pinecone: Some users may be unable to access the Pinecone web console. All API services remain fully operational.Major · Oct 20, 2025, 17:43 UTC
• Miro: User search degradationMajor · Oct 20, 2025, 17:47 UTC
• Pusher: US3 cluster - major outageMajor · Oct 20, 2025, 18: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