Layer 4 Load Balancing
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="proxy.php?url=https%3A%2F%2Fstatuscodefyi.com%2Fiframe%2Fglossary%2Flayer-4-load-balancing%2F" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://statuscodefyi.com/glossary/layer-4-load-balancing/
Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/glossary/layer-4-load-balancing/)
Use the native HTML custom element.
Load balancing performed at the OSI transport layer (Layer 4) using TCP/UDP IP addresses and port numbers to route traffic without inspecting application-layer content such as HTTP headers or URLs. L4 load balancers establish two TCP connections — one from client to LB and one from LB to backend — and forward bytes between them at very high throughput with minimal latency overhead. Because they do not parse application data, L4 balancers cannot perform URL-based routing, cookie-based sticky sessions, or TLS termination. Common implementations include AWS NLB, HAProxy TCP mode, and Linux's IPVS (used by kube-proxy in Kubernetes).