Read the Docs在2026年6月中下旬经历了其历史上最大规模和最复杂的分布式拒绝服务攻击1。这次攻击持续了近十天，峰值时基础设施每分钟遭受550万个请求的冲击1，较正常日峰值的10万请求/分钟高出约100倍1。
攻击来自全球数百个网络及数百万个独立IP地址，包括住宅IP块和主要/次要托管提供商1。攻击者采用了高度自适应的策略，包括HTTP头部和TLS参数随机化、针对非缓存路径如404和302重定向的目标攻击，以及自适应的"Yo-Yo模式"行为1。
为应对这一威胁，Read the Docs实施了多层防御措施1。该平台依托Cloudflare CDN缓存、部署了IP、ASN、主机名和浏览器指纹等多维度速率限制规则、采用目标性的挑战验证而非全局JavaScript挑战，并通过Terraform管理基础设施代码1。最终，这些防御措施使服务在不对合法用户施加JavaScript挑战的情况下基本保持可用性1。
Read the Docs experienced its largest and most sophisticated distributed denial-of-service attack in mid-to-late June 2026, with traffic surging to approximately 5.5 million requests per minute at its peak—roughly 100 times the normal daily peak of 100,000 requests per minute 1. The assault persisted for nearly ten days and originated from millions of independent IP addresses spanning hundreds of autonomous systems globally, including residential IP blocks and major hosting providers 1.
The attack demonstrated advanced evasion techniques, including randomization of HTTP headers and TLS parameters, targeting of non-cached paths such as 404 errors and 302 redirects, and adaptive behavior patterns known as the "Yo-Yo" mode that adjusted tactics in response to defensive measures 1. To mitigate the incident while preserving service availability for legitimate users, Read the Docs deployed a multi-layered defense strategy that included Cloudflare CDN caching, rate limiting rules applied across multiple dimensions—encompassing IP addresses, autonomous system numbers, hostnames, and browser fingerprints—and targeted challenges rather than site-wide JavaScript verification 1. Infrastructure management through code-based tools like Terraform also played a role in the response 1. Throughout the attack, the platform maintained core service availability without subjecting legitimate users to JavaScript challenges 1.
评论
还没有评论，欢迎留下第一条。