Skip to content
Cloudflare ยท Cloud and hostingJul 14, 2025, 21:52 UTC

1.1.1.1 public DNS resolver unreachable for 62 minutes

CriticalConfig changeUpdated 38h ago
Jul 14, 21:52 UTCJul 14, 22:54 UTC
Duration
1h 2m
Impact
Critical
Root cause
Config change
Cloudflare, 90 days
56 incidents
Affected
1.1.1.1 ResolverGateway DNSGlobal

Lesson: Latent config errors can sit for weeks; progressive deployment and legacy-system cleanup matter as much as the change that finally triggers them.

What happened

A service topology configuration error, introduced weeks earlier with no impact, was triggered by a later change and withdrew the 1.1.1.1 prefixes from Cloudflare data centers. Not an attack or a BGP hijack.

More from Cloudflare

Full history

Also caused by configuration change

All
StartedIncidentDuration
Sep 2423:36 UTCKey Value service restartsRender0m
Sep 2414:08 UTCThe Salesforce integration is unavailable for some customersHubSpot7h 18m
Sep 2218:20 UTCPhone Number APIs and Console Were Returning Incorrect 404 ResponsesTwilio0m
Sep 1211:04 UTCSome customers experiencing blurry image previews and download issuesSlack8h 56m
Sep 1107:18 UTCINC20000213Snowflake6h 1m
Sep 407:34 UTCINC20000199Snowflake2h 36m

Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Outages by email

Saturday mornings: the week's major outages, new postmortems and disclosed breaches, only in weeks that had some.

Double opt-in. Unsubscribe any time.