Hats Network | LogoHats Network
NetworkLatencyPairs

Melbourne to Seattle Latency, Ping & RTT | AS203314

Melbourne to Seattle ping and RTT: 172.2 ms, 1.52 ms jitter, 128.93 ms fiber floor, and 74.9% efficiency across AS203314. Updated 2026-07-19.

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

Latency Summary

MetricValue
RTT172.2 ms
Jitter1.52 ms
Packet Loss0.04%
Standard Fiber Floor128.93 ms
Fiber Efficiency74.9%
Latency TierFair
Source RegionAsia Pacific
Destination RegionNorth America

Theoretical Fiber Latency

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

Physical ReferenceValue
WGS-84 geodesic distance13,166 km
Vacuum RTT floor87.83 ms
Standard fiber RTT floor (ng=1.4679n_g=1.4679)128.93 ms
Low-latency fiber material floor128.41 ms
Engineering floor (5% path allowance)135.4 ms
Research 1.33× mapped-fiber reference171.48 ms
Estimated unamplified path loss2764.9 dB
Transparent optical spans / inline amplifiers173 / 172
Published RTT inflation over fiber floor1.34×

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 RTT170.2 ms
Median RTT (p50)172.1 ms
95th percentile RTT (p95)174.3 ms
Maximum RTT174.9 ms
Jitter1.52 ms
Packet loss0.04%

RTT trend

Estimated route stability across the selected time window.

Average
172.0 ms
Minimum
170.3 ms
Maximum
174.1 ms
Average loss
0.02%

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