npm: elevated 404 rates for scoped modules
Timeline of updates
- resolved
From 10:17am PST to 10:39am PST today the registry was returning 404s for some scoped module tarballs. We rolled out a configuration change to our CDN and served an incorrect version format in package.json files. The incident was resolved by rolling back to the previous configuration. 404 rates are now 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-03-09 19:16 UTC, resolved after 0 min, 1 update(s).
- Title
- elevated 404 rates for scoped modules
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/nmgsv47bqvlg
npm profileRecent npm incidentsAll outages on March 9, 2016npm in March 2016MarkdownJSON