TL;DR
- Solana withstands week-long DDoS attack, one of largest ever recorded.
- Network remained operational without a full shutdown under 6 Tbps peak traffic.
- Attack used distributed, multi-source flooding to overwhelm capacity.
Solana withstood a large-scale distributed denial-of-service attack that persisted for more than a week, according to network data shared by analyst. The assault reached a peak close to 6 terabits per second, ranking as the fourth-largest DDoS attack recorded against a distributed system. Despite the sustained pressure, the network continued operating without a full shutdown.
Launched in 2020, Solana operates as a proof-of-stake blockchain, relying on validators who lock SOL tokens to secure operations. High transaction throughput and fast processing helped the chain gain traction over recent years. At the same time, prior service interruptions placed reliability under scrutiny during earlier growth phases.
The recent attack relied on a classic denial-of-service method
Attackers flooded the network with excessive traffic in an attempt to overload capacity and block access for legitimate users. The scale increased risk, as traffic originated from multiple sources rather than a single point, raising the difficulty of filtering malicious requests.
A distributed attack spreads load across many origins, forcing defenders to manage traffic across wide vectors. Solana faced that challenge for several consecutive days. Network participants and infrastructure providers absorbed the influx while keeping core functions active, according to monitoring reports.
The episode highlighted both exposure and endurance
High throughput attracted hostile attention, while validator coordination and traffic controls limited broader disruption. Traders noted that the attack intensity placed Solana among the most targeted distributed systems recorded to date.
Solana’s experience added another data point to ongoing discussions around blockchain reliability under hostile conditions. The network remained accessible for users during the event, reinforcing confidence among developers and operators who depend on continuous availability for on-chain activity.
