Rewindex

CompaniesnpmIncidents

npm: intermittent Publish and Install Failures

MinorStatus: resolvedStarted Resolved (3.7 h)3 updatesstspg.io (opens in new tab)
Part of an outage event

Azure west us outage, Jul 23, 2026 · 25 vendors, 26 incidents

npm’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +1 h 5 min vs the first vendor naming Azure)

Swipe sideways to see the whole diagram.

same windowAzure west usown incident not archivedWithin an hour2 vendors, 1 blamed AzureJFrog, Optimizely1 to 4 hours later2 vendors, 2 blamed AzureWiz, Sumo LogicLater1 vendorContentstacknpm (this incident)posted +1 h 5 min
same windowAzure west usown incident not archivedWithin an hour2 vendors, 1 blamed AzureJFrog, Optimizely1 to 4 hours later2 vendors, 2 blamed AzureWiz, Sumo LogicLater1 vendorContentstacknpm (this incident)posted +1 h 5 min
npm is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Azure west us<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 1 blamed Azure<br/>JFrog, Optimizely"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 2 blamed Azure<br/>Wiz, Sumo Logic"]:::blames
  root --> h4
  later["Later<br/>1 vendor<br/>Contentstack"]:::names
  root --> later
  me["npm (this incident)<br/>posted +1 h 5 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Package publishingPackage installation

Timeline of updates

  1. investigating

    We are currently investigating this issue.

  2. monitoring

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

  3. resolved

    This incident has been resolved.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

npm profileRecent npm incidentsMarkdownJSON