npm: [Scheduled] DNS migration
Timeline of updates
- resolved
We have completed the migration to a different DNS provider for npmjs.com without issue. It can take up to 24 hours before all ISPs have caught up to the change so we will continue to monitor the situation; if you see any domain resolution issues please get in touch.
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 2018-08-30 20:02 UTC, resolved after 1.0 h, 1 update(s).
- Title
- [Scheduled] DNS migration
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/ykw662xwvjxt
npm profileRecent npm incidentsAll outages on August 30, 2018npm in August 2018MarkdownJSON