Today we mitigated 1.1.1.1
Jun 1, 2018Marek Majkowski

Summary
This post details an incident where Cloudflare's internal DDoS mitigation system, Gatebot, mistakenly identified legitimate traffic to the 1.1.1.1 DNS resolver as an attack due to a new integration with the Provision API. This led to a 17-minute outage of the 1.1.1.1 service. The post highlights the complexity of Gatebot's reactive automation stage and the importance of thorough testing when integrating new systems, especially those that interact with critical infrastructure like DNS resolvers. It underscores a lesson learned in improving internal systems and testing procedures for future mitigation efforts.
More from the Website Security & Threat Management trail
- We tested our own WAF with frontier AI models. Here’s what we found
- When scanners miss the attack: how Cloudflare Client-Side Security protects storefronts
- Introducing automatic remediation policies with Cloudflare CASB
- Introducing context-aware vulnerability discovery and remediation with Cloudflare Managed Defense and OpenAI Daybreak Models
- Introducing Adaptive Intelligence: undermining the economics of every bot attack