Solana withstood a massive 6 Tbps DDoS attack without interruptions: a milestone for the network

By the end of 2025, Solana demonstrated unprecedented resilience by keeping its network operational during a sustained DDoS attack of approximately 6 terabits per second for several weeks. This event marks a significant turning point for a network that previously faced severe criticism for vulnerabilities to such attacks. Co-founder Anatoly Yakovenko publicly announced the incident on December 9, describing it as the worst active threat Solana has faced, although the network experienced no impact on its operation.

Solana’s ability to absorb an attack of this magnitude without service degradation represents a qualitative leap in blockchain infrastructure engineering. Throughout the assault, slot latency remained at zero, meaning validators continued producing blocks without detectable delays. Pipe Network, a critical infrastructure provider for Solana, verified these data, confirming that transaction confirmations stayed around 450 milliseconds on average, with P90 confirmations below 700 milliseconds.

To contextualize the scale of the event, a 6 Tbps volumetric attack generates billions of packets per second directed at network infrastructure. Under such pressure, it would be normal to see significant increases in latency, block loss, or delays in transaction confirmations. However, Solana maintained its nominal performance, suggesting substantial advances in network architecture.

Resilient Infrastructure: How Solana Withstood the Assault

Solana’s performance during the sustained DDoS reflects deliberate investments in infrastructure improvements made over recent years. Mert Mumtaz, CEO of Helius, noted that most users remained completely unaware of the attack thanks to the level of engineering deployed by the Solana team. This approach contrasts with how similar situations were handled a few years ago.

Among the implemented improvements is Firedancer, a next-generation validator client developed by Jump Crypto, specifically designed to optimize performance under extreme stress conditions. These infrastructural updates have transformed how Solana handles potential threats to its network.

From Turbulent Past to Solid Present

Solana’s current ability to resist DDoS attacks sharply contrasts with its history in 2021 and 2022. During that period, the network experienced multiple outages caused by similar incidents. In September 2021, an attack during a token sale event took the network offline for 17 hours. Additional incidents in December 2021 and January 2022 raised concerns about centralization and the architectural robustness of the blockchain.

May 2022 marked the most critical point, when a DDoS attack caused the seventh outage of the year, fueling doubts about Solana’s reliability as production infrastructure. Since then, the network has reported zero outages since May 2023, demonstrating that engineering investments have had tangible effects.

Implications for the Future of DDoS in Blockchain

Although the 6 Tbps attack is significant, the global cybersecurity landscape shows even larger attacks in 2025. Cloudflare mitigated incidents exceeding 29.7 Tbps during the third quarter, mainly orchestrated by the Aisuru botnet. Microsoft Azure blocked a 15.72 Tbps attack targeting Australian infrastructure in October. This contextualizes Solana’s achievement: maintaining functionality under 6 Tbps pressure remains exceptional in the blockchain space, though it does not set a global record for attacks.

In market terms, the price of SOL has remained relatively stable despite the event. According to recent data, Solana trades at $85.25 with a market capitalization of $48.69 billion. The network has shown robust activity, reflecting confidence in its improved architecture among users and institutional investors.

This episode underscores that developments in security and resilience of blockchain networks are as critical as scalability. Solana has turned a historical vulnerability into a competitive differentiator, demonstrating that the issue was not inherent to its consensus design but required infrastructure refinements that have now been successfully realized.