npm incident: Publishing Packages Degraded Performance

Affected components

• Package publishing

1. resolvedSep 15, 2026, 16:35 UTC

   This incident has been resolved.

2. investigatingSep 15, 2026, 16:13 UTC

   We are investigating delays affecting npm package publishing. Some newly published package versions may take longer than expected to become available.

What APIStatus.watch saw

• Sep 15, 2026, 16:15 UTCoperational → degraded
• Sep 15, 2026, 16:40 UTCdegraded → operational
• Sep 15, 2026, 17:25 UTCoperational → degraded

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• Resend: Delayed email sendingMajor · Sep 15, 2026, 15:49 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• CircleCI: Customers may experience delays in UI updatesMinor · Sep 15, 2026, 14:42 UTC
• Telnyx: Outbound Messaging LatencyMinor · Sep 15, 2026, 15:27 UTC
• Plaid: Elevated Item add errorsMinor · Sep 15, 2026, 16:31 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