npm: 404s on certain registry reads
Timeline of updates
- resolved
A fix has been verified and rolled out.
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: minor) posted by npm, started 2018-06-27 17:38 UTC, resolved after 10 h, 1 update(s).
- Title
- 404s on certain registry reads
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/xt6t05ffsqfh
npm profileRecent npm incidentsAll outages on June 27, 2018npm in June 2018MarkdownJSON