1.1.1.1 public DNS resolver unreachable for 62 minutes
Jul 14, 21:52 UTCJul 14, 22:54 UTC
Duration
1h 2m
Impact
Critical
Root cause
Config change
Cloudflare, 90 days
50 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| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2318:42 UTC | Network Performance Degradation , Asia-Pacific | minor | Ongoing |
| Sep 2315:54 UTC | Elevated Errors with any / all in http_response_cache_settings | minor | 2h 14m |
| Sep 2309:08 UTC | Intermittent authentication errors for API and R2 | minor | 11h 51m |
| Sep 2308:09 UTC | Increased Errors for Durable Objects | minor | 1h 51m |
| Sep 2304:08 UTC | Elevated number of R2 503 errors in Australian Eastern Coast region | minor | 17m |
| Sep 2300:42 UTC | Issues with 1.1.1.1 for Families | minor | 44m |
Also caused by configuration change
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 2218:20 UTC |  Twilio | Phone Number APIs and Console Were Returning Incorrect 404 ResponsesTwilio | none | 0m |
| Sep 1211:04 UTC |  Slack | Some customers experiencing blurry image previews and download issuesSlack | minor | 8h 56m |
| Sep 1107:18 UTC |  Snowflake | INC20000213Snowflake | critical | 6h 1m |
| Sep 407:34 UTC | Snowflake | INC20000199Snowflake | critical | 2h 36m |
| Sep 109:58 UTC | Snowflake | INC20000190Snowflake | major | 3h 52m |
| Sep 108:01 UTC |  Sentry | Sentry requests timing out / 504'sSentry | major | 3h 20m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.