npm: Package Publish Failures on Public Registry
Timeline of updates
- resolved
We have had time to observe that the fix applied 7 hours ago has been able to handle our swings in demand. Thank you all for your support and patience while our engineers investigated, remediated and monitored this situation.
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 2019-12-16 14:14 UTC, resolved after 9.3 h, 1 update(s).
- Title
- Package Publish Failures on Public Registry
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/lg9535dl2ff3
npm profileRecent npm incidentsAll outages on December 16, 2019npm in December 2019MarkdownJSON