Cloud Egress Costs 2026: What It Really Costs to Leave AWS, Azure & GCP

Cloud & Infrastructure · Running Costs · ~18 min read

We priced what it costs to move 10 TB out of the major clouds, added the charges that don’t appear on the pricing page, and checked what the EU Data Act really changes in January 2027. Short version: the law fixes one scenario. Your bill lives in the other three.

BY OWEN CALDER · NOVEMBER 2026 · PRICES CHECKED AGAINST PUBLISHED RATES AS OF SEPTEMBER 2026

Every cloud migration plan I’ve reviewed has a slide that says “portable by design”. The containers are standard, the database is open source, the infrastructure is in Terraform. Then someone runs the transfer estimate for the data itself, and the project quietly goes back for another budget round.

That’s egress: what a provider charges for data leaving its network. Uploading is free everywhere. Downloading, serving, replicating and leaving are not. Nobody hides this — it’s on every pricing page — but very few teams model it until they’re already trying to move.

This post pulls together three things: published egress rates as compiled by the independent pricing index EgressCost (verified September 2026), a sharp recent analysis of exit costs by infrastructure architect Kees Baggerman on his blog My Virtual Vision, and our own arithmetic on top. I’ve split it into the questions I’d want answered before signing off any exit plan.

// how to read this

Rates are US-region internet egress unless stated, and change often — check the provider’s own page before you budget. Where a number is our calculation rather than a published figure, the table says so. Quotes are from published material and are attributed; nobody quoted has reviewed this post.

$ cat summary.txt

$0

Cost to send 10 TB to the internet from Cloudflare R2, which charges no egress at all

$1,137

The same 10 TB from Google Cloud on its Premium network tier

+73%

How much NAT and cross-zone charges can add to a 10 TB AWS bill (our calculation)

12.01.27

The date EU law bans switching charges — for one specific kind of move

// part one · the price list

What does leaving actually cost?

01

Why is egress priced so differently from ingress?

Because the asymmetry is the point. Free ingress removes every reason not to bring your data in. Metered egress means that the bigger your dataset grows, the more it costs to take it anywhere else. Providers will tell you it funds their global network — which is true — but it also works as a very effective retention mechanism.

The rates are published openly. AWS, for example, lists its data transfer tiers on the Amazon EC2 pricing page: the first 100 GB a month is free, the next 10 TB costs $0.09 per GB, and the rate steps down as volume grows.

// owen’s takeThe tier boundaries are binary on AWS: “first 10 TB” means 10,240 GB, not 10,000. It’s a small thing, but it’s exactly the kind of detail that makes two estimates of the same move disagree by a few percent.

02

So what does 10 TB cost, provider by provider?

Here’s the entry-tier rate for internet egress, and what a single 10 TB month costs on each. The spread between cheapest and most expensive is the entire bill.

Table 1 — 10 TB of internet egress in one month
ProviderEntry rate / GBFree allowance10 TB / month
Cloudflare R2$0.00All volumes$0
Oracle Cloud$0.0085 after allowance10 TB / month$0
Backblaze B2$0.01 (free to Cloudflare CDN)Partner network~$100
Microsoft Azure$0.087100 GB~$861
Amazon Web Services$0.09100 GB~$913
Google Cloud (Premium Tier)$0.12 first TB, then $0.11Minimal~$1,137

Hyperscaler and R2 figures: published rates as compiled by the EgressCost index, US regions, verified September 2026. Oracle and Backblaze figures are our calculation from the same published entry rates. Google’s Standard network tier is cheaper than Premium; price it in Google’s own calculator for your route.

03

Does the gap shrink as you move more data?

No — it grows. Per-GB rates fall with volume, but they never approach zero, so the absolute difference between providers keeps widening. Baggerman makes the same point about the curve: at around 1 PB, an exit costs roughly 61 times a 10 TB exit — cheaper per gigabyte, but nowhere near free.

“A 100 TB exit is not 10× the cost of a 10 TB exit. A 1 PB exit works out at about 61×, still expensive enough to derail a project plan that assumed the EU Data Act made it free.”— Kees Baggerman, My Virtual Vision
Table 2 — Monthly internet egress cost by volume
Monthly volumeTypical workloadAWSAzureGoogle (Premium)R2
1 TBSmall SaaS$83$78$123$0
10 TBMid-sized SaaS$913$861$1,137$0
50 TBLarger platform$4,395$4,182$4,413$0
100 TBMedia / heavy API$7,980$7,683$8,509$0

Source: EgressCost index, US regions, after free allowances, verified September 2026. We re-ran the AWS 100 TB line from the published tiers ($0.09 → $0.085 → $0.07) and got $7,978 — consistent.

04

Is that a lot, compared with what I already pay to store the data?

This is the comparison I find most useful, because it turns an abstract per-GB number into something a finance team instantly understands. If you keep data in standard object storage on AWS, taking it out once costs roughly three and a half to four months of storage rent.

Table 3 — The “exit tax” in months of storage (AWS, S3 Standard, us-east-1) — our calculation
DatasetStorage / monthStorage / yearOne-time egress to leaveExit = months of storage
10 TB~$236~$2,830~$913~3.9
100 TB~$2,304~$27,650~$7,980~3.5

Our calculation using S3 Standard list storage of $0.023/GB-month for the first 50 TB and $0.022 above, and the egress figures in Table 2. Excludes request charges, retrieval fees for colder storage classes, and the hidden meters below.

// part two · the meters you didn’t see

The pricing page shows one meter. Your bill has several.

05

What else gets charged when data moves?

Internet egress is the line everybody prices. The others sit inside the network path and are easy to miss in an estimate, because they don’t look like “egress” on the invoice. On AWS, the main ones are a NAT Gateway processing fee for traffic leaving private subnets, a charge in each direction for traffic crossing availability zones, and an hourly fee for every public IPv4 address.

Table 4 — The hidden meters, and what they add to a 10 TB month on AWS
ChargePublished rateWhen it appliesOn 10 TB
Internet egress (base)$0.09/GB (first 10 TB)Any data leaving AWS to the internet$913
NAT Gateway processing$0.045/GBTraffic from private subnets routed through NAT+$461
Cross-AZ transfer$0.01/GB each wayData crossing zones on its way out+$205
Public IPv4 addresses$0.005/hour each (~$43.80/yr)Every public IPv4 you holdper IP
Worst-case 10 TB monthNAT + cross-AZ on every byte~$1,579

Rates as published by AWS and compiled by the EgressCost index. Totals are our calculation for a worst case where all 10 TB passes through a NAT Gateway and crosses one zone boundary each way. That’s +73% on the base egress line — and it’s more common than it sounds in default VPC designs.

06

Are these prices going down?

Mostly they’re flat, and in one notable case they went up. On 1 May 2026, Google raised its North American peering egress rates — on CDN Interconnect, Direct Peering and Carrier Peering — from $0.04 to $0.08 per GiB. Standard internet egress didn’t change, so most workloads pay what they did before. But if you’d built a cost model around cheap peering, it just doubled.

The downward pressure comes from the zero-egress providers. Cloudflare R2, Backblaze B2 and Wasabi have spent the past two years making “store it somewhere that doesn’t charge you to read it” a credible default for media and backups.

// owen’s takeRun aws ec2 describe-addresses and count. I’ve yet to audit an account that didn’t have a few Elastic IPs attached to nothing, each quietly billing $43.80 a year. It’s small money, but it’s a perfect proxy for how closely anyone is watching the network bill.

// part three · the law

Doesn’t the EU Data Act make leaving free?

07

What exactly changes, and when?

Less than the headlines suggest, and with a specific date attached. Baggerman’s reading of Regulation (EU) 2023/2854 is the clearest I’ve seen, and he’s careful to note he’s an architect, not a lawyer — as am I. Check anything here with your own legal team.

11 January 2024

Reduced switching charges

Providers may only charge switching fees capped at the costs directly linked to the switch. Egress counts as a switching charge under Article 2(36).

Since then

Switching credits, on application

AWS, Azure and Google all offer free egress for customers leaving — but as a process you apply for, document and complete in a fixed window (60 days on Azure; 180 days on AWS for customers outside the EU), not as a default price.

September 2025

Google Data Transfer Essentials

Qualifying multicloud traffic for EU and UK customers is billed at zero once you opt in and declare it.

12 January 2027

Switching charges banned

Providers may no longer charge for switching at all. A one-way, permanent move off a provider becomes free by law.

08

So what’s still on the meter after January 2027?

Nearly everything that isn’t a clean, one-way exit. The ban covers switching. It doesn’t cover the traffic that most organisations actually generate.

“All of that is metered after January 2027 exactly as it is today.”— Kees Baggerman, on routine egress, multicloud, BCDR replication, in-parallel use and internal transfer
Table 5 — Which moves the Data Act actually makes free
ScenarioFree after 12 Jan 2027?Why
Full one-way exitYesThis is the “switching” the law covers
Exit test / round tripNoYou extract, test and come back — that isn’t switching
Running two clouds in parallelNot by defaultArticle 34(2) lets providers pass on their costs for in-parallel use
Partial rebalance to another cloudNoStandard egress, often at the most expensive tier because volumes are small
Backup / DR replicationNoRoutine traffic, metered as normal
Cross-zone, NAT, inter-regionNoInternal transfer, outside the switching definition
Serving your usersNoOrdinary internet egress

Summary of Baggerman’s reading of Articles 2(36), 29 and 34(2). Not legal advice.

09

Who should worry most?

Regulated financial firms in the EU. Under DORA, exit plans for critical outsourced services have to be tested, and a real exit test is a round trip — exactly the scenario the Data Act doesn’t cover. Baggerman models a 5,000-seat virtual desktop estate and finds the data that actually has to move — user profiles, golden images, session recordings, snapshots — usually lands at 100 to 250 TB, not the 50 TB the project plan assumed. That makes each test a recurring budget line rather than a one-off.

// owen’s takeYou don’t need to be a bank for this to matter. Swap “DORA exit test” for “we want to try a second provider for a quarter” and the economics are identical. The partial rebalance is the most common real-world move and the one with the worst per-GB rate.

$ git commit -m

“An exit plan that does not name the egress tariff, the volume estimate, and the mitigation path is documentation, not strategy.”

— Kees Baggerman, My Virtual Vision

// part four · what actually helps

Making the meter run slower.

10

Is a dedicated connection worth it?

At volume, yes. AWS Direct Connect, Azure ExpressRoute and Google Cloud Interconnect carry much lower per-GB rates than internet egress. Baggerman’s example: moving 250 TB over Direct Connect at $0.02/GB cuts the transfer line from $16,691 to $5,120 (using EU Ireland internet tiers). The catch is the port: a dedicated 10 Gbps connection runs about $2.25 an hour, roughly $1,640 a month, before cross-connect and carrier circuit costs. Since September 2026, AWS also offers flat-rate pricing on 10G and 100G dedicated connections.

So where’s the break-even? We ran it against a monthly 10 G port.

monthly cost: internet egress vs Direct Connect (10 G port + $0.02/GB)

10 TB internet
$913
10 TB via DX
$1,845
25 TB internet
$2,219
25 TB via DX
$2,152
40 TB internet
$3,524
40 TB via DX
$2,459

Our calculation: AWS internet tiers ($0.09 to 10 TB, $0.085 above), 1 TB = 1,024 GB, 100 GB free; Direct Connect at $0.02/GB plus a ~$1,640/month port. Ignores cross-connect, carrier circuit and any flat-rate option. Break-even lands around 24 TB a month — below that, the port costs more than it saves.

11

What else works, roughly in order of effort?

Most of the savings come from boring decisions made early. Here’s how I’d rank the options for a typical small-to-mid team.

Table 6 — Egress reduction options, ranked
TacticEffortBest forWhat it cuts
Delete what nobody needsLowEveryoneStale snapshots, old logs and recordings — cuts storage now and egress later
Compress before transferLowAPIs, logs, text-heavy dataBytes on the wire; text often shrinks dramatically
Put a CDN in frontLow–mediumStatic assets, media, downloadsOrigin egress, served from cache instead
Gateway endpoints for object storageLowPrivate workloads talking to S3NAT processing on that traffic
Move to IPv6 where possibleMediumNew servicesIPv4 charges and, in some designs, the need for NAT
Zero-egress storage for mediaMediumVideo, images, public datasetsInternet egress on read-heavy data
Dedicated interconnectHighSteady 25 TB+ a month, exit testsPer-GB rate, at the cost of a port
Separate “must leave” dataHigh (early)Anyone with an exit planThe volume you’d actually have to move

That last row is the one that pays off most and gets done least. If the data you’d need to take with you lives in the same buckets as telemetry, analytics and five years of logs, your exit project is much bigger than it needs to be. Keeping them separate costs nothing on day one.

$ cat exit-readiness.md

The exit-readiness checklist

If you can tick all of these, your exit plan is a plan. If you can’t, it’s a hope with a Terraform repo.

exit-readiness.md
  • A volume estimate of the data that physically has to move, split by type
  • The egress tariff that applies, with the source page and the date you checked it
  • Hidden meters included: NAT, cross-zone, inter-region, IPv4
  • The scenario named: one-way exit, round-trip test, parallel run or partial move
  • The mitigation chosen: switching credit, interconnect, or paid egress — with a cost
  • Lifecycle rules so you aren’t paying to move data nobody wants
  • “Must leave” data stored separately from everything else
  • At least one test run, with what it actually cost written down

$ man egress

Questions people ask

What is cloud egress?

The charge for data leaving a provider’s network — to the internet, to another cloud or to your own data centre. Data coming in (ingress) is free on every major provider.

Which cloud has the cheapest egress?

Cloudflare R2 charges nothing for egress, and Oracle includes 10 TB a month free. Among the three largest providers, Azure is slightly cheaper than AWS at entry level, and Google’s Premium Tier is the most expensive.

Does the EU Data Act make leaving my cloud free?

From 12 January 2027, a full one-way switch can’t be charged for. Round-trip tests, parallel running, partial moves, backups and internal transfer are still billed as normal.

What is a NAT Gateway charge?

On AWS, traffic from private subnets that goes out through a NAT Gateway is charged a processing fee of $0.045/GB on top of normal egress. Gateway endpoints for S3 avoid it for storage traffic.

When is Direct Connect worth it?

On our numbers, once you steadily move more than roughly 24 TB a month, or for large one-off exit tests. Below that, the monthly port fee costs more than the per-GB saving.

How do I find egress on my bill?

On AWS, filter Cost Explorer by usage types containing DataTransfer-Out, plus NAT Gateway and inter-AZ usage types. Azure and Google show it under bandwidth and network egress respectively.

Sources: published provider rates as compiled by the independent EgressCost index (verified September 2026); Kees Baggerman, “Egress Is the Second Lock-In: Modeling the Real Cost of Leaving Your Cloud Provider”, My Virtual Vision, November 2026; AWS published EC2 and S3 pricing. Calculations marked as ours are illustrative and use list prices only. Nothing here is legal advice on the EU Data Act or DORA.

Spotted a price that changed? Tell us — we update posts rather than delete them.

Contact Us

We'd love to hear from you