How has the overall landscape of DDoS activity evolved, given that your data shows a 41 per cent rise in attacks in just a few months?
Other than the overall record increase of DDoS attacks in 2025, our recent Radar Report has shown that the landscape has also shifted in terms of location and attack type. Although South America and the Netherlands remain top sources for attacks, Hong Kong now accounts for 17 per cent of all network-layer and 10 per cent of all application- layer attacks. Tese findings indicate that attackers are expanding into emerging areas.
We’ve also seen a rapid increase in application layer attacks (28 per cent to 38 per cent) from Q3-Q4 2024 to Q1-Q2 2025) compared to network-layer attacks, revealing an overall trend toward multi- layered attacks. Tese application-layer attacks particularly impact sectors with a high degree of customer interaction like gaming. Today’s botnets already have enough firepower to take entire data centres offline, making the consequences of a successful attack truly catastrophic.
What lessons should hosting providers take from this incident regarding proactive cybersecurity investment and infrastructure design?
While gaming companies used to be the top DDoS attack target, threat actors are now shifting to attack their hosting providers in order to cause more widespread damage, and this incident is just one example of that new phenomenon. An attack on one hosting provider can have ripple effects: massive service outages and reputation damage to dozens of dependent companies. Tech now represents 30 per cent of DDoS attacks compared to gaming’s 19 per cent, so hosting providers need to recognise that they’re now at the frontline.
Tis attack also underscored an ongoing escalation in both the scale and sophistication of DDoS attacks today. Hosting providers need an equally layered defence approach that anticipates attacker strategies and protects critical digital assets holistically. Botnets will continue to evolve and exploit unsecured infrastructure, so hosting providers need to implement solutions capable of addressing the modern threat landscape.
Can you expand on the importance of globally distributed infrastructure in defending against attacks of this magnitude?
Globally distributed infrastructure is essential to defending against the sophisticated capabilities of modern threat actors for a few reasons. Firstly, Gcore’s 210+ PoPs enable scrubbing close to the source of the attack, which reduces the load on core systems. At the
same time, as I’ve mentioned, the 200+ Tbps total filtering capacity prevents any one single region from over-saturation, which allows for the low-latency filtering that is necessary to keep gaming and other applications online.
Finally, a global infrastructure ensures system resilience against multi-regional botnets like AISURU. With a presence that spans six continents, Gcore can accurately track the geographical sources of DDoS attacks using attackers’ IP addresses and the geographic locations of the data centres where malicious traffic is targeted. A global presence therefore enables greater visibility over the threat landscape.
In your experience, how often do you see attackers exploiting unsecured IoT or regional device networks, and what measures can enterprises take to reduce these vulnerabilities?
DDoS attacks are increasing in part because of the growth in unsecured IoT devices, and the recent 6 Tbps attack revealed the capability of botnets such as AISURU to exploit these devices to launch attacks of multi-regional origin and massive volumetric scale. Tis is sure to only increase in 2026.
Companies need solutions that deliver real-time detection, intelligent mitigation and global reach. However, DDoS defence is about more than a sophisticated solution or a proven track record. Staying ahead of DDoS threats requires a clear understanding of the evolving tactics and strategies employed by cyber attackers.
Finally, what does this incident tell us about the future of DDoS defence? Is AI-driven, integrated protection now a non-negotiable requirement?
In 2025, we have seen a shift toward more sophisticated, multi- layered attack strategies that target the application layer. Tis changes the defensive focus from the perimeter inward, toward the logic of user interactions.
Te application layer is much harder to protect: you need to filter out malicious traffic without harming the real application, which requires deep packet inspection to understand what’s inside and what the request is trying to do. In this context, the convergence of DDoS mitigation and L7 behavioural inspection has become critical. Attacks of this scale and intensity demonstrate that manual or reactive systems are no longer adequate. AI-driven, always on protection is necessary to secure modern hosting and tech infrastructure. A sophisticated, multi-layered approach must be the new standard for modern DDoS defence.
91
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134
