Cloud Load Balancer Calculator
Price a Google Cloud load balancer from forwarding rules, data processed and egress, and size it against peak traffic.
Inputs
The first five forwarding rules are billed at one blended hourly rate.
Monthly Cost
$824.10
Forwarding Rule Charge
$18.25
Data Processing Charge
$76.29
Internet Egress Charge
$729.56
Data Processed
9 TiB
Peak Throughput
655.4Mbps
Cost per Million Requests
$1.6482
Egress Share of the Bill
88.5%
Step by step
Values used
Forwarding rules = 3 rules; Rules covered by the base charge = 5 rules; Base charge for the included rules = 0.0250 USD/hour; Charge per additional rule = 0.0100 USD/hour; Requests per month = 500 millions; Average response size = 20 KB; Data processing price per GiB = 0.0080 USD/GiB; Share of responses leaving Google's network = 90 %; Internet egress price per GiB = 0.0850 USD/GiB; Hours in the billing month = 730 hours; Peak requests per second = 4,000 RPS
Cloud Load Balancer
monthly = (base rule charge + extra rules × per-rule charge) × hours + processed GiB × processing price + egress GiB × egress price, where processed GiB = requests × response size.
Monthly Cost
= 824.10
Forwarding Rule Charge
= 18.25
Data Processing Charge
= 76.29
Internet Egress Charge
= 729.56
Data Processed
= 10,240,000,000,000
Peak Throughput
= 655.4 Mbps
How it works
A Google Cloud load balancer has two very different cost components: a small fixed hourly charge per forwarding rule, and a per-GiB data processing charge that scales with traffic. Internet egress is billed on top and is usually several times the processing rate, which is why the egress share of the bill is called out separately. Teams optimise the hourly rule charge and ignore the per-GiB lines, when for any real traffic volume egress and processing dominate — compressing responses or serving them from cache moves the bill far more than consolidating rules. Confirm processing and egress rates for your region and destination in the Google Cloud pricing calculator.
Formula
Cloud Load Balancer
monthly = (base rule charge + extra rules × per-rule charge) × hours + processed GiB × processing price + egress GiB × egress price, where processed GiB = requests × response size.
- forwarding rule
- The billable front-end of a load balancer — the first five share one hourly charge
- processed GiB
- Bytes the load balancer handles, billed separately from internet egress
- egress share
- Portion of responses that leave Google's network and attract internet egress rates
Frequently Asked Questions
How is Cloud Load Balancer calculated?
monthly = (base rule charge + extra rules × per-rule charge) × hours + processed GiB × processing price + egress GiB × egress price, where processed GiB = requests × response size. A Google Cloud load balancer has two very different cost components: a small fixed hourly charge per forwarding rule, and a per-GiB data processing charge that scales with traffic. Internet egress is billed on top and is usually several times the processing rate, which is why the egress share of the bill is called out separately.
Why does Cloud Load Balancer matter?
Teams optimise the hourly rule charge and ignore the per-GiB lines, when for any real traffic volume egress and processing dominate — compressing responses or serving them from cache moves the bill far more than consolidating rules. Confirm processing and egress rates for your region and destination in the Google Cloud pricing calculator.
What values do I need to enter?
This calculator takes 11 inputs: Forwarding rules, Rules covered by the base charge, Base charge for the included rules, Charge per additional rule, Requests per month, Average response size, Data processing price per GiB, Share of responses leaving Google's network, Internet egress price per GiB, Hours in the billing month, Peak requests per second. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Do health checks and backend services cost extra?
Health checks are not billed separately. Backend services and URL maps are configuration objects rather than billable resources — the meters that matter are forwarding rules, data processed and egress.