Home » PC Tech & Gaming News » Cloudflare DDOS Attack Disrupts Dozens of Sites: Cloudflare down

Cloudflare DDOS Attack Disrupts Dozens of Sites: Cloudflare down

A massive web network Cloudflare has suffered a DDOS attack, knocking dozens of sites offline.

Updated: Jun 30, 2022 9:42 am
Cloudflare DDOS Attack Disrupts Dozens of Sites: Cloudflare down

WePC is reader-supported. When you buy through links on our site, we may earn an affiliate commission. Prices subject to change. Learn more

Earlier this month, millions of people awoke to outages across dozens of sites. Each of these outages was presumed to be an isolated incident, but as it turns out, they’re part of a much bigger picture. The Cloudflare DDOS Attack.

If you want to know more about this incident, Cloudflare should update its blog addressing this issue.

Update: Cloudflare is down again as of 30th June 2022. The cause is currently unknown.

Twinbrush Glitch 2

What is Cloudflare? 

Cloudflare is one of the world’s largest networks on the internet and has been providing safe and reliable web hosting for millions of companies around the world since 2010. The Cloudflare service acts as a reverse proxy for web traffic, meaning  Cloudflare is a server that sits in front of web servers and forwards client requests to web servers

Cloudflare mainly provides DDoS mitigation services that protect customers from distributed denial of service (DDoS) attacks, and they are very good at it – most of the time. 

The attack

Cloudflare is very used to providing its clients with DDoS protection, but over the last few months, Cloudflare has found itself a target of a few DDoS attacks. On the 27th of April 2022, Cloudflare managed to mitigate a 15M requests per second HTTPS DDoS attack. However, the attack was not successful. 

Today, however (21st of June 2022) somebody managed to launch a DDoS attack against Cloudflare, knocking out dozens of company websites that relied on its network and hosting services. We don’t yet know who launched the attack, but we estimate it may be the attackers that failed to take down Cloudflare just over a month ago. 

Affected sites 

Here’s a list of some of the sites affected by the Cloudflare DDoS attack. Note that when we say affected we don’t necessarily mean down. Users could experience anything from fully down webpages to minor load time increases. 

  • Us (WePC) – thanks attackers 
  • DIscord – a VOIP and instant messaging platform. 
  • Parcel force – a worldwide parcel delivery service.
  • Amazon Web Services – Amazons cloud services. 
  • Steam – a PC gaming platform.
  • Shopify – an E-commerce platform 
  • Bet 365 – a betting platform 
  • Nord VPN – a VPN providor 
  • Ring – a video doorbell service 
  • Coinbase – a digital asset exchange platform
  • Valorant – video game servers
  • Genshin Impact – video game servers
  • Twitter – a social platform
  • MEGA – a file hosting platform

There are many more affected sites than this, if you’d like a full list you can visit Down Detector and have a browse. 

The DDoS attack has been mitigated

It’s not all bad news, however, upon the completion of this article the issue was fixed, and services resumed to normal. The DDoS attack has been successfully mitigated by Cloudflare. 

It’s unknown yet how much damage the outage cost in terms of worldwide company revenue, but we expect it to be in the millions. The total outage time was around 1 hour.

Cyber attacks get more and more sophisticated by the day, and to counteract this so do ways to defend against them. We’re sure Cloudflare is going to use this opportunity to strengthen its defense against future attacks and come back stronger than it’s ever been. 


Jack is a Tech and News Writer who has a vast and proficient knowledge of CPUs, Motherboards, and Computer technology.

Trusted Source

WePC’s mission is to be the most trusted site in tech. Our editorial content is 100% independent and we put every product we review through a rigorous testing process before telling you exactly what we think. We won’t recommend anything we wouldn’t use ourselves. Read more