Hats Network | LogoHats Network
NetworkLatencyPairs

Ashburn to Melbourne Latency, Ping & RTT | AS203314

Ashburn to Melbourne ping and RTT: 204.3 ms, 1.22 ms jitter, 160.09 ms fiber floor, and 78.4% efficiency across AS203314. Updated 2026-07-19.

🇺🇸 This page compares the published ping and round-trip time (RTT) from Ashburn (IAD) to 🇦🇺 Melbourne (MEL) with vacuum and optical-fiber physical limits.

Latency Summary

MetricValue
RTT204.3 ms
Jitter1.22 ms
Packet Loss0.04%
Standard Fiber Floor160.09 ms
Fiber Efficiency78.4%
Latency TierFair
Source RegionNorth America
Destination RegionAsia Pacific

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Ashburn (39.04372, -77.48749) and Melbourne (-37.81400, 144.96332). It does not disclose either facility address.

Physical ReferenceValue
WGS-84 geodesic distance16,348.2 km
Vacuum RTT floor109.06 ms
Standard fiber RTT floor (ng=1.4679n_g=1.4679)160.09 ms
Low-latency fiber material floor159.45 ms
Engineering floor (5% path allowance)168.12 ms
Research 1.33× mapped-fiber reference212.92 ms
Estimated unamplified path loss3433.1 dB
Transparent optical spans / inline amplifiers215 / 214
Published RTT inflation over fiber floor1.28×

Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full theoretical fiber latency, GeoNames, attenuation, and amplifier methodology.

Stability & Trend

The following estimated indicators summarize route stability for the current publication period and are intended for comparative planning rather than SLA evaluation.

Stability IndicatorValue
Minimum RTT203.2 ms
Median RTT (p50)204.1 ms
95th percentile RTT (p95)206 ms
Maximum RTT207.4 ms
Jitter1.22 ms
Packet loss0.04%

RTT trend

Estimated route stability across the selected time window.

Average
204.1 ms
Minimum
202.3 ms
Maximum
205.8 ms
Average loss
0.03%

Route Context

About This Measurement

Published RTT reflects best-case backbone path behavior. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. Stability indicators are comparative estimates, and none of these values is an SLA.


Data auto-generated on July 19, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

On this page