Tokyo, Japan to Melbourne, Australia ICMP RTT measurement: 111.3 ms average, 0% packet loss, Good tier, route variability context.

🇯🇵 Tokyo, Japan (TYO) → 🇦🇺 Melbourne, Australia (MEL)

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

During the 2026-08-15T04:03:13Z round, 50 ICMP echo round-trip samples from Tokyo to Melbourne averaged 111.3 ms, with a minimum of 106.15 ms and a maximum of 131.83 ms. Zero packets were lost, and jitter was 3.7 ms, matching the Good latency tier.

The 8,156.1 km great-circle distance gives a vacuum floor of 54.41 ms and a direct-fiber floor of 79.87 ms. The measured average is 1.39 times that fiber floor, equivalent to roughly 72% direct-fiber efficiency; the route therefore sits moderately above the theoretical fiber minimum.

Within the same round, this route ranked 7th among the 19 outbound routes from Tokyo, placing it in the faster half of the set. Its standard deviation of 5.18 ms works out to about 4.7% of the 111.3 ms average, a little above the 3.08% median variability across the route set. The result is a stable mid-pack option for Japan-to-Australia traffic, with absolute latency dictated mostly by distance.

Latency Summary

Metric	Value
RTT	111.3 ms
Jitter	3.7 ms
Packet Loss	0%
Standard Fiber Floor	79.87 ms
Fiber Efficiency	71.8%
Latency Tier	Good
Source Region	Asia Pacific
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: TYO → MEL

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

Sample distribution: box = interquartile range (108.2–112.4 ms), median 110.0 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 (79.9 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	131.83
2	100	117.77
3	200	112.59
4	300	108.33
5	400	108.52
6	500	106.93
7	600	106.15
8	700	113.52
9	800	113.27
10	900	110.02
11	1000	117.83
12	1100	109.65
13	1200	106.67
14	1300	110.05
15	1400	127.19
16	1500	124.06
17	1600	112.14
18	1700	117.84
19	1800	112.42
20	1900	110.67
21	2000	116.68
22	2100	109.79
23	2200	107.23
24	2300	107.48
25	2400	111.48
26	2500	113.45
27	2600	108.81
28	2700	106.39
29	2800	106.61
30	2900	109.59
31	3000	108.41
32	3100	107.81
33	3200	107.08
34	3300	111.67
35	3400	111.78
36	3500	110.29
37	3600	109.97
38	3700	108.14
39	3800	107.58
40	3900	106.24
41	4000	112.33
42	4100	110.70
43	4200	108.57
44	4300	110.43
45	4400	109.09
46	4500	107.03
47	4600	114.84
48	4700	108.75
49	4800	108.26
50	4900	111.07

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 Tokyo (35.68950, 139.69171) and Melbourne (-37.81400, 144.96332). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	8,156.1 km
Vacuum RTT floor	54.41 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	79.87 ms
Low-latency fiber material floor	79.55 ms
Engineering floor (5% path allowance)	83.88 ms
Research 1.33× mapped-fiber reference	106.23 ms
Estimated unamplified path loss	1712.8 dB
Transparent optical spans / inline amplifiers	108 / 107
Published RTT inflation over fiber floor	1.39×

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	106.15 ms
Average RTT	111.3 ms
Maximum RTT	131.83 ms
Standard deviation	5.18 ms
Stdev / average	4.7%

RTT trend

Estimated route stability across the selected time window.

Average: 111.2 ms
Minimum: 110.4 ms
Maximum: 111.7 ms
Average loss: 0.03%

Route Context

Departure PoP: Tokyo (TYO)
Destination PoP: Melbourne (MEL)
Region overview: Asia Pacific → Asia Pacific
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Melbourne to Tokyo latency and RTT — 113.2 ms

Fastest routes departing Tokyo (TYO)

Tokyo to Taipei latency and RTT — 32.1 ms
Tokyo to Hong Kong latency and RTT — 45.6 ms
Tokyo to Singapore latency and RTT — 69.6 ms
Tokyo to Seattle latency and RTT — 84.6 ms
Tokyo to Los Angeles latency and RTT — 101.5 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
Hong Kong to Melbourne latency and RTT — 137.4 ms
Taipei to Melbourne latency and RTT — 143.6 ms
Los Angeles to Melbourne latency and RTT — 145.4 ms

Same corridor (Asia Pacific → Asia Pacific)

Melbourne to Sydney latency and RTT — 9.8 ms
Hong Kong to Taipei latency and RTT — 15.2 ms
Taipei to Hong Kong latency and RTT — 15.4 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/tyo-mel.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → 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.

Tokyo, Japan → Melbourne, Australia RTT