Minor impactResolvedDevOps

npm incident: Issue with publishing packages

npm reported this minor-impact incident on its official status page on Sep 24, 2024, 22:49 UTC. It was resolved after 1h 47m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Sep 24, 2024, 22:49 UTC
started
Sep 25, 2024, 00:37 UTC
resolved
1h 47m
duration
Minor
impact

Affected components

  • Package publishing

Timeline

updates from npm's status page ↗
  1. resolvedSep 25, 2024, 00:37 UTC

    This incident has been resolved.

  2. monitoringSep 25, 2024, 00:12 UTC

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

  3. identifiedSep 25, 2024, 00:12 UTC

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

  4. investigatingSep 24, 2024, 22:49 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.

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

← Previous: README files not rendering on npmjs.com website (Aug 9, 2024)Next: Failures to publish packlages (Oct 10, 2024) →
npm incident on Sep 24, 2024: Issue with publishing packages · APIStatus.watch