npm: [Scheduled] skimdb.npmjs.com IP address change & sequence number jump
Timeline of updates
- resolved
Cutover is complete. DNS will take time to propagate, so the older hardware is still serving the unscoped public registry database and will continue to do so until Monday.
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
Maintenance posted by npm, started 2016-08-06 02:01 UTC, resolved after 12 min, 1 update(s).
- Title
- [Scheduled] skimdb.npmjs.com IP address change & sequence number jump
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/669mzfs17fkr
npm profileRecent npm incidentsAll outages on August 6, 2016npm in August 2016MarkdownJSON