# npm: elevated 404 rates for scoped modules

> npm status incident “elevated 404 rates for scoped modules” on 2016-03-09: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/nmgsv47bqvlg
Last updated: 2016-03-09T19:16:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2016-03-09 19:16 UTC · Resolved: 2016-03-09 19:16 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/nmgsv47bqvlg](https://status.npmjs.org/incidents/nmgsv47bqvlg)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2016-03-09 19:16 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/npm/incidents/nmgsv47bqvlg
- Citation: npm, “elevated 404 rates for scoped modules” (2016-03-09 19:16 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/nmgsv47bqvlg (CC BY 4.0).
- Markdown link: `[npm: elevated 404 rates for scoped modules (2016-03-09)](https://rewindex.com/company/npm/incidents/nmgsv47bqvlg)`


---
Canonical: https://rewindex.com/company/npm/incidents/nmgsv47bqvlg · Markdown: https://rewindex.com/company/npm/incidents/nmgsv47bqvlg.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/nmgsv47bqvlg · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:53:09.871Z