# npm: some readmes are unavailable on npmjs.com

> npm status incident “some readmes are unavailable on npmjs.com” on 2017-01-26: impact none (vendor’s label), 3.7 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/tj3qsythtgg8
Last updated: 2017-01-26T16:50:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2017-01-26 13:09 UTC · Resolved: 2017-01-26 16:50 UTC · Duration: 3.7 h
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/tj3qsythtgg8](https://status.npmjs.org/incidents/tj3qsythtgg8)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2017-01-26 16:50 UTC: 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 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 2017-01-26 13:09 UTC, resolved after 3.7 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/npm/incidents/tj3qsythtgg8
- Citation: npm, “some readmes are unavailable on npmjs.com” (2017-01-26 13:09 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/tj3qsythtgg8 (CC BY 4.0).
- Markdown link: `[npm: some readmes are unavailable on npmjs.com (2017-01-26)](https://rewindex.com/company/npm/incidents/tj3qsythtgg8)`


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