Minor impactResolvedDevOps

npm incident: Issue with search and replication feed

npm reported this minor-impact incident on its official status page on Jun 17, 2024, 19:59 UTC. It was resolved after 1h 37m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Jun 17, 2024, 19:59 UTC
started
Jun 17, 2024, 21:36 UTC
resolved
1h 37m
duration
Minor
impact

Affected components

  • Package search
  • Replication Feed

Timeline

updates from npm's status page ↗
  1. resolvedJun 17, 2024, 21:36 UTC

    This incident has been resolved.

  2. monitoringJun 17, 2024, 21:14 UTC

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

  3. identifiedJun 17, 2024, 20:08 UTC

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

  4. investigatingJun 17, 2024, 19:59 UTC

    We are currently investigating an issue related to search and replication feed.

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: Failures publishing, deprecating, and installing packages (Jun 11, 2024)Next: Intermittent Issues with View Package (Jun 20, 2024) →
npm incident on Jun 17, 2024: Issue with search and replication feed · APIStatus.watch