# 🇦🇺 Melbourne Ping & Network Latency (MEL) | AS203314

## 🇦🇺 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-16T04:07:28Z`.

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](https://www.geonames.org/2158177) — -37.81400, 144.96332
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** MEL1
* **Upstream transit:** HE / Superloop

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------ |
| Fastest Route         | [🇦🇺 Melbourne (MEL) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mel-syd-rtt) (**9.8 ms**) — Ultra-Low |
| Slowest Route         | [🇦🇺 Melbourne (MEL) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/mel-jnb-rtt) (**405.5 ms**)     |
| Average RTT           | **203.0 ms**                                                                                                 |
| Average Jitter        | **1.75 ms**                                                                                                  |
| Average Packet Loss   | **0.04%**                                                                                                    |
| Best Fiber Efficiency | **84.2%**                                                                                                    |
| 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](/docs/network/latency/theoretical-fiber-latency).

## 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 **143.2 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](/docs/network/latency/pairs/mel-syd-rtt)**   | 6.99 ms     | 71.3%      | 0.12 ms | 0%    | Ultra-Low |
| 🇸🇬 Singapore (SIN)    | **[88.4](/docs/network/latency/pairs/mel-sin-rtt)**  | 59.22 ms    | 67%        | 0.89 ms | 0.02% | Good      |
| 🇯🇵 Tokyo (TYO)        | **[112](/docs/network/latency/pairs/mel-tyo-rtt)**   | 79.87 ms    | 71.3%      | 0.86 ms | 0%    | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[138.5](/docs/network/latency/pairs/mel-hkg-rtt)** | 72.38 ms    | 52.3%      | 1.39 ms | 0.19% | Good      |
| 🇹🇼 Taipei (TPE)       | **[143.2](/docs/network/latency/pairs/mel-tpe-rtt)** | 72.25 ms    | 50.5%      | 0.65 ms | 0%    | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[148.4](/docs/network/latency/pairs/mel-lax-rtt)** | 125 ms      | 84.2%      | 1.28 ms | 0.07% | Good      |
| 🇺🇸 Seattle (SEA)      | **[172.1](/docs/network/latency/pairs/mel-sea-rtt)** | 128.93 ms   | 74.9%      | 1.49 ms | 0%    | Fair      |
| 🇺🇸 Miami (MIA)        | **[201](/docs/network/latency/pairs/mel-mia-rtt)**   | 152.69 ms   | 76%        | 1.83 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[203.9](/docs/network/latency/pairs/mel-iad-rtt)** | 160.09 ms   | 78.5%      | 2.45 ms | 0.02% | Fair      |
| 🇺🇸 New York (NYC)     | **[204.2](/docs/network/latency/pairs/mel-nyc-rtt)** | 163.27 ms   | 80%        | 2.1 ms  | 0%    | Fair      |
| 🇫🇷 Marseille (MRS)    | **[233.5](/docs/network/latency/pairs/mel-mrs-rtt)** | 162.36 ms   | 69.5%      | 2.54 ms | 0%    | Fair      |
| 🇷🇺 Moscow (MOW)       | **[236.1](/docs/network/latency/pairs/mel-mow-rtt)** | 141.13 ms   | 59.8%      | 2.48 ms | 0.05% | Fair      |
| 🇫🇷 Paris (PAR)        | **[246.5](/docs/network/latency/pairs/mel-par-rtt)** | 164.4 ms    | 66.7%      | 1.53 ms | 0.13% | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[248.6](/docs/network/latency/pairs/mel-fra-rtt)** | 159.77 ms   | 64.3%      | 2.09 ms | 0.16% | Fair      |
| 🇬🇧 London (LON)       | **[252](/docs/network/latency/pairs/mel-lon-rtt)**   | 165.48 ms   | 65.7%      | 2.3 ms  | 0.04% | High      |
| 🇳🇱 Amsterdam (AMS)    | **[252.8](/docs/network/latency/pairs/mel-ams-rtt)** | 161.98 ms   | 64.1%      | 1.86 ms | 0%    | High      |
| 🇩🇪 Berlin (BER)       | **[254.7](/docs/network/latency/pairs/mel-ber-rtt)** | 156.34 ms   | 61.4%      | 1.95 ms | 0%    | High      |
| 🇧🇷 São Paulo (GRU)    | **[305.3](/docs/network/latency/pairs/mel-gru-rtt)** | 128.34 ms   | 42%        | 1.69 ms | 0%    | High      |
| 🇿🇦 Johannesburg (JNB) | **[405.5](/docs/network/latency/pairs/mel-jnb-rtt)** | 101.33 ms   | 25%        | 3.75 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](/docs/network/latency/pairs/syd-mel-rtt)**   | 9.38 ms   | 11.84 ms  | 0.46 ms |
| 2    | 🇸🇬 Singapore (SIN)   | **[88.6 ms](/docs/network/latency/pairs/sin-mel-rtt)**  | 86.6 ms   | 94.44 ms  | 1.9 ms  |
| 3    | 🇯🇵 Tokyo (TYO)       | **[113.9 ms](/docs/network/latency/pairs/tyo-mel-rtt)** | 107.58 ms | 128.46 ms | 4.6 ms  |
| 4    | 🇭🇰 Hong Kong (HKG)   | **[138.4 ms](/docs/network/latency/pairs/hkg-mel-rtt)** | 132.66 ms | 153.75 ms | 4.9 ms  |
| 5    | 🇹🇼 Taipei (TPE)      | **[142 ms](/docs/network/latency/pairs/tpe-mel-rtt)**   | 135.86 ms | 164.91 ms | 6.17 ms |
| 6    | 🇺🇸 Los Angeles (LAX) | **[148.2 ms](/docs/network/latency/pairs/lax-mel-rtt)** | 142.14 ms | 162.19 ms | 5.38 ms |
| 7    | 🇺🇸 Seattle (SEA)     | **[170.1 ms](/docs/network/latency/pairs/sea-mel-rtt)** | 164.93 ms | 189.47 ms | 4.46 ms |
| 8    | 🇺🇸 Miami (MIA)       | **[200.7 ms](/docs/network/latency/pairs/mia-mel-rtt)** | 190.44 ms | 231.45 ms | 9.1 ms  |
| 9    | 🇺🇸 Ashburn (IAD)     | **[203.9 ms](/docs/network/latency/pairs/iad-mel-rtt)** | 200.88 ms | 217.16 ms | 3.32 ms |
| 10   | 🇺🇸 New York (NYC)    | **[205.1 ms](/docs/network/latency/pairs/nyc-mel-rtt)** | 196.41 ms | 229.31 ms | 6.74 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](/docs/network/latency/pairs/syd-mel-rtt)**   | 6.99 ms     | 71.3%      | 0.12 ms | 0.19% | Ultra-Low |
| 🇸🇬 Singapore (SIN)    | **[88.6](/docs/network/latency/pairs/sin-mel-rtt)**  | 59.22 ms    | 66.8%      | 0.7 ms  | 0%    | Good      |
| 🇯🇵 Tokyo (TYO)        | **[113.9](/docs/network/latency/pairs/tyo-mel-rtt)** | 79.87 ms    | 70.1%      | 1.25 ms | 0.05% | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[138.4](/docs/network/latency/pairs/hkg-mel-rtt)** | 72.38 ms    | 52.3%      | 1.41 ms | 0%    | Good      |
| 🇹🇼 Taipei (TPE)       | **[142](/docs/network/latency/pairs/tpe-mel-rtt)**   | 72.25 ms    | 50.9%      | 1.12 ms | 0.08% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[148.2](/docs/network/latency/pairs/lax-mel-rtt)** | 125 ms      | 84.3%      | 1.74 ms | 0.06% | Good      |
| 🇺🇸 Seattle (SEA)      | **[170.1](/docs/network/latency/pairs/sea-mel-rtt)** | 128.93 ms   | 75.8%      | 0.98 ms | 0%    | Fair      |
| 🇺🇸 Miami (MIA)        | **[200.7](/docs/network/latency/pairs/mia-mel-rtt)** | 152.69 ms   | 76.1%      | 1.72 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[203.9](/docs/network/latency/pairs/iad-mel-rtt)** | 160.09 ms   | 78.5%      | 1.06 ms | 0.15% | Fair      |
| 🇺🇸 New York (NYC)     | **[205.1](/docs/network/latency/pairs/nyc-mel-rtt)** | 163.27 ms   | 79.6%      | 1.79 ms | 0.04% | Fair      |
| 🇫🇷 Marseille (MRS)    | **[234.2](/docs/network/latency/pairs/mrs-mel-rtt)** | 162.36 ms   | 69.3%      | 1.1 ms  | 0%    | Fair      |
| 🇷🇺 Moscow (MOW)       | **[235.9](/docs/network/latency/pairs/mow-mel-rtt)** | 141.13 ms   | 59.8%      | 1.11 ms | 0%    | Fair      |
| 🇫🇷 Paris (PAR)        | **[246.4](/docs/network/latency/pairs/par-mel-rtt)** | 164.4 ms    | 66.7%      | 1.59 ms | 0.17% | Fair      |
| 🇬🇧 London (LON)       | **[249.6](/docs/network/latency/pairs/lon-mel-rtt)** | 165.48 ms   | 66.3%      | 2.17 ms | 0%    | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[250.1](/docs/network/latency/pairs/fra-mel-rtt)** | 159.77 ms   | 63.9%      | 2.57 ms | 0%    | High      |
| 🇳🇱 Amsterdam (AMS)    | **[252.5](/docs/network/latency/pairs/ams-mel-rtt)** | 161.98 ms   | 64.1%      | 1.77 ms | 0.03% | High      |
| 🇩🇪 Berlin (BER)       | **[256.2](/docs/network/latency/pairs/ber-mel-rtt)** | 156.34 ms   | 61%        | 3.01 ms | 0.03% | High      |
| 🇧🇷 São Paulo (GRU)    | **[274.7](/docs/network/latency/pairs/gru-mel-rtt)** | 128.34 ms   | 46.7%      | 1.71 ms | 0.08% | High      |
| 🇿🇦 Johannesburg (JNB) | **[406.2](/docs/network/latency/pairs/jnb-mel-rtt)** | 101.33 ms   | 24.9%      | 2.56 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) | HKG  | Hong Kong | **138.5** | Good      |
| [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN  | Singapore | **88.4**  | Good      |
| [🇦🇺 Sydney (SYD)](./syd-sydney)       | SYD  | Australia | **9.8**   | Ultra-Low |
| [🇹🇼 Taipei (TPE)](./tpe-taipei)       | TPE  | Taiwan    | **143.2** | Good      |
| [🇯🇵 Tokyo (TYO)](./tyo-tokyo)         | TYO  | Japan     | **112**   | Good      |

## Frequently Asked Questions

**What is the fastest route to Melbourne?**

The fastest measured route to Melbourne (MEL) is [Sydney (SYD) → Melbourne (MEL)](/docs/network/latency/pairs/syd-mel-rtt), 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)](/docs/network/latency/pairs/mel-syd-rtt), 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)](/docs/network/latency/pairs/mel-jnb-rtt), averages **405.5 ms** RTT.

## Open Data

Measured latency data for Melbourne (MEL) is published daily under [CC BY 4.0](https://creativecommons.org/licenses/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/`](/opendata/latency/latest/pairs/) — for example [mel-syd.pings.csv](/opendata/latency/latest/pairs/mel-syd.pings.csv), the 50-probe ICMP echo round for [Melbourne (MEL) → Sydney (SYD)](/docs/network/latency/pairs/mel-syd-rtt).
* **Dataset documentation** — [/opendata/latency/](/opendata/latency/) covers file formats, versioning, checksums, and the aggregated full-matrix releases.

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) for side-by-side comparison across all 20 PoPs.*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/mel-melbourne).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.