EC2 Network Throughput Calculator
Model an EC2 transfer across burst and baseline network bandwidth, with protocol overhead, to get a real transfer time.
Inputs
The 'up to' figure on the instance type page — sustainable only while network credits last.
What the instance holds indefinitely once burst credits are spent.
Headers, TLS, ACKs and window limits typically cost 8–15% of line rate.
Transfer Time
517.7minutes
Effective Burst Rate
1,406MB/s
Effective Baseline Rate
84MB/s
Moved While Bursting
2,531.3GB
Average Throughput Achieved
1.29Gbps
Burst Credit Verdict
Exhausts burst credits and falls back to the baseline rate
Step by step
Values used
Burst network bandwidth = 12.50 Gbps; Sustained baseline bandwidth = 0.7500 Gbps; Burst duration available = 30 minutes; Data to transfer = 5,000 GB; Protocol and encryption efficiency = 90 %
EC2 Network Throughput
MB/s = Gbps × 125 × efficiency; transfer time = burst window + remaining bytes ÷ baseline rate once credits are spent.
Transfer Time
= 517.7 minutes
Effective Burst Rate
= 1,406 MB/s
Effective Baseline Rate
= 84 MB/s
Moved While Bursting
= 2,531.3 GB
Average Throughput Achieved
= 1.29 Gbps
Burst Credit Verdict
= Exhausts burst credits and falls back to the baseline rate
How it works
Smaller EC2 instance types advertise an 'up to' network figure funded by a credit bucket and a much lower sustained baseline. Any transfer long enough to drain the bucket therefore runs in two phases, and the average throughput lands between the two rates — often far closer to the baseline. The efficiency factor accounts for headers, TLS and acknowledgements, which never let you reach the raw line rate. Sizing a migration or backup window off the 'up to' number is the single most common EC2 network planning error, and it can be an order of magnitude optimistic on a small instance.
Formula
EC2 Network Throughput
MB/s = Gbps × 125 × efficiency; transfer time = burst window + remaining bytes ÷ baseline rate once credits are spent.
- 125
- Conversion from Gbps to MB/s (1000 ÷ 8)
- burst
- Credit-funded 'up to' bandwidth on the instance type
- baseline
- Rate the instance sustains after credits run out
Frequently Asked Questions
How is EC2 Network Throughput calculated?
MB/s = Gbps × 125 × efficiency; transfer time = burst window + remaining bytes ÷ baseline rate once credits are spent. Smaller EC2 instance types advertise an 'up to' network figure funded by a credit bucket and a much lower sustained baseline. Any transfer long enough to drain the bucket therefore runs in two phases, and the average throughput lands between the two rates — often far closer to the baseline. The efficiency factor accounts for headers, TLS and acknowledgements, which never let you reach the raw line rate.
Why does EC2 Network Throughput matter?
Sizing a migration or backup window off the 'up to' number is the single most common EC2 network planning error, and it can be an order of magnitude optimistic on a small instance.
What values do I need to enter?
This calculator takes 5 inputs: Burst network bandwidth, Sustained baseline bandwidth, Burst duration available, Data to transfer, Protocol and encryption efficiency. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Which instance types have a sustained rate instead of a burst?
Generally the larger sizes: types at 4xlarge and above (and anything advertising a plain Gbps figure without 'up to') hold their rated bandwidth continuously. If a transfer window is critical, size up or split the transfer across instances.
You might also need
- EC2 Instance Cost CalculatorCommonly used together
- EC2 EBS Bandwidth CalculatorCommonly used together
- EC2 Fleet Capacity CalculatorCommonly used together
- EC2 Instance Right-Sizing CalculatorAlso in AWS Compute
- Reserved Instance Savings CalculatorAlso in AWS Compute
- EC2 Boot Time CalculatorAlso in AWS Compute