Statistics for ICMP round-trip time from Miami, USA to Melbourne, Australia: 200.7 ms average, jitter, packet loss and min/max latency.

🇺🇸 Miami, USA (MIA) → 🇦🇺 Melbourne, Australia (MEL)

Measurement round: 2026-08-15T04:03:13Z.

In the 2026-08-15T04:03:13Z round, ICMP echo RTT from Miami to Melbourne averaged 200.7 ms over 50 samples, with a minimum of 194.14 ms, a maximum of 218.98 ms, and no packet loss. The standard deviation of 5.43 ms and jitter of 4.3 ms make this a notably steady long-haul route.

Melbourne sits roughly 15,591.9 km from Miami, so the fiber floor is about 152.69 ms; the measured RTT is 1.31 times that floor, or 76.1% fiber efficiency. It was ranked 17th of 19 outbound routes in the same round, a position consistent with the long physical distance to Melbourne's southern Australian backbone.

The observed spread is roughly 2.7% of the average RTT, below the 3.08% median across the route set. That combination of low loss, moderate jitter, and better-than-median stability makes Miami-to-Melbourne a dependable path when consistent latency matters more than raw RTT.

Latency Summary

Metric	Value
RTT	200.7 ms
Jitter	4.3 ms
Packet Loss	0%
Standard Fiber Floor	152.69 ms
Fiber Efficiency	76.1%
Latency Tier	Fair
Source Region	North America
Destination Region	Asia Pacific

Ping Measurement Series

The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart.

Ping series: MIA → MEL

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 200.7 ± 0.77 ms (SE)

Sample distribution: box = interquartile range (196.8–202.7 ms), median 199.6 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.

How to read this chart

The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.

The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (152.7 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	195.33
2	100	194.14
3	200	203.77
4	300	197.06
5	400	195.05
6	500	195.30
7	600	195.06
8	700	198.79
9	800	196.96
10	900	199.95
11	1000	195.51
12	1100	200.82
13	1200	206.76
14	1300	213.36
15	1400	210.43
16	1500	202.74
17	1600	200.66
18	1700	202.53
19	1800	199.29
20	1900	200.23
21	2000	218.98
22	2100	212.37
23	2200	202.69
24	2300	200.46
25	2400	196.18
26	2500	202.63
27	2600	200.62
28	2700	210.68
29	2800	203.25
30	2900	197.24
31	3000	194.76
32	3100	206.79
33	3200	202.54
34	3300	204.20
35	3400	202.72
36	3500	207.22
37	3600	198.85
38	3700	199.87
39	3800	197.36
40	3900	202.82
41	4000	197.08
42	4100	197.63
43	4200	194.94
44	4300	199.27
45	4400	197.93
46	4500	196.15
47	4600	196.68
48	4700	196.08
49	4800	194.38
50	4900	198.89

Download This Route's Data

This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See About This Measurement for citation guidance.

Download this dataset

Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

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

Physical Reference	Value
WGS-84 geodesic distance	15,591.9 km
Vacuum RTT floor	104.02 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	152.69 ms
Low-latency fiber material floor	152.07 ms
Engineering floor (5% path allowance)	160.34 ms
Research 1.33× mapped-fiber reference	203.07 ms
Estimated unamplified path loss	3274.3 dB
Transparent optical spans / inline amplifiers	205 / 204
Published RTT inflation over fiber floor	1.31×

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 current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	194.14 ms
Average RTT	200.7 ms
Maximum RTT	218.98 ms
Standard deviation	5.43 ms
Stdev / average	2.7%

RTT trend

Estimated route stability across the selected time window.

Average: 201.0 ms
Minimum: 199.3 ms
Maximum: 202.5 ms
Average loss: 0.03%

Route Context

Departure PoP: Miami (MIA)
Destination PoP: Melbourne (MEL)
Region overview: North America → Asia Pacific
Corridor overview: North America to Asia Pacific
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Melbourne to Miami latency and RTT — 200.2 ms

Fastest routes departing Miami (MIA)

Miami to Ashburn latency and RTT — 27.3 ms
Miami to New York latency and RTT — 34 ms
Miami to Los Angeles latency and RTT — 56.8 ms
Miami to Seattle latency and RTT — 82 ms
Miami to London latency and RTT — 100.7 ms

Fastest routes arriving at Melbourne (MEL)

Sydney to Melbourne latency and RTT — 9.8 ms
Singapore to Melbourne latency and RTT — 87.8 ms
Tokyo to Melbourne latency and RTT — 111.3 ms
Hong Kong to Melbourne latency and RTT — 137.4 ms
Taipei to Melbourne latency and RTT — 143.6 ms

Same corridor (North America → Asia Pacific)

Seattle to Tokyo latency and RTT — 84.8 ms
Los Angeles to Tokyo latency and RTT — 100.9 ms
Seattle to Taipei latency and RTT — 115.1 ms

About This Measurement

Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA.

The measurement round behind this page is published as open data under CC BY 4.0 in the Hats Network latency dataset. Per-pair files are available at /opendata/latency/latest/pairs/mia-mel.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Melbourne round 2026-08-15T04:03:13Z, CC BY 4.0".

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

Miami, USA → Melbourne, Australia RTT