Cloudflare owned DNS service faced a Critical issue during the new interaction and goes down for 17 Minutes that lead to 1.1.1.1 DNS Resolver to be Globally Inaccessible.
Also, DDoS Mitigation system launch DDoS on its own infrastructure and no DDOS Attacks was protected while downtime being occurred.
DNS 1.1.1.1 was recently announced by Cloudflare which is one of the Internet’s Fastest DNS Service that extremely focuses to prevent sophisticated DDoS attacks.
Also, Cloudflare using Gatebot DDoS mitigation pipeline that performs hundreds of mitigations a day also Gatebot mainly protecting Cloudflare infrastructure and their customers from L3/L4 and L7 attacks.
Users Pointing their Router level DNS resolution at 1.1.1.1 on 31 May, 7:58 UTC would have experienced Exactly 17 Minutes disruption.
Cloudflare deploys mitigations for large DDoS attacks to reduce the CPU consumed by malicious traffic Also implemented multiple layers of defense.
The organization should always focus on their networks and make sure that you’re implementing best DDoS Mitigation Services Also you can check the DDoS Downtime using DDoS Downtime Calculator.
Today we mitigated 1.1.1.1 – https://t.co/AOeski90dO pic.twitter.com/kQrdo6eY3N
— Cloudflare (@Cloudflare) June 1, 2018
What Actually Went Wrong with Cloudflare’s Gatebot
Cloudflare was tried to deployed new code that introduced Gatebot to Provision API which is one of the Cloudflare’s internal integration points that helps to figure out the IP’s addresses belongs to one of Cloudflare’s addresses or not.
But Provision API didn’t know about that 1.1.1.0/24 and 1.0.0.0/24 are special IP ranges and during the integration work, they didn’t implement this manual exception.
Earlier time Cloudflare mitigations were applied manually by their tireless System Reliability Engineers and later Gatebot were introduced by Cloudflare to aid and reduce the manual Work.
In this case, Cloudflare forgot to implement this manual exception while They were doing the integration work.
So Cloudflare’s Gatebot suddenly started interpreting traffic to 1.1.1.1 as a DDoS attack on its infrastructure.
According to Cloudflare, The automatic systems deployed DNS mitigations for our DNS resolver IP ranges for 17 minutes, between 17:58 and 18:13 May 31st UTC. This caused 1.1.1.1 DNS resolver to be globally inaccessible.
In this case, Cloudflare was completely transparent and said, “We want to apologize to all of our customers. We will use today’s incident to improve. The next time we mitigate 1.1.1.1 traffic, we will make sure there is a legitimate attack hitting us.”
Also Read:
Dutch Banks are Suffering From Back to Back DDoS Attacks – Online Banking Goes Offline
15 Years Prison for 46-year-old Mexico Man Who Launched DDoS Attack against Ex-employer Websites
