rewindex

CompaniesnpmIncidents

npm: Some package publishing failed

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

Timeline of updates

  1. resolved

    We have addressed some package publish failures, caused due to application of managed security firewall rule in our edge workers.

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 2022-06-06 00:00 UTC, resolved after 0 min, 1 update(s).

Title
Some package publishing failed
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/v1drvxcz4032

npm profileRecent npm incidentsAll outages on June 6, 2022npm in June 2022MarkdownJSON