rewindex

CompaniesnpmIncidents

npm: Publish failures

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

Timeline of updates

  1. resolved

    Publications are back to normal.

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-02-04 23:09 UTC, resolved after 1.4 h, 1 update(s).

Title
Publish failures
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/nplngmfhlmbg

npm profileRecent npm incidentsAll outages on February 4, 2016npm in February 2016MarkdownJSON