npm incident: Package Publish Degradation

Affected components

• Package publishing

1. resolvedSep 15, 2026, 18:19 UTC

   This incident has been resolved.

2. identifiedSep 15, 2026, 18:18 UTC

   Stable

3. identifiedSep 15, 2026, 17:20 UTC

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

4. investigatingSep 15, 2026, 17:20 UTC

   We are currently investigating this issue.

What APIStatus.watch saw

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

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
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Long Codes to Bouygues Telecom FranceMinor · Sep 12, 2026, 22:08 UTC
• Twilio: Missing Data in Voice Insights / Console Subaccount RollupMinor · Sep 15, 2026, 03:51 UTC
• Twilio: Pages Not Accessible in Twilio ConsoleMinor · Sep 15, 2026, 15:21 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Multiple Networks in PeruMinor · Sep 15, 2026, 15:26 UTC
• Telnyx: Outbound Messaging LatencyMinor · Sep 15, 2026, 15:27 UTC
• Plaid: Elevated Item add errorsMinor · Sep 15, 2026, 16:31 UTC
• LiveKit: Investigating reports of intermittently increased API latency impacting Egress, Ingress, and SIPMinor · Sep 15, 2026, 17:04 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