How long does a 10 TB data migration to the cloud take? WAN latency and the TCP window trap
A 10 TB cloud migration over 10 GbE at 40 ms RTT takes 70 days with the default 64 KB TCP window, or 2 hours 13 minutes with window scaling. Check which regime your stack lands in before committing to a cutover date.
A 10 TB cloud migration over a 10 Gbps private link with 40 ms round-trip time (a typical same-continent cloud interconnect) takes about 70 days when the default 64 KB TCP window is in play. With RFC 1323 window scaling enabled, the same transfer drops to 2 hours 13 minutes. The 700x gap between those two numbers is why latency modeling matters for migration planning and why a naive size-over-speed calculator will set you up for a missed cutover.
By TechCompare · Updated
Calculator
Data Transfer Calculator
Configuration
Latency & TCP window model
Window-limited to 13.1 MbpsModel is on with 40 ms RTT (Same continent) and a 64 KB unscaled TCP receive window. Change the settings below to see how a different RTT or window affects the transfer.
Coast-to-coast US, ~4000 km
Window scaling lets the TCP window grow past the 64 KB limit (up to 1 GiB). Modern Windows, Linux, and macOS enable it by default, but older firewalls, load balancers, and legacy consumer routers silently strip the option, reintroducing the 64 KB cap at ~40+ ms RTT.
Bandwidth-delay product limit
The TCP window, not the link, is the bottleneck. Your 10 Gbps connection is delivering 0.13% of its rated speed because the receive window (64 KB) can't stay full long enough at 40 ms RTT. That's the bandwidth-delay product at work.
Speed Comparison
How this is calculated
The naive math (10 TB divided by 10 Gbps) gives 2 hours 13 minutes, and that is what most transfer calculators return. It is the number you'd see only if window scaling is negotiated and the link is otherwise idle. With the unscaled 64 KB window and 40 ms RTT the throughput ceiling is 64 KB / 0.04 s = 13.1 Mbps, which is 0.13% of the 10 Gbps link. Scaling opens the window up to 1 GiB, which pushes the ceiling past the link rate so the transfer runs at the full 10 Gbps. The planning question is which of those two regimes your stack actually lands in, and the answer depends on the OS, the transfer tool, and whether anything along the path strips the TCP options.
Verdict
A 10 TB cloud migration over a 10 Gbps private link at 40 ms round-trip time takes about 70 days 15 hours with the default unscaled 64 KB TCP window, or 2 hours 13 minutes once RFC 1323 window scaling is negotiated and the window can grow past the 12 MB the bandwidth-delay product demands. The 700x gap between those two regimes is the structural reason a naive size-divided-by-speed calculator is dangerous for migration planning: the 2 hours 13 minutes figure is correct only if window scaling is on, the link is idle, and nothing along the path strips the TCP options, whereas the 70-day figure is what you actually get when any of those conditions fails. The planning move is to validate the scaling regime with a small probe transfer before committing a cutover date, because the difference between 2 hours and 70 days is the difference between a routine migration and a missed deadline.
More WAN scenarios
Related guides
Frequently asked questions
How long does a 10 TB cloud migration really take?
What is the bandwidth-delay product for 10 GbE at 40 ms?
Should I use a physical transfer appliance for a 10 TB migration?
Does rsync or SMB Multichannel help with WAN migration throughput?
Related tools
Display Bandwidth Calculator
Check if your HDMI/DP cable supports your resolution and refresh rate.
Use tool ➜RAID Calculator
Calculate usable capacity and fault tolerance for RAID 0, 1, 5, 6, and 10.
Use tool ➜RAM Latency Calculator
Convert DDR3/DDR4/DDR5 timings (CL, tRCD, tRP, tRAS) into true latency in nanoseconds.
Use tool ➜Data Read Visualizer
Visualize the massive speed difference between CPU cache, RAM, and storage.
Use tool ➜