Load Balancers are bandwidth neutral with traffic charges applied to the attached instances rather than the load balancer itself.
Vultr Load Balancers are bandwidth neutral. They do not incur separate bandwidth charges. Instead, all traffic routed through a load balancer is billed on the attached instances that send and receive the data.
When a client request enters through the load balancer and is forwarded to an instance, the traffic is counted as ingress on that instance. When the instance responds, the outbound traffic is billed as egress from that instance. The load balancer only distributes traffic, it does not add extra bandwidth usage on top of what your instances consume.
Each instance includes a monthly bandwidth quota based on its plan. Only egress traffic counts toward this quota. If your total outbound traffic exceeds the allowance, the standard overage rate of $0.01 per GB is appplied. This means that while the load balancer itself does not generate bandwidth costs, workloads with heavy traffic routed through it can increase egress usage on backend instances and lead to overage charges.
0 Comments
Be the first to comment and share your perspective with the community.