npm: Intermittent scoped module installation failures from US East
Timeline of updates
- resolved
The registry was returning elevated rates of 503s from a specific origin host that US East users were likely to be routed to. This was due to a misconfiguration that caused requests to an internal service to be rejected. This configuration has been corrected. 503 rates are back down 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-01-27 17:31 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent scoped module installation failures from US East
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/pbfpkmhlbmkk
npm profileRecent npm incidentsAll outages on January 27, 2016npm in January 2016MarkdownJSON