rewindex

CompaniesnpmIncidents

npm: DNS misconfiguration cached in ISP DNS caches

MajorStatus: resolvedStarted Resolved (45 h)1 updatestatus.npmjs.org (opens in new tab)

Timeline of updates

  1. resolved

    Global DNS caches are now reporting correct records and we have seen a return to normal incoming traffic levels. If you are still seeing DNS, SSL or other network related issues please get in touch through our support channels.

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: major) posted by npm, started 2018-08-31 15:35 UTC, resolved after 45 h, 1 update(s).

Title
DNS misconfiguration cached in ISP DNS caches
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/v22ffls5cd6h

npm profileRecent npm incidentsAll outages on August 31, 2018npm in August 2018MarkdownJSON