Formula & Calculator
Round Trip Time (Transmission + Propagation)
Estimates total round-trip time for a request-response exchange by combining transmission and propagation delays for both directions.
Interpretation
Round trip time (RTT) is the total time for a packet to travel to the destination and back. RTT = 2 × (transmission time + propagation time). Example: T_trans=1 ms, T_prop=20 ms → RTT = 2×(1+20) = 42 ms.
Variables
| Symbol | Quantity | Unit |
|---|---|---|
| RTT | Round-trip time | s |
| T_trans | Transmission time (one way) | s |
| T_prop | Propagation time (one way) | s |
What it means
Round‑trip time (RTT) is a fundamental network metric that measures the duration from the moment a packet is sent until its acknowledgment is received. It includes the sum of transmission times (serialization delays) and propagation delays on both the forward and reverse paths. Propagation delay depends on the physical distance and the speed of signal (typically near the speed of light), while transmission delay is determined by packet size and link speed. In practice, RTT also includes queuing and processing delays at routers. RTT is critical for TCP performance because it dictates the minimum time for the sender to react to congestion and determines the retransmission timeout. High RTT (e.g., satellite links) reduces throughput unless the window size is increased. RTT is measured using tools like ping. Understanding its components helps diagnose network bottlenecks and design applications that are resilient to latency. The formula illustrates that both transmission and propagation contribute, and optimizing either can improve overall performance.
Worked example
Round Trip Time – Two Examples
Real‑World| Parameter | Value |
|---|---|
| T_trans (each way) | 1 ms |
| T_prop (each way) | 10 ms |
| Parameter | Value |
|---|---|
| T_trans | 0.1 ms |
| T_prop | 0.5 ms |
Common mistakes
- Factor of 2: RTT is twice the one‑way time (transmission + propagation). Do not forget the factor 2.
- Propagation delay: This depends on distance and speed of light in the medium (e.g., fibre).
- Transmission delay: Packet size divided by bandwidth – separate from propagation.
- Queuing and processing: The formula does not include queuing or processing delays, which can add to RTT.
- Variable RTT: RTT can vary due to congestion; use measured RTT for accurate values.
Applications
Round trip time (RTT) is the total time for a packet to travel to a destination and back, including both transmission and propagation delays. It is a key metric in network performance, affecting TCP throughput, user experience, and application responsiveness. Engineers use RTT to tune timers, to design congestion control algorithms (e.g., TCP Reno, BBR), and to assess the performance of cloud services. In distributed systems, RTT influences consistency protocols and load balancing decisions. Understanding the components of RTT (transmission + propagation) helps in diagnosing network issues, selecting data centre locations, and optimising content delivery networks.
- TCP timer and retransmission tuning
- Performance analysis of web and cloud services
- Design of load balancers and CDN
- Geographic distribution of servers
- Real‑time application quality assessment
Frequently Asked Questions
RTT is the time it takes for a packet to travel from source to destination and back (including the time for the destination to process and send a response). The basic formula is RTT = 2 × (T_trans + T_prop), where T_trans is the transmission time for the packet (both directions) and T_prop is the one‑way propagation delay. In practice, RTT also includes queuing and processing delays at routers.
One‑way delay is the time for a packet to travel from source to destination. RTT is the round‑trip time, which is twice the one‑way delay (plus any processing/queuing). In TCP, RTT is measured by timing a packet and its ACK.
- Using one‑way propagation delay instead of RTT – for TCP, we need the round‑trip.
- Ignoring queuing and processing delays – these can add significant jitter and increase RTT.
- Assuming symmetric paths – the forward and reverse paths may have different delays.
- Using the formula for a single packet – RTT can vary with packet size because transmission time depends on size.
RTT includes the transmission time for the packet (and the ACK). Larger packets take longer to transmit, so RTT increases with packet size. For a 1500‑byte packet on a 100 Mbps link, transmission time is 120 µs each way, so it adds 240 µs to RTT.
TCP throughput is limited by the window size and RTT: Throughput ≤ Window / RTT. Therefore, a larger RTT reduces the achievable throughput for a given window size. This is why high‑latency links (e.g., satellite) require large TCP windows to achieve high throughput.
RTT is typically measured using the ping command, which sends an ICMP echo request and measures the time to receive the reply. It is also measured by TCP when calculating the retransmission timeout (RTO).
RTT consists of:
- Transmission time – for sending the packet and receiving the ACK.
- Propagation delay – light travel time.
- Queuing delay – time spent in router queues.
- Processing delay – time to process headers and generate ACK.
For multiple hops, the propagation delay is the sum of propagation delays on each link. The transmission time is still the total time to send the packet, but if store‑and‑forward is used, the transmission time at each hop may add. The RTT then becomes 2 × (sum of propagation delays + sum of transmission times) plus processing.
- Local LAN: < 1 ms.
- Cross‑country fiber: 20‑50 ms.
- Transatlantic fiber: 60‑100 ms.
- Geostationary satellite: ~500 ms (due to 35,000 km altitude).
- Online gaming – low RTT is essential for responsiveness.
- VoIP – delay must be < 150 ms for good quality.
- TCP performance tuning – adjusting window sizes.
- Geographic load balancing – routing requests to the closest server.