SYN Flood Explained
Half-open connections can fill tables faster than you think.
A SYN flood sends massive volumes of TCP SYN packets without completing the three-way handshake. The target allocates state for each SYN until memory and connection tables are exhausted.
Normal TCP handshake
Client sends SYN. Server replies SYN-ACK and reserves state. Client completes with ACK - connection established.
Each half-open SYN-ACK waits for a timeout if the final ACK never arrives.
Normal TCP handshake, left to right
- 01
SYN
The client requests a TCP connection.
- 02
SYN-ACK
The server acknowledges the client's SYN and sends its own SYN.
- 03
ACK
The client confirms; the connection is established and data can flow.
How the attack works
Attackers spoof source IPs or use botnets to send SYN packets. The server responds with SYN-ACK to forged addresses, leaving half-open entries.
Even high-performance servers and load balancers can degrade when the SYN queue fills - legitimate users see timeouts.
SYN flood, from packet to impact
- 01
SYN requests
Bots or spoofed sources send a high rate of TCP connection-start packets.
- 02
Half-open state
The target sends SYN-ACKs and waits for final ACKs that never arrive, consuming connection capacity.
- 03
Service pressure
As state queues fill, legitimate connection attempts time out. Edge filtering drops abnormal SYN traffic before it reaches the origin.
SYN-ACK flood
SYN-ACK is normally the server's reply to a SYN. A flood of unsolicited SYN-ACKs consumes bandwidth and packet-processing capacity; spoofed SYN requests can also make third-party servers reflect replies toward a victim.
TMW Shield evaluates TCP flags, flow direction and service baselines to mitigate anomalous or reflected packets upstream while preserving expected handshakes.
SYN-ACK flood, left to right
- 01
Unexpected SYN-ACK
The target receives replies without matching connection requests.
- 02
Traffic pressure
Flooded or reflected packets consume bandwidth and processing.
- 03
Validate at the edge
TMW Shield checks flow context and drops anomalous traffic while passing valid sessions.
ACK flood
ACK packets are normal in established TCP sessions, so the flag alone is not proof of an attack. At high rates, ACK floods can pressure links and packet-processing systems.
TMW Shield uses rate, flow context and the protected service profile rather than blocking ACK flags indiscriminately.
ACK flood, left to right
- 01
High-rate ACKs
Distributed sources send excessive TCP ACK packets to a protected service.
- 02
Capacity pressure
Traffic consumes link and packet-processing capacity even when packets look valid.
- 03
Context-aware filtering
Edge rules compare behavior with service expectations, then drop attack traffic and pass legitimate sessions.
Mitigation techniques
SYN cookies: encode state in the SYN-ACK sequence number instead of storing it - Linux supports this natively.
Edge scrubbing drops abnormal SYN rates before they hit origin. Rate limits per source /24 and challenge mechanisms on L7 reverse proxies complement L4 filtering.
SYN flood FAQ
- SYN floods are Layer 4 (transport) because they abuse TCP mechanics, even if targeting port 443.
Stop SYN floods before they reach your server
TMW Shield detects abnormal SYN rates within seconds and filters before your router's connection table saturates.