Networking costs explained: egress, transfer boundaries, NAT, and private connectivity

Start with a calculator if you need a first-pass estimate, then use this guide to validate the assumptions and catch the billing traps.

This is the cross-provider networking system budgeting parent page. Use it before you jump into one provider or one transfer path in isolation.

Most teams under-estimate networking because they model only internet egress. The reliable workflow is to list each boundary and price it separately: internet, cross-zone, cross-region, CDN origin egress, plus NAT/private endpoints. Move into provider-specific networking pages only after the broader network cost shape is clear.

When this page should be your main guide

• You still need to separate internet egress, transfer, NAT, private endpoints, and CDN-origin paths as distinct cost surfaces.
• You know networking is the problem but have not yet decided whether the next step is cross-provider or provider-specific.
• You want the broader system map before moving into AWS, Azure, or GCP network pages.

The biggest budgeting mistake is treating networking as one egress line

Network bills often become unpredictable because several boundaries expand together. Internet egress, cross-zone traffic, cross-region replication, NAT processed GB, and endpoint-hour charges do not behave the same way even if teams see them as one "network" bucket.

• Boundary confusion: teams pick rates before they have identified which path is billed.
• Topology drift: retries, cache misses, or routing changes quietly move traffic onto more expensive paths.
• Provider jump too early: readers often need the system map before a provider-specific deep dive is useful.

1) List your boundaries

• Internet egress: bytes to end users or external services.
• Cross-zone: east-west traffic across zones/availability zones.
• Cross-region: replication, DR, multi-region reads.
• CDN origin egress: origin to CDN cache fill.
• NAT / private endpoints: endpoint-hours + GB processed.

2) Estimate GB/month (practical methods)

• From provider billing exports (best).
• From throughput charts (Mbps to GB/month).
• From requests/day x average response size.

Network boundary worksheet

• Path A: internet to end users (public API, downloads, media).
• Path B: cross-zone east-west service traffic.
• Path C: cross-region replication and disaster recovery sync.
• Path D: origin-to-CDN cache fill transfer.
• Path E: NAT or private endpoint processed GB and endpoint hours.

3) Price each boundary separately

Provider-specific hubs

Start with a provider page only after the broader network cost shape is clear. AWS readers should move next to AWS network costs.

Spike triage checklist

1. Find which boundary moved first: internet, zone, region, or endpoint processing.
2. Check deploy and incident windows for retry amplification.
3. Verify cache hit rate and origin fetch behavior for CDN-backed services.
4. Re-run baseline and peak scenarios with corrected boundary inputs.

More networking guides

Related guides

Related calculators

FAQ