Start with the decision
Choose a provider by estimating how much data your application sends out, then comparing how each provider bills that outbound traffic. For projects that serve files or media, the per-gigabyte rate and the included traffic can matter more than the headline compute price.
Egress is data that leaves a provider's network. It includes responses sent to users, files downloaded from storage, and traffic sent to other networks. The egress fee is the charge for that outbound movement.
Egress surprises bills because it grows with success. A popular download or a busy API can send far more data than the compute behind it ever used. Inbound traffic is often not billed, which makes the outbound line easy to overlook until the invoice arrives.
Check how egress is priced
Providers price outbound data in a few common ways. Some charge a flat rate for each gigabyte sent. Others use tiers, where the rate drops as volume rises, or set different rates for each destination. Read the per-gigabyte price before comparing headline numbers.
Compare the rate for the destinations you actually use. Traffic to the public internet, to another provider, and to a different region can each carry its own rate. A low rate for a single destination can still cost more if most of your traffic goes elsewhere.
Look at the provider's pricing terms for the per-gigabyte rate, whether it is tiered, and which destinations are priced separately. Note whether the rates apply to every region or only some.
Check how much traffic is included
Some providers include a set amount of outbound traffic before any charge applies. Others cap the total they will charge in a month. Including traffic and capping the bill are different things, so a plan that includes traffic does not always cap the bill.
Look at whether the included traffic is counted monthly, across the whole account, or for each resource. Also find out whether unused amounts roll into the next month. Do not assume a plan's included traffic covers every service you run.
In the provider's documentation, look for the monthly included amount, how it is measured, and what happens when the limit is reached. Some limits slow service or halt it, rather than adding a charge, so read that part closely.
Check where traffic goes
Traffic between services in the same region is often billed at a lower rate, or not at all. Crossing regions, leaving a provider's network, or reaching another cloud is more likely to be billed. Placing storage and compute together can remove a large share of the outbound bill.
A private link between networks, sometimes called an interconnect, can change how outbound charges apply for large transfers. Its value depends on volume and on the providers involved. Read each provider's terms before assuming the link will lower the bill.
In the provider's pricing terms, look for the rules on same-region traffic, cross-region traffic, and any private link options. Rules like these often decide the bill more than the rate does.
Reduce egress with caching and a delivery network
Caching keeps copies of popular responses close to users, so fewer requests reach the origin server. Fewer origin requests mean less data leaving the origin network. A content delivery network, or CDN, does the same job across many locations at once.
Smaller responses help as well. Compress text, send only the fields a client needs, and serve large files from the region where most users are.
In the delivery provider's documentation, look for the outbound rate, whether cache hits are billed, and whether origin traffic is priced separately. Compare the full bill with your current setup before you switch.
Who should pick what
The right choice depends more on the shape of your traffic than on the headline price.
- Small projects with light traffic should look for a simple per-gigabyte rate and a clear included amount.
- Teams that serve large files or video should compare tiered rates and the cost of a delivery network.
- Applications that move data between their own services should favor same-region placement and check cross-region rules.
- Teams with steady, high outbound volume should ask providers about commitment options and read the private link terms.
Questions readers ask
- Egress and bandwidth: are they the same? Providers use the word bandwidth in different ways, so check what each term means in their documentation. Egress refers specifically to the outbound part.
- Inbound traffic: is it billed? Often it is not, but some providers do charge for it. Check the pricing terms for each direction.
- Delivery networks: do they remove outbound charges? They can lower origin egress because many requests are answered from cache. Their own delivery may still be billed, so compare the full bill.