npm: Access cache issues preventing access to private modules
Timeline of updates
- resolved
Flushing the cache appears to have resolved the issue.
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-05-31 21:45 UTC, resolved after 2.4 h, 1 update(s).
- Title
- Access cache issues preventing access to private modules
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/m0l93f2hypx1
npm profileRecent npm incidentsAll outages on May 31, 2016npm in May 2016MarkdownJSON