npm: 404s for a small number of package installs
Timeline of updates
- resolved
A bug in a recently updated service caused a small number of packages (in fact we believe only 2 were actually affected) to 404 on install if they had recently been the subject of a security advisory. The root cause was identified and fix pushed soon after. It was in no way related to the planned DNS migration which did not proceed as planned at 12:00 UTC but instead was postponed. We're sorry for the disruption this caused to some of our users, please do get in touch through our support channels if you see any other issues.
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-08-30 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- 404s for a small number of package installs
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/gnqjntz7gx0y
npm profileRecent npm incidentsAll outages on August 30, 2018npm in August 2018MarkdownJSON