# 🇦🇺 Sydney Ping & Network Latency (SYD) | AS203314

## 🇦🇺 Sydney (SYD)

Sydney is Australia's primary internet gateway and the landing point for major trans-Pacific cables connecting Australia to the Americas and Asia.

Measurement round: `2026-08-16T04:07:28Z`.

This page provides round-trip time (RTT) latency metrics between the **Sydney (SYD)** PoP and every other node on the Hats Network (AS203314) global backbone.

### PoP Highlights

* **Location:** Sydney, Australia (Asia Pacific)
* **Region:** Asia Pacific
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 2147714](https://www.geonames.org/2147714) — -33.86785, 151.20732
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** SYD1
* **Upstream transit:** HE / Superloop
* **Peering / IX:** Equinix SY

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------ |
| Fastest Route         | [🇦🇺 Sydney (SYD) → 🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/syd-mel-rtt) (**9.8 ms**) — Ultra-Low |
| Slowest Route         | [🇦🇺 Sydney (SYD) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/syd-jnb-rtt) (**412.5 ms**)        |
| Average RTT           | **201.2 ms**                                                                                                 |
| Average Jitter        | **1.71 ms**                                                                                                  |
| Average Packet Loss   | **0.06%**                                                                                                    |
| Best Fiber Efficiency | **86.5%**                                                                                                    |
| 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

Sydney sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **9.8 ms** (Melbourne (MEL)) to **135.7 ms** (Hong Kong (HKG)).

Sydney is Australia's primary internet gateway and a landing point for major trans-Pacific cables toward the Americas and Asia.

## Outbound Latency from Sydney (SYD)

Round-trip time in milliseconds **from Sydney** to all other backbone PoPs, sorted fastest to slowest.

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇦🇺 Melbourne (MEL)    | **[9.8](/docs/network/latency/pairs/syd-mel-rtt)**   | 6.99 ms     | 71.3%      | 0.12 ms | 0.19% | Ultra-Low |
| 🇸🇬 Singapore (SIN)    | **[94.5](/docs/network/latency/pairs/syd-sin-rtt)**  | 61.63 ms    | 65.2%      | 0.84 ms | 0%    | Good      |
| 🇯🇵 Tokyo (TYO)        | **[101.3](/docs/network/latency/pairs/syd-tyo-rtt)** | 76.31 ms    | 75.3%      | 0.74 ms | 0%    | Good      |
| 🇹🇼 Taipei (TPE)       | **[131.7](/docs/network/latency/pairs/syd-tpe-rtt)** | 70.88 ms    | 53.8%      | 1.51 ms | 0%    | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[135.7](/docs/network/latency/pairs/syd-hkg-rtt)** | 71.97 ms    | 53%        | 0.65 ms | 0.19% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[136.5](/docs/network/latency/pairs/syd-lax-rtt)** | 118.13 ms   | 86.5%      | 1.54 ms | 0.12% | Good      |
| 🇺🇸 Seattle (SEA)      | **[161.9](/docs/network/latency/pairs/syd-sea-rtt)** | 121.96 ms   | 75.3%      | 1.74 ms | 0.03% | Fair      |
| 🇺🇸 Miami (MIA)        | **[191.5](/docs/network/latency/pairs/syd-mia-rtt)** | 147.18 ms   | 76.9%      | 0.95 ms | 0.12% | Fair      |
| 🇺🇸 New York (NYC)     | **[191.9](/docs/network/latency/pairs/syd-nyc-rtt)** | 156.57 ms   | 81.6%      | 2.06 ms | 0.07% | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[195.3](/docs/network/latency/pairs/syd-iad-rtt)** | 153.48 ms   | 78.6%      | 1.26 ms | 0.15% | Fair      |
| 🇫🇷 Marseille (MRS)    | **[240.5](/docs/network/latency/pairs/syd-mrs-rtt)** | 165.41 ms   | 68.8%      | 2.18 ms | 0%    | Fair      |
| 🇷🇺 Moscow (MOW)       | **[242.2](/docs/network/latency/pairs/syd-mow-rtt)** | 141.84 ms   | 58.6%      | 1.9 ms  | 0.11% | Fair      |
| 🇫🇷 Paris (PAR)        | **[250.3](/docs/network/latency/pairs/syd-par-rtt)** | 166.06 ms   | 66.3%      | 2.41 ms | 0%    | High      |
| 🇩🇪 Frankfurt (FRA)    | **[254.4](/docs/network/latency/pairs/syd-fra-rtt)** | 161.37 ms   | 63.4%      | 2.54 ms | 0%    | High      |
| 🇬🇧 London (LON)       | **[256.5](/docs/network/latency/pairs/syd-lon-rtt)** | 166.37 ms   | 64.9%      | 2.97 ms | 0.09% | High      |
| 🇳🇱 Amsterdam (AMS)    | **[258.9](/docs/network/latency/pairs/syd-ams-rtt)** | 162.93 ms   | 62.9%      | 1.18 ms | 0.16% | High      |
| 🇩🇪 Berlin (BER)       | **[260.5](/docs/network/latency/pairs/syd-ber-rtt)** | 157.54 ms   | 60.5%      | 2.14 ms | 0%    | High      |
| 🇧🇷 São Paulo (GRU)    | **[296.7](/docs/network/latency/pairs/syd-gru-rtt)** | 131 ms      | 44.2%      | 1.93 ms | 0%    | High      |
| 🇿🇦 Johannesburg (JNB) | **[412.5](/docs/network/latency/pairs/syd-jnb-rtt)** | 108.32 ms   | 26.3%      | 3.8 ms  | 0%    | High      |

## Fastest Routes to Sydney (SYD)

The 10 fastest measured routes **to Sydney**, 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    | 🇦🇺 Melbourne (MEL)   | **[9.8 ms](/docs/network/latency/pairs/mel-syd-rtt)**   | 9.36 ms   | 11.08 ms  | 0.4 ms  |
| 2    | 🇸🇬 Singapore (SIN)   | **[94.5 ms](/docs/network/latency/pairs/sin-syd-rtt)**  | 92.37 ms  | 99.4 ms   | 1.76 ms |
| 3    | 🇯🇵 Tokyo (TYO)       | **[101.9 ms](/docs/network/latency/pairs/tyo-syd-rtt)** | 97.82 ms  | 112.89 ms | 3.32 ms |
| 4    | 🇹🇼 Taipei (TPE)      | **[133.2 ms](/docs/network/latency/pairs/tpe-syd-rtt)** | 129.47 ms | 143.28 ms | 3.02 ms |
| 5    | 🇭🇰 Hong Kong (HKG)   | **[137.2 ms](/docs/network/latency/pairs/hkg-syd-rtt)** | 129.36 ms | 162.96 ms | 6.53 ms |
| 6    | 🇺🇸 Los Angeles (LAX) | **[137.6 ms](/docs/network/latency/pairs/lax-syd-rtt)** | 134.53 ms | 146.99 ms | 2.45 ms |
| 7    | 🇺🇸 Seattle (SEA)     | **[161.3 ms](/docs/network/latency/pairs/sea-syd-rtt)** | 157.6 ms  | 177.48 ms | 3.32 ms |
| 8    | 🇺🇸 Miami (MIA)       | **[191.5 ms](/docs/network/latency/pairs/mia-syd-rtt)** | 181.65 ms | 213.36 ms | 7.74 ms |
| 9    | 🇺🇸 New York (NYC)    | **[192.6 ms](/docs/network/latency/pairs/nyc-syd-rtt)** | 185.89 ms | 212.11 ms | 5.61 ms |
| 10   | 🇺🇸 Ashburn (IAD)     | **[193.6 ms](/docs/network/latency/pairs/iad-syd-rtt)** | 185.3 ms  | 213.55 ms | 6.56 ms |

## Inbound Latency to Sydney (SYD)

Round-trip time in milliseconds **from all other PoPs to Sydney**. 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      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇦🇺 Melbourne (MEL)    | **[9.8](/docs/network/latency/pairs/mel-syd-rtt)**   | 6.99 ms     | 71.3%      | 0.12 ms | 0%    | Ultra-Low |
| 🇸🇬 Singapore (SIN)    | **[94.5](/docs/network/latency/pairs/sin-syd-rtt)**  | 61.63 ms    | 65.2%      | 0.53 ms | 0%    | Good      |
| 🇯🇵 Tokyo (TYO)        | **[101.9](/docs/network/latency/pairs/tyo-syd-rtt)** | 76.31 ms    | 74.9%      | 0.92 ms | 0.2%  | Good      |
| 🇹🇼 Taipei (TPE)       | **[133.2](/docs/network/latency/pairs/tpe-syd-rtt)** | 70.88 ms    | 53.2%      | 1.48 ms | 0%    | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[137.2](/docs/network/latency/pairs/hkg-syd-rtt)** | 71.97 ms    | 52.5%      | 0.86 ms | 0.17% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[137.6](/docs/network/latency/pairs/lax-syd-rtt)** | 118.13 ms   | 85.9%      | 1.65 ms | 0%    | Good      |
| 🇺🇸 Seattle (SEA)      | **[161.3](/docs/network/latency/pairs/sea-syd-rtt)** | 121.96 ms   | 75.6%      | 1.49 ms | 0%    | Fair      |
| 🇺🇸 Miami (MIA)        | **[191.5](/docs/network/latency/pairs/mia-syd-rtt)** | 147.18 ms   | 76.9%      | 0.88 ms | 0%    | Fair      |
| 🇺🇸 New York (NYC)     | **[192.6](/docs/network/latency/pairs/nyc-syd-rtt)** | 156.57 ms   | 81.3%      | 0.91 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[193.6](/docs/network/latency/pairs/iad-syd-rtt)** | 153.48 ms   | 79.3%      | 1.68 ms | 0%    | Fair      |
| 🇫🇷 Marseille (MRS)    | **[240.6](/docs/network/latency/pairs/mrs-syd-rtt)** | 165.41 ms   | 68.7%      | 2.14 ms | 0%    | Fair      |
| 🇷🇺 Moscow (MOW)       | **[241.8](/docs/network/latency/pairs/mow-syd-rtt)** | 141.84 ms   | 58.7%      | 2.66 ms | 0%    | Fair      |
| 🇫🇷 Paris (PAR)        | **[249.7](/docs/network/latency/pairs/par-syd-rtt)** | 166.06 ms   | 66.5%      | 1.18 ms | 0%    | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[256](/docs/network/latency/pairs/fra-syd-rtt)**   | 161.37 ms   | 63%        | 1.5 ms  | 0.16% | High      |
| 🇳🇱 Amsterdam (AMS)    | **[258](/docs/network/latency/pairs/ams-syd-rtt)**   | 162.93 ms   | 63.2%      | 2.35 ms | 0.11% | High      |
| 🇬🇧 London (LON)       | **[258.1](/docs/network/latency/pairs/lon-syd-rtt)** | 166.37 ms   | 64.5%      | 1.58 ms | 0.18% | High      |
| 🇩🇪 Berlin (BER)       | **[262.1](/docs/network/latency/pairs/ber-syd-rtt)** | 157.54 ms   | 60.1%      | 3.1 ms  | 0.15% | High      |
| 🇧🇷 São Paulo (GRU)    | **[265.5](/docs/network/latency/pairs/gru-syd-rtt)** | 131 ms      | 49.3%      | 1.66 ms | 0%    | High      |
| 🇿🇦 Johannesburg (JNB) | **[412.6](/docs/network/latency/pairs/jnb-syd-rtt)** | 108.32 ms   | 26.3%      | 2.3 ms  | 0.07% | High      |

## Asia Pacific Peers

Sydney 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 | **135.7** | Good      |
| [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL  | Australia | **9.8**   | Ultra-Low |
| [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN  | Singapore | **94.5**  | Good      |
| [🇹🇼 Taipei (TPE)](./tpe-taipei)       | TPE  | Taiwan    | **131.7** | Good      |
| [🇯🇵 Tokyo (TYO)](./tyo-tokyo)         | TYO  | Japan     | **101.3** | Good      |

## Frequently Asked Questions

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

The fastest measured route to Sydney (SYD) is [Melbourne (MEL) → Sydney (SYD)](/docs/network/latency/pairs/mel-syd-rtt), averaging **9.8 ms** RTT (Ultra-Low).

**What is the fastest route from Sydney?**

The fastest measured route from Sydney (SYD) is [Sydney (SYD) → Melbourne (MEL)](/docs/network/latency/pairs/syd-mel-rtt), averaging **9.8 ms** RTT (Ultra-Low).

**How well connected is Sydney to the Hats Network backbone?**

Sydney (SYD) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Sydney (SYD) → Johannesburg (JNB)](/docs/network/latency/pairs/syd-jnb-rtt), averages **412.5 ms** RTT.

## Open Data

Measured latency data for Sydney (SYD) 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 Sydney is published as `syd-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [syd-mel.pings.csv](/opendata/latency/latest/pairs/syd-mel.pings.csv), the 50-probe ICMP echo round for [Sydney (SYD) → Melbourne (MEL)](/docs/network/latency/pairs/syd-mel-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/syd-sydney).
- **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.