Singapore → Melbourne, Australia RTT
ICMP RTT measurements from Singapore, Singapore to Melbourne, Australia: average latency, jitter, packet loss, and stability for the SIN-MEL route.
🇸🇬 Singapore (SIN) → 🇦🇺 Melbourne, Australia (MEL)
Measurement round: 2026-08-16T04:07:28Z.
For round 2026-08-16T04:07:28Z, ICMP echo RTT from Singapore to Melbourne averaged 88.6 ms, with a minimum of 86.6 ms and a maximum of 94.44 ms across 50 samples. Loss was 0%, jitter was 1.59 ms, and the standard deviation was 1.9 ms, so the sample set was tightly grouped.
Melbourne is roughly 6,047 km from Singapore, where the fiber-floor estimate is 59.22 ms. The observed average is 1.5 times that floor, translating to 66.8% fiber-path efficiency — a reasonable result for an intercontinental Asia-Pacific path.
The route placed 4th among the 19 outbound routes in the network's Singapore egress set, and its variation-to-average figure is comfortably below the network median of 3.28%. With no packet loss and a max-to-min spread of about 7.8 ms, this route offers a dependable ICMP round-trip reference for Singapore–Melbourne connectivity in this round.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 88.6 ms |
| Jitter | 1.59 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 59.22 ms |
| Fiber Efficiency | 66.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: SIN → MEL
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 88.6 ± 0.27 ms (SE)
Sample distribution: box = interquartile range (87.2–89.1 ms), median 88.1 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 (59.2 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 91.65 |
| 2 | 100 | 88.41 |
| 3 | 200 | 87.38 |
| 4 | 300 | 88.03 |
| 5 | 400 | 90.42 |
| 6 | 500 | 88.08 |
| 7 | 600 | 87.12 |
| 8 | 700 | 86.78 |
| 9 | 800 | 88.85 |
| 10 | 900 | 87.66 |
| 11 | 1000 | 87.16 |
| 12 | 1100 | 88.19 |
| 13 | 1200 | 87.09 |
| 14 | 1300 | 86.79 |
| 15 | 1400 | 86.75 |
| 16 | 1500 | 86.62 |
| 17 | 1600 | 86.60 |
| 18 | 1700 | 91.61 |
| 19 | 1800 | 89.53 |
| 20 | 1900 | 88.27 |
| 21 | 2000 | 87.44 |
| 22 | 2100 | 86.85 |
| 23 | 2200 | 88.25 |
| 24 | 2300 | 90.65 |
| 25 | 2400 | 94.05 |
| 26 | 2500 | 89.71 |
| 27 | 2600 | 94.44 |
| 28 | 2700 | 90.72 |
| 29 | 2800 | 88.05 |
| 30 | 2900 | 90.26 |
| 31 | 3000 | 88.15 |
| 32 | 3100 | 87.18 |
| 33 | 3200 | 86.75 |
| 34 | 3300 | 86.83 |
| 35 | 3400 | 86.95 |
| 36 | 3500 | 86.79 |
| 37 | 3600 | 88.94 |
| 38 | 3700 | 87.41 |
| 39 | 3800 | 88.86 |
| 40 | 3900 | 92.74 |
| 41 | 4000 | 91.76 |
| 42 | 4100 | 88.80 |
| 43 | 4200 | 88.34 |
| 44 | 4300 | 87.45 |
| 45 | 4400 | 89.03 |
| 46 | 4500 | 87.40 |
| 47 | 4600 | 87.84 |
| 48 | 4700 | 88.86 |
| 49 | 4800 | 87.42 |
| 50 | 4900 | 89.09 |
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.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Singapore (1.28967, 103.85007) and Melbourne (-37.81400, 144.96332). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 6,046.9 km |
| Vacuum RTT floor | 40.34 ms |
| Standard fiber RTT floor () | 59.22 ms |
| Low-latency fiber material floor | 58.98 ms |
| Engineering floor (5% path allowance) | 62.18 ms |
| Research 1.33× mapped-fiber reference | 78.76 ms |
| Estimated unamplified path loss | 1269.9 dB |
| Transparent optical spans / inline amplifiers | 80 / 79 |
| Published RTT inflation over fiber floor | 1.5× |
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-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 86.6 ms |
| Average RTT | 88.6 ms |
| Maximum RTT | 94.44 ms |
| Standard deviation | 1.9 ms |
| Stdev / average | 2.1% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 88.6 ms
- Minimum
- 87.8 ms
- Maximum
- 89.2 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: Singapore (SIN)
- Destination PoP: Melbourne (MEL)
- Region overview: Asia Pacific → Asia Pacific
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Melbourne to Singapore latency and RTT — 88.4 ms
Fastest routes departing Singapore (SIN)
- Singapore to Hong Kong latency and RTT — 30.8 ms
- Singapore to Taipei latency and RTT — 45.8 ms
- Singapore to Tokyo latency and RTT — 68.9 ms
- Singapore to Sydney latency and RTT — 94.5 ms
- Singapore to Marseille latency and RTT — 140.6 ms
Fastest routes arriving at Melbourne (MEL)
- Sydney to Melbourne latency and RTT — 9.8 ms
- Tokyo to Melbourne latency and RTT — 113.9 ms
- Hong Kong to Melbourne latency and RTT — 138.4 ms
- Taipei to Melbourne latency and RTT — 142 ms
- Los Angeles to Melbourne latency and RTT — 148.2 ms
Same corridor (Asia Pacific → Asia Pacific)
- Melbourne to Sydney latency and RTT — 9.8 ms
- Hong Kong to Taipei latency and RTT — 14.7 ms
- Taipei to Hong Kong latency and RTT — 15.5 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/sin-mel.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0".
Data auto-generated on August 16, 2026. Explore the full interactive latency matrix or browse more city-pair routes.