🇦🇺 Melbourne Ping & Network Latency (MEL) | AS203314
Melbourne (MEL) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 18 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.
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.
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 18 other PoPs across 4 continents
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇦🇺 Melbourne (MEL) → 🇦🇺 Sydney (SYD) (9.8 ms) — Ultra-Low |
| Slowest Route | 🇦🇺 Melbourne (MEL) → 🇧🇷 São Paulo (GRU) (310.2 ms) |
| Average RTT | 187.9 ms |
| Average Jitter | 1.54 ms |
| Average Packet Loss | 0.06% |
| Best Fiber Efficiency | 84.9% |
| Intra-Region Peers | 5 PoPs in Asia Pacific |
| Total Routes | 18 outbound / 18 inbound (100% coverage) |
Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.
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.12% | Ultra-Low |
| 🇸🇬 Singapore (SIN) | 89.4 | 59.22 ms | 66.2% | 0.55 ms | 0.15% | Good |
| 🇯🇵 Tokyo (TYO) | 113.9 | 79.87 ms | 70.1% | 0.67 ms | 0.01% | Good |
| 🇭🇰 Hong Kong (HKG) | 128.1 | 72.38 ms | 56.5% | 0.74 ms | 0.03% | Good |
| 🇹🇼 Taipei (TPE) | 131.9 | 72.25 ms | 54.8% | 1.47 ms | 0% | Good |
| 🇺🇸 Los Angeles (LAX) | 147.2 | 125 ms | 84.9% | 1.64 ms | 0.14% | Good |
| 🇺🇸 Seattle (SEA) | 172.2 | 128.93 ms | 74.9% | 1.52 ms | 0.04% | Fair |
| 🇺🇸 Miami (MIA) | 199.5 | 152.69 ms | 76.5% | 1.7 ms | 0.06% | Fair |
| 🇺🇸 Ashburn (IAD) | 202.7 | 160.09 ms | 79% | 1 ms | 0% | Fair |
| 🇺🇸 New York (NYC) | 206.3 | 163.27 ms | 79.1% | 2.23 ms | 0.11% | Fair |
| 🇫🇷 Marseille (MRS) | 225.7 | 162.36 ms | 71.9% | 1.1 ms | 0.15% | Fair |
| 🇫🇷 Paris (PAR) | 236.4 | 164.4 ms | 69.5% | 2.01 ms | 0% | Fair |
| 🇷🇺 Moscow (MOW) | 238.1 | 141.13 ms | 59.3% | 2.48 ms | 0.09% | Fair |
| 🇬🇧 London (LON) | 239.6 | 165.48 ms | 69.1% | 2.02 ms | 0.07% | Fair |
| 🇩🇪 Frankfurt (FRA) | 240.2 | 159.77 ms | 66.5% | 1.98 ms | 0% | Fair |
| 🇳🇱 Amsterdam (AMS) | 245.1 | 161.98 ms | 66.1% | 2.9 ms | 0.05% | Fair |
| 🇩🇪 Berlin (BER) | 246.3 | 156.34 ms | 63.5% | 1.16 ms | 0.07% | Fair |
| 🇧🇷 São Paulo (GRU) | 310.2 | 128.34 ms | 41.4% | 2.39 ms | 0% | High |
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.07% | Ultra-Low |
| 🇸🇬 Singapore (SIN) | 89.4 | 59.22 ms | 66.2% | 0.94 ms | 0.19% | Good |
| 🇯🇵 Tokyo (TYO) | 111.1 | 79.87 ms | 71.9% | 1.33 ms | 0.06% | Good |
| 🇭🇰 Hong Kong (HKG) | 127.6 | 72.38 ms | 56.7% | 1.16 ms | 0% | Good |
| 🇹🇼 Taipei (TPE) | 134.5 | 72.25 ms | 53.7% | 0.65 ms | 0.15% | Good |
| 🇺🇸 Los Angeles (LAX) | 145.6 | 125 ms | 85.8% | 1.5 ms | 0.1% | Good |
| 🇺🇸 Seattle (SEA) | 172.6 | 128.93 ms | 74.7% | 1.55 ms | 0% | Fair |
| 🇺🇸 Miami (MIA) | 202.6 | 152.69 ms | 75.4% | 1.88 ms | 0.04% | Fair |
| 🇺🇸 New York (NYC) | 203.9 | 163.27 ms | 80.1% | 1.34 ms | 0% | Fair |
| 🇺🇸 Ashburn (IAD) | 204.3 | 160.09 ms | 78.4% | 1.22 ms | 0.04% | Fair |
| 🇫🇷 Marseille (MRS) | 225.6 | 162.36 ms | 72% | 2.53 ms | 0.09% | Fair |
| 🇫🇷 Paris (PAR) | 238 | 164.4 ms | 69.1% | 1.79 ms | 0.03% | Fair |
| 🇷🇺 Moscow (MOW) | 238.9 | 141.13 ms | 59.1% | 2.12 ms | 0.05% | Fair |
| 🇬🇧 London (LON) | 239.3 | 165.48 ms | 69.2% | 2.59 ms | 0.17% | Fair |
| 🇩🇪 Frankfurt (FRA) | 240.5 | 159.77 ms | 66.4% | 2.71 ms | 0.13% | Fair |
| 🇳🇱 Amsterdam (AMS) | 245.6 | 161.98 ms | 66% | 1.99 ms | 0.16% | Fair |
| 🇩🇪 Berlin (BER) | 246.6 | 156.34 ms | 63.4% | 1.84 ms | 0.01% | Fair |
| 🇧🇷 São Paulo (GRU) | 276.6 | 128.34 ms | 46.4% | 2.14 ms | 0.11% | 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 | 128.1 | Good |
| 🇸🇬 Singapore (SIN) | SIN | Singapore | 89.4 | Good |
| 🇦🇺 Sydney (SYD) | SYD | Australia | 9.8 | Ultra-Low |
| 🇹🇼 Taipei (TPE) | TPE | Taiwan | 131.9 | Good |
| 🇯🇵 Tokyo (TYO) | TYO | Japan | 113.9 | Good |
Data auto-generated on July 19, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 19 PoPs.
🇭🇰 Hong Kong Ping & Network Latency (HKG) | AS203314
Hong Kong (HKG) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 18 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 18 Hats Network (AS203314) backbone PoPs.