What this estimate includes
The model charges for bytes that leave the source region toward the destination you select: public internet, another region of the same cloud, or (where a SKU exists) same-region traffic that the vendor bills. AWS’s and Azure’s monthly internet-out grants are applied when “include free tier” is on. Cloudflare R2 and Workers internet egress is documented at $0 on the public pricing pages we check, so the grant toggle does not change that row.
What it does not include
A real bill also contains pieces this page does not pretend to price. Call them out in your own budget rather than treating a zero as “free”:
- NAT gateway hours and NAT data processing
- Load-balancer or private-link data processing
- CloudFront, Cloud CDN, or Cloudflare CDN request and regional SKUs (the hit-ratio slider only shrinks origin-to-internet remainder)
- Inter-AZ traffic that some catalogs bill even inside one region
- Taxes, committed-use discounts, and private contracts
How to read the ranking
Providers are sorted by estimated monthly total for the inputs you typed, not by a claim that one cloud is “cheaper.” Change the destination from internet to cross-region and the order often changes: Google Cloud prices internet egress by geography, AWS by a simpler regional table, Cloudflare by a documented zero for R2/Workers internet out. If two rows look close, open the breakdown — free-tier grants and GB vs GiB assumptions move the number more than marketing pages admit.
Use the result to decide whether transfer belongs in the same region as compute, whether a CDN is worth the extra SKUs, or whether object storage with zero egress is the actual lever. Then confirm on the provider invoice. Sources and the last price check are on the methodology page.