rewindex

CompaniesnpmIncidents

npm: Partially-failed publications earlier today

No impact listedStatus: resolvedStarted Resolved (4.3 h)1 updatestatus.npmjs.org (opens in new tab)

Timeline of updates

  1. resolved

    Failed versions have been cleaned up from metadata for nearly all of the packages affected. We were unable to repair 23 newly-published packages and will be in contact with the publishers.

From npm’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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 status.npmjs.org (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by npm, started 2016-03-25 18:39 UTC, resolved after 4.3 h, 1 update(s).

Title
Partially-failed publications earlier today
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/x726c1qdddf6

npm profileRecent npm incidentsAll outages on March 25, 2016npm in March 2016MarkdownJSON