# 🇸🇬 Singapore Ping & Network Latency (SIN) | AS203314

## 🇸🇬 Singapore (SIN)

Singapore is Southeast Asia's dominant interconnection hub, bridging South Asia, Australia, and East Asia through dense submarine cable landings.

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

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

### PoP Highlights

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

### Facility & Interconnection

* **Facility:** SIN1
* **Upstream transit:** HE / Cogent / NTT
* **Peering / IX:** Equinix IX

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                            |
| --------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇸🇬 Singapore (SIN) → 🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/sin-hkg-rtt) (**30.8 ms**) — Excellent |
| Slowest Route         | [🇸🇬 Singapore (SIN) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/sin-jnb-rtt) (**312.6 ms**)         |
| Average RTT           | **156.6 ms**                                                                                                     |
| Average Jitter        | **1.11 ms**                                                                                                      |
| Average Packet Loss   | **0.08%**                                                                                                        |
| Best Fiber Efficiency | **84.0%**                                                                                                        |
| 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

Singapore sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **30.8 ms** (Hong Kong (HKG)) to **94.5 ms** (Sydney (SYD)).

Singapore is Southeast Asia's dominant interconnection hub, bridging South Asia, Australia and East Asia through dense submarine cable landings.

## Outbound Latency from Singapore (SIN)

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

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇭🇰 Hong Kong (HKG)    | **[30.8](/docs/network/latency/pairs/sin-hkg-rtt)**  | 25.24 ms    | 81.9%      | 0.23 ms | 0.1%  | Excellent |
| 🇹🇼 Taipei (TPE)       | **[45.8](/docs/network/latency/pairs/sin-tpe-rtt)**  | 31.77 ms    | 69.4%      | 0.25 ms | 0%    | Excellent |
| 🇯🇵 Tokyo (TYO)        | **[68.9](/docs/network/latency/pairs/sin-tyo-rtt)**  | 52 ms       | 75.5%      | 0.41 ms | 0%    | Excellent |
| 🇦🇺 Melbourne (MEL)    | **[88.6](/docs/network/latency/pairs/sin-mel-rtt)**  | 59.22 ms    | 66.8%      | 0.7 ms  | 0%    | Good      |
| 🇦🇺 Sydney (SYD)       | **[94.5](/docs/network/latency/pairs/sin-syd-rtt)**  | 61.63 ms    | 65.2%      | 0.53 ms | 0%    | Good      |
| 🇫🇷 Marseille (MRS)    | **[140.6](/docs/network/latency/pairs/sin-mrs-rtt)** | 103.79 ms   | 73.8%      | 1.48 ms | 0.2%  | Good      |
| 🇷🇺 Moscow (MOW)       | **[147.7](/docs/network/latency/pairs/sin-mow-rtt)** | 82.49 ms    | 55.8%      | 0.99 ms | 0.11% | Good      |
| 🇫🇷 Paris (PAR)        | **[151.4](/docs/network/latency/pairs/sin-par-rtt)** | 105.19 ms   | 69.5%      | 1.07 ms | 0.12% | Fair      |
| 🇺🇸 Seattle (SEA)      | **[151.5](/docs/network/latency/pairs/sin-sea-rtt)** | 127.22 ms   | 84%        | 1.11 ms | 0%    | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[151.6](/docs/network/latency/pairs/sin-fra-rtt)** | 100.56 ms   | 66.3%      | 0.77 ms | 0.04% | Fair      |
| 🇬🇧 London (LON)       | **[155.4](/docs/network/latency/pairs/sin-lon-rtt)** | 106.35 ms   | 68.4%      | 1.17 ms | 0.06% | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[155.8](/docs/network/latency/pairs/sin-ams-rtt)** | 102.86 ms   | 66%        | 1.04 ms | 0.19% | Fair      |
| 🇩🇪 Berlin (BER)       | **[160.3](/docs/network/latency/pairs/sin-ber-rtt)** | 97.19 ms    | 60.6%      | 0.88 ms | 0.19% | Fair      |
| 🇺🇸 Los Angeles (LAX)  | **[168.2](/docs/network/latency/pairs/sin-lax-rtt)** | 138.43 ms   | 82.3%      | 1.78 ms | 0.03% | Fair      |
| 🇺🇸 New York (NYC)     | **[209.3](/docs/network/latency/pairs/sin-nyc-rtt)** | 150.29 ms   | 71.8%      | 1.38 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[210](/docs/network/latency/pairs/sin-iad-rtt)**   | 152.14 ms   | 72.4%      | 2.32 ms | 0%    | Fair      |
| 🇺🇸 Miami (MIA)        | **[221.7](/docs/network/latency/pairs/sin-mia-rtt)** | 166.27 ms   | 75%        | 1.1 ms  | 0.19% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[311.4](/docs/network/latency/pairs/sin-gru-rtt)** | 156.67 ms   | 50.3%      | 2.4 ms  | 0.1%  | High      |
| 🇿🇦 Johannesburg (JNB) | **[312.6](/docs/network/latency/pairs/sin-jnb-rtt)** | 84.85 ms    | 27.1%      | 1.51 ms | 0.19% | High      |

## Fastest Routes to Singapore (SIN)

The 10 fastest measured routes **to Singapore**, 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    | 🇭🇰 Hong Kong (HKG) | **[31.5 ms](/docs/network/latency/pairs/hkg-sin-rtt)**  | 29.73 ms  | 35.06 ms  | 1.22 ms |
| 2    | 🇹🇼 Taipei (TPE)    | **[44.3 ms](/docs/network/latency/pairs/tpe-sin-rtt)**  | 42.61 ms  | 50.6 ms   | 1.64 ms |
| 3    | 🇯🇵 Tokyo (TYO)     | **[69.4 ms](/docs/network/latency/pairs/tyo-sin-rtt)**  | 66.32 ms  | 80.7 ms   | 3.27 ms |
| 4    | 🇦🇺 Melbourne (MEL) | **[88.4 ms](/docs/network/latency/pairs/mel-sin-rtt)**  | 83.08 ms  | 108.06 ms | 4.37 ms |
| 5    | 🇦🇺 Sydney (SYD)    | **[94.5 ms](/docs/network/latency/pairs/syd-sin-rtt)**  | 89.04 ms  | 106.31 ms | 3.56 ms |
| 6    | 🇫🇷 Marseille (MRS) | **[139.6 ms](/docs/network/latency/pairs/mrs-sin-rtt)** | 132.36 ms | 163.5 ms  | 6.56 ms |
| 7    | 🇷🇺 Moscow (MOW)    | **[147.3 ms](/docs/network/latency/pairs/mow-sin-rtt)** | 144.41 ms | 156.92 ms | 2.32 ms |
| 8    | 🇫🇷 Paris (PAR)     | **[150.3 ms](/docs/network/latency/pairs/par-sin-rtt)** | 144.03 ms | 164.23 ms | 4.53 ms |
| 9    | 🇺🇸 Seattle (SEA)   | **[151.1 ms](/docs/network/latency/pairs/sea-sin-rtt)** | 143.38 ms | 172.46 ms | 6.94 ms |
| 10   | 🇩🇪 Frankfurt (FRA) | **[151.4 ms](/docs/network/latency/pairs/fra-sin-rtt)** | 148.19 ms | 159.42 ms | 2.49 ms |

## Inbound Latency to Singapore (SIN)

Round-trip time in milliseconds **from all other PoPs to Singapore**. 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      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇭🇰 Hong Kong (HKG)    | **[31.5](/docs/network/latency/pairs/hkg-sin-rtt)**  | 25.24 ms    | 80.1%      | 0.33 ms | 0.05% | Excellent |
| 🇹🇼 Taipei (TPE)       | **[44.3](/docs/network/latency/pairs/tpe-sin-rtt)**  | 31.77 ms    | 71.7%      | 0.22 ms | 0.11% | Excellent |
| 🇯🇵 Tokyo (TYO)        | **[69.4](/docs/network/latency/pairs/tyo-sin-rtt)**  | 52 ms       | 74.9%      | 0.62 ms | 0%    | Excellent |
| 🇦🇺 Melbourne (MEL)    | **[88.4](/docs/network/latency/pairs/mel-sin-rtt)**  | 59.22 ms    | 67%        | 0.89 ms | 0.02% | Good      |
| 🇦🇺 Sydney (SYD)       | **[94.5](/docs/network/latency/pairs/syd-sin-rtt)**  | 61.63 ms    | 65.2%      | 0.84 ms | 0%    | Good      |
| 🇫🇷 Marseille (MRS)    | **[139.6](/docs/network/latency/pairs/mrs-sin-rtt)** | 103.79 ms   | 74.3%      | 1.19 ms | 0%    | Good      |
| 🇷🇺 Moscow (MOW)       | **[147.3](/docs/network/latency/pairs/mow-sin-rtt)** | 82.49 ms    | 56%        | 1.11 ms | 0.17% | Good      |
| 🇫🇷 Paris (PAR)        | **[150.3](/docs/network/latency/pairs/par-sin-rtt)** | 105.19 ms   | 70%        | 1.32 ms | 0%    | Fair      |
| 🇺🇸 Seattle (SEA)      | **[151.1](/docs/network/latency/pairs/sea-sin-rtt)** | 127.22 ms   | 84.2%      | 1.4 ms  | 0%    | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[151.4](/docs/network/latency/pairs/fra-sin-rtt)** | 100.56 ms   | 66.4%      | 0.7 ms  | 0%    | Fair      |
| 🇬🇧 London (LON)       | **[156.5](/docs/network/latency/pairs/lon-sin-rtt)** | 106.35 ms   | 68%        | 1.57 ms | 0%    | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[157.6](/docs/network/latency/pairs/ams-sin-rtt)** | 102.86 ms   | 65.3%      | 0.82 ms | 0%    | Fair      |
| 🇩🇪 Berlin (BER)       | **[158.3](/docs/network/latency/pairs/ber-sin-rtt)** | 97.19 ms    | 61.4%      | 0.87 ms | 0.19% | Fair      |
| 🇺🇸 Los Angeles (LAX)  | **[167.7](/docs/network/latency/pairs/lax-sin-rtt)** | 138.43 ms   | 82.5%      | 1.33 ms | 0%    | Fair      |
| 🇺🇸 New York (NYC)     | **[208.7](/docs/network/latency/pairs/nyc-sin-rtt)** | 150.29 ms   | 72%        | 1.83 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[211.5](/docs/network/latency/pairs/iad-sin-rtt)** | 152.14 ms   | 71.9%      | 1.77 ms | 0%    | Fair      |
| 🇺🇸 Miami (MIA)        | **[223.1](/docs/network/latency/pairs/mia-sin-rtt)** | 166.27 ms   | 74.5%      | 1.42 ms | 0.08% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[297.1](/docs/network/latency/pairs/gru-sin-rtt)** | 156.67 ms   | 52.7%      | 2.14 ms | 0.08% | High      |
| 🇿🇦 Johannesburg (JNB) | **[311.6](/docs/network/latency/pairs/jnb-sin-rtt)** | 84.85 ms    | 27.2%      | 3.35 ms | 0%    | High      |

## Asia Pacific Peers

Singapore 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 | **30.8** | Excellent |
| [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL  | Australia | **88.6** | Good      |
| [🇦🇺 Sydney (SYD)](./syd-sydney)       | SYD  | Australia | **94.5** | Good      |
| [🇹🇼 Taipei (TPE)](./tpe-taipei)       | TPE  | Taiwan    | **45.8** | Excellent |
| [🇯🇵 Tokyo (TYO)](./tyo-tokyo)         | TYO  | Japan     | **68.9** | Excellent |

## Frequently Asked Questions

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

The fastest measured route to Singapore (SIN) is [Hong Kong (HKG) → Singapore (SIN)](/docs/network/latency/pairs/hkg-sin-rtt), averaging **31.5 ms** RTT (Excellent).

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

The fastest measured route from Singapore (SIN) is [Singapore (SIN) → Hong Kong (HKG)](/docs/network/latency/pairs/sin-hkg-rtt), averaging **30.8 ms** RTT (Excellent).

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

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

## Open Data

Measured latency data for Singapore (SIN) 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 Singapore is published as `sin-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [sin-hkg.pings.csv](/opendata/latency/latest/pairs/sin-hkg.pings.csv), the 50-probe ICMP echo round for [Singapore (SIN) → Hong Kong (HKG)](/docs/network/latency/pairs/sin-hkg-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/sin-singapore).
- **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.