# npm: DNS misconfiguration cached in ISP DNS caches

> npm status incident “DNS misconfiguration cached in ISP DNS caches” on 2018-08-31: impact major (vendor’s label), 45 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/v22ffls5cd6h
Last updated: 2018-09-02T12:26:00Z

- Impact (vendor’s label): major
- Status: resolved
- Started: 2018-08-31 15:35 UTC · Resolved: 2018-09-02 12:26 UTC · Duration: 45 h
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/v22ffls5cd6h](https://status.npmjs.org/incidents/v22ffls5cd6h)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2018-09-02 12:26 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/npm/incidents/v22ffls5cd6h
- Citation: npm, “DNS misconfiguration cached in ISP DNS caches” (2018-08-31 15:35 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/v22ffls5cd6h (CC BY 4.0).
- Markdown link: `[npm: DNS misconfiguration cached in ISP DNS caches (2018-08-31)](https://rewindex.com/company/npm/incidents/v22ffls5cd6h)`


---
Canonical: https://rewindex.com/company/npm/incidents/v22ffls5cd6h · Markdown: https://rewindex.com/company/npm/incidents/v22ffls5cd6h.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/v22ffls5cd6h · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:58:44.670Z