npm: some readmes are unavailable on npmjs.com
Timeline of updates
- resolved
README rendering of new package publications was lagging behind, due to a production database running out of space. We have corrected this issue, and will be adding monitoring to prevent similar issues in the future. The database that ran out of space stored only README information, which has now caught up. No data was lost.
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 2017-01-26 13:09 UTC, resolved after 3.7 h, 1 update(s).
- Title
- some readmes are unavailable on npmjs.com
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/tj3qsythtgg8
npm profileRecent npm incidentsAll outages on January 26, 2017npm in January 2017MarkdownJSON