🇦🇺 Melbourne Ping & Network Latency (MEL) | AS203314
Melbourne (MEL) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
🇦🇺 Melbourne (MEL)
Melbourne anchors Hats Network's southern Australian backbone with diverse path options across the Pacific and via Southeast Asia.
Measurement round: 2026-08-15T04:03:13Z.
This page provides round-trip time (RTT) latency metrics between the Melbourne (MEL) PoP and every other node on the Hats Network (AS203314) global backbone.
Average RTT from Melbourne to every other PoP
Round average of 19 measured routes, sorted slowest first · whiskers mark ±1 standard deviation within each round
How to read this chart
Each bar is the average round-trip time of one 50-probe ICMP echo round from Melbourne (MEL) to the destination PoP. The whisker at the end of each bar spans the average ± one standard deviation of that round — long whiskers mark jittery routes, short whiskers mark stable ones.
Full 19-destination dataset
| Destination | Avg RTT (ms) | Stdev (ms) | Distance (km) |
|---|---|---|---|
| Johannesburg (JNB) | 405.40 | 14.99 | 10,347 |
| São Paulo (GRU) | 307.90 | 12.62 | 13,105 |
| London (LON) | 257.10 | 8.68 | 16,898 |
| Berlin (BER) | 256.60 | 7.86 | 15,965 |
| Amsterdam (AMS) | 252.50 | 7.97 | 16,541 |
| Frankfurt (FRA) | 250.50 | 5.99 | 16,315 |
| Paris (PAR) | 243.60 | 10.32 | 16,788 |
| Moscow (MOW) | 235.90 | 7.04 | 14,412 |
| Marseille (MRS) | 233.40 | 6.97 | 16,579 |
| Ashburn (IAD) | 205.30 | 4.45 | 16,348 |
| New York (NYC) | 205.30 | 9.25 | 16,672 |
| Miami (MIA) | 200.20 | 8.60 | 15,592 |
| Seattle (SEA) | 169.50 | 5.30 | 13,166 |
| Los Angeles (LAX) | 147.70 | 2.24 | 12,764 |
| Taipei (TPE) | 141.70 | 6.80 | 7,378 |
| Hong Kong (HKG) | 137.40 | 4.26 | 7,391 |
| Tokyo (TYO) | 113.20 | 3.06 | 8,156 |
| Singapore (SIN) | 88.30 | 4.34 | 6,047 |
| Sydney (SYD) | 9.80 | 0.21 | 714 |
RTT vs. distance from Melbourne
Average RTT against great-circle distance for the same 19 routes · shaded bands mark latency tiers · points are colored by continent
How to read this chart
Each point is one destination PoP: the horizontal axis is the measured average RTT, the vertical axis is the WGS-84 great-circle distance from Melbourne. Points close to the bottom-left are routes that run near the physical fiber limit; points drifting upward-right follow longer paths. The shaded vertical bands mark the latency tiers (Ultra-Low <30 ms, Low 30–80 ms, Mid 80–150 ms, High >150 ms).
Underlying measurements
| Destination | Avg RTT (ms) | Distance (km) |
|---|---|---|
| Johannesburg (JNB) | 405.40 | 10,347 |
| São Paulo (GRU) | 307.90 | 13,105 |
| London (LON) | 257.10 | 16,898 |
| Berlin (BER) | 256.60 | 15,965 |
| Amsterdam (AMS) | 252.50 | 16,541 |
| Frankfurt (FRA) | 250.50 | 16,315 |
| Paris (PAR) | 243.60 | 16,788 |
| Moscow (MOW) | 235.90 | 14,412 |
| Marseille (MRS) | 233.40 | 16,579 |
| Ashburn (IAD) | 205.30 | 16,348 |
| New York (NYC) | 205.30 | 16,672 |
| Miami (MIA) | 200.20 | 15,592 |
| Seattle (SEA) | 169.50 | 13,166 |
| Los Angeles (LAX) | 147.70 | 12,764 |
| Taipei (TPE) | 141.70 | 7,378 |
| Hong Kong (HKG) | 137.40 | 7,391 |
| Tokyo (TYO) | 113.20 | 8,156 |
| Singapore (SIN) | 88.30 | 6,047 |
| Sydney (SYD) | 9.80 | 714 |
Fastest routes into Melbourne
Measured RTT from 19 other PoPs into Melbourne (MEL), sorted fastest first · each row spans min–max with a dot at the average
How to read this chart
Each row is one 50-probe ICMP echo round from another PoP into Melbourne (MEL): the line spans the minimum to maximum round-trip time observed, and the dot marks the average. Short rows are stable routes; rows sitting far right are slow ones. RTT is not symmetric — the path back into Melbourne can differ from the outbound path shown in the charts above.
Full 19-source dataset
| Source | Avg RTT (ms) | Min (ms) | Max (ms) | Distance (km) |
|---|---|---|---|---|
| Sydney (SYD) | 9.80 | 9.31 | 11.05 | 714 |
| Singapore (SIN) | 87.80 | 83.85 | 99.49 | 6,047 |
| Tokyo (TYO) | 111.30 | 106.15 | 131.83 | 8,156 |
| Hong Kong (HKG) | 137.40 | 134.39 | 147.99 | 7,391 |
| Taipei (TPE) | 143.60 | 137.35 | 161.06 | 7,378 |
| Los Angeles (LAX) | 145.40 | 140.77 | 154.01 | 12,764 |
| Seattle (SEA) | 171.40 | 163.98 | 188.68 | 13,166 |
| Miami (MIA) | 200.70 | 194.14 | 218.98 | 15,592 |
| Ashburn (IAD) | 203.40 | 192.25 | 242.64 | 16,348 |
| New York (NYC) | 205.90 | 195.79 | 240.19 | 16,672 |
| Marseille (MRS) | 234.30 | 226.80 | 246.06 | 16,579 |
| Moscow (MOW) | 236.10 | 222.69 | 261.35 | 14,412 |
| Paris (PAR) | 246.30 | 236.33 | 275.83 | 16,788 |
| Frankfurt (FRA) | 249.70 | 238.76 | 277.50 | 16,315 |
| Amsterdam (AMS) | 254.20 | 243.41 | 279.26 | 16,541 |
| Berlin (BER) | 255.80 | 243.27 | 295.40 | 15,965 |
| London (LON) | 258.50 | 254.09 | 273.79 | 16,898 |
| São Paulo (GRU) | 274.70 | 266.02 | 305.43 | 13,105 |
| Johannesburg (JNB) | 406.30 | 385.74 | 451.93 | 10,347 |
PoP Highlights
- Location: Melbourne, Australia (Asia Pacific)
- Region: Asia Pacific
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 2158177 — -37.81400, 144.96332
- Coverage: RTT measurements to 19 other PoPs across 5 continents
Facility & Interconnection
- Facility: MEL1
- Upstream transit: HE / Superloop
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇦🇺 Melbourne (MEL) → 🇦🇺 Sydney (SYD) (9.8 ms) — Ultra-Low |
| Slowest Route | 🇦🇺 Melbourne (MEL) → 🇿🇦 Johannesburg (JNB) (405.4 ms) |
| Average RTT | 203.2 ms |
| Average Jitter | 1.43 ms |
| Average Packet Loss | 0.08% |
| Best Fiber Efficiency | 84.6% |
| Intra-Region Peers | 5 PoPs in Asia Pacific |
| Total Routes | 19 outbound / 19 inbound (100% coverage) |
Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.
Geographic & Network Position
Melbourne sits on Hats Network's Asia Pacific backbone. Measured round-trip times to its 5 intra-region peers range from 9.8 ms (Sydney (SYD)) to 141.7 ms (Taipei (TPE)).
Melbourne anchors the southern Australian backbone with paths across the Pacific and via Southeast Asia.
Outbound Latency from Melbourne (MEL)
Round-trip time in milliseconds from Melbourne to all other backbone PoPs, sorted fastest to slowest.
| Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| 🇦🇺 Sydney (SYD) | 9.8 | 6.99 ms | 71.3% | 0.12 ms | 0.05% | Ultra-Low |
| 🇸🇬 Singapore (SIN) | 88.3 | 59.22 ms | 67.1% | 0.45 ms | 0.12% | Good |
| 🇯🇵 Tokyo (TYO) | 113.2 | 79.87 ms | 70.6% | 0.65 ms | 0% | Good |
| 🇭🇰 Hong Kong (HKG) | 137.4 | 72.38 ms | 52.7% | 1.19 ms | 0.04% | Good |
| 🇹🇼 Taipei (TPE) | 141.7 | 72.25 ms | 51% | 0.96 ms | 0.15% | Good |
| 🇺🇸 Los Angeles (LAX) | 147.7 | 125 ms | 84.6% | 1.13 ms | 0% | Good |
| 🇺🇸 Seattle (SEA) | 169.5 | 128.93 ms | 76.1% | 1.16 ms | 0% | Fair |
| 🇺🇸 Miami (MIA) | 200.2 | 152.69 ms | 76.3% | 1.37 ms | 0.14% | Fair |
| 🇺🇸 Ashburn (IAD) | 205.3 | 160.09 ms | 78% | 1.95 ms | 0.15% | Fair |
| 🇺🇸 New York (NYC) | 205.3 | 163.27 ms | 79.5% | 0.96 ms | 0.11% | Fair |
| 🇫🇷 Marseille (MRS) | 233.4 | 162.36 ms | 69.6% | 1.27 ms | 0.08% | Fair |
| 🇷🇺 Moscow (MOW) | 235.9 | 141.13 ms | 59.8% | 1.81 ms | 0% | Fair |
| 🇫🇷 Paris (PAR) | 243.6 | 164.4 ms | 67.5% | 2.28 ms | 0.17% | Fair |
| 🇩🇪 Frankfurt (FRA) | 250.5 | 159.77 ms | 63.8% | 1.61 ms | 0.16% | High |
| 🇳🇱 Amsterdam (AMS) | 252.5 | 161.98 ms | 64.1% | 2.36 ms | 0.14% | High |
| 🇩🇪 Berlin (BER) | 256.6 | 156.34 ms | 60.9% | 2.04 ms | 0.02% | High |
| 🇬🇧 London (LON) | 257.1 | 165.48 ms | 64.4% | 1.78 ms | 0.08% | High |
| 🇧🇷 São Paulo (GRU) | 307.9 | 128.34 ms | 41.7% | 1.79 ms | 0% | High |
| 🇿🇦 Johannesburg (JNB) | 405.4 | 101.33 ms | 25% | 2.37 ms | 0.06% | High |
Fastest Routes to Melbourne (MEL)
The 10 fastest measured routes to Melbourne, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.
| Rank | Source | Avg RTT | Min | Max | Stdev |
|---|---|---|---|---|---|
| 1 | 🇦🇺 Sydney (SYD) | 9.8 ms | 9.31 ms | 11.05 ms | 0.4 ms |
| 2 | 🇸🇬 Singapore (SIN) | 87.8 ms | 83.85 ms | 99.49 ms | 3.67 ms |
| 3 | 🇯🇵 Tokyo (TYO) | 111.3 ms | 106.15 ms | 131.83 ms | 5.18 ms |
| 4 | 🇭🇰 Hong Kong (HKG) | 137.4 ms | 134.39 ms | 147.99 ms | 2.62 ms |
| 5 | 🇹🇼 Taipei (TPE) | 143.6 ms | 137.35 ms | 161.06 ms | 4.85 ms |
| 6 | 🇺🇸 Los Angeles (LAX) | 145.4 ms | 140.77 ms | 154.01 ms | 3.55 ms |
| 7 | 🇺🇸 Seattle (SEA) | 171.4 ms | 163.98 ms | 188.68 ms | 5.88 ms |
| 8 | 🇺🇸 Miami (MIA) | 200.7 ms | 194.14 ms | 218.98 ms | 5.43 ms |
| 9 | 🇺🇸 Ashburn (IAD) | 203.4 ms | 192.25 ms | 242.64 ms | 9.05 ms |
| 10 | 🇺🇸 New York (NYC) | 205.9 ms | 195.79 ms | 240.19 ms | 8.8 ms |
Inbound Latency to Melbourne (MEL)
Round-trip time in milliseconds from all other PoPs to Melbourne. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.
| Source | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| 🇦🇺 Sydney (SYD) | 9.8 | 6.99 ms | 71.3% | 0.12 ms | 0.11% | Ultra-Low |
| 🇸🇬 Singapore (SIN) | 87.8 | 59.22 ms | 67.4% | 0.86 ms | 0% | Good |
| 🇯🇵 Tokyo (TYO) | 111.3 | 79.87 ms | 71.8% | 0.6 ms | 0.07% | Good |
| 🇭🇰 Hong Kong (HKG) | 137.4 | 72.38 ms | 52.7% | 1.09 ms | 0.07% | Good |
| 🇹🇼 Taipei (TPE) | 143.6 | 72.25 ms | 50.3% | 0.97 ms | 0% | Good |
| 🇺🇸 Los Angeles (LAX) | 145.4 | 125 ms | 86% | 1.15 ms | 0% | Good |
| 🇺🇸 Seattle (SEA) | 171.4 | 128.93 ms | 75.2% | 1.22 ms | 0.01% | Fair |
| 🇺🇸 Miami (MIA) | 200.7 | 152.69 ms | 76.1% | 1.32 ms | 0.12% | Fair |
| 🇺🇸 Ashburn (IAD) | 203.4 | 160.09 ms | 78.7% | 1.13 ms | 0.14% | Fair |
| 🇺🇸 New York (NYC) | 205.9 | 163.27 ms | 79.3% | 1.1 ms | 0% | Fair |
| 🇫🇷 Marseille (MRS) | 234.3 | 162.36 ms | 69.3% | 1.2 ms | 0% | Fair |
| 🇷🇺 Moscow (MOW) | 236.1 | 141.13 ms | 59.8% | 1.37 ms | 0.11% | Fair |
| 🇫🇷 Paris (PAR) | 246.3 | 164.4 ms | 66.7% | 1.35 ms | 0.13% | Fair |
| 🇩🇪 Frankfurt (FRA) | 249.7 | 159.77 ms | 64% | 2.91 ms | 0.09% | Fair |
| 🇳🇱 Amsterdam (AMS) | 254.2 | 161.98 ms | 63.7% | 1.73 ms | 0.16% | High |
| 🇩🇪 Berlin (BER) | 255.8 | 156.34 ms | 61.1% | 1.62 ms | 0% | High |
| 🇬🇧 London (LON) | 258.5 | 165.48 ms | 64% | 1.26 ms | 0% | High |
| 🇧🇷 São Paulo (GRU) | 274.7 | 128.34 ms | 46.7% | 1.98 ms | 0% | High |
| 🇿🇦 Johannesburg (JNB) | 406.3 | 101.33 ms | 24.9% | 3.08 ms | 0% | High |
Asia Pacific Peers
Melbourne is one of 6 Hats Network PoPs in Asia Pacific. Intra-region routes offer the lowest latency and highest path diversity.
| PoP | Code | Country | RTT (ms) | Tier |
|---|---|---|---|---|
| 🇭🇰 Hong Kong (HKG) | HKG | Hong Kong | 137.4 | Good |
| 🇸🇬 Singapore (SIN) | SIN | Singapore | 88.3 | Good |
| 🇦🇺 Sydney (SYD) | SYD | Australia | 9.8 | Ultra-Low |
| 🇹🇼 Taipei (TPE) | TPE | Taiwan | 141.7 | Good |
| 🇯🇵 Tokyo (TYO) | TYO | Japan | 113.2 | Good |
Frequently Asked Questions
What is the fastest route to Melbourne?
The fastest measured route to Melbourne (MEL) is Sydney (SYD) → Melbourne (MEL), averaging 9.8 ms RTT (Ultra-Low).
What is the fastest route from Melbourne?
The fastest measured route from Melbourne (MEL) is Melbourne (MEL) → Sydney (SYD), averaging 9.8 ms RTT (Ultra-Low).
How well connected is Melbourne to the Hats Network backbone?
Melbourne (MEL) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, Melbourne (MEL) → Johannesburg (JNB), averages 405.4 ms RTT.
Open Data
Measured latency data for Melbourne (MEL) is published daily under CC BY 4.0 as part of the Hats Network open latency dataset:
- Per-route files — every directed route from Melbourne is published as
mel-<destination>.pings.{csv,json,yaml}under/opendata/latency/latest/pairs/— for example mel-syd.pings.csv, the 50-probe ICMP echo round for Melbourne (MEL) → Sydney (SYD). - Dataset documentation — /opendata/latency/ covers file formats, versioning, checksums, and the aggregated full-matrix releases.
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 20 PoPs.
🇭🇰 Hong Kong Ping & Network Latency (HKG) | AS203314
Hong Kong (HKG) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
🇸🇬 Singapore Ping & Network Latency (SIN) | AS203314
Singapore (SIN) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.