Egress Fees and the Real Cost of Multi-Cloud
    Cost Optimization
    9 min read

    Egress Fees and the Real Cost of Multi-Cloud

    Every arrow that crosses a cloud, region, or zone boundary is metered. Current egress prices, where they bite, and how to estimate the bill before you move.

    Will Schulz
    Will Schulz
    CEO

    Multi-cloud architecture diagrams rarely show a price on the arrows. But every arrow that crosses a provider boundary, a region boundary, or even an availability zone boundary is metered, and for data-heavy systems those arrows can end up costing more than the boxes.

    This post covers what moving data actually costs at the major providers as of November 2026, where egress tends to bite in practice, a set of design rules that keep it under control, and how to estimate the bill before you move anything. Prices change often; treat every number below as a snapshot from the provider's own pricing pages.

    What the Meters Actually Say

    AWS gives every customer 100 GB of free data transfer out to the internet each month, aggregated across all services and regions except China and GovCloud [1]. Beyond that, the AWS Price List for US East (N. Virginia) lists internet egress at $0.090 per GB for the first 10 TB a month, $0.085 per GB for the next 40 TB, $0.070 per GB for the next 100 TB, and $0.050 per GB above 150 TB [2]. The same price list charges $0.010 per GB for regional data transfer in, out, or between EC2 availability zones, $0.01 per GB from N. Virginia to Ohio, and $0.02 per GB from N. Virginia to Oregon or Ireland [2].

    Google Cloud prices in GiB. Traffic between zones in the same region costs $0.01 per GiB, while traffic within a single zone over internal addresses is free [3]. Inter-region VM-to-VM traffic is $0.02 per GiB within North America or within Europe, $0.05 per GiB between North America and Europe, and up to $0.14 per GiB for routes touching South America [3].

    Azure's bandwidth page lists the first 100 GB a month of internet egress as free, then $0.087 per GB for the next 10 TB from North America or Europe, falling to $0.05 per GB in the highest published tier [4]. Inter-region transfer within North America or Europe is $0.02 per GB, and $0.05 per GB from those continents to another one [4].

    The cheaper end of the market looks very different. Cloudflare R2 lists Standard storage at $0.015 per GB-month and egress as free, charging instead for operations: $4.50 per million Class A requests and $0.36 per million Class B requests [5]. Hetzner includes 20 TB of traffic with its CX cloud servers in the EU and charges 1 euro ($1.20) per TB beyond that [6]. DigitalOcean includes a plan-dependent outbound allowance with each Droplet and bills additional outbound transfer at $0.01 per GiB, with inbound free [7]. On Vercel, the Hobby plan includes the first 100 GB of Fast Data Transfer, Pro pricing varies by region, and Fast Origin Transfer between the CDN and Vercel Functions is metered separately on both request and response bytes [8].

    The spread is the point. Twenty terabytes of monthly egress from AWS N. Virginia, priced on the tiers above, comes to roughly $1,790 [2]. The same volume fits inside a single Hetzner EU server's included allowance [6]. Where bytes leave from is an architectural decision, not a billing detail. Our egress fees reference table lists the published allowance and first-tier rate for all 17 platforms AW3 Host deploys to, with worked 1 TB and 10 TB examples.

    Where Egress Really Bites

    The expensive pattern is almost never a single big transfer. It is a chatty, steady-state flow that nobody budgeted because it looked like internal traffic on the diagram.

    Database in one cloud, compute in another

    This is the classic mistake. A team keeps its primary Postgres on AWS and moves application servers to another provider for cheaper compute or GPUs. Every query result now leaves AWS over the internet. If the application pulls 5 TB of result sets a month, that is about 5,020 billable GB after the free allowance, or roughly $450 a month at the first-tier rate [1][2], before counting what the other provider charges on its side for the queries and writes it sends back. Worse, the free 100 GB is shared across your whole AWS account, so in practice it is probably already spent [1].

    Replication and backups

    Continuous replication is a fixed tax that scales with your write volume, not your traffic. Replicating 1 TB of changes a day from N. Virginia to Ireland inside AWS costs about $614 a month at $0.02 per GB [2]. Sending the same 30 TB a month to a different cloud over the internet is priced as internet egress instead, roughly $2,650 a month on the published tiers [2]. Cross-cloud disaster recovery is often worth it, but the replication stream should be a line item in the decision, not a surprise.

    Logs, metrics, and traces

    Observability shipping is the flow most teams forget. Every log line, span, and metric sample that leaves a VPC for a third-party observability vendor is internet egress. At 50 GB of logs a day, roughly 1.5 TB a month, that is around $140 a month from AWS N. Virginia at first-tier rates [2], and verbose debug logging or high-cardinality traces can multiply it quickly. It creeps rather than spikes, which is why it goes unnoticed.

    Cross-AZ chatter inside one provider

    Even inside a single region the meter runs. At $0.01 per GB on both AWS and Google Cloud [2][3], a service mesh that routes requests to whichever replica is free, regardless of zone, can generate a meaningful bill on a busy cluster. Multi-zone availability is worth paying for; sending every cache read to another zone is not.

    Design Rules That Keep Egress in Check

    1. Keep data and compute together. The service that reads a dataset most often should run in the same provider and region as that dataset. If you want cheaper compute elsewhere, move the data with it. 2. Make the cross-boundary interface coarse. If two clouds must talk, send summaries, aggregates, and finished results across the boundary, not raw rows or per-request lookups. 3. Cache at the edge. Serve static assets and cacheable responses from a CDN so the origin sends each object once rather than once per user. AWS, for example, includes 1 TB a month of free transfer out from CloudFront [9]. 4. Compress everything that crosses a boundary. APIs, log shippers, and replication streams all benefit; JSON and logs shrink substantially. 5. Route by data locality. When you run in several places, send requests to the deployment that sits next to the data they need, rather than purely to the lowest-latency or lowest-cost endpoint. 6. Put zero-egress storage where reads fan out. Frequently downloaded objects such as model weights or media suit storage priced on operations rather than bandwidth, such as R2 [5]. 7. Filter observability at the source. Drop debug logs, sample traces, and aggregate metrics before they leave your network.

    Exit Waivers and the EU Data Act

    The big providers have softened the cost of leaving. On 5 March 2024, AWS announced free data transfer out to the internet for customers moving off AWS [9]. You request it through AWS Support and receive credits for the migrated data, and you do not have to close your account [9]. According to the post's update notes, eligible customers outside the EU get 180 days to complete the move, the earlier requirement to be transferring more than 100 GB a month was removed in September 2025, and eligibility now covers moving all data off AWS or all data off a particular service [9]. Google Cloud announced on 11 January 2024 that customers leaving Google Cloud for another provider or on-premises can migrate their data at no network data transfer cost, and said the offer applies to customers globally [10].

    The regulatory driver is the EU Data Act, Regulation (EU) 2023/2854, which applies from 12 September 2025 [11]. Article 29 allows providers to impose reduced switching charges from 11 January 2024 to 12 January 2027, capped at the costs directly linked to the switch, and bans switching charges entirely from 12 January 2027 [11]. The more interesting clause for multi-cloud teams is Article 34: when a service is used in parallel with another provider's service, providers may still charge data egress fees, but only to pass on the egress costs they incur, without exceeding them [11].

    The waivers and Article 29 are about leaving, a one-time migration. They do not make steady-state multi-cloud traffic free. Article 34 limits parallel-use egress charges to cost, but it does not abolish them. If your architecture depends on continuous cross-cloud data flows, plan to keep paying for them.

    How to Estimate Before You Move

    Do the arithmetic before the migration, not after the first invoice. 1. Draw every data flow, including replication, backups, log shipping, CI artifact pulls, and third-party API calls, and mark which ones cross a zone, region, or provider boundary. 2. Measure current volumes from flow logs, load balancer metrics, or your provider's cost and usage reports, in GB per month per flow. 3. Price each crossing flow using the sending provider's published rate for that path, and remember that tiers apply to aggregate monthly volume. 4. Add the steady-state total to the one-time migration cost, then check whether an exit waiver covers the migration portion. 5. Model growth. Price the flows at two or three times today's volume. 6. Compare the result against the savings that motivated the move. If cheaper compute elsewhere saves $2,000 a month but the new data path costs $2,500, the move is a loss.

    How AW3 Host Fits

    AW3 Host is a control plane for deploying to 17 providers, including AWS, GCP, Azure, Cloudflare, Hetzner, DigitalOcean, and Vercel, from one dashboard and API. Two parts of it are relevant here. Daily cost sync and budget policies help you notice when spend on a provider moves, so a creeping observability or replication bill is visible sooner. Weighted and geo routing let you send traffic to the deployment that sits next to its data, which is the locality rule above put into practice.

    What it will not do is make egress cheaper or redesign a chatty architecture for you. If your database lives on one provider and your compute on another, AW3 Host can deploy both and route between them, but the bytes still cross the boundary and the sending provider still bills for them.

    Takeaways

    Internet egress from the hyperscalers sits around $0.09 per GB at typical volumes, inter-region transfer around $0.02 per GB, and even cross-zone traffic is metered, while some providers include terabytes of transfer or charge nothing for it at all. Exit waivers and the EU Data Act reduce the cost of leaving, not the cost of running across clouds. Keep data and compute together, make cross-boundary interfaces coarse, cache and compress, route by locality, and price every arrow on the diagram before you commit to it.

    Sources

    1. Amazon EC2 On-Demand Pricing — Amazon Web Services, 2026
    2. AWS Price List: AWSDataTransfer offer file, US East (N. Virginia) — Amazon Web Services, 2026
    3. Network pricing — Google Cloud, 2026
    4. Bandwidth pricing — Microsoft Azure, 2026
    5. R2 pricing — Cloudflare, 2026
    6. Traffic — Hetzner Docs, 2026
    7. Bandwidth billing — DigitalOcean Docs, 2026
    8. CDN pricing and usage — Vercel, 2026
    9. Free data transfer out to internet when moving out of AWS — AWS News Blog, 2024
    10. Eliminating data transfer fees when migrating off Google Cloud — Google Cloud Blog, 2024
    11. Regulation (EU) 2023/2854 (Data Act) — EUR-Lex, Publications Office of the European Union, 2023
    EgressMulti-CloudFinOpsData Transfer
    Will Schulz
    Will Schulz
    CEO

    Writing about cloud infrastructure, DevOps best practices, and the future of application deployment. Follow for weekly insights on multi-cloud strategies and platform engineering.

    Stay Updated

    Get the latest articles on cloud infrastructure, DevOps, and platform engineering delivered to your inbox weekly.