Free tool
What is traffic between your availability zones costing you?
Enter the GB a month that cross availability zones, in total or by service pair. See the monthly cost on AWS, where both the sending and the receiving side pay, the same traffic on Google Cloud, and what Azure's pricing page says.
- Prices come from each vendor's own pricing page, with the date we checked them.
- Every result shows its formula and inputs, so you can check the math.
- Everything is calculated in your browser. Nothing you enter is sent anywhere.
Loading prices…
Results
Cross-AZ data transfer per month
AWS, per month
n/a
Google Cloud, per month
n/a
Kept in the zone
n/a
By service pair
| Traffic | GB crossing zones | AWS GB billed (both sides) | AWS per month | Google Cloud per month |
|---|
The math
Azure
Loading…
Check Azure's bandwidth pricing page for your Region before you assume the line item exists. This tool doesn't put a price on it.
Cutting it
Keep traffic in the zone, and know what it costs you
Topology-aware routing
In Kubernetes, send Service traffic to endpoints in the caller's zone. On 1.27 and later, add the annotation service.kubernetes.io/topology-mode: Auto; on 1.31 and later you can set trafficDistribution: PreferClose in the Service spec instead. Start with your highest-traffic Services.
Tradeoff: if one zone has two pods and another has eight, local routing overloads the small zone. Auto backs off when endpoints are too uneven; PreferClose does not. Check the per-zone endpoint counts first and fix the spread with topologySpreadConstraints.
Zone-local replicas
Read from a copy in your own zone. For Kafka, set broker.rack to each broker's AZ ID, set replica.selector.class=org.apache.kafka.common.replica.RackAwareReplicaSelector on the brokers, and set client.rack on each consumer to its own AZ ID (on MSK, use AZ IDs like use1-az1, not names like us-east-1a). For databases and caches, point readers at a replica in their zone.
Tradeoff: each extra replica costs money, and keeping it in sync is cross-zone traffic too. Followers can serve slightly stale reads. Keep databases, brokers and other stateful data multi-AZ: don't pin production to one zone to save on transfer.
How to check
Find your own numbers
- In Cost Explorer, group by usage type and look for entries ending in
DataTransfer-Regional-Bytes. The usage amount counts both sides, so pick "The bill's DataTransfer-Regional-Bytes usage" above when you use it. - To find the source, query the Cost and Usage Report in Athena for that usage type, grouped by
line_item_resource_id. - To see which services talk across zones, turn on VPC Flow Logs with a custom format that includes
az-id, map each destination to its subnet's AZ ID, and sumbyteswhere the two differ. Send them to S3 and turn them off after a week, since flow logs have their own cost. - The full query and commands are in Gotcha 5 of our free guide, 12 cloud bill gotchas.
Optional
Get the free guide: 12 cloud bill gotchas, and how to get the money back.
The calculator works without it. The signup sends only your email address.
Privacy
Your numbers stay on this page
- The calculator runs in your browser. The page loads its own price list from this site and sends nothing you type.
- Its Content-Security-Policy only allows connections back to this site, and it loads no third-party scripts, fonts or trackers.
- A shared link keeps your inputs after the
#, service pair names included. Browsers never send that part of a link to a server. - The only request with something you typed is the optional email signup. It sends your email address and the tool's name, nothing else.
Want us to look at the real thing?
Book a free 30-minute consult: we'll look at your bill with you, no obligation and no sales pitch. Or check your own cloud bill first with our free Cloud Bill Gotchas Checker.
Book a free 30-minute consult