google_compute_route cost estimation
A VPC route is free. It tells traffic where to go within a network. The cost sits on the next hop it points at, such as a Cloud NAT gateway or a VM, and the egress it enables.
A google_compute_route is a static entry in a VPC routing table that directs traffic for a destination range to a next hop: an instance, an internal load balancer, a VPN tunnel, or the default internet gateway. Routes are free. There is no charge for the route, for the number of routes, or for traffic that a route directs.
The cost is always the next hop and the traffic. A default route to the internet gateway lets instances generate per-GB internet egress. A route pointing at a NAT setup relies on a Cloud NAT gateway (google_compute_router_nat) that bills per gateway-hour plus per-GB processing. A route to a VPN tunnel relies on Cloud VPN, which has its own hourly tunnel charge and egress. A route sending traffic through a next-hop instance turns that VM into a chokepoint that carries compute and egress cost.
The practical lever is what you route where. Routing Google API traffic through Private Google Access rather than a NAT next hop avoids NAT processing charges. c3x prices the NAT gateways, VPN tunnels, and egress that routes feed traffic into, and treats the routes themselves as the free direction they provide.
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "google_compute_route" "egress_internet" {
name = "egress-internet"
network = google_compute_network.main.id
dest_range = "0.0.0.0/0"
next_hop_gateway = "default-internet-gateway"
priority = 1000
}Pricing dimensions
What you actually pay for when you provision google_compute_route.
| Dimension | Unit | What's being charged |
|---|---|---|
| Route | free | The route, and any number of routes, have no charge. Traffic a route directs is not billed for routing. $0 |
| Next hop (NAT / VPN) | per hour + per GB | A route to a NAT or VPN next hop relies on a paid gateway that bills per hour plus per-GB data. Cloud NAT: ~$0.044/gateway-hour + $0.045/GB |
| Egress the route enables | per GB | Internet or cross-region egress generated by traffic sent along a route. ~$0.12/GB internet egress (Premium tier) |
Optimization tips
Common ways to reduce google_compute_route cost without changing the workload.
Prefer Private Google Access over a NAT route
Removes NAT processing on Google API trafficRouting Google API traffic through Private Google Access avoids sending it via a Cloud NAT next hop, removing NAT data-processing charges on that traffic.
Avoid next-hop instance bottlenecks
A route through a next-hop VM funnels traffic through one instance that pays compute and egress. Native Cloud NAT is usually cheaper and more scalable than a self-managed NAT VM.
Keep default routes scoped
A broad default route to the internet gateway lets any instance generate egress. Combine with tight firewall egress rules to keep the resulting per-GB cost predictable.
FAQ
Does a GCP route cost money?
No. Static and dynamic routes in a VPC are free, with no per-route charge. Cost comes from the next hop a route points at and the egress it enables.
Why does adding a route seem to increase my bill?
The route itself is free, but it enables traffic to a paid next hop. A route to a NAT gateway or VPN tunnel lets traffic flow through a billed component, and a route to the internet gateway enables per-GB egress.
How do I estimate the cost behind a route?
Price the next hop and the traffic. c3x prices Cloud NAT, Cloud VPN, and next-hop instances, plus the internet and cross-region egress the route feeds, and treats the route as free.
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including google_compute_route.