npm: Connectivity disruption for users in certain areas
Timeline of updates
- resolved
Our systems are back to full operation. Local DNS issues are still lingering for some users.
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 2016-10-21 12:10 UTC, resolved after 8.6 h, 1 update(s).
- Title
- Connectivity disruption for users in certain areas
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/24cdxprk291y
npm profileRecent npm incidentsAll outages on October 21, 2016npm in October 2016MarkdownJSON