# About Hats Network > **AS203314 - Global BGP Backbone** > > Hats Network Inc. operates a **global BGP backbone** with Points of Presence (PoPs) across Asia, Europe, and the Americas. We are dedicated to building a safer and more advanced next-generation network infrastructure. > > * **Founded:** 16 Aug 2022 > * **ASN:** AS203314 > * **Peering Policy:** Open Peering > * **Network Type:** Eyeball ISP & Transit Provider > * **Global PoPs:** 16+ across 4 continents > * **Backbone Capacity:** 1 Tbps+ aggregated > * **Upstream Providers:** Cogent (AS174), NTT (AS2914), Hurricane Electric (AS6939), PCCW Global (AS3491), iFog (AS34927) ## Our Vision We imagine a world where network connectivity is seamless, secure and accessible to everyone. Our mission is to: 1. **Build** a robust, global BGP backbone with redundant infrastructure 2. **Enable** open peering and interconnection to improve Internet resilience 3. **Deliver** reliable IP-Transit services with transparent pricing 4. **Innovate** continuously to meet the demands of a rapidly evolving digital world ## Network Resources - [Global PoP Map](/#network) — View our interactive global network map and Points of Presence locations across Asia, Europe, and the Americas. - [GeoFeed](https://hatsnet.io/geofeed/all.csv) — Subscribe to our Geographic Feed (RFC 8805) for the latest updates on IP geographical mappings. - [PeeringDB](https://www.peeringdb.com/asn/203314) — View our complete peering information, including IX participation and contact details. - [BGP Tools](https://bgp.tools/as/203314) — Explore our routing information, prefixes, and ASN connectivity on BGP.tools. ## Global Presence > Interactive content is available on the canonical HTML page. > Our network spans **16+ PoPs** across **4 continents**, providing low-latency connectivity and diverse routing options. Key backbone routes include **HKG ↔ TPE at 15 ms**, **AMS ↔ FRA at 5 ms**, **IAD ↔ NYC at 6 ms**, and **SIN ↔ MEL at 89 ms**. ### Core Locations | Region | City | IATA | Capacity | IX Exchanges | Status | | ----------- | --------- | -------------- | -------- | -------------------------------- | ------ | | Hong Kong | Hong Kong | HKG1/HKG2/HKG3 | 50 Gbps | Equinix HK, HKIX | Active | | Japan | Tokyo | TYO2 | 100 Gbps | Equinix Tokyo, JPIX, BBIX, JPNAP | Active | | Singapore | Singapore | SIN1 | 200 Gbps | Equinix SG, SGIX | Active | | Netherlands | Amsterdam | AMS | 40 Gbps | AMS-IX, NL-IX | Active | | Germany | Frankfurt | FRA | 100 Gbps | DE-CIX Frankfurt | Active | | UK | London | LON | 100 Gbps | LINX | Active | ### Edge Locations | Region | City | IATA | Capacity | IX Exchanges | Status | | ------------ | ------------ | --------- | -------- | ---------------------- | ------- | | Taiwan | Taipei | TPE1/TPE2 | 20 Gbps | STUIX, TPIX-TW, TWIX | Active | | Germany | Berlin | BER | — | DE-CIX, BCIX | Active | | France | Calais | CQF1 | 1 Gbps | — | Active | | France | Marseille | MRS | 80 Gbps | France-IX | Active | | USA | Los Angeles | LAX | 100 Gbps | SFMIX | Active | | USA | Ashburn | IAD | — | — | Active | | USA | New York | NYC | 150 Gbps | NYIIX, DE-CIX New York | Active | | USA | Seattle | SEA | 100 Gbps | SIX Seattle | Active | | Canada | Toronto | YYZ1 | — | — | Active | | Australia | Melbourne | MEL | — | HE / Superloop | Active | | South Africa | Johannesburg | JNB | — | HE Only | Planned | | Brazil | São Paulo | GRU | — | NTT / Ascenty | Planned | ### Backbone Latency Matrix Key routes (representative sample, updated periodically): | Route | RTT (ms) | Region Pair | | ----------------------- | -------- | -------------- | | Hong Kong → Taipei | \~15 | Intra-Asia | | Hong Kong → Singapore | \~32 | Intra-Asia | | Amsterdam → Frankfurt | \~5 | Intra-Europe | | Amsterdam → London | \~6 | Intra-Europe | | Ashburn → New York | \~6 | Intra-NorthAm | | New York → London | \~92 | Trans-Atlantic | | Hong Kong → Los Angeles | \~145 | Trans-Pacific | | Singapore → Melbourne | \~89 | Asia-Oceania | For the full auto-updated RTT matrix across all 19 PoPs, see the [Backbone Latency Matrix](/docs/network/latency) page. ### Featured Market Notes #### Los Angeles (LAX) Los Angeles is one of our primary west-coast handoff markets for trans-Pacific reach, bridging Asia-facing capacity into dense North American carrier ecosystems. Measured latency: **\~145 ms to HKG**, **\~101 ms to TYO**, **\~26 ms to SEA**, connected via SFMIX with 100 Gbps committed capacity. #### New York (NYC) New York represents our east-coast financial and transatlantic market focus, where low-latency delivery and backbone diversity matter most for enterprise-grade traffic profiles. Measured latency: **\~92 ms to LON** (trans-Atlantic), **\~57 ms to LAX** (cross-continental), **\~6 ms to IAD** (metro), with 150 Gbps committed capacity and NYIIX + DE-CIX New York peering. #### Seattle (SEA) Seattle serves as our Pacific Northwest gateway with exceptionally low latency to East Asia. Measured latency: **\~85 ms to TYO**, **\~115 ms to TPE**, **\~130 ms to HKG**, connected via SIX Seattle with 100 Gbps committed capacity and upstream providers HE, Cogent. #### Marseille (MRS) Marseille is a strategic Mediterranean cable landing market that strengthens south-European access to EMEA and subsea routes between east and west. Measured latency: **\~14 ms to FRA**, **\~21 ms to BER**, **\~26 ms to LON**, connected via France-IX with 80 Gbps committed capacity. #### Calais (CQF1) Calais is our French edge gateway, announcing `2a0c:9a40:95ea::/48` through MoeDove (AS44324). Its location code is `253`, and it provides an additional European path for the North American backbone. #### Toronto (YYZ1) Toronto is our Canadian edge gateway and a North American path toward Europe. It announces `2a0c:9a40:95eb::/48` and `2a13:a5c7:2526::/48` through ParadoxNetworks (AS52025); the primary node address is `2a13:a5c7:2526:1001::1` and its location code is `304`. #### Melbourne (MEL) Melbourne provides our Oceania foothold, connecting Australia to our Asia-Pacific backbone via Singapore. Measured latency: **\~89 ms to SIN**, **\~114 ms to TYO**, **\~138 ms to HKG**, via HE and Superloop upstream connectivity. ## Contact Us > **Need Help?** > > If you have any questions, peering requests, or abuse concerns, please feel free to reach out to the appropriate team below. ### Contact Information | Team | Email Address | Purpose | | ----------- | ----------------------------------------------- | ------------------------------------ | | **Sales** | [sales@hatsnet.io](mailto:sales@hatsnet.io) | IP-Transit orders, pricing inquiries | | **Peering** | [peering@hatsnet.io](mailto:peering@hatsnet.io) | Peering requests, PNI arrangements | | **NOC** | [noc@hatsnet.io](mailto:noc@hatsnet.io) | Network issues, outages | | **Support** | [support@hatsnet.io](mailto:support@hatsnet.io) | Abuse reports, general support | ## Quick Links - [Peering Policy](/docs/peering) — Learn about our open peering policy and how to establish a session with AS203314. - [IP Transit](/docs/transit) — Explore our IP-Transit services in Asia and Europe. - [BGP Communities](/docs/community) — View our BGP community strings for route management. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/about). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Quick Start Guide > **Hats Network Inc. (AS203314)** > > Hats Network operates a global BGP backbone focused on building next-generation network infrastructure. We provide IP transit, peering, and specialized routing services across Asia, Europe, and the Americas. Our documentation covers network architecture, peering policies, transit services, and technical resources for network operators. - [About Hats Network](/docs/about) — Company overview, PoP locations, geofeed, and contact information. - [Our Services](/docs/services) — Enterprise private networks, dedicated lines, premium user access, and performance routing profiles. - [Getting Peering ➡️](/docs/peering) — Open peering policy, IX presence, and peering coordinates. - [Getting IP-Transit ➡️](/docs/transit) — Transit availability, pricing, and service coverage. - [BGP Communities Reference](/docs/community) — Community strings for route control and traffic engineering. - [Need to Report Abuse?](/docs/legal/report-abuse) — Please report any violations by our end-users, including DMCA, SPAM, DDoS attacks and other such activities. ## Documentation Map --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Control BGP Communities Control communities allow you to **dictate prefix announcements** and manipulate path attributes dynamically. Attach these communities to routes you announce to AS203314 to control how we propagate them. > **Traffic Engineering** > > These communities give you fine-grained control over route propagation and path prepending outside Hats Network. ## Blackhole & Filtering | Community | Action | | -------------- | -------------------------------------- | | `203314:0:666` | Do not announce this route (blackhole) | **Usage**: Stop announcement of a prefix (e.g., during DDoS mitigation or IP address deprecation). **Note**: Equivalent to standard blackhole community `65535:65281`. ## Propagation Control Control which types of peers receive your routes: | Community | Action | | ------------ | ------------------------- | | `203314:1:0` | Do not send to Upstream | | `203314:1:1` | Do not send to Peering | | `203314:1:2` | Do not send to Downstream | > **Example Use Cases**: > > * Use `203314:1:0` to prevent transit from carrying your prefix > * Use `203314:1:1` to keep traffic limited to IX route servers > * Use `203314:1:2` to prevent customer leakage ## Geographic Restrictions Control route propagation based on location: ### Regional | Community | Action | | --------------- | --------------------------------------------------- | | `203314:2:1` | Do not send to other regions (Disable Cross Region) | | `203314:2:2` | Do not send to other PoPs (Disable Cross PoP) | | `203314:201:XX` | Do not send to Region `XX` | **Examples**: ```text # Keep traffic within Asia only 203314:2:1 # Disable cross-region 203314:201:300 # Exclude North America 203314:201:200 # Exclude Europe ``` ### Pop | Community | Action | | ---------------- | ------------------------ | | `203314:202:XXX` | Do not send to PoP `XXX` | **Examples**: ```text # Exclude specific PoPs 203314:202:301 # Do not announce via Seattle 203314:202:131 # Do not announce via Tokyo 203314:202:102 # Do not announce via Hong Kong HKG2 ``` ## Path Prepending Control AS-path prepending for routes **outside** Hats Network: > **Scope**: Path prepending only affects routes announced to external peers (upstream, peering, customers)-not internal routing. | Community | Action | | -------------- | ------------------------------- | | `203314:220:1` | Prepend 1x outside Hats Network | | `203314:220:2` | Prepend 2x outside Hats Network | | `203314:220:3` | Prepend 3x outside Hats Network | | `203314:220:4` | Prepend 4x outside Hats Network | | `203314:220:5` | Prepend 5x outside Hats Network | **Usage**: Deprioritize specific prefixes for inbound traffic engineering. ## Community Decision Flow ## Usage Examples ### Example 1: Local Traffic Only Announce a prefix only within a specific region: ```text # Announce to Asia West only 203314:2:1 # Disable cross-region ``` ### Example 2: Deprioritize Backup Prefix Make a backup prefix less attractive: ```text # Deprioritize via path prepending 203314:220:3 # Prepend 3x AS203314 ``` ### Example 3: Selective Peering Announce only to specific peer types: ```text # Announce to peering and customers only 203314:1:0 # Do not send to upstream ``` ### Example 4: Exclude Location Prevent announcement via specific location: ```text # Exclude PoP-specific announcement 203314:202:301 # Do not send via Seattle ``` ### Example 5: Combined Control Combine multiple communities for complex policies: ```text # Deprioritized, Asia-only, no upstream 203314:1:0 # No upstream 203314:2:1 # Asia only 203314:220:2 # Prepend 2x ``` ## Implementation Notes > **Best Practices**: > > 1. **Test before production**: Use `203314:220:1` (1x prepend) to verify communities work > 2. **Monitor impact**: Check route servers and looking glasses after applying changes > 3. **Document your policies**: Keep track of which prefixes use which communities > 4. **Use conservative prepends**: 3x prepend is usually sufficient; 5x is extreme ## Configuration Examples (JunOS / BIRD2) AS203314 communities are **BGP Large Communities** (RFC 8092). On JunOS they are written with the `large:` prefix (for example `large:203314:0:666`). In BIRD2 they are handled via `bgp_large_community` with `(203314, 0, 666)` tuples. > **Export Policy Safety Default (Strongly Recommended)** > > The BIRD2 examples below are **export policies**. The default action should be `reject;` to prevent > route leaks if someone copy-pastes into production.\ > For JunOS, it's also recommended to add a final `term REJECT-ALL then reject` as a safety catch-all. ### Junos **Example: Blackhole (`203314:0:666`)** ```bash set policy-options community HATS-BLACKHOLE members large:203314:0:666 set policy-options policy-statement EXPORT-TO-HATS term BLACKHOLE from route-filter 203.0.113.0/24 exact set policy-options policy-statement EXPORT-TO-HATS term BLACKHOLE then community add HATS-BLACKHOLE set policy-options policy-statement EXPORT-TO-HATS term BLACKHOLE then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` **Example: No Upstream (`203314:1:0`) + Prepend 3x (`203314:220:3`)** ```bash set policy-options community HATS-NO-UPSTREAM members large:203314:1:0 set policy-options community HATS-PREPEND-3X members large:203314:220:3 set policy-options policy-statement EXPORT-TO-HATS term BACKUP from route-filter 203.0.113.0/24 exact set policy-options policy-statement EXPORT-TO-HATS term BACKUP then community add [ HATS-NO-UPSTREAM HATS-PREPEND-3X ] set policy-options policy-statement EXPORT-TO-HATS term BACKUP then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` **Example: Keep in-region + Exclude a PoP (`203314:2:1` + `203314:202:253`)** ```bash set policy-options community HATS-NO-CROSS-REGION members large:203314:2:1 set policy-options community HATS-NO-AMS members large:203314:202:253 set policy-options policy-statement EXPORT-TO-HATS term LOCAL-ONLY from route-filter 203.0.113.0/24 exact set policy-options policy-statement EXPORT-TO-HATS term LOCAL-ONLY then community add [ HATS-NO-CROSS-REGION HATS-NO-AMS ] set policy-options policy-statement EXPORT-TO-HATS term LOCAL-ONLY then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` ### Bird2 **Example: Blackhole (`203314:0:666`)** ```bird2 filter export_to_hats_v4 { if net = 203.0.113.0/24 then { bgp_large_community.add((203314, 0, 666)); accept; } reject; # Safety default } ``` **Example: No Upstream (`203314:1:0`) + Prepend 3x (`203314:220:3`)** ```bird2 filter export_to_hats_v4 { if net = 203.0.113.0/24 then { bgp_large_community.add((203314, 1, 0)); bgp_large_community.add((203314, 220, 3)); accept; } reject; # Safety default } ``` **Example: Keep in-region + Exclude a PoP (`203314:2:1` + `203314:202:253`)** ```bird2 filter export_to_hats_v4 { if net = 203.0.113.0/24 then { bgp_large_community.add((203314, 2, 1)); bgp_large_community.add((203314, 202, 253)); accept; } reject; # Safety default } ``` ## Related Information * **[PoP Codes](/docs/community/pop-codes)** - Reference for PoP numbers (XXX) in geographic restrictions * **[Region Codes](/docs/community/region-codes)** - Reference for region numbers (XX) in geographic restrictions * **[Internal Communities](/docs/community/internal-communities)** - Communities we attach to routes we announce > **Important**: Control communities are applied to routes **you announce to AS203314**. They do not affect routes we announce to you. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/community/control-communities). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # BGP Communities > **AS203314 BGP Communities** > > Hats Network (AS203314) uses a **comprehensive BGP community structure** to help network operators manage their routing policies effectively. ## Community System Overview ## Quick Reference | Category | Community | Purpose | Details | | ------------------- | ---------------- | ------------------------- | ------------------------------------------------------------------------------------- | | **Origin** | `203314:110:XX` | Route source type | [See Origin →](/docs/community/internal-communities#route-origin) | | **PoP** | `203314:120:XXX` | Learned at PoP | [See PoP-Based →](/docs/community/internal-communities#pop-based-communities) | | **PoP Pass** | `203314:125:XXX` | Passed through PoP | [See PoP-Based →](/docs/community/internal-communities#pop-based-communities) | | **Region** | `203314:130:XX` | Learned in region | [See Region-Based →](/docs/community/internal-communities#region-based-communities) | | **Region Pass** | `203314:135:XX` | Passed through region | [See Region-Based →](/docs/community/internal-communities#region-based-communities) | | **Blackhole** | `203314:0:666` | Do not announce | [See Blackhole →](/docs/community/control-communities#blackhole--filtering) | | **No Upstream** | `203314:1:0` | Do not send to upstream | [See Propagation →](/docs/community/control-communities#propagation-control) | | **No Peering** | `203314:1:1` | Do not send to peering | [See Propagation →](/docs/community/control-communities#propagation-control) | | **No Customer** | `203314:1:2` | Do not send to downstream | [See Propagation →](/docs/community/control-communities#propagation-control) | | **No Cross-Region** | `203314:2:1` | Keep within region | [See Geo Restrictions →](/docs/community/control-communities#geographic-restrictions) | | **No Cross-PoP** | `203314:2:2` | Keep within PoP | [See Geo Restrictions →](/docs/community/control-communities#geographic-restrictions) | | **No Region** | `203314:201:XX` | Exclude region | [See Geo Restrictions →](/docs/community/control-communities#geographic-restrictions) | | **No PoP** | `203314:202:XXX` | Exclude PoP | [See Geo Restrictions →](/docs/community/control-communities#geographic-restrictions) | | **Prepend 1x** | `203314:220:1` | Prepend AS 1 time | [See Path Prepending →](/docs/community/control-communities#path-prepending) | | **Prepend 2x** | `203314:220:2` | Prepend AS 2 times | [See Path Prepending →](/docs/community/control-communities#path-prepending) | | **Prepend 3x** | `203314:220:3` | Prepend AS 3 times | [See Path Prepending →](/docs/community/control-communities#path-prepending) | | **Prepend 4x** | `203314:220:4` | Prepend AS 4 times | [See Path Prepending →](/docs/community/control-communities#path-prepending) | | **Prepend 5x** | `203314:220:5` | Prepend AS 5 times | [See Path Prepending →](/docs/community/control-communities#path-prepending) | ## Community Categories - [Internal Communities](/docs/community/internal-communities) — Route origin types, PoP locations, and region codes for identifying where routes are learned. - [Control Communities](/docs/community/control-communities) — Traffic engineering communities for blackhole, propagation control, and path prepending. - [PoP Codes](/docs/community/pop-codes) — 3-digit codes for each Point of Presence used in location-based communities. - [Region Codes](/docs/community/region-codes) — 2-digit geographic region codes for area-based routing policies. ## Usage Examples > ### Common Scenarios > > * Keep traffic local: > > ```bird2 > bgp_large_community.add((203314, 2, 1)); # Do not send to other regions > ``` > > * Deprioritize upstream: > > ```bird2 > bgp_large_community.add((203314, 220, 3)); # Prepend 3x to upstream routes > ``` > > * Exclude specific PoP: > > ```bird2 > bgp_large_community.add((203314, 202, 253)); # Do not send to AMS > ``` ## Configuration Examples (JunOS / BIRD2) Below are minimal snippets showing how to **attach AS203314 large communities** to the prefixes you announce to us. > **Export Policy Safety Default (Strongly Recommended)** > > These snippets are **export policies**. For BIRD2, use `reject;` as the default action to prevent > route leaks.\ > For JunOS, add a final `term REJECT-ALL then reject` as a safety catch-all. > **Documentation Prefixes** > > These examples use documentation-only prefixes from RFC 5737 / RFC 3849 (e.g. `203.0.113.0/24`, > `2001:db8::/32`). Replace them with your real announced prefixes. ### Junos **Keep traffic local (`203314:2:1`)** ```bash set policy-options community HATS-NO-CROSS-REGION members large:203314:2:1 set policy-options policy-statement EXPORT-TO-HATS term LOCAL from route-filter 203.0.113.0/24 exact set policy-options policy-statement EXPORT-TO-HATS term LOCAL then community add HATS-NO-CROSS-REGION set policy-options policy-statement EXPORT-TO-HATS term LOCAL then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` **Deprioritize a backup prefix (`203314:220:3`)** ```bash set policy-options community HATS-PREPEND-3X members large:203314:220:3 set policy-options policy-statement EXPORT-TO-HATS term BACKUP from route-filter 203.0.113.0/24 exact set policy-options policy-statement EXPORT-TO-HATS term BACKUP then community add HATS-PREPEND-3X set policy-options policy-statement EXPORT-TO-HATS term BACKUP then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` **IPv6 variant** ```bash set policy-options community HATS-NO-CROSS-REGION members large:203314:2:1 set policy-options policy-statement EXPORT-TO-HATS term LOCAL-V6 from route-filter 2001:db8:203:113::/48 exact set policy-options policy-statement EXPORT-TO-HATS term LOCAL-V6 then community add HATS-NO-CROSS-REGION set policy-options policy-statement EXPORT-TO-HATS term LOCAL-V6 then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` ### Bird2 **Keep traffic local (`203314:2:1`)** ```bird2 filter export_to_hats_v4 { if net = 203.0.113.0/24 then { bgp_large_community.add((203314, 2, 1)); accept; } reject; # Safety default } ``` **Deprioritize a backup prefix (`203314:220:3`)** ```bird2 filter export_to_hats_v4 { if net = 203.0.113.0/24 then { bgp_large_community.add((203314, 220, 3)); accept; } reject; # Safety default } ``` **IPv6 variant** ```bird2 filter export_to_hats_v6 { if net = 2001:db8:203:113::/48 then { bgp_large_community.add((203314, 2, 1)); accept; } reject; # Safety default } ``` ## Related Resources - [Peering Policy](/docs/peering) — Learn how to establish BGP peering with AS203314. - [IP Transit](/docs/transit) — Get IP-Transit with BGP community support. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/community). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Internal BGP Communities Internal communities indicate **where routes are learned from** and whether they are uniquely announced. These communities help you identify the source and path of routes received from AS203314. > **Community Format:** `203314:XXX:YY` where `XXX` is the category and `YY` is the specific value. ## Route Origin These communities indicate **how** a route was learned by Hats Network: | Community | Description | Unique | | ---------------- | ------------------------------------ | ------ | | `203314:110:10` | Route learned from Upstream | Yes | | `203314:110:20` | Route learned from Downstream | Yes | | `203314:110:30` | Route learned from Peering | Yes | | `203314:110:110` | Route originated within Hats Network | Yes | **Unique** means this route is only announced via this method-if you see `203314:110:30`, the route is exclusively available via peering. ## PoP-Based Communities These communities identify **which PoP** a route was learned at or passed through: ### Learned Routes learned **at** a specific PoP (entry point): | Community | Description | Unique | | ---------------- | -------------------------- | ------ | | `203314:120:XXX` | Route learned at PoP `XXX` | Yes | **Example**: `203314:120:101` means the route was learned at Hong Kong (HKG1). ### Passed Routes that **passed through** a PoP (transit): | Community | Description | Unique | | ---------------- | ------------------------------ | ------ | | `203314:125:XXX` | Route passed through PoP `XXX` | No | **Example**: `203314:125:101` means the route passed through Hong Kong (HKG1). ## Region-Based Communities These communities identify **which region** a route was learned in or passed through: ### Learned Routes learned **within** a specific region: | Community | Description | Unique | | --------------- | ---------------------------- | ------ | | `203314:130:XX` | Route learned in Region `XX` | Yes | **Example**: `203314:130:100` means the route was learned in Asia (West). ### Passed Routes that **passed through** a region: | Community | Description | Unique | | --------------- | -------------------------------- | ------ | | `203314:135:XX` | Route passed through Region `XX` | No | **Example**: `203314:135:100` means the route passed through Asia (West). ## Usage Examples ### Identify Route Source Determine if a route comes from peering, upstream, or our customers: ```bird2 # These large communities are attached by AS203314 on routes you receive. # You typically match them in your import policy: filter import_prefer_peering_v4 { if (203314, 110, 30) ~ bgp_large_community then bgp_local_pref = 200; # prefer peering-learned routes if (203314, 110, 10) ~ bgp_large_community then bgp_local_pref = 80; # de-prioritize upstream-learned routes accept; } ``` ### Identify Entry Location Determine where a route entered our network: ```bird2 filter import_prefer_asia_pops_v4 { if (203314, 120, 101) ~ bgp_large_community then bgp_local_pref = 200; # entered at HKG1 (Hong Kong) if (203314, 120, 131) ~ bgp_large_community then bgp_local_pref = 180; # entered at TYO2 (Tokyo) accept; } ``` ### Filter by Region Accept routes only from specific regions: ```bird2 # Only accept routes learned in Asia West filter import_only_asia_west_v4 { if (203314, 130, 100) ~ bgp_large_community then accept; reject; } # Reject routes that passed through Europe (both West=200 and East=250) filter import_reject_europe_transit_v4 { if (203314, 135, 200) ~ bgp_large_community then reject; if (203314, 135, 250) ~ bgp_large_community then reject; accept; } ``` ## Policy Examples (JunOS / BIRD2) Internal communities are also **BGP Large Communities**. You can match them in your import policy to influence local preference, selection, or filtering. ### Junos **Prefer routes learned in Asia West (`203314:130:100`)** ```bash set policy-options community HATS-REGION-ASIA-W members large:203314:130:100 set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W from community HATS-REGION-ASIA-W set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W then local-preference 200 set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W then accept ``` **Reject routes learned from Upstream (`203314:110:10`)** ```bash set policy-options community HATS-ORIGIN-UPSTREAM members large:203314:110:10 set policy-options policy-statement IMPORT-FROM-HATS term NO-UPSTREAM from community HATS-ORIGIN-UPSTREAM set policy-options policy-statement IMPORT-FROM-HATS term NO-UPSTREAM then reject ``` ### Bird2 **Prefer routes learned in Asia West (`203314:130:100`)** ```bird2 filter import_from_hats_v4 { if (203314, 130, 100) ~ bgp_large_community then { bgp_local_pref = 200; accept; } accept; } ``` **Reject routes learned from Upstream (`203314:110:10`)** ```bird2 filter import_from_hats_v4 { if (203314, 110, 10) ~ bgp_large_community then reject; accept; } ``` ## Related Information * **[PoP Codes](/docs/community/pop-codes)** - Reference for PoP numbers (XXX) * **[Region Codes](/docs/community/region-codes)** - Reference for region numbers (XX) * **[Control Communities](/docs/community/control-communities)** - Traffic engineering communities > **Tip**: Internal communities are automatically attached to routes we announce to you. Use them to make informed routing decisions based on route origin and location. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/community/internal-communities). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # PoP Codes Each Point of Presence (PoP) has a unique **3-digit code** used in community strings like `203314:120:XXX` and `203314:202:XXX`. > **Usage**: These codes identify specific PoP locations in internal communities (`120:XXX`, `125:XXX`) and control communities (`202:XXX`). ## PoP Code Reference | Location | IATA | Generation | Type | PoP Code | Notes | | --------- | ---- | ---------- | ---- | -------- | ------ | | Hong Kong | HKG1 | Gen2 | Core | 101 | Unique | | Hong Kong | HKG2 | Gen2 | Core | 102 | Unique | | Hong Kong | HKG3 | Gen2 | Core | 103 | | | Taiwan | TPE1 | Gen2 | Core | 121 | | | Taiwan | TPE2 | Gen2 | Core | 122 | | | Tokyo | TYO1 | Gen2 | Edge | 111 | | | Tokyo | TYO2 | Gen2 | Core | 131 | Unique | | Singapore | SIN1 | Gen2 | Core | 151 | Unique | | Seattle | SEA | Gen2 | Core | 301 | | | Ashburn | IAD | Gen2 | Core | 302 | | | San Jose | SJC | Gen2 | Edge | 303 | | | Toronto | YYZ1 | Gen2 | Edge | 304 | Unique | | Moscow | MOW | Gen2 | Core | 201 | | | Frankfurt | FRA | Gen2 | Edge | 252 | | | Zurich | ZRH | Gen2 | Edge | 251 | | | Calais | CQF1 | Gen2 | Edge | 253 | Unique | | Berlin | BER | Gen2 | Edge | 254 | Unique | | London | LON | Gen2 | Edge | 255 | Unique | | Melbourne | MEL | Gen2 | Edge | 451 | | ## Type Definitions * **Core PoP**: Major interconnection points with multiple upstream providers * **Edge PoP**: Smaller presence focused on local connectivity ## Generation Definitions * **Gen2**: Second-generation infrastructure (current deployment) ## Using PoP Codes ### In Internal Communities Identify where a route was learned: ```bird2 # Learned-at tags (set by AS203314 on routes you receive): # (203314, 120, 101) -> HKG1 (Hong Kong) # (203314, 120, 131) -> TYO2 (Tokyo) # (203314, 120, 302) -> IAD (Ashburn) filter prefer_hkg1_routes_v4 { if (203314, 120, 101) ~ bgp_large_community then bgp_local_pref = 200; accept; } ``` ### In Control Communities Exclude specific PoPs from receiving announcements: ```bird2 bgp_large_community.add((203314, 202, 301)); # Do not announce via Seattle bgp_large_community.add((203314, 202, 131)); # Do not announce via Tokyo bgp_large_community.add((203314, 202, 102)); # Do not announce via HKG2 ``` ### Configuration Snippets (JunOS / BIRD2) Use PoP codes in the control community `203314:202:XXX` to exclude specific locations. For example, Calais is `253`, so the large community is `203314:202:253`. ### Junos ```bash set policy-options community HATS-NO-CQF members large:203314:202:253 set policy-options policy-statement EXPORT-TO-HATS term NO-CQF from route-filter 203.0.113.0/24 exact set policy-options policy-statement EXPORT-TO-HATS term NO-CQF then community add HATS-NO-CQF set policy-options policy-statement EXPORT-TO-HATS term NO-CQF then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` ### Bird2 ```bird2 filter export_to_hats_v4 { if net = 203.0.113.0/24 then { bgp_large_community.add((203314, 202, 253)); # no CQF accept; } reject; # Safety default } ``` ## Related Information * **[Region Codes](/docs/community/region-codes)** - Geographic region groupings * **[Internal Communities](/docs/community/internal-communities)** - Using PoP codes in location-based communities * **[Control Communities](/docs/community/control-communities)** - Using PoP codes in traffic engineering > **Tip**: PoP codes are primarily used for granular traffic engineering when you need to control route propagation at the location level. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/community/pop-codes). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Region Codes Regions are grouped by **geographic area** with 2-digit codes used in community strings like `203314:130:XX` and `203314:201:XX`. > **Usage**: These codes identify geographic regions in internal communities (`130:XX`, `135:XX`) and control communities (`201:XX`). ## Region Code Reference | Region Name | Area | Code | Notes | | ----------- | ----- | ---- | ---------------------------- | | Asia | West | 100 | Hong Kong, Taiwan | | Asia | East | 150 | Japan, Singapore | | Europe | West | 200 | UK, Ireland, France | | Europe | East | 250 | Germany, Netherlands, Russia | | Americas | North | 300 | USA, Canada | | Americas | South | 350 | Brazil, Argentina | | Australia | West | 400 | Perth | | Australia | East | 450 | Melbourne, Sydney | | Antarctica | - | 500 | Research networks | ## Regional Groupings ### Asia (100, 150) **Asia West (100)**: Hong Kong, Taiwan, mainland China **Asia East (150)**: Japan, Korea, Singapore, Southeast Asia ### Europe (200, 250) **Europe West (200)**: UK, Ireland, France, Benelux, Iberia **Europe East (250)**: Germany, DACH, Netherlands, Nordics, Eastern Europe ### Americas (300, 350) **North America (300)**: United States, Canada, Mexico **South America (350)**: Brazil, Argentina, Chile, Colombia ### Oceania (400, 450) **Australia West (400)**: Western Australia **Australia East (450)**: Eastern states (NSW, VIC, QLD) ## Using Region Codes ### In Internal Communities Identify where a route was learned: ```bird2 # Learned-in tags (set by AS203314 on routes you receive): # (203314, 130, 100) -> Asia West # (203314, 130, 150) -> Asia East # (203314, 130, 300) -> North America filter prefer_asia_west_routes_v4 { if (203314, 130, 100) ~ bgp_large_community then bgp_local_pref = 200; accept; } ``` ### In Control Communities Control geographic propagation: ```bird2 bgp_large_community.add((203314, 2, 1)); # Disable cross-region bgp_large_community.add((203314, 201, 300)); # Exclude North America bgp_large_community.add((203314, 201, 200)); # Exclude Europe ``` ### Configuration Snippets (JunOS / BIRD2) Region codes are used in large communities like `203314:201:XX` (exclude region) and `203314:130:XX` (learned in region). Below are minimal examples you can adapt. ### Junos **Exclude North America (`203314:201:300`)** ```bash set policy-options community HATS-NO-NA members large:203314:201:300 set policy-options policy-statement EXPORT-TO-HATS term NO-NA from route-filter 203.0.113.0/24 exact set policy-options policy-statement EXPORT-TO-HATS term NO-NA then community add HATS-NO-NA set policy-options policy-statement EXPORT-TO-HATS term NO-NA then accept set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then reject ``` **Prefer routes learned in Asia West (`203314:130:100`)** ```bash set policy-options community HATS-ASIA-W members large:203314:130:100 set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W from community HATS-ASIA-W set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W then local-preference 200 set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W then accept ``` ### Bird2 **Exclude North America (`203314:201:300`)** ```bird2 filter export_to_hats_v4 { if net = 203.0.113.0/24 then { bgp_large_community.add((203314, 201, 300)); accept; } reject; # Safety default } ``` **Prefer routes learned in Asia West (`203314:130:100`)** ```bird2 filter import_from_hats_v4 { if (203314, 130, 100) ~ bgp_large_community then bgp_local_pref = 200; accept; } ``` ### Regional Filtering Examples **Accept only Asian routes**: ```text # Allow only Asia West and Asia East if (community matches 203314:130:1*) then accept else reject ``` **Prefer local region**: ```text # Higher local preference for Asia West if (community matches 203314:130:100) then localpref 200 if (community matches 203314:130:150) then localpref 150 if (community matches 203314:130:300) then localpref 100 ``` ## Related Information * **[PoP Codes](/docs/community/pop-codes)** - Specific location codes within regions * **[Internal Communities](/docs/community/internal-communities)** - Using region codes in location-based communities * **[Control Communities](/docs/community/control-communities)** - Using region codes in traffic engineering > **Tip**: Region codes are ideal for high-level geographic traffic engineering when you don't need PoP-level granularity. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/community/region-codes). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Content and Data License **Effective date:** July 12, 2026 Hats Network Inc. makes selected public data and original documentation available under the Creative Commons licenses described below. These licenses apply only to material for which Hats Network Inc. owns the necessary rights. ## Public Latency Data — CC BY 4.0 The publicly displayed Hats Network Backbone Latency Dataset is licensed under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/). This dataset includes published RTT measurements, PoP codes, city and region labels, update dates, and public exports derived from those measurements. You may share and adapt this data, including commercially, provided that you give appropriate credit, link to the license and source dataset, and indicate whether changes were made. Suggested attribution: > Hats Network Backbone Latency Dataset © Hats Network Inc., > [https://hatsnet.io/docs/network/latency](https://hatsnet.io/docs/network/latency), licensed under CC BY 4.0. ## Original Documentation — CC BY-SA 4.0 Original explanatory articles published in Hats Network Documentation are licensed under the [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/), unless a page states otherwise. You may share and adapt these articles, including commercially, provided that you give appropriate credit, link to the license, indicate changes, and distribute adaptations under the same or a compatible license. Suggested attribution: > “\[Article title],” Hats Network Documentation © Hats Network Inc., \[original article URL], > licensed under CC BY-SA 4.0. ## Exclusions These Creative Commons licenses do not apply to: * Hats Network names, trademarks, service marks, logos, or other brand assets; * software, source code, configuration, APIs, or infrastructure designs; * third-party text, images, data, trademarks, or other material; * customer information, private telemetry, raw operational logs, credentials, or security data; * network services, service-level commitments, commercial offers, or contractual rights. Third-party material remains subject to its original terms. Nothing in these licenses grants permission to imply endorsement by or affiliation with Hats Network Inc. ## No Warranty Licensed content and data are provided “as is,” without warranties of accuracy, completeness, availability, fitness for a particular purpose, or non-infringement. To the maximum extent permitted by law, Hats Network Inc. is not liable for losses arising from their use. For licensing questions, contact [legal@hatsnet.io](mailto:legal@hatsnet.io). --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/legal/content-and-data-license). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Legal This section collects all legal documents and policies that govern the Hats Network Inc. (AS203314) website, documentation, and open data publications. - [Privacy Policy](/docs/legal/privacy-policy) — How we collect, use, and protect personal information. - [Terms of Service](/docs/legal/terms-of-service) — The terms that govern use of our website and services. - [Content & Data License](/docs/legal/content-and-data-license) — Licensing for documentation content (CC BY-SA 4.0) and open data (CC BY 4.0). - [Report Abuse](/docs/legal/report-abuse) — How to report abuse originating from our network. - [IP Rental](/docs/legal/ip-rental) — Terms specific to IP address rental services. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/legal). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # IP Address Rental Terms > **Effective Date:** June 1, 2024\ > **Last Revised:** August 24, 2024 ## 1. Service Description Our company provides IP address rental services. The lessee agrees to comply with all applicable laws, regulations, and these Terms of Service. > **What is IP Rental?** > > IP Address Rental allows you to lease IPv4 or IPv6 addresses from Hats Network Inc. for your infrastructure needs. This service is ideal for: > > * Hosting providers requiring additional IP space > * Research and development projects > * Temporary network expansions ## 2. Responsibilities and Penalties Lessees are responsible for all activities associated with their rented IP address. ### General Complaints > **Penalty:** $5 per incident, maximum $20 per billing period Including but not limited to: * DMCA copyright complaints * Spam complaints (unsolicited email) * Unauthorized marketing activity complaints * Minor service abuse complaints ### Severe Misconduct > **Penalty:** $15 per incident, maximum $30 per billing period > > Severe misconduct carries heavier penalties and may lead to swift suspensions. Including but not limited to: * Network scanning activities (port scanning, vulnerability scanning) * Spreading malware or viruses * Participating in network attacks (DDoS, brute force) * Unauthorized system intrusion attempts * Phishing activities * Hosting illegal content ### IP Blacklisting > **Penalty:** \$30 per incident OR 6-month service extension IP addresses listed on major blacklists including: | Blacklist | Type | | --------------------- | ----------------------------------- | | Spamhaus | Email reputation | | DNSBL | DNS-based blacklist | | SORBS | Spam and Open Relay Blocking System | | SpamCop | Spam reporting | | Cisco Talos | Security intelligence | | Microsoft SmartScreen | Email filtering | | Google Safe Browsing | Web safety | ## 3. Payment and Penalty Enforcement > **Important:** All penalty fees will be added to the lessee's next invoice. Penalties take effect immediately upon notification. Failure to pay may result in service suspension or termination. ### Payment Terms * Invoices are issued monthly * Payment is due within 14 days of invoice date * Late payments subject to 1.5% monthly service charge * All fees are non-refundable unless otherwise stated ## 4. Service Termination > **Termination Policy** > > The company reserves the right to terminate services due to severe or repeated violations **without refund**. ### Severe Violations Include: * Multiple occurrences of severe misconduct * Repeated IP blacklisting * Engagement in illegal activities * Non-payment of fees for 30+ days ### Voluntary Termination: Lessees may terminate service with 30 days written notice. No refunds for prepaid unused periods. ## 5. Disclaimer The company is not responsible for any losses or damages resulting from the lessee's use of the IP address. The lessee agrees to indemnify and hold the company harmless from any claims arising from their use of the service. ## 6. Monitoring and Reporting > The company has the right to monitor IP usage to ensure compliance with these terms. Lessees agree to promptly report any abuse or unauthorized use. We monitor for: * Unusual traffic patterns * Blacklist status changes * Abuse reports from third parties * Compliance with AUP (Acceptable Use Policy) ## 7. Amendment of Terms The company reserves the right to modify these Terms of Service at any time. Modified terms will be: 1. Posted on the company website 2. Emailed to the lessee's registered contact 3. Effective 30 days after posting **Continued use implies acceptance of modified terms.** ## 8. Notice of Changes The company reserves the right to make changes to these terms without prior notice in cases of: * Emergency security issues * Legal or regulatory requirements * Force majeure events ## Questions? - [Contact Sales](mailto:sales@hatsnet.io) — For questions about IP rental availability and pricing. - [Contact Support](mailto:support@hatsnet.io) — For abuse reports or compliance questions. *** > *By using this service, the lessee agrees to abide by these terms.* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/legal/ip-rental). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Privacy Policy > **Effective Date:** March 24, 2026\ > **Last Revised:** March 24, 2026 ## Introduction Hats Network Inc. (AS203314) is committed to protecting your privacy and ensuring you have a positive experience on our website and while using our services. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our website and use our services. > Please read this Privacy Policy carefully. If you do not agree with our policies and practices, please do not use our services. ## Information We Collect ### Information You Provide Directly * Contact information (name, email, phone, company name) via contact forms * Account information when you register for services * Payment information processed securely through third-party providers * Communication history and support inquiries ### Information Collected Automatically * IP address and device information * Browser type and operating system * Pages visited, time spent, and referring URLs * Network performance metrics and latency measurements * Cookies and similar tracking technologies ## How We Use Your Information We use the information we collect for the following purposes: * Provide, maintain, and improve our services * Process transactions and send related information * Send technical notices and support messages * Respond to inquiries and customer support requests * Monitor and analyze usage patterns and service performance * Detect, prevent, and address technical issues and fraud * Comply with legal obligations and enforce agreements * Send marketing communications (with your consent) ## Information Sharing > We do not sell your personal information to third parties. We may share information with: * **Service providers** - Hosting, payment processing, analytics * **Business partners** - With your consent * **Law enforcement** - When required by law * **Other parties** - In connection with company transactions ## Data Security We implement appropriate technical and organizational measures to protect your data against unauthorized access, alteration, disclosure, or destruction. However, no method of transmission over the internet or electronic storage is 100% secure. We cannot guarantee absolute security. > You are responsible for maintaining the confidentiality of your account credentials. ## Cookies and Tracking We use cookies to enhance your experience and analyze site usage. You may control cookie settings through your browser preferences. Third-party analytics providers may collect usage data to help us understand how visitors use our site. ## Third-Party Links Our site may contain links to external sites not governed by this privacy policy. We are not responsible for the privacy practices of third-party websites. ## Children's Privacy > Our services are not directed to persons under 18 years of age. We do not knowingly collect personal information from children under 18. ## Your Privacy Rights Depending on your jurisdiction, you may have rights to: * **Access** - Request a copy of your personal data * **Correction** - Update inaccurate or incomplete information * **Deletion** - Request deletion of your personal data (subject to legal obligations) * **Portability** - Receive your data in a structured, commonly used format * **Opt-out** - Decline marketing communications To exercise these rights, contact us at [privacy@hatsnet.io](mailto:privacy@hatsnet.io). ## Data Retention We retain your information as long as necessary to: * Provide services to you * Comply with legal obligations * Resolve disputes and enforce agreements * Maintain business records Once the purpose is fulfilled, we securely delete or anonymize the information. ## Changes to Privacy Policy > We may update this policy periodically. Changes take effect 30 days after posting on our website. > > **Continued use of our services implies acceptance of the updated policy.** ## Contact Us - [Privacy Questions](mailto:privacy@hatsnet.io) — For privacy-related inquiries. - [Account & Security](mailto:support@hatsnet.io) — For account security concerns. *** *By using Hats Network Inc. services, you acknowledge that you have read and understood this Privacy Policy.* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/legal/privacy-policy). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Report Abuse ## How to Report Abuse If you have discovered abusive activity involving Hats Network Inc. infrastructure, please report it to our Security Team: - [Email Report](mailto:abuse@hatsnet.io) — Send abuse reports with detailed information to our Security Team. > Our Security Team will investigate your report accordingly. Please note that we may not be able to provide specific updates regarding your report(s) due to privacy reasons. ## Required Information To expedite investigation, your abuse report **must include**: Source IP address(es) The IP address(es) originating the abusive activity. Destination IP address(es) The IP address(es) being targeted or receiving the abuse. Destination port(s) Specific port(s) involved in the abusive activity. Exact date/time stamp and timezone Precise timing of the activity (e.g., 2026-03-24 15:30:45 UTC). > **Important Notice** > > *Incomplete reports may not be processed.* If your abuse report does not contain enough information to identify the source of the abuse, we may not follow up with you regarding your report(s). ## Important Notice ### Blacklisted Report Sources Abuse reports from the following sources will be **automatically ignored** due to history of false reports: | Source | Status | | ------------- | ----------- | | bitninja.info | Blacklisted | | myipr.com.cn | Blacklisted | | aldimna.com | Blacklisted | ### Ignored Email Domains > **Note** > > When submitting an abuse report, please use your **work email** address whenever possible to ensure that the report is properly investigated. Reports from these email domains will not be processed: | Domain | Status | | ------------------- | ----------- | | @tsinghua.edu.org | Ignored | | @163.com / @126.com | Gray-listed | | @qq.com | Gray-listed | | @sina.com | Gray-listed | | @mail.ru | Gray-listed | ## What Constitutes Abuse? Reportable abusive activities include: * **DDoS Attacks** - Distributed Denial of Service attacks * **Malware Distribution** - Hosting or spreading malicious software * **Phishing** - Unauthorized attempts to collect sensitive information * **Network Scanning** - Unauthorized port scans or vulnerability assessments * **Spam** - Unsolicited bulk communications * **Copyright Infringement** - Unauthorized use of intellectual property * **Illegal Content** - Hosting of illegal material * **Intrusion Attempts** - Unauthorized access to systems ## Security Best Practices When reporting abuse: 1. **Include Evidence** - Packet captures, logs, or screenshots when possible 2. **Be Specific** - Provide exact timestamps and port information 3. **One Report Per Issue** - Submit separate reports for different incidents 4. **Follow Up** - Reference your original email if sending additional information ## Investigation Timeline | Report Type | Processing Time | Notes | | -------------- | --------------- | ------------------------------------ | | Standard Email | 24-48 hours | Reviewed during business hours (UTC) | | Urgent Cases | 4 hours | Critical infrastructure threats only | > All reports are treated confidentially. Do not publicly disclose that you have reported abuse to Hats Network Inc., as this may compromise the investigation. *** Thank you for helping keep our network secure and abuse-free. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/legal/report-abuse). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Terms of Service > **Effective Date:** March 24, 2026\ > **Last Revised:** July 12, 2026 ## Agreement to Terms By accessing and using this website and services provided by Hats Network Inc. (AS203314), you accept and agree to be bound by the terms and provision of this agreement. > If you do not agree to abide by these terms, please do not use this service. We reserve the right to modify these terms at any time. Your continued use of the website following the posting of revised Terms means that you accept and agree to the changes. ## Service Description Hats Network Inc. provides: * IP transit with redundant upstream connections * Direct Internet Exchange (IX) peering * Low-latency routing with specialized network optimization * Network monitoring and DDoS mitigation * Custom network solutions for enterprise clients ## Acceptable Use Policy ### Prohibited Activities You agree not to engage in any of the following prohibited activities: ### Common * Harassment, abuse, or threats toward individuals or organizations - Transmission of malware, viruses, or harmful code - Spam or unsolicited bulk email transmission - Copyright infringement or intellectual property violation - Phishing, spoofing, or social engineering attacks ### Severe * Network scanning, port scanning, or vulnerability assessment without authorization - Distributed Denial of Service (DDoS) attacks or similar abuse - Unauthorized access or intrusion attempts - Hosting of illegal content or facilitating illegal services - Any illegal activities or violation of laws and regulations ### Violation Penalties | Violation Type | Penalty | Consequence | | ------------------- | ----------------- | ------------------------- | | First violation | Written warning | $5-$15 penalty fee | | Repeated violations | Multiple warnings | Service suspension option | | Severe violation | Immediate action | Service termination | | Criminal activity | Legal reporting | Law enforcement involved | > **Important** > > The company reserves the right to terminate services **without refund** for severe or repeated violations. ## Payment Terms > **Billing Cycle:** Monthly * Invoices issued on the first day of each billing period * Payment due within 14 days of invoice date * Accepted payment methods: credit card, bank transfer, ACH * Late payments subject to 1.5% monthly service charge * Service suspension after 30 days of non-payment * All fees are exclusive of applicable taxes and levies * Refund policy: No refunds for partial months or prepaid periods ## Service Levels & Uptime Hats Network Inc. commits to maintaining **99.99% network availability** across our core infrastructure. ### SLA Details * Uptime calculated monthly * Excludes scheduled maintenance windows * Excludes force majeure events * Scheduled maintenance announced ≥14 days in advance when possible * Service credits available for downtime exceeding SLA (details in service agreement) * Network performance statistics available via portal and API ## Limitation of Liability > TO THE MAXIMUM EXTENT PERMITTED BY LAW, HATS NETWORK INC. > > SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES. Our liability is limited to the amount paid by customer in the 12 months preceding the claim. ### We are not responsible for: * Third-party network issues or connectivity problems * Data loss or corruption caused by misuse or negligence * Service interruptions due to force majeure events * Loss of revenue, profit, or business opportunities * Customer's failure to maintain backups or redundancy ## Service Termination ### Either Party May Terminate * 30 days written notice required * Customer must migrate services within 30 days * Customer must remove any IPs in use within 30 days * No refunds provided for customer-initiated termination ### Immediate Termination Permitted For: * Material breach of this agreement by either party * Illegal activity or security violations * Non-payment of invoices for 30+ days * Violation of Acceptable Use Policy ## Additional Terms ### Intellectual Property and Open Licenses Unless expressly licensed otherwise, Hats Network Inc. retains all rights in its services, software, branding, and materials. Public latency datasets and original documentation articles are available under the terms described in our [Content and Data License](/docs/legal/content-and-data-license). - **Intellectual Property** — Openly licensed materials follow our Content and Data License; all other rights are reserved. - **Warranties Disclaimer** — Services provided 'as-is' without warranties. We don't warrant uninterrupted service. - **Indemnification** — You indemnify us from claims arising from service use or terms violations. - **Governing Law** — Governed by applicable laws. Disputes resolved through binding arbitration. - **Entire Agreement** — This agreement and service amendments constitute the entire agreement. - **Severability** — If any provision is invalid, remaining provisions continue in full effect. ## Questions? - [Legal Questions](mailto:legal@hatsnet.io) — For legal inquiries and interpretations. - [Abuse Reports](mailto:abuse@hatsnet.io) — Report violations and suspicious activity. - [Technical Support](mailto:support@hatsnet.io) — For service and technical support. *** > *By using Hats Network Inc. services, you acknowledge that you have read, understood, and agree to be bound by these Terms of Service.* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/legal/terms-of-service). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Peering Policy - AS203314 > **Open Peering Policy** > > Hats Network Inc. (AS203314) maintains an **open peering policy**. We welcome peering requests from networks that meet the requirements below, subject to available capacity, route security, operational readiness, and mutual agreement. > > Current interconnection locations, addresses, and network statistics are maintained on our [PeeringDB record](https://www.peeringdb.com/asn/203314), which is the authoritative source for operational peering data. ## Policy at a Glance | Item | Policy | | --------------------- | ---------------------------------------------------------------------------------------- | | General policy | Open | | Autonomous system | AS203314 | | IRR AS-SET | `AS203314:AS-HATS` | | Address families | IPv4 and IPv6; dual-stack sessions are preferred where both are available | | Traffic ratio | No fixed ratio requirement | | Minimum IX traffic | None | | Multiple locations | Preferred for resilience | | Bilateral IX contract | Not normally required | | Operational source | [PeeringDB](https://www.peeringdb.com/asn/203314) for current IX, facility, and NOC data | ## Technical Requirements Networks requesting peering must: 1. Operate a publicly routable **Autonomous System Number (ASN)**. 2. Announce at least one globally routable **IPv4 /24** or **IPv6 /48** prefix. 3. Maintain a complete and current [PeeringDB](https://www.peeringdb.com/) profile, including routing, facility, and 24×7 NOC information. 4. Maintain accurate route or route-set objects in a public **Internet Routing Registry (IRR)**. 5. Connect at a shared Internet Exchange or data centre, or use a mutually approved [Layer 2/3 tunnel](/docs/peering/via-tunnel) endpoint. 6. Provide sufficient, stable interconnection capacity and avoid sustained congestion or packet loss. Dual-stack peering is preferred whenever both networks support IPv4 and IPv6 at the interconnection. Single-stack sessions may be accepted when an address family is unavailable at a specific location. ## Routing and Security Policy ### Route registration and validation * Peers must keep their IRR objects, RPKI Route Origin Authorizations (ROAs), and PeeringDB data accurate and up to date. * AS203314 builds inbound filters from public routing data and may reject unregistered routes, RPKI-invalid announcements, bogons, default routes, malformed AS paths, and prefixes more specific than IPv4 /24 or IPv6 /48. * Peers should announce only their own routes and customer routes represented by their published AS-SET. * Route-security practices should align with [MANRS](https://www.manrs.org/) principles. RPKI-valid announcements are strongly preferred; RPKI-invalid announcements are rejected. ### Route exchange * AS203314 generally advertises its eligible routes in all peering locations. Announcements may vary for maintenance, traffic engineering, security, or service-specific reasons. * We accept standard BGP communities where operationally supported. See our [BGP Communities reference](/docs/community) for available controls. * Peers must configure a reasonable maximum-prefix limit based on current PeeringDB and IRR data, with enough headroom for normal growth. Material changes should be coordinated with our NOC. * Do not rely on Multi-Exit Discriminator (MED) handling unless it has been agreed in advance. * Neither party may use a static route, a default route, or any other mechanism to send traffic for destinations not announced to that party through BGP. * Traffic may not be forwarded through a third party over the peering interconnection unless both networks have explicitly agreed to that service. > **Filtering and session protection** > > AS203314 may suspend a session that leaks routes, exceeds its agreed prefix limit, causes instability, or creates a security or operational risk. We will make a reasonable effort to notify the peer through its registered NOC contact. ## Operational Requirements Peers must provide a [**24×7 NOC**](/docs/about#contact-us) capable of working with us on routing incidents, performance degradation, denial-of-service attacks, abuse, and security events. * NOC email and telephone details must remain current on PeeringDB. * Both parties should communicate planned maintenance that may materially affect the interconnection. * Peers must investigate route leaks, session instability, abuse, or congestion promptly. * BGP MD5 and BFD may be enabled where supported and mutually agreed. * Operational issues should be reported to [noc@hatsnet.io](mailto:noc@hatsnet.io); new peering requests should be sent to [peering@hatsnet.io](mailto:peering@hatsnet.io). ## Capacity and Traffic * There is **no minimum traffic requirement** for peering over an Internet Exchange. * A [Private Network Interconnect (PNI)](/docs/peering/via-cross-connect) may be preferred when traffic is sustained above **1 Gbps**, when an IX path is congested, or when resilience and traffic engineering justify a dedicated interconnection. * PNI speed, optics, cross-connect, and redundancy are agreed per location. 10G and 100G single-mode fibre are preferred where available. * Peers should begin capacity-upgrade planning when sustained peak utilization exceeds **50%**, and complete the upgrade before congestion affects traffic. ## How to Peer ### Step 1: Verify eligibility Confirm the requirements above and review our current [PeeringDB record](https://www.peeringdb.com/asn/203314) for common locations, session addresses, and expected route counts. ### Step 2: Send a request Email [peering@hatsnet.io](mailto:peering@hatsnet.io) with your ASN, PeeringDB URL, requested location and address families, expected traffic, advertised prefix count, and preferred interconnection method. ### Step 3: Configure and validate After both parties confirm the session details, configure route filters, maximum-prefix protection, and any agreed MD5 or BFD settings. We will validate route exchange and reachability before considering the session operational. ## Peering Methods - [Internet Exchange](https://www.peeringdb.com/asn/203314) — Public peering at our current Internet Exchange locations. - [Private Interconnect (PNI)](/docs/peering/via-cross-connect) — Dedicated cross-connect or private VLAN at a supported facility. - [Tunnel Peering](/docs/peering/via-tunnel) — A mutually approved Layer 2 or Layer 3 tunnel interconnection. ## Policy Administration Meeting this policy does not guarantee a peering relationship. Hats Network may accept, decline, suspend, or terminate peering where capacity, security, commercial, legal, or operational considerations require it. We may update this policy as our network evolves; material session changes will be coordinated through the registered NOC contacts whenever practical. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/peering). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Peering via Cross Connect (PNI) ## Supported Data Centres We currently allow Private Network Interconnect (PNI) at the following data centres, grouped by country/region: ### 🇭🇰 Hong Kong * [Equinix HK1](https://www.equinix.com/data-centers/asia-pacific-colocation/hong-kong-colocation/hong-kong-data-centers/hk1) * [Equinix HK2](https://www.equinix.com/data-centers/asia-pacific-colocation/hong-kong-colocation/hong-kong-data-centers/hk2) * [Equinix HK3](https://www.equinix.com/data-centers/asia-pacific-colocation/hong-kong-colocation/hong-kong-data-centers/hk3) * [TGT Hong Kong DC 2](https://www.towngastelecom.com/locations/) ### 🇯🇵 Japan * [Equinix TY8](https://www.equinix.com/locations/asia-colocation/japan-colocation/tokyo-data-centers/ty8/) * [Equinix TY9](https://www.equinix.com/locations/asia-colocation/japan-colocation/tokyo-data-centers/ty9/) ### 🇸🇬 Singapore * [Equinix SG1](https://www.equinix.com/locations/singapore-colocation/singapore-data-center/sg1/) ### 🇺🇸 United States * [CoreSite LA2](https://www.coresite.com/data-center/la2-los-angeles-ca) > To arrange a cross-connect, please [contact our peering team](/docs/about#contact-us). --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/peering/via-cross-connect). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Peering via Layer 2 Tunnel Layer 2 tunnels encapsulate Ethernet frames, creating a virtual bridge between networks. Use this when you need to carry VLAN-tagged traffic or extend a broadcast domain. > **Layer 2 Tunnel Overview** > > In all examples below, replace placeholder values with your actual configuration: > > * `{name}` - Tunnel interface name > * `{yourside ip}` - Your public IP address > * `{ourside ip}` - Our endpoint IP address > * `{your tunnel ip cidr}` - Your tunnel IP/subnet > * `{vni}` - VxLAN Network Identifier (24-bit value) ## Protocol Choice ## GRETAP **GRETAP** (GRE Bridging) operates at Layer 2, encapsulating Ethernet frames inside GRE. Use this when you need a transparent L2 bridge over the tunnel. ### Shell ```shell ip link add {name} type gretap local {yourside ip} remote {ourside ip} ttl 255 ip addr add {your tunnel ip cidr} dev {name} ip link set dev {name} up ``` ### Netplan 1. Create a Netplan configuration file: ```yaml title="/etc/netplan/10-{name}.yaml" network: version: 2 tunnels: { name }: mode: gretap local: { yourside ip } remote: { ourside ip } ttl: 255 addresses: - { your tunnel ip cidr } ``` 2. Apply the configuration: ```sh netplan apply ``` ### Systemd 1. Create the `.netdev` file: ```ini title="/etc/systemd/network/10-{name}.netdev" [NetDev] Name = {name} Kind = gretap [Tunnel] Local = {yourside ip} Remote = {ourside ip} TTL = 255 ``` 2. Configure the tunnel IP address: ```ini title="/etc/systemd/network/10-{name}.network" [Match] Name = {name} [Network] Address = {your tunnel ip cidr} ``` 3. Apply the configuration: ```sh systemctl restart systemd-networkd ``` ## VxLAN **VxLAN** (Virtual Extensible LAN) is a Layer 2 overlay protocol that encapsulates Ethernet frames in UDP. It's designed for large-scale multi-tenant environments and software-defined networks. > The default VxLAN destination port is **4789** (IANA-assigned). The VNI is a 24-bit identifier (0-16777215). ### Shell ```shell ip link add {name} type vxlan local {yourside ip} remote {ourside ip} dstport 4789 id {vni} ttl 255 ip addr add {your tunnel ip cidr} dev {name} ip link set dev {name} up ``` ### Netplan > Netplan's VxLAN support requires **netplan ≥ 0.106** (Ubuntu 23.04+). 1. Create a Netplan configuration file: ```yaml title="/etc/netplan/10-{name}.yaml" network: version: 2 tunnels: { name }: mode: vxlan local: { yourside ip } remote: { ourside ip } port: 4789 id: { vni } ttl: 255 addresses: - { your tunnel ip cidr } ``` 2. Apply the configuration: ```sh netplan apply ``` ### Systemd 1. Create the `.netdev` file: ```ini title="/etc/systemd/network/10-{name}.netdev" [NetDev] Name = {name} Kind = vxlan [VXLAN] VNI = {vni} Local = {yourside ip} Remote = {ourside ip} DestinationPort = 4789 TTL = 255 ``` 2. Configure the tunnel IP address: ```ini title="/etc/systemd/network/10-{name}.network" [Match] Name = {name} [Network] Address = {your tunnel ip cidr} ``` 3. Apply the configuration: ```sh systemctl restart systemd-networkd ``` ## GRETAP vs VxLAN | Feature | GRETAP | VxLAN | | ------------------ | ---------------- | ------------------- | | Protocol | IP Protocol 47 | UDP port 4789 | | Encapsulation | GRE header | UDP + VxLAN header | | MTU overhead | 38 bytes | 50 bytes | | NAT traversal | Limited | Better (UDP-based) | | Multi-cast support | Yes | Yes | | Use case | Simple L2 bridge | Data center overlay | ## Considerations > **Important Notes for Layer 2 Tunneling** > > * **MTU**: Layer 2 tunnels add significant overhead. Reduce your MTU accordingly (typically 1450-1476 bytes). > * **Broadcast domain**: The tunnel extends your broadcast domain, which may cause issues with certain protocols. > * **Spanning Tree**: Be cautious with STP over tunnels-consider using RSTP or disabling STP on the tunnel interface. > * **Performance**: Layer 2 tunneling has more overhead than Layer 3. Use only when necessary. ## Next Steps Once you have configured the tunnel: 1. Verify connectivity using `ping` or `traceroute` 2. Configure your BGP daemon (BIRD, FRR, etc.) to use the tunnel interface 3. [Contact us](/docs/about#contact-us) to finalize the peering session > **Prefer Layer 3?** For most peering scenarios, Layer 3 tunnels (WireGuard, GRE) are recommended due to lower overhead and better performance. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/peering/via-layer2-tunnel). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Peering via Layer 3 Tunnel Layer 3 tunnels encapsulate IP packets at the network layer. This is the recommended approach for most peering scenarios due to lower overhead and better performance compared to Layer 2 tunneling. > **Layer 3 Tunnel Overview** > > In all examples below, replace placeholder values with your actual configuration: > > * `{name}` - Tunnel interface name > * `{yourside ip}` - Your public IP address > * `{ourside ip}` - Our endpoint IP address > * `{yourside port}` - Your source port (WireGuard) > * `{ourside port}` - Our destination port (WireGuard) > * `{your tunnel ip cidr}` - Your tunnel IP/subnet > * `{our public key}` - Our WireGuard public key > * `{your private key}` - Your WireGuard private key ## Tunnel Profile Selection ## WireGuard **WireGuard** is a modern, lightweight VPN protocol that provides encrypted Layer 3 tunneling. It's our recommended choice for secure peering due to its simplicity and performance. ### Wg Quick Create a WireGuard configuration file: ```ini title="/etc/wireguard/{name}.conf" [Interface] Address = {your tunnel ip cidr} ListenPort = {yourside port} PrivateKey = {your private key} # Disable WireGuard's built-in routing table management when using # an external routing daemon (e.g. BIRD, FRR) Table = off [Peer] PublicKey = {our public key} AllowedIPs = 0.0.0.0/0, ::/0 Endpoint = {ourside ip}:{ourside port} PersistentKeepalive = 25 ``` ### Systemd 1. Create the `.netdev` file: ```ini title="/etc/systemd/network/10-{name}.netdev" [NetDev] Name = {name} Kind = wireguard [WireGuard] ListenPort = {yourside port} PrivateKey = {your private key} [WireGuardPeer] PublicKey = {our public key} AllowedIPs = 0.0.0.0/0, ::/0 Endpoint = {ourside ip}:{ourside port} PersistentKeepalive = 25 ``` 2. Configure the tunnel IP address: ```ini title="/etc/systemd/network/10-{name}.network" [Match] Name = {name} [Network] Address = {your tunnel ip cidr} ``` 3. Apply the configuration: ```sh systemctl restart systemd-networkd ``` ### Enable Enable and start the WireGuard service (wg-quick only): ```sh systemctl enable --now wg-quick@{name} ``` ## GRE Tunnel **GRE** (Generic Routing Encapsulation) operates at Layer 3 and is suitable for routing IPv4/IPv6 traffic over an IPv4 underlay. It's simple, widely-supported, and has minimal overhead. ### Shell ```shell ip tunnel add {name} mode gre local {yourside ip} remote {ourside ip} ttl 255 ip addr add {your tunnel ip cidr} dev {name} ip link set dev {name} up ``` ### Netplan 1. Create a Netplan configuration file: ```yaml title="/etc/netplan/10-{name}.yaml" network: version: 2 tunnels: { name }: mode: gre local: { yourside ip } remote: { ourside ip } ttl: 255 addresses: - { your tunnel ip cidr } ``` 2. Apply the configuration: ```sh netplan apply ``` ### Systemd 1. Create the `.netdev` file: ```ini title="/etc/systemd/network/10-{name}.netdev" [NetDev] Name = {name} Kind = gre [Tunnel] Local = {yourside ip} Remote = {ourside ip} TTL = 255 ``` 2. Configure the tunnel IP address: ```ini title="/etc/systemd/network/10-{name}.network" [Match] Name = {name} [Network] Address = {your tunnel ip cidr} ``` 3. Apply the configuration: ```sh systemctl restart systemd-networkd ``` ## SIT / ip6gre (IPv6 Tunneling) **SIT** (Simple Internet Transition) tunnels IPv6 traffic over an IPv4 underlay and is commonly used for 6in4 connectivity. **ip6gre** provides full GRE encapsulation for IPv6 and is preferred when you need GRE key support or multi-protocol capability. ### Sit Shell ```shell # SIT: IPv6-in-IPv4 ip tunnel add {name} mode sit local {yourside ipv4} remote {ourside ipv4} ttl 255 ip addr add {your tunnel ipv6 cidr} dev {name} ip link set dev {name} up ``` ### Ip6gre Shell ```shell # ip6gre: GRE over IPv4 carrying IPv6 ip tunnel add {name} mode ip6gre local {yourside ipv4} remote {ourside ipv4} ttl 255 ip addr add {your tunnel ipv6 cidr} dev {name} ip link set dev {name} up ``` ### Netplan 1. Create a Netplan configuration file: ```yaml title="/etc/netplan/10-{name}.yaml" network: version: 2 tunnels: { name }: # Use 'sit' for 6in4, or 'ip6gre' for GRE-encapsulated IPv6 mode: sit local: { yourside ipv4 } remote: { ourside ipv4 } ttl: 255 addresses: - { your tunnel ipv6 cidr } ``` 2. Apply the configuration: ```sh netplan apply ``` ### Systemd 1. Create the `.netdev` file: ```ini title="/etc/systemd/network/10-{name}.netdev" [NetDev] Name = {name} # Kind = sit (for 6in4) # Kind = ip6gre (for GRE over IPv4 carrying IPv6) Kind = sit [Tunnel] Local = {yourside ipv4} Remote = {ourside ipv4} TTL = 255 ``` 2. Configure the tunnel IP address: ```ini title="/etc/systemd/network/10-{name}.network" [Match] Name = {name} [Network] Address = {your tunnel ipv6 cidr} ``` 3. Apply the configuration: ```sh systemctl restart systemd-networkd ``` ## Protocol Comparison | Protocol | Encryption | IPv4 | IPv6 | Overhead | NAT Traversal | | --------- | ---------- | ---- | ---- | -------- | ------------- | | WireGuard | Yes | ✓ | ✓ | 32 bytes | Good (UDP) | | GRE | No | ✓ | ✓ | 28 bytes | Limited | | SIT | No | N/A | ✓ | 20 bytes | Limited | | ip6gre | No | N/A | ✓ | 28 bytes | Limited | > **Protocol Selection Guide** > > * **WireGuard**: Best for secure peering, supports both IPv4 and IPv6 > * **GRE**: Simple, widely-supported, good for IPv4 peering > * **SIT/ip6gre**: Use when you only need IPv6 transport over IPv4 ## MTU Considerations Layer 3 tunnels add overhead to each packet. Adjust your MTU accordingly: | Protocol | Overhead | Recommended MTU | | --------- | -------- | --------------- | | WireGuard | 32 bytes | 1468 | | GRE | 28 bytes | 1472 | | SIT | 20 bytes | 1480 | | ip6gre | 28 bytes | 1472 | Example for WireGuard: ```sh ip link set dev {name} mtu 1468 ``` ## Next Steps Once you have configured the tunnel: 1. Verify connectivity using `ping` or `traceroute` 2. Configure your BGP daemon (BIRD, FRR, etc.) to use the tunnel interface 3. [Contact us](/docs/about#contact-us) to finalize the peering session > After successfully setting up the tunnel, contact us to finalize the peering session with AS203314. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/peering/via-layer3-tunnel). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Peering via Tunnel Establishing a peering connection with AS203314 via tunnel is useful when physical interconnection is not feasible. We support both Layer 2 and Layer 3 tunneling protocols. > **When to Use Tunnel Peering** > > Tunnel peering is typically used when: > > * You're not co-located with us at any IXP or data center > * Physical cross-connect is not available or cost-prohibitive > * You need a temporary peering arrangement before establishing physical connectivity > * You're in a region where we don't have physical presence ## Tunnel Architecture ## Layer 2 vs Layer 3 Tunneling ### L2 **Layer 2 tunnels** encapsulate Ethernet frames, creating a virtual bridge between networks. **Protocols**: GRETAP, VxLAN **Use cases**: * Carrying VLAN-tagged traffic * Running bridging protocols (STP, LLDP) * Extending a broadcast domain **Considerations**: Higher overhead than Layer 3, not suitable for long-distance peering. [Learn more about Layer 2 tunnels →](/docs/peering/via-layer2-tunnel) ### L3 **Layer 3 tunnels** encapsulate IP packets, operating at the network layer. **Protocols**: WireGuard, GRE, SIT/ip6gre **Use cases**: * Standard BGP peering * IPv6 transport over IPv4 (6in4) * Encrypted peering (WireGuard) **Considerations**: Lower overhead, more efficient for most peering scenarios. [Learn more about Layer 3 tunnels →](/docs/peering/via-layer3-tunnel) ## Configuration Examples All tunnel configurations use placeholder values that you'll replace with actual values: ```yaml # Replace these placeholders with your actual values your_name: "{tunnel name}" yourside_ip: "{your public IP}" ourside_ip: "{our endpoint IP}" yourside_port: "{your source port (WireGuard)}" ourside_port: "{our destination port (WireGuard)}" your_tunnel_ip: "{your tunnel IP address}" our_tunnel_ip: "{our tunnel IP address}" tunnel_cidr: "{tunnel subnet CIDR}" vni: "{VxLAN Network Identifier}" public_key: "{our WireGuard public key}" private_key: "{your WireGuard private key}" ``` ## Protocol Comparison | Protocol | Layer | Encryption | Multi-protocol | Use Case | | --------- | ----- | ---------- | -------------- | ---------------------- | | WireGuard | L3 | Yes | IPv4/IPv6 | Secure, modern peering | | GRE | L3 | No | IPv4/IPv6 | Simple IP tunneling | | GRETAP | L2 | No | Ethernet | Bridging, VLANs | | VxLAN | L2 | No | Ethernet | Data center overlay | | SIT | L3 | No | IPv6-over-IPv4 | 6in4 connectivity | | ip6gre | L3 | No | IPv6-over-IPv4 | GRE for IPv6 | - [Layer 2 Tunnels](/docs/peering/via-layer2-tunnel) — GRETAP and VxLAN for Ethernet-layer encapsulation. - [Layer 3 Tunnels](/docs/peering/via-layer3-tunnel) — WireGuard, GRE, and SIT for IP-layer encapsulation. ## Next Steps 1. Choose the appropriate tunnel type for your use case 2. Follow the configuration examples 3. Contact us to finalize the peering session > **Need help deciding?** > > For most peering scenarios, Layer 3 tunnels (especially WireGuard or GRE) are recommended due to lower overhead and better performance. --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/peering/via-tunnel). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Hats BDL | Dedicated Internet Access **Hats BDL (Business Dedicated Line)** is enterprise-grade Dedicated Internet Access with contractual bandwidth guarantees and 99.99% SLA backing. Purpose-built for organizations that cannot afford downtime. > **Market Reality** > > Shared broadband is typically oversubscribed, which can translate into congestion and performance instability under load. > > So, **Hats BDL** eliminates this risk with dedicated fiber and guaranteed CIR. > > Source: [CTC Technology & Energy: All Mbps Are Not Created Equal](https://www.ctcnet.us/wp-content/uploads/2014/02/CTC-ConnectivityPerformanceFactorsBrief0213141.pdf) ## Why Hats BDL Over Standard Broadband | Capability | Business Broadband | Hats BDL | | ----------------------- | --------------------------- | ------------------------------ | | **Bandwidth Guarantee** | Best effort / shared | CIR with contractual guarantee | | **SLA Availability** | None or limited | 99.99% with financial backing | | **Latency Consistency** | Variable (peak-hour spikes) | Predictable, low jitter | | **Symmetry** | Often asymmetric | Symmetric upload/download | | **Static IPs** | Dynamic or limited | Block assignment available | | **Support Response** | Standard business hours | 24/7 with escalation paths | ## Use Cases ### Primary Uplink Mission-critical office connectivity with guaranteed access to cloud SaaS platforms. Eliminates productivity loss during peak hours. ### Data Center Interconnect Redundant circuits and dual-homed connectivity between facilities. Diverse paths eliminate single points of failure for enterprise networks. ### Cloud Access Direct, low-latency access to AWS, Azure, and Google Cloud. Predictable performance for hybrid cloud and multi-cloud deployments. ### VoIP and UCaaS Voice and unified communications demand sub-150ms latency with minimal jitter. Dedicated bandwidth eliminates call quality issues. > **Benchmarks for Critical Workloads** > > > TU-T guidance commonly uses \<150ms one-way delay for highly interactive voice tasks. > > > Microsoft’s Teams connectivity test passes with UDP latency \<100ms, UDP jitter \<30ms, and UDP packet loss \<1%. > > Sources: [ITU-T Rec. G.114 (05/2003)](https://www.itu.int/rec/dologin_pub.asp?lang=e\&id=T-REC-G.114-200305-I!!PDF-E), [Microsoft 365 network connectivity test tool](https://learn.microsoft.com/en-us/microsoft-365/enterprise/office-365-network-mac-perf-onboarding-tool?view=o365-worldwide) ## Delivery Options ### Bgp **For organizations with their own ASN and routing policies.** * BGP session established to your edge router * Full routing table or default route options * Support for inbound/outbound policy coordination * Enables dual-homing and traffic engineering Ideal for enterprises requiring granular path control and multi-homed resilience. ### Static **For streamlined deployments without BGP complexity.** * Static route configuration at the demarcation * Faster provisioning and turn-up * Ideal for single-site deployments and branches * Reduced technical overhead for smaller IT teams ### L2 **When you prefer to terminate routing on your equipment.** * VLAN handoff to your router/firewall stack * Transparent Layer 2 transport * Compatible with HA firewall pairs and SD-WAN edge devices * Simplifies multi-site routing consistency Preferred for SD-WAN deployments and standardized security appliances. ## Technical Specifications | Specification | Details | | ------------------------ | ---------------------------------------- | | **Committed Rate (CIR)** | 100% of contracted bandwidth, guaranteed | | **Availability SLA** | 99.99% with service credits | | **Latency SLA** | \< 10ms to major IX points from PoP | | **Jitter Target** | \< 2ms (95th percentile) | | **Packet Loss** | \< 0.1% during normal operation | | **MTTR** | 4-hour response for critical issues | | **IPv6** | Native dual-stack support | > **Global Backbone RTT (Realtime)** > > For the full auto-updated RTT matrix across our PoPs (Backbone measurements), see: [Backbone > Latency Matrix](/docs/network/latency) ## Deployment Process ### Site Survey Verify fiber availability and path diversity at your location. ### Handoff Selection Choose BGP, static routes, or L2 transport based on your infrastructure. ### Provisioning Physical installation and acceptance testing. ### Go Live Production handover with 24/7 NOC escalation. ## Frequently Asked Questions ### What is CIR and why does it matter? CIR (Committed Information Rate) is the bandwidth we contractually guarantee under all network conditions. Unlike "up to" speeds from broadband providers, CIR ensures your operations never degrade due to congestion. ### How does the 99.99% SLA work? Our availability SLA defines uptime targets and triggers automatic service credits if unmet. Coverage extends from the demarcation point to our core network. Monthly uptime reports provided. ### Can I get redundant paths? Yes. Dual-homed configurations with diverse fiber paths are available. Options include active/active load balancing or active/standby failover. BGP deployments enable automatic prefix failover. ### What equipment do I need? BGP requires a router with BGP-4 support. Static and L2 handoffs work with standard enterprise firewalls and routers. Technical specs provided during quoting to ensure compatibility. ### How long does installation take? Standard installations complete in 20-30 business days where fiber exists. New construction timelines vary based on permitting. Milestone updates provided throughout. ### Do you support SD-WAN integration? Yes. L2 Transport handoff is purpose-built for SD-WAN edge devices. Transparent Layer 2 delivery ensures seamless integration with leading SD-WAN platforms. *** ## Get Connected Email **[sales@hatsnet.io](mailto:sales@hatsnet.io)** with your site address and bandwidth requirements. We respond within one business day. *** > **Ready to Crank It Up?** > > **[Contact Sales](#contact)** to discuss Hats SR for your media workflows. > > Hats Network Inc. (AS203314): *[Imagine a world where network connectivity is seamless, secure and accessible to everyone.](/about)* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/services/business-dedicated-line). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Hats EPN | SD-WAN as a Service **Hats EPN (Enterprise Private Network)** is a fully managed private connectivity service that delivers enterprise-grade WAN without the operational overhead of building and maintaining your own SD-WAN infrastructure. > **Why Managed WAN?** > > Get all the benefits of Software-Defined Connectivity-traffic segmentation, predictable latency, and multi-site orchestration-without hiring specialized network engineers or managing complex edge devices. ## Why Managed WAN? Most enterprises don't want to become networking companies. Here's how Hats EPN compares to the DIY approach: | Aspect | Self-Built SD-WAN | Hats EPN (Managed) | | --------------------------- | ------------------------------------------- | ------------------------------- | | **Setup Time** | 3-6 months (hardware, config, testing) | Days to weeks | | **Expertise Required** | Senior network engineers on staff | Zero - we handle everything | | **Ongoing Ops** | 24/7 NOC, patch management, troubleshooting | Included in service | | **Hardware Investment** | CAPEX for edge appliances | OPEX only - no hardware to buy | | **Multi-vendor Complexity** | Integrating firewalls, SD-WAN, monitoring | Single unified service | | **Scaling** | Manual provisioning, capacity planning | On-demand bandwidth adjustments | | **SLA Accountability** | You own all uptime risk | 99.99% SLA with Hats Network | **Bottom line**: Focus on your business while we manage the network infrastructure. ## Delivery Models ### Routed **Managed routed connectivity** for enterprises who want us to handle the core routing infrastructure while they focus on their applications. **What You Get**: * Software-defined routing with traffic segmentation * BGP peering at your edge (optional) * Complete traffic isolation between environments * Automatic failover and path optimization * Predictable latency across our private backbone **Best For**: * Multi-office WAN with centralized internet breakout * Cloud on-ramp integration (AWS, Azure, GCP) * Segmented environments (production, development, voice, security zones) * Enterprises without deep networking expertise in-house ### Switched **Transparent Ethernet transport** for customers who prefer to manage their own routing stack while we handle the underlying transport. **What You Get**: * Ethernet handoff at each site (VLAN-tagged) * Single broadcast domain across all locations * You control all IP addressing and routing protocols * Transparent transport for multicast and custom protocols * MAC learning and forwarding managed by Hats **Best For**: * High-availability router pairs with VRRP/HSRP * Customer-managed SD-WAN appliances requiring L2 handoff * Legacy applications requiring flat Layer-2 adjacency * Organizations with existing networking teams ### Underlay **Stable transport foundation** for enterprises running their own SD-WAN, SASE, or custom overlay solutions. **What You Get**: * Stable IP transport with measurable, consistent latency * No encryption overhead (your overlay handles security) * Predictable path characteristics for intelligent path selection * Dual-stack IPv4/IPv6 support * Clean handoff to your edge devices **Best For**: * SD-WAN fabric underlay (any vendor) * SASE architecture foundation * Custom overlay with proprietary encryption requirements * Hybrid WAN combining private transport with internet backup ## Architecture **Simple connection model**: We manage the complex backbone. You get a clean handoff at each site. ## Use Cases ### Multi-Site Enterprise WAN Connect offices, factories, and data centers with consistent performance. Hats EPN provides the backbone while your IT team focuses on applications, not routing tables. * **Manufacturing**: Connect global production facilities to ERP systems * **Retail**: Link stores to centralized POS and inventory systems * **Professional Services**: Reliable video conferencing between offices ### Cloud Access Direct, optimized paths to major cloud providers. Your cloud workloads perform like they're on your local network. * **AWS Direct Connect** integration * **Azure ExpressRoute** connectivity * **Multi-cloud** architectures with consistent performance ### Critical Workloads When latency and jitter directly impact revenue, Hats EPN delivers the predictability that internet connections can't match. * **Financial Trading**: Sub-50ms latency between trading venues * **Healthcare**: Reliable DICOM image transfers for telemedicine * **Real-time Collaboration**: Consistent video and voice quality > **Benchmarks for Critical Workloads** > > > TU-T guidance commonly uses \<150ms one-way delay for highly interactive voice tasks. > > > Microsoft’s Teams connectivity test passes with UDP latency \<100ms, UDP jitter \<30ms, and UDP packet loss \<1%. > > Sources: [ITU-T Rec. G.114 (05/2003)](https://www.itu.int/rec/dologin_pub.asp?lang=e\&id=T-REC-G.114-200305-I!!PDF-E), [Microsoft 365 network connectivity test tool](https://learn.microsoft.com/en-us/microsoft-365/enterprise/office-365-network-mac-perf-onboarding-tool?view=o365-worldwide) ## Service Specifications | Specification | Routed | Switched | Underlay | | ------------------- | -------------------- | ------------- | ------------- | | **Handoff Type** | BGP or Static | 802.1Q VLAN | IP or BGP | | **Routing Control** | Hats-managed | You manage | Minimal | | **MTU** | 1500 or 9000 (Jumbo) | 1500 or 9000 | 1500 or 9000 | | **Multicast** | Available | Transparent | No | | **IPv6** | Native | Native | Native | | **SLA** | 99.99% uptime | 99.99% uptime | 99.99% uptime | ## Traffic Segmentation & QoS Built-in traffic classification without complex configuration: | Traffic Class | Priority | Treatment | Typical Use | | ------------- | ----------- | -------------------- | ------------------------- | | **Real-Time** | Highest | Guaranteed bandwidth | Voice, video conferencing | | **Critical** | High | Low latency queue | Trading systems, ERP | | **Business** | Standard | Standard forwarding | Email, SaaS applications | | **Default** | Best effort | Standard forwarding | Bulk transfers, backups | **No VRF configuration needed** - traffic segmentation is handled by our platform based on your requirements. ## FAQ ### What's the difference between Routed and Switched Private Network? **Routed Private Network**: We manage the routing. You connect your edge device to our network, and we handle all the complexity of path selection, traffic segmentation, and optimization. Best for organizations that want "it just works." **Switched Private Network**: We provide transparent Ethernet transport between your sites. Your routers see each other as directly connected on the same LAN segment. You manage all IP addressing and routing. Best for organizations with existing networking teams who want control. Choose Routed for simplicity. Choose Switched if you have specific routing protocol requirements or need Layer-2 adjacency between sites. ### Can I use Hats EPN as an SD-WAN underlay? Yes. Our SD-WAN Underlay option is purpose-built for this use case. We provide stable, measurable IP transport with consistent latency characteristics-exactly what SD-WAN solutions need for accurate path selection. Benefits of using Hats EPN as your underlay: * **Consistent baselines**: Your SD-WAN makes better path decisions with stable metrics * **Reduced tunnel flapping**: No internet jitter causing unnecessary failover events * **Guaranteed bandwidth**: Private backbone capacity independent of internet congestion * **Simplified ops**: We maintain the underlay; you focus on overlay policies Compatible with all major SD-WAN platforms including VeloCloud, Fortinet, Palo Alto, Cisco, and open-source solutions. ### How does traffic segmentation work? Hats EPN uses Software-Defined Connectivity to create isolated traffic domains. Think of them as virtual networks that share physical infrastructure but never intersect. Common segmentation patterns we support: * **Environment Isolation**: Production, staging, and development as separate virtual networks * **Traffic Type Separation**: Voice traffic on its own segment with priority treatment * **Security Zones**: Guest networks, corporate data, and PCI-compliant traffic fully isolated * **Departmental Segments**: Different business units with controlled interconnectivity You define the segments. We handle the implementation-no complex configuration on your end. ### What does 'fully managed' actually mean? With Hats EPN, you don't need network engineers on staff: **We Handle**: * Core network design and operation * Routing protocol management and optimization * 24/7 monitoring and incident response * Capacity planning and scaling * Software updates and security patches * Peering and upstream relationships **You Handle**: * Your edge devices (routers, firewalls) * Your internal LAN * Your application configuration You get a simple handoff at each site. Everything behind that is our responsibility. ### What are the latency commitments? We provide baseline latency measurements during onboarding. Typical inter-PoP latencies on our private backbone: > **Global Backbone RTT (Realtime)** > > For the full auto-updated RTT matrix across our PoPs (Backbone measurements), see: [Backbone > Latency Matrix](/docs/network/latency) | Route | Latency | | --------------------- | -------- | | Hong Kong ↔ Tokyo | 35-45ms | | Hong Kong ↔ Singapore | 35-45ms | | Tokyo ↔ Los Angeles | 90-110ms | | Frankfurt ↔ Amsterdam | 5-8ms | Our SLA covers latency variance (jitter) and packet loss, not just uptime. Because we control the backbone, we can guarantee performance characteristics that internet-based solutions cannot match. ### Can we connect to cloud providers? Yes. Hats EPN integrates with major cloud platforms: * **AWS**: Direct Connect via our partner locations * **Microsoft Azure**: ExpressRoute connectivity * **Google Cloud**: Dedicated Interconnect * **Alibaba Cloud**: Express Connect Cloud connectivity is integrated into your private network segments, creating seamless hybrid cloud architecture. Your cloud resources appear as just another site on your WAN. ### How quickly can we get started? Typical deployment timeline: | Phase | Timeline | Details | | ---------------- | --------- | ---------------------------------- | | **Discovery** | 1-2 days | Requirements, topology design | | **Contracting** | 3-5 days | Service order, terms | | **Provisioning** | 5-15 days | Circuit activation, cross-connects | | **Testing** | 1-2 days | Validation, acceptance | | **Go-Live** | - | Production traffic | **Total: 2-4 weeks** from signature to production - significantly faster than traditional carrier services. Existing Hats Network customers can often add EPN services in days, leveraging existing infrastructure. ## Getting Started ### Schedule a Consultation Tell us about your sites, bandwidth needs, and any cloud connectivity requirements. We'll design a topology that fits. ### Review Your Design We provide a detailed proposal including topology, SLAs, and pricing. No surprises. ### Provisioning We handle circuit coordination, equipment installation, and configuration. You provide the cross-connect details. ### Go Live We validate end-to-end connectivity, establish baseline performance metrics, and hand over operational documentation. > **Ready to simplify your WAN?** > > Contact our team: **[sales@hatsnet.io](mailto:sales@hatsnet.io)** > > Include: > > * Number of sites and locations > * Bandwidth requirements per site > * Preferred delivery model (Routed/Switched/Underlay) > * Cloud connectivity needs > * Target deployment regions *** > **Ready to Crank It Up?** > > **[Contact Sales](#contact)** to discuss Hats SR for your media workflows. > > Hats Network Inc. (AS203314): *[Imagine a world where network connectivity is seamless, secure and accessible to everyone.](/about)* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/services/enterprise-private-network). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Hats GO - Load Up. Lock In. > You'll need a new excuse for your K.D.R. *** ## The Problem Lag kills more than bad aim. Every competitive player knows the pain: you peek first, you die first. Your crosshair was on their head-server says otherwise. That 80ms routing through three different carriers? It's giving your opponent the advantage. **Peeker's disadvantage.** Bad hit registration. Rollback eating your inputs. When milliseconds decide matches, your network is part of your loadout. Most "gaming" solutions add hops, encryption overhead, or tunnel you through oversubscribed servers. That's not optimization-it's a handicap. *** ## What Is Hats GO (Gaming Optimized)? **Hats GO** is competitive-grade routing. Not a VPN. Not a tunnel. Not a magic button. We build direct network paths to major game infrastructure through strategic Internet Exchange peering. Your traffic hits the game server faster because we eliminated the detours-not because we wrapped it in extra layers. * **Direct IX peering** at HKIX, JPIX, DE-CIX, AMS-IX * **BGP-level optimization**-no encryption overhead * **Sub-30ms or nothing** to major competitive servers * **99.99% uptime** with automatic failover Think of it as a dedicated lane on the information highway. Same road, better path. *** ## The Numbers When your ping is the difference between clutching and choking. > **Global Backbone RTT (Realtime)** > > For the full auto-updated RTT matrix across our PoPs (Backbone measurements), see: [Backbone > Latency Matrix](/docs/network/latency) | Route | Standard Path (Ping / Loss) | Hats GO (Ping / Loss) | Overall Improvement | | --------------------- | --------------------------- | --------------------- | ------------------- | | Hong Kong → Singapore | 60\~200ms / 4\~8% | 30\~45ms / \<1% | \~74% | | Hong Kong → Tokyo | 80\~150ms / 3\~7% | 45\~55ms / \<1% | \~60% | | Hong Kong → Taipei | 30\~80ms / 2\~5% | 15\~30ms / \<1% | \~61% | | Hong Kong → Seattle | 150\~200ms / 8\~15% | 130\~150ms / 1\~2% | \~28% | | Hong Kong → Frankfurt | 200\~270ms / 10\~20% | 150\~170ms / 1\~3% | \~42% | | Hong Kong → Sydney | 150\~200ms / 8\~12% | 120\~150ms / 1\~2% | \~30% | > **How We Calculate Improvement** > > To account for the severe impact of packet loss on gaming (rubberbanding and desync), we calculate the improvement based on **Effective Latency**, which factors in the penalty of packet retransmission. > > **Variables:** > > * **$E$**: Effective Latency > * **$P$**: ICMP Latency (Base Ping) > * **$L$**: Packet Loss Rate > * **$std$ / $go$**: Subscripts for Standard Path and Hats GO > > **1. Effective Latency Base Formula:** > > ```math > E = \frac{P}{1 - L} > ``` > > **2. Improvement Calculation:** > > ```math > I = \left(1-\frac{P_{go} \times (1 - L_{std})}{P_{std} \times (1 - L_{go})} \right) \times 100\% > ``` \* Measured from HKG PoP. Your mileage varies based on location and last-mile conditions. *** ## How It Works ### Direct Peering We don't ask intermediaries for favors. We're plugged directly into the same exchanges where game publishers host their infrastructure. | IX Location | Publishers On-Site | | ----------- | ------------------------------- | | **HKIX** | Tencent, Garena, Riot SEA | | **JPIX** | Square Enix, Sega, Bandai Namco | | **DE-CIX** | EU game servers, Ubisoft EU | | **AMS-IX** | Valve EU, EA EU | Fewer hops = fewer milliseconds = fewer excuses. ### Route Engineering Our BGP policies don't leave routing to chance. * **Community tagging** - Game traffic gets priority paths * **Local preference** - IX routes over transit, always * **AS-path control** - Inbound optimization for symmetric latency This is network engineering at the protocol level. No added latency from encryption or tunnel termination. ### Qos Raw speed means nothing if your packets arrive inconsistently. | Metric | Target | | ---------------- | ------ | | Packet Loss | \<0.1% | | Jitter | \<2ms | | Latency Variance | \<5% | Stable ping matters more than low average ping. A consistent 35ms beats a spiky 25-60ms every time. *** ## By Game Type Different games. Different demands. Same standard. | Genre | Examples | Target Latency | Why It Matters | | ----------------- | -------------------- | -------------- | -------------------------------------------------------------------------- | | **FPS** | CS2, Valorant, Apex | Sub-30ms | Peeker's advantage. Hit reg. When every frame counts in a duel. | | **Fighting** | SF6, Tekken 8, GBVSR | Sub-16ms | Rollback netcode works best with minimal delay. Frame-perfect inputs. | | **MOBA** | Dota 2, LoL | Sub-50ms | Skill-shot timing. Team fight responsiveness. No stutter on clutch plays. | | **Battle Royale** | PUBG, Fortnite | Sub-40ms | Position updates. Hit registration at range. Circle closure reaction time. | > **References for Competitive Latency Ceilings** > > Epic describes \<=20ms as “good” latency, 20-100ms as “acceptable”, and >=100ms as “poor” for Fortnite. > > Source: [Epic Games: Understanding latency or ping in Fortnite](https://www.epicgames.com/help/fortnite-battle-royale-c-202300000001636/technical-support-c-202300000001719/fortnite-latency-and-ping-troubleshooting-a202300000010042) *** ## Coverage Hats GO routes available at these PoPs: **Asia-Pacific** * Hong Kong (HKG) * Tokyo (NRT) * Singapore (SIN) **Europe** * Frankfurt (FRA) * Amsterdam (AMS) **North America** * Los Angeles (LAX) * New York (NYC) Contact sales for availability in your region. *** ## FAQ ### Is this a VPN? No. Hats GO operates at the network routing level-BGP peering and direct IX connections. There's no encryption overhead, no tunnel wrapping, no additional hops. Your traffic travels natively over optimized paths, not through a middleman server. ### Will this lower my ping? If you're on a suboptimal route to game servers where we have peering, yes-often significantly. If you're already geographically close with good routing, improvements may be marginal. We can run latency tests from your location before you commit. ### Does this work with my ISP? Hats GO is delivered through BGP peering or IP transit arrangements-typically for businesses, data centers, or esports venues. Residential access varies by region and ISP partnership. Contact sales to discuss your specific setup. ### Which games benefit most? Any latency-sensitive multiplayer title. FPS and fighting games see the most dramatic improvements due to their frame-level precision requirements. MOBAs and battle royales benefit from consistent routing and reduced jitter. ### Is this legal for competitive play? Yes. Hats GO uses standard internet routing protocols-no packet manipulation, no artificial lag reduction, no circumvention of regional restrictions. It's optimized connectivity, not a circumvention tool. ### Can I try it first? Qualified business customers can request latency measurements and trials. Contact our sales team with your location and target game servers-we'll show you the numbers before you buy. *** > **Ready to Crank It Up?** > > **[Contact Sales](#contact)** to discuss Hats SR for your media workflows. > > Hats Network Inc. (AS203314): *[Imagine a world where network connectivity is seamless, secure and accessible to everyone.](/about)* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/services/gaming-optimized). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Hats Network Services We offer an enterprise-grade connectivity portfolio designed for businesses and professionals of all sizes. *** > ## Service Catalog - [Hats EPN](/docs/services/enterprise-private-network) — SD-WAN as a Service. Multi-site private connectivity with traffic segmentation and guaranteed SLAs. - [Hats BDL](/docs/services/business-dedicated-line) — Enterprise DIA. Committed bandwidth with flexible handoff options for offices and critical endpoints. - [Hats PUL](/docs/services/premium-user-line) — Performance IP. Low-jitter access for latency-sensitive professionals and distributed teams. - [Hats GO](/docs/services/gaming-optimized) — Competitive Gaming Routes. Sub-30ms paths to publishers via direct IX peering. - [Hats SR](/docs/services/streaming-ready) — Media-Grade Connectivity. High-throughput infrastructure for 4K/8K delivery with CDN peering. *** ## Service Selection Decision Tree Unsure which service fits your needs? Follow this decision tree: ## Quick Selection Guide ### Saas **Primary Need**: Secure, segmented connectivity between offices and cloud. | Requirement | Recommended | | ----------------------- | -------------- | | 3+ sites, private mesh | Hats EPN | | Single site, SLA-backed | Hats BDL | | Hybrid cloud handoff | Hats EPN + BGP | ### Multi Site **Primary Need**: Reliable inter-office connectivity that scales. | Site Count | Recommended | | -------------- | ------------------------- | | 2–3 locations | Hats BDL (point-to-point) | | 4+ locations | Hats EPN (full mesh) | | Remote workers | Hats PUL (endpoints) | ### Creative **Primary Need**: Low-jitter access to cloud suites and collaboration tools. | Use Case | Recommended | | --------------------- | ----------- | | Video editing teams | Hats PUL | | Animation/VFX studios | Hats BDL | | Distributed teams | Hats EPN | ### Gaming **Primary Need**: Minimal latency to game servers and tournament infra. | Organization | Recommended | | -------------------------- | --------------------- | | Esports teams & facilities | Hats GO | | Tournament organizers | Hats GO + BGP | | Gaming cafes/chains | Hats BDL + GO profile | ### Media **Primary Need**: Consistent throughput for high-bitrate video. | Scale | Recommended | | ------------------- | ----------------------- | | Individual creators | Hats PUL | | OTT platforms | Hats SR | | CDN operators | IP Transit + SR profile | *** ## Service Architecture Overview ## Why Enterprise-Grade | Feature | Best-Effort Internet | Hats Enterprise-Grade | | --------- | ------------------------ | ---------------------------- | | Bandwidth | Shared, oversubscribed | Committed CIR | | Routing | Cost-optimized, variable | BGP-controlled deterministic | | Peering | Multi-transit hops | Direct IX at 15+ exchanges | | SLA | None | 99.99% uptime with credits | | Support | Business hours | 24/7 NOC | *** ## Frequently Asked Questions ### What's the difference between Hats BDL and standard business broadband? Hats BDL provides **committed bandwidth**, you receive 100% of purchased capacity 100% of the time. Standard broadband is "best effort" and commonly oversubscribed (for example, cable/DSL can be 50:1+ on business tiers, while Metro Ethernet is often 10:1 or less). BDL also includes symmetric speeds, static IPs, SLA guarantees, and BGP peering options. > **Sources** > > Oversubscription examples and typical ratios: [CTC Technology & Energy: All Mbps Are Not Created > Equal (Connectivity Performance > Factors)](https://www.ctcnet.us/wp-content/uploads/2014/02/CTC-ConnectivityPerformanceFactorsBrief0213141.pdf) ### Can I start with one service and upgrade later? Yes. Many customers begin with Hats BDL for individual sites, then migrate to Hats EPN as they add locations. Handoff types remain consistent during migration. Contact your account manager to discuss upgrade paths. ### Does Hats EPN replace my existing SD-WAN? Hats EPN provides network-layer traffic engineering without overlay complexity. For customers requiring SD-WAN appliances, we partner with vendors to deliver managed solutions over our backbone. ### What's the typical installation timeline? | Service | Timeline | | -------- | -------------------- | | Hats PUL | 5\~10 business days | | Hats BDL | 15\~30 business days | | Hats EPN | 30\~45 business days | Expedited installation available in select markets. ### Which PoPs support GO and SR profiles? Gaming and Streaming profiles are available at our IX-connected locations: **Asia-Pacific**: Hong Kong, Tokyo, Singapore\ **Europe**: Frankfurt, Amsterdam, London\ **North America**: Los Angeles, New York, Ashburn Contact sales for current availability and latency estimates. *** ## Get Started > **Contact Sales** > > Unsure which service fits your requirements? Our team can analyze your current connectivity and recommend the optimal configuration. > > **[sales@hatsnet.io](mailto:sales@hatsnet.io)** - include your current setup, bandwidth needs, and any performance issues. *** > **Ready to Crank It Up?** > > **[Contact Sales](#contact)** to discuss Hats SR for your media workflows. > > Hats Network Inc. (AS203314): *[Imagine a world where network connectivity is seamless, secure and accessible to everyone.](/about)* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/services). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Hats PUL | Gaming & Cloud Performance IP ## What It Is **Hats PUL (Premium User Line)** is Performance IP connectivity - not a VPN, not a proxy, not a tunnel. We give your traffic a direct lane. Through our own AS203314 backbone, direct IX peering with major gaming publishers and cloud providers, and intelligent routing that cuts out the congested public internet. Think of it as upgrading from a shared road to a dedicated expressway. Same destination. Entirely different ride. *** ## The Problem Standard ISP routes are built for **capacity**, not **latency**. Your packets zigzag through tier-1 carriers, hit overcrowded peering points, and get routed through whatever's cheapest - not what's fastest. The result? * Jitter that ruins your spray control * 150ms+ routes to servers that should be 30ms away * Inconsistent hit registration * Rubberbanding at the worst possible moment You're paying for "gigabit" but getting lag spikes that no bandwidth can fix. *** ## The Solution **Direct Peering. Intelligent Routing. Performance IP.** | What We Do | What It Means | | -------------------------- | ------------------------------------------------------------------------------------------- | | **Direct IX Peering** | Traffic enters our network and exits directly at major IX points. No middlemen. No detours. | | **AS203314 Backbone** | Our own infrastructure. Our own routes. Full control over path selection. | | **Gaming-Optimized Paths** | Routes tuned for UDP consistency, not just TCP throughput. | | **Multi-Hub Redundancy** | Automatic failover between our PoPs without dropping your session. | The outcome? Sub-30ms latency to major gaming and cloud regions. Consistent ping. Predictable performance. *** ## By The Numbers > **Global Backbone RTT (Realtime)** > > For the full auto-updated RTT matrix across our PoPs (Backbone measurements), see: [Backbone > Latency Matrix](/docs/network/latency) Real-world latency from our core PoPs to major destinations: | Route | Standard ISP | Hats PUL | Improvement | | --------------------- | ------------ | -------- | ------------ | | Singapore → Hong Kong | 45-60ms | 28-32ms | \~40% faster | | Tokyo → Seoul | 55-70ms | 32-38ms | \~45% faster | | Frankfurt → Amsterdam | 25-35ms | 12-15ms | \~55% faster | | Los Angeles → Tokyo | 140-160ms | 95-105ms | \~30% faster | Your mileage may vary, but the pattern doesn't: **shorter paths, lower latency, less jitter.** > **References for Competitive Latency Ceilings** > > Epic describes \<=20ms as “good” latency, 20-100ms as “acceptable”, and >=100ms as “poor” for Fortnite. > > Source: [Epic Games: Understanding latency or ping in Fortnite](https://www.epicgames.com/help/fortnite-battle-royale-c-202300000001636/technical-support-c-202300000001719/fortnite-latency-and-ping-troubleshooting-a202300000010042) *** ## Who It's For ### Competitive Gamers Stop losing duels to ping. Get the stable connection your mechanics deserve. ### Streamers & Content Creators Low-latency gaming + stable upstream. No more "sorry, lag" moments on stream. ### Remote Workers Video calls that don't stutter. File transfers that don't crawl. A connection that just works. ### Cloud Developers Direct, low-latency access to AWS, Azure, GCP regions. Faster deploys. Snappier terminals. *** ## How It Works 1. **Connect** - Route your traffic through our nearest PoP 2. **Optimize** - Our edge routers select the best path in real-time 3. **Win** - Lower latency, reduced jitter, consistent performance No software to install. No configuration headaches. Just better routing. *** ## FAQ ### Is this a VPN? **No.** Hats PUL is Performance IP connectivity through route optimization. We don't encrypt your traffic, change your IP location, or provide "privacy" features. We're a network infrastructure service - not a VPN provider. ### Will this work with my ISP? Yes. Hats PUL operates at the network layer and is compatible with any internet connection. We optimize the path *after* your traffic reaches our edge. ### Does it support all games? Any game that uses standard IP networking will benefit from lower latency and reduced jitter. We don't modify game traffic - we just deliver it faster. ### What's the catch? No catch. We're a network operator (AS203314) with our own infrastructure. We peer directly with major networks. That's the edge - literally. ### How do I get started? Contact our team for availability in your region. We'll set up your Performance IP connection and get you routed through our backbone. *** > **Ready to Crank It Up?** > > **[Contact Sales](#contact)** to discuss Hats SR for your media workflows. > > Hats Network Inc. (AS203314): *[Imagine a world where network connectivity is seamless, secure and accessible to everyone.](/about)* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/services/premium-user-line). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Hats SR | Media-Grade Connectivity Big stream? Major release? Crank up your bandwidth on the fly. Hats SR delivers **Media-Grade Connectivity** - sustained throughput engineered for professional 4K/8K workflows, not speed test bragging rights. > **Why Quality Matters** > > According to [Conviva's 2025 research](https://www.conviva.ai/2025-state-of-digital-experience-report/): > > > Every 1% degradation in Quality of Experience leads to a 1% increase in customer churn. > > Buffering and quality switches directly impact viewer retention and revenue. *** ## The Problem: Burst vs. Sustained Standard networks are built for speed tests, not real-world streaming: ### Oversubscription **The Problem**: Consumer ISPs heavily oversubscribe bandwidth, assuming not everyone uses it simultaneously. **The Impact**: * Bitrate throttling (4K drops to 720p) * Buffering during high-action scenes * Inconsistent quality throughout playback **Our Solution**: Hats SR provisions dedicated capacity with direct CDN peering to maintain quality during peak demand periods. ### Peak Hour **The Problem**: During peak hours (7-11 PM), ISP peering links to CDNs often run at saturation. **The Impact**: * Higher latency to cache * Increased startup time * Frequent quality switches **Our Solution**: We maintain low-latency paths to major CDNs via IX peering at STUIX, NL-IX, DE-CIX, HKIX, and more. ### Burst Sustained **The Problem**: Speed tests measure burst capacity, but 8K streaming requires sustained 100Mbps+ for hours. **The Impact**: * High initial speed, then quality drops * Inability to maintain 8K streams * Degradation during long viewing sessions **Our Solution**: Our network is provisioned for sustained throughput with redundant upstream providers. *** ## What Is "Hats SR"? Hats SR (Streaming Ready) is **Media-Grade Connectivity** - network infrastructure engineered for sustained bandwidth delivery, not burst speed tests. Unlike consumer internet that optimizes for occasional speed test snapshots, Hats SR is built for: * **Sustained throughput** - hours of consistent 4K/8K delivery * **Direct CDN peering** - bypassing congested transit paths * **Low jitter** - stable bitrates without quality switches * **Redundant architecture** - 99.99% uptime SLA *** ## Bandwidth Requirements Professional media workflows have specific bandwidth needs: | Quality | Resolution | Recommended Bandwidth | Typical Bitrate\* | | ------- | ----------- | --------------------- | ----------------- | | HD | 1080p | 10-15 Mbps | 5-9 Mbps | | Full HD | 1080p60 | 15-25 Mbps | 9-15 Mbps | | 4K | 2160p | 25-50 Mbps | 15-25 Mbps | | 4K HDR | 2160p + HDR | 40-60 Mbps | 20-35 Mbps | | 8K | 4320p | 100+ Mbps | 50-80+ Mbps | Hats SR handles multiple concurrent 4K/8K streams without degradation - whether you're delivering to an OTT platform or producing live content. > **Sources** > > Bandwidth/bitrate reference points: [Netflix-recommended internet > speeds](https://help.netflix.com/en/node/306), [YouTube Live - Bitrate > Recommendations](https://support.google.com/youtube/answer/2853702?hl=en) *** ## CDN Peering We maintain direct peering with major content delivery networks through Internet Exchange points: | CDN | IX Access Points | Key Benefit | | -------------------- | --------------------------- | ---------------------------------------- | | Netflix Open Connect | SIX Seattle, AMS-IX, others | 4K/8K content served locally | | Google Global Cache | Multiple IX locations | YouTube and Google services optimization | | Akamai | Multiple IX locations | Broad content delivery network access | | Cloudflare | Multiple IX locations | Content delivery + performance | | Amazon CloudFront | Multiple IX locations | AWS-originated content optimization | | Fastly | Multiple IX locations | Real-time content and API optimization | > **IX Advantage** > > Our presence at major Internet Exchange points (HKIX, JPIX, DE-CIX, AMS-IX) provides direct paths to CDN infrastructure that would otherwise require multiple transit hops. *** ## Use Cases ### Video Platforms Deliver consistent 4K/8K experiences to global audiences: * OTT platforms * Media publishers * VOD services * Corporate video delivery ### Live Production Reliable upload capacity for professional live production: * 4K60 streaming to multiple platforms simultaneously * Stable bitrates for broadcast-quality productions * Low-latency options for interactive streaming * Remote production workflows ### Enterprise Streaming Clear video communication without quality degradation: * All-hands meetings in 4K * Executive broadcasts * Town halls and events * Microsoft Teams, Zoom, Google Meet optimization *** ## Technical Specifications | Specification | Value | | ----------------- | ---------------------------------- | | Minimum Bandwidth | 100 Mbps sustained per stream (8K) | | Global Capacity | 1 Tbps+ backbone capacity | | Jitter | \<2ms (95th percentile) | | Packet Loss | \<0.1% (normal operation) | | IX Peering | HKIX, JPIX, DE-CIX, AMS-IX, STUIX | | Uptime SLA | 99.99% with automatic failover | > **Global Backbone RTT (Realtime)** > > For the full auto-updated RTT matrix across our PoPs (Backbone measurements), see: [Backbone > Latency Matrix](/docs/network/latency) *** ## Regional Availability Hats SR is available at PoPs with high CDN density: **Asia-Pacific**: Hong Kong, Tokyo, Singapore **North America**: Los Angeles, New York **Europe**: Frankfurt, Amsterdam Additional locations available upon request. *** ## FAQ ### What makes Hats SR different from business internet? Business internet plans often still follow consumer oversubscription models. Hats SR is explicitly provisioned for sustained bandwidth with direct CDN peering, ensuring your 4K/8K streams maintain quality even during peak hours. ### How do you handle peak hours? We provision peering capacity based on peak-hour demand projections and leverage multiple upstream providers with automatic failover. This maintains performance during the 7-11 PM period when networks often degrade. ### Can Hats SR support live production workflows? Yes. Hats SR is ideal for live production with stable upload bandwidth for multi-platform streaming. For ultra-low latency requirements (remote production, live shopping), contact us to discuss specific needs. ### What happens if a CDN has issues? Our network maintains diverse paths through multiple IX locations and upstream providers. If one CDN experiences issues, traffic can often be rerouted to alternative paths or CDNs. ### Do you offer dedicated infrastructure? For enterprise customers with high-volume requirements, we can discuss custom infrastructure solutions. Contact sales to explore options for your use case. ### What is the minimum commitment? Hats SR service requirements vary by region and bandwidth needs. Contact our sales team for a custom quote based on your specific requirements. *** > **Ready to Crank It Up?** > > **[Contact Sales](#contact)** to discuss Hats SR for your media workflows. > > Hats Network Inc. (AS203314): *[Imagine a world where network connectivity is seamless, secure and accessible to everyone.](/about)* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/services/streaming-ready). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Asia Transit ## 🇭🇰 Hong Kong (HKG3) > [View HKG3 Routes in BGP Tools →](https://bgp.tools/prefix/2602:2a3:300::/41#connectivity) | Feature | Value | Notes | | ---------------- | ----- | ------------------------ | | IPv4 IP-Transit | ✅ | Do not use for Anti-DDoS | | IPv6 IP-Transit | ✅ | Connected AS174 & AS6939 | | Automated Filter | ❌ | Prefix list required | ### Upstream * Hytron Network Limited ([AS202662](https://bgp.tools/as/202662)) * Cogent Communications ([AS174](https://bgp.tools/as/174)) * Hurricane Electric ([AS6939](https://bgp.tools/as/6939)) * CDN77 ([AS60068](https://bgp.tools/as/60068)) ### Peering * 🇭🇰 HKIX (Hong Kong) *(via AS202662)* * 🇭🇰 Equinix IX (Hong Kong) *(via AS202662)* *** ## 🇸🇬 Singapore (SIN1) | Feature | Value | Notes | | ---------------- | ----- | ------------------------ | | IPv4 IP-Transit | ✅ | Do not use for Anti-DDoS | | IPv6 IP-Transit | ✅ | Connected AS2914 & AS174 | | Automated Filter | ❌ | Prefix list required | ### Upstream * Nearoute Limited ([AS51847](https://bgp.tools/as/51847)) * Cogent Communications ([AS174](https://bgp.tools/as/174)) * NTT ([AS2914](https://bgp.tools/as/2914)) ### Peering * 🇸🇬 Equinix IX (Singapore) *(via Upstream)* *** ## 🇯🇵 Tokyo, Japan (TYO2) | Feature | Value | Notes | | ---------------- | ----- | --------------------------------- | | IPv4 IP-Transit | ✅ | Do not use for Anti-DDoS | | IPv6 IP-Transit | ✅ | Connected AS2914 & AS174 & AS3491 | | Automated Filter | ❌ | Prefix list required | ### Upstream * Nearoute Limited ([AS51847](https://bgp.tools/as/51847)) * Cogent Communications ([AS174](https://bgp.tools/as/174)) * NTT ([AS2914](https://bgp.tools/as/2914)) * PCCW Global ([AS3491](https://bgp.tools/as/3491)) ### Peering * 🇯🇵 Equinix IX (Tokyo) *(via Upstream)* *** ## 🇹🇼 Taipei (TPE2) > This location is currently **Closed** for new IP-Transit orders. [View Route Map in BGP Tools > →](https://bgp.tools/prefix/2a0c:9a40:95e3::/48#connectivity) | Feature | Value | Notes | | ---------------- | ----- | ----------------------- | | IPv6 IP-Transit | ✅ | Connected AS6939 | | IPv6 to Cogent | ❌ | Unconnected AS174 | | Automated Filter | ✅ | Supports RPKI ROA / IRR | ### Upstream * Hurricane Electric ([AS6939](https://bgp.tools/as/6939)) ### Peering * 🇹🇼 STUIX (Taipei) --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/transit/asia). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Europe Transit ## 🇳🇱 Amsterdam, NL (AMS) > [View AMS Route Map in BGP Tools →](https://bgp.tools/prefix/2a0c:9a40:95e3::/48#connectivity) | Feature | Value | Notes | | ---------------- | ----- | -------------------------- | | IPv6 IP-Transit | ✅ | Direct Connected to AS6939 | | IPv6 to Cogent | ✅ | Reachable via AS34927 | | Automated Filter | ✅ | Supports RPKI ROA / IRR | ### Upstream * Hurricane Electric ([AS6939](https://bgp.tools/as/6939)) * iFog GmbH ([AS34927](https://bgp.tools/as/34927)) ### Peering * 🇳🇱 NL-IX (Amsterdam) *** ## 🇩🇪 Frankfurt, DE (FRA) > [View FRA Routes in BGP Tools →](https://bgp.tools/prefix/2a0c:9a40:95e2::/48#connectivity) | Feature | Value | Notes | | ---------------- | ----- | -------------------------- | | IPv6 IP-Transit | ✅ | Direct Connected to AS6939 | | IPv6 to Cogent | ✅ | Reachable via AS34927 | | Automated Filter | ❌ | Prefix list required | ### Upstream * Hurricane Electric ([AS6939](https://bgp.tools/as/6939)) * iFog GmbH ([AS34927](https://bgp.tools/as/34927)) ### Peering * 🇩🇪 Loc-IX (Frankfurt) --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/transit/europe). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # IP Transit Services > **IP Transit from AS203314** > > Hats Network Inc. provides **high-quality IP-Transit** services with diverse upstream connectivity across Asia and Europe. Our network features: > > * **Multi-homed** upstream connectivity (Cogent, NTT, HE, PCCW) > * **IPv4 and IPv6** dual-stack support > * **Competitive pricing** with flexible commit options > * **24/7 NOC** support for critical issues ## Transit Ordering Flow ## Available Locations We currently offer IP-Transit at the following locations: | Continent | Country | City | Datacenter | Status | | --------- | ----------- | ------------- | ---------- | ------ | | Europe | Netherlands | Amsterdam | TBD | Open | | Asia | Hong Kong | Tseung Kwan O | HKG3 | Open | | Asia | Singapore | Singapore | SIN1 | Open | | Asia | Japan | Tokyo | TYO2 | Open | | Asia | Taiwan | Taipei | TPE2 | Closed | ## How to Order ### Choose Your Location Review our [Asia](/docs/transit/asia) and [Europe](/docs/transit/europe) transit pages to find the location that best fits your needs. Consider factors such as: * **Latency requirements** to your target markets * **Upstream diversity** available at each location * **IPv4 vs IPv6** availability ### Contact Sales Send an email to [sales@hatsnet.io](mailto:sales@hatsnet.io) with the following information: * Company name and ASN * Desired location and bandwidth requirements * Estimated commit level * BGP communities or special routing requirements ### Setup & Turn-up Once your order is confirmed, our team will: 1. Provision the cross-connect or tunnel 2. Establish BGP sessions 3. Announce your prefixes 4. Provide 24/7 NOC contact information ## Location Details - [Asia Transit](/docs/transit/asia) — Hong Kong, Singapore, Tokyo, and Taipei locations with connections to major Asian IXs. - [Europe Transit](/docs/transit/europe) — Amsterdam and Frankfurt locations with diverse European connectivity. ## Technical Specifications > **Standard Features** > > All IP-Transit services include: > > * **BGP Communities** for traffic engineering > * **RPKI/IRR filtering** (where available) > * **Looking glass** access for route verification > * **Real-time** traffic graphs > * **Email** notifications for maintenance windows ### Supported Protocols | Protocol | Support | Notes | | -------- | -------- | ------------------------------ | | IPv4 | Full | Available at all locations | | IPv6 | Full | Native dual-stack | | BGP-4 | Full | Standard and large communities | | BFD | Optional | For faster convergence | ### Upstream Networks Our network is multi-homed to major Tier-1 and Tier-2 providers: * **Cogent Communications** (AS174) * **Hurricane Electric** (AS6939) * **NTT Communications** (AS2914) * **PCCW Global** (AS3491) * **iFog GmbH** (AS34927) ## Pricing > Pricing varies by location and commit level. Please [contact our sales team](mailto:sales@hatsnet.io) for a custom quote. ## Support For technical support or questions about our IP-Transit services: * **Sales:** [sales@hatsnet.io](mailto:sales@hatsnet.io) * **NOC:** [noc@hatsnet.io](mailto:noc@hatsnet.io) --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/transit). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # 🇳🇱 Amsterdam Ping & Network Latency (AMS) | AS203314 ## 🇳🇱 Amsterdam (AMS) One of the world's most connected internet hubs — home to AMS-IX, the largest Internet Exchange globally. Hats Network peers directly with major European transit carriers at this PoP. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Amsterdam (AMS)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Amsterdam, Netherlands (Europe) * **Region:** Europe * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 2759794](https://www.geonames.org/2759794) — 52.37403, 4.88969 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** AMS1 * **Upstream transit:** HE / Cogent / Telia / Liberty Global * **Peering / IX:** NL-IX @ ANS > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ------------------------------------------------------------------------------------------------------------ | | Fastest Route | [🇳🇱 Amsterdam (AMS) → 🇬🇧 London (LON)](/docs/network/latency/pairs/ams-lon-rtt) (**5.2 ms**) — Ultra-Low | | Slowest Route | [🇳🇱 Amsterdam (AMS) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/ams-syd-rtt) (**258 ms**) | | Average RTT | **112.4 ms** | | Average Jitter | **0.86 ms** | | Average Packet Loss | **0.05%** | | Best Fiber Efficiency | **83.9%** | | Intra-Region Peers | 6 PoPs in Europe | | 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 Amsterdam sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **5.2 ms** (London (LON)) to **38.1 ms** (Moscow (MOW)). Amsterdam anchors the Northwest European corridor (London–Amsterdam–Frankfurt–Paris), one of the densest interconnection ecosystems in the world. ## Outbound Latency from Amsterdam (AMS) Round-trip time in milliseconds **from Amsterdam** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇬🇧 London (LON) | **[5.2](/docs/network/latency/pairs/ams-lon-rtt)** | 3.51 ms | 67.4% | 0.12 ms | 0.09% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[5.9](/docs/network/latency/pairs/ams-fra-rtt)** | 3.57 ms | 60.6% | 0.12 ms | 0.05% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[7](/docs/network/latency/pairs/ams-par-rtt)** | 4.22 ms | 60.3% | 0.12 ms | 0.03% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[7.2](/docs/network/latency/pairs/ams-ber-rtt)** | 5.67 ms | 78.8% | 0.12 ms | 0.19% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[19.6](/docs/network/latency/pairs/ams-mrs-rtt)** | 9.89 ms | 50.5% | 0.12 ms | 0.03% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[38.1](/docs/network/latency/pairs/ams-mow-rtt)** | 21.1 ms | 55.4% | 0.38 ms | 0% | Excellent | | 🇺🇸 New York (NYC) | **[68.6](/docs/network/latency/pairs/ams-nyc-rtt)** | 57.56 ms | 83.9% | 0.31 ms | 0% | Excellent | | 🇺🇸 Ashburn (IAD) | **[75.7](/docs/network/latency/pairs/ams-iad-rtt)** | 60.94 ms | 80.5% | 0.75 ms | 0.05% | Excellent | | 🇺🇸 Miami (MIA) | **[106](/docs/network/latency/pairs/ams-mia-rtt)** | 73.03 ms | 68.9% | 1.03 ms | 0.01% | Good | | 🇺🇸 Seattle (SEA) | **[130.2](/docs/network/latency/pairs/ams-sea-rtt)** | 76.86 ms | 59% | 1.26 ms | 0.04% | Good | | 🇺🇸 Los Angeles (LAX) | **[133.7](/docs/network/latency/pairs/ams-lax-rtt)** | 87.74 ms | 65.6% | 0.65 ms | 0% | Good | | 🇭🇰 Hong Kong (HKG) | **[155.9](/docs/network/latency/pairs/ams-hkg-rtt)** | 91.05 ms | 58.4% | 1.21 ms | 0.05% | Fair | | 🇸🇬 Singapore (SIN) | **[157.6](/docs/network/latency/pairs/ams-sin-rtt)** | 102.86 ms | 65.3% | 0.82 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[168.7](/docs/network/latency/pairs/ams-tpe-rtt)** | 92.72 ms | 55% | 1.29 ms | 0.11% | Fair | | 🇿🇦 Johannesburg (JNB) | **[171.9](/docs/network/latency/pairs/ams-jnb-rtt)** | 88.05 ms | 51.2% | 1.1 ms | 0.1% | Fair | | 🇧🇷 São Paulo (GRU) | **[175.5](/docs/network/latency/pairs/ams-gru-rtt)** | 95.79 ms | 54.6% | 1.53 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[198.2](/docs/network/latency/pairs/ams-tyo-rtt)** | 91.18 ms | 46% | 1.27 ms | 0.14% | Fair | | 🇦🇺 Melbourne (MEL) | **[252.5](/docs/network/latency/pairs/ams-mel-rtt)** | 161.98 ms | 64.1% | 1.77 ms | 0.03% | High | | 🇦🇺 Sydney (SYD) | **[258](/docs/network/latency/pairs/ams-syd-rtt)** | 162.93 ms | 63.2% | 2.35 ms | 0.11% | High | ## Fastest Routes to Amsterdam (AMS) The 10 fastest measured routes **to Amsterdam**, 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 | 🇬🇧 London (LON) | **[5.2 ms](/docs/network/latency/pairs/lon-ams-rtt)** | 5.03 ms | 5.75 ms | 0.16 ms | | 2 | 🇩🇪 Frankfurt (FRA) | **[5.9 ms](/docs/network/latency/pairs/fra-ams-rtt)** | 5.62 ms | 6.84 ms | 0.25 ms | | 3 | 🇫🇷 Paris (PAR) | **[7 ms](/docs/network/latency/pairs/par-ams-rtt)** | 6.65 ms | 8.5 ms | 0.33 ms | | 4 | 🇩🇪 Berlin (BER) | **[7.2 ms](/docs/network/latency/pairs/ber-ams-rtt)** | 6.91 ms | 7.91 ms | 0.23 ms | | 5 | 🇫🇷 Marseille (MRS) | **[20.3 ms](/docs/network/latency/pairs/mrs-ams-rtt)** | 19.62 ms | 22.75 ms | 0.64 ms | | 6 | 🇷🇺 Moscow (MOW) | **[37.6 ms](/docs/network/latency/pairs/mow-ams-rtt)** | 37.09 ms | 39.9 ms | 0.57 ms | | 7 | 🇺🇸 New York (NYC) | **[68.7 ms](/docs/network/latency/pairs/nyc-ams-rtt)** | 66.97 ms | 74.13 ms | 1.38 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[75.2 ms](/docs/network/latency/pairs/iad-ams-rtt)** | 72.76 ms | 84.12 ms | 2.32 ms | | 9 | 🇺🇸 Miami (MIA) | **[106 ms](/docs/network/latency/pairs/mia-ams-rtt)** | 103.48 ms | 113.5 ms | 2.2 ms | | 10 | 🇺🇸 Seattle (SEA) | **[128.6 ms](/docs/network/latency/pairs/sea-ams-rtt)** | 126.47 ms | 138.71 ms | 2.06 ms | ## Inbound Latency to Amsterdam (AMS) Round-trip time in milliseconds **from all other PoPs to Amsterdam**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇬🇧 London (LON) | **[5.2](/docs/network/latency/pairs/lon-ams-rtt)** | 3.51 ms | 67.4% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[5.9](/docs/network/latency/pairs/fra-ams-rtt)** | 3.57 ms | 60.6% | 0.12 ms | 0% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[7](/docs/network/latency/pairs/par-ams-rtt)** | 4.22 ms | 60.3% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[7.2](/docs/network/latency/pairs/ber-ams-rtt)** | 5.67 ms | 78.8% | 0.12 ms | 0% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[20.3](/docs/network/latency/pairs/mrs-ams-rtt)** | 9.89 ms | 48.7% | 0.17 ms | 0.16% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[37.6](/docs/network/latency/pairs/mow-ams-rtt)** | 21.1 ms | 56.1% | 0.28 ms | 0.17% | Excellent | | 🇺🇸 New York (NYC) | **[68.7](/docs/network/latency/pairs/nyc-ams-rtt)** | 57.56 ms | 83.8% | 0.33 ms | 0.03% | Excellent | | 🇺🇸 Ashburn (IAD) | **[75.2](/docs/network/latency/pairs/iad-ams-rtt)** | 60.94 ms | 81% | 0.34 ms | 0.02% | Excellent | | 🇺🇸 Miami (MIA) | **[106](/docs/network/latency/pairs/mia-ams-rtt)** | 73.03 ms | 68.9% | 0.87 ms | 0.08% | Good | | 🇺🇸 Seattle (SEA) | **[128.6](/docs/network/latency/pairs/sea-ams-rtt)** | 76.86 ms | 59.8% | 1.46 ms | 0.13% | Good | | 🇺🇸 Los Angeles (LAX) | **[132.1](/docs/network/latency/pairs/lax-ams-rtt)** | 87.74 ms | 66.4% | 0.78 ms | 0% | Good | | 🇭🇰 Hong Kong (HKG) | **[154.4](/docs/network/latency/pairs/hkg-ams-rtt)** | 91.05 ms | 59% | 0.87 ms | 0% | Fair | | 🇸🇬 Singapore (SIN) | **[155.8](/docs/network/latency/pairs/sin-ams-rtt)** | 102.86 ms | 66% | 1.04 ms | 0.19% | Fair | | 🇿🇦 Johannesburg (JNB) | **[163.2](/docs/network/latency/pairs/jnb-ams-rtt)** | 88.05 ms | 54% | 1.84 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[166.5](/docs/network/latency/pairs/tpe-ams-rtt)** | 92.72 ms | 55.7% | 0.78 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[180](/docs/network/latency/pairs/gru-ams-rtt)** | 95.79 ms | 53.2% | 1.53 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[197.4](/docs/network/latency/pairs/tyo-ams-rtt)** | 91.18 ms | 46.2% | 1.09 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[252.8](/docs/network/latency/pairs/mel-ams-rtt)** | 161.98 ms | 64.1% | 1.86 ms | 0% | High | | 🇦🇺 Sydney (SYD) | **[258.9](/docs/network/latency/pairs/syd-ams-rtt)** | 162.93 ms | 62.9% | 1.18 ms | 0.16% | High | ## Europe Peers Amsterdam is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | --------------------------------------- | ---- | ------- | -------- | --------- | | [🇩🇪 Berlin (BER)](./ber-berlin) | BER | Germany | **7.2** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA | Germany | **5.9** | Ultra-Low | | [🇬🇧 London (LON)](./lon-london) | LON | UK | **5.2** | Ultra-Low | | [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS | France | **19.6** | Ultra-Low | | [🇷🇺 Moscow (MOW)](./mow-moscow) | MOW | Russia | **38.1** | Excellent | | [🇫🇷 Paris (PAR)](./par-paris) | PAR | France | **7** | Ultra-Low | ## Frequently Asked Questions **What is the fastest route to Amsterdam?** The fastest measured route to Amsterdam (AMS) is [London (LON) → Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-rtt), averaging **5.2 ms** RTT (Ultra-Low). **What is the fastest route from Amsterdam?** The fastest measured route from Amsterdam (AMS) is [Amsterdam (AMS) → London (LON)](/docs/network/latency/pairs/ams-lon-rtt), averaging **5.2 ms** RTT (Ultra-Low). **How well connected is Amsterdam to the Hats Network backbone?** Amsterdam (AMS) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Amsterdam (AMS) → Sydney (SYD)](/docs/network/latency/pairs/ams-syd-rtt), averages **258 ms** RTT. ## Open Data Measured latency data for Amsterdam (AMS) 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 Amsterdam is published as `ams-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [ams-lon.pings.csv](/opendata/latency/latest/pairs/ams-lon.pings.csv), the 50-probe ICMP echo round for [Amsterdam (AMS) → London (LON)](/docs/network/latency/pairs/ams-lon-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/ams-amsterdam). - **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. # 🇩🇪 Berlin Ping & Network Latency (BER) | AS203314 ## 🇩🇪 Berlin (BER) Germany's capital and a growing digital hub, Berlin serves as the primary interconnection point between Eastern and Western European networks on the Hats Network backbone. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Berlin (BER)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Berlin, Germany (Europe) * **Region:** Europe * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 2950159](https://www.geonames.org/2950159) — 52.52437, 13.41053 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** BER1 * **Upstream transit:** DE-CIX / RETN / NTT * **Peering / IX:** BCIX > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ------------------------------------------------------------------------------------------------------------ | | Fastest Route | [🇩🇪 Berlin (BER) → 🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/ber-fra-rtt) (**6.1 ms**) — Ultra-Low | | Slowest Route | [🇩🇪 Berlin (BER) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/ber-syd-rtt) (**262.1 ms**) | | Average RTT | **114.8 ms** | | Average Jitter | **1.11 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **78.8%** | | Intra-Region Peers | 6 PoPs in Europe | | 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 Berlin sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **6.1 ms** (Frankfurt (FRA)) to **28.6 ms** (Moscow (MOW)). Berlin sits on the east–west European corridor, bridging the Western European hubs with Eastern European networks. ## Outbound Latency from Berlin (BER) Round-trip time in milliseconds **from Berlin** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇩🇪 Frankfurt (FRA) | **[6.1](/docs/network/latency/pairs/ber-fra-rtt)** | 4.16 ms | 68.2% | 0.12 ms | 0% | Ultra-Low | | 🇳🇱 Amsterdam (AMS) | **[7.2](/docs/network/latency/pairs/ber-ams-rtt)** | 5.67 ms | 78.8% | 0.12 ms | 0% | Ultra-Low | | 🇬🇧 London (LON) | **[15.2](/docs/network/latency/pairs/ber-lon-rtt)** | 9.15 ms | 60.2% | 0.15 ms | 0.14% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[15.6](/docs/network/latency/pairs/ber-par-rtt)** | 8.62 ms | 55.3% | 0.16 ms | 0% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[20.2](/docs/network/latency/pairs/ber-mrs-rtt)** | 11.62 ms | 57.5% | 0.16 ms | 0.06% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[28.6](/docs/network/latency/pairs/ber-mow-rtt)** | 15.8 ms | 55.2% | 0.33 ms | 0% | Ultra-Low | | 🇺🇸 New York (NYC) | **[79.6](/docs/network/latency/pairs/ber-nyc-rtt)** | 62.7 ms | 78.8% | 0.5 ms | 0.08% | Excellent | | 🇺🇸 Ashburn (IAD) | **[85.7](/docs/network/latency/pairs/ber-iad-rtt)** | 66.05 ms | 77.1% | 0.79 ms | 0% | Good | | 🇺🇸 Miami (MIA) | **[118.3](/docs/network/latency/pairs/ber-mia-rtt)** | 78.44 ms | 66.3% | 0.76 ms | 0% | Good | | 🇺🇸 Seattle (SEA) | **[139.7](/docs/network/latency/pairs/ber-sea-rtt)** | 79.73 ms | 57.1% | 1.63 ms | 0.2% | Good | | 🇺🇸 Los Angeles (LAX) | **[140.9](/docs/network/latency/pairs/ber-lax-rtt)** | 91.39 ms | 64.9% | 1.62 ms | 0.1% | Good | | 🇭🇰 Hong Kong (HKG) | **[144.9](/docs/network/latency/pairs/ber-hkg-rtt)** | 85.85 ms | 59.3% | 1.29 ms | 0.08% | Good | | 🇹🇼 Taipei (TPE) | **[156.8](/docs/network/latency/pairs/ber-tpe-rtt)** | 87.84 ms | 56% | 1.45 ms | 0.17% | Fair | | 🇸🇬 Singapore (SIN) | **[158.3](/docs/network/latency/pairs/ber-sin-rtt)** | 97.19 ms | 61.4% | 0.87 ms | 0.19% | Fair | | 🇿🇦 Johannesburg (JNB) | **[172.1](/docs/network/latency/pairs/ber-jnb-rtt)** | 86.53 ms | 50.3% | 1.56 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[186.5](/docs/network/latency/pairs/ber-gru-rtt)** | 100.2 ms | 53.7% | 2.2 ms | 0.01% | Fair | | 🇯🇵 Tokyo (TYO) | **[187.5](/docs/network/latency/pairs/ber-tyo-rtt)** | 87.53 ms | 46.7% | 1.21 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[256.2](/docs/network/latency/pairs/ber-mel-rtt)** | 156.34 ms | 61% | 3.01 ms | 0.03% | High | | 🇦🇺 Sydney (SYD) | **[262.1](/docs/network/latency/pairs/ber-syd-rtt)** | 157.54 ms | 60.1% | 3.1 ms | 0.15% | High | ## Fastest Routes to Berlin (BER) The 10 fastest measured routes **to Berlin**, 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 | 🇩🇪 Frankfurt (FRA) | **[6.1 ms](/docs/network/latency/pairs/fra-ber-rtt)** | 5.91 ms | 6.79 ms | 0.18 ms | | 2 | 🇳🇱 Amsterdam (AMS) | **[7.2 ms](/docs/network/latency/pairs/ams-ber-rtt)** | 6.88 ms | 8.21 ms | 0.31 ms | | 3 | 🇫🇷 Paris (PAR) | **[15.5 ms](/docs/network/latency/pairs/par-ber-rtt)** | 14.87 ms | 17.28 ms | 0.57 ms | | 4 | 🇬🇧 London (LON) | **[16.2 ms](/docs/network/latency/pairs/lon-ber-rtt)** | 15.5 ms | 19.35 ms | 0.73 ms | | 5 | 🇫🇷 Marseille (MRS) | **[20.6 ms](/docs/network/latency/pairs/mrs-ber-rtt)** | 19.99 ms | 21.74 ms | 0.35 ms | | 6 | 🇷🇺 Moscow (MOW) | **[27.5 ms](/docs/network/latency/pairs/mow-ber-rtt)** | 26.72 ms | 29.96 ms | 0.74 ms | | 7 | 🇺🇸 New York (NYC) | **[78.8 ms](/docs/network/latency/pairs/nyc-ber-rtt)** | 77.15 ms | 84.9 ms | 1.59 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[86.1 ms](/docs/network/latency/pairs/iad-ber-rtt)** | 84.07 ms | 94.45 ms | 2.05 ms | | 9 | 🇺🇸 Miami (MIA) | **[117.3 ms](/docs/network/latency/pairs/mia-ber-rtt)** | 113.83 ms | 127.02 ms | 2.73 ms | | 10 | 🇺🇸 Los Angeles (LAX) | **[139.3 ms](/docs/network/latency/pairs/lax-ber-rtt)** | 136.33 ms | 148.84 ms | 2.96 ms | ## Inbound Latency to Berlin (BER) Round-trip time in milliseconds **from all other PoPs to Berlin**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇩🇪 Frankfurt (FRA) | **[6.1](/docs/network/latency/pairs/fra-ber-rtt)** | 4.16 ms | 68.2% | 0.12 ms | 0% | Ultra-Low | | 🇳🇱 Amsterdam (AMS) | **[7.2](/docs/network/latency/pairs/ams-ber-rtt)** | 5.67 ms | 78.8% | 0.12 ms | 0.19% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[15.5](/docs/network/latency/pairs/par-ber-rtt)** | 8.62 ms | 55.6% | 0.13 ms | 0% | Ultra-Low | | 🇬🇧 London (LON) | **[16.2](/docs/network/latency/pairs/lon-ber-rtt)** | 9.15 ms | 56.5% | 0.12 ms | 0.02% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[20.6](/docs/network/latency/pairs/mrs-ber-rtt)** | 11.62 ms | 56.4% | 0.24 ms | 0% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[27.5](/docs/network/latency/pairs/mow-ber-rtt)** | 15.8 ms | 57.5% | 0.3 ms | 0.13% | Ultra-Low | | 🇺🇸 New York (NYC) | **[78.8](/docs/network/latency/pairs/nyc-ber-rtt)** | 62.7 ms | 79.6% | 0.67 ms | 0% | Excellent | | 🇺🇸 Ashburn (IAD) | **[86.1](/docs/network/latency/pairs/iad-ber-rtt)** | 66.05 ms | 76.7% | 0.7 ms | 0% | Good | | 🇺🇸 Miami (MIA) | **[117.3](/docs/network/latency/pairs/mia-ber-rtt)** | 78.44 ms | 66.9% | 1.4 ms | 0% | Good | | 🇺🇸 Los Angeles (LAX) | **[139.3](/docs/network/latency/pairs/lax-ber-rtt)** | 91.39 ms | 65.6% | 1.58 ms | 0.12% | Good | | 🇺🇸 Seattle (SEA) | **[140.9](/docs/network/latency/pairs/sea-ber-rtt)** | 79.73 ms | 56.6% | 1.36 ms | 0.01% | Good | | 🇭🇰 Hong Kong (HKG) | **[145.1](/docs/network/latency/pairs/hkg-ber-rtt)** | 85.85 ms | 59.2% | 0.83 ms | 0.18% | Good | | 🇹🇼 Taipei (TPE) | **[158.6](/docs/network/latency/pairs/tpe-ber-rtt)** | 87.84 ms | 55.4% | 1.84 ms | 0.09% | Fair | | 🇸🇬 Singapore (SIN) | **[160.3](/docs/network/latency/pairs/sin-ber-rtt)** | 97.19 ms | 60.6% | 0.88 ms | 0.19% | Fair | | 🇿🇦 Johannesburg (JNB) | **[172.1](/docs/network/latency/pairs/jnb-ber-rtt)** | 86.53 ms | 50.3% | 1.75 ms | 0.11% | Fair | | 🇯🇵 Tokyo (TYO) | **[186.1](/docs/network/latency/pairs/tyo-ber-rtt)** | 87.53 ms | 47% | 1.64 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[191.3](/docs/network/latency/pairs/gru-ber-rtt)** | 100.2 ms | 52.4% | 2.12 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[254.7](/docs/network/latency/pairs/mel-ber-rtt)** | 156.34 ms | 61.4% | 1.95 ms | 0% | High | | 🇦🇺 Sydney (SYD) | **[260.5](/docs/network/latency/pairs/syd-ber-rtt)** | 157.54 ms | 60.5% | 2.14 ms | 0% | High | ## Europe Peers Berlin is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | --------------------------------------- | ---- | ----------- | -------- | --------- | | [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS | Netherlands | **7.2** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA | Germany | **6.1** | Ultra-Low | | [🇬🇧 London (LON)](./lon-london) | LON | UK | **15.2** | Ultra-Low | | [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS | France | **20.2** | Ultra-Low | | [🇷🇺 Moscow (MOW)](./mow-moscow) | MOW | Russia | **28.6** | Ultra-Low | | [🇫🇷 Paris (PAR)](./par-paris) | PAR | France | **15.6** | Ultra-Low | ## Frequently Asked Questions **What is the fastest route to Berlin?** The fastest measured route to Berlin (BER) is [Frankfurt (FRA) → Berlin (BER)](/docs/network/latency/pairs/fra-ber-rtt), averaging **6.1 ms** RTT (Ultra-Low). **What is the fastest route from Berlin?** The fastest measured route from Berlin (BER) is [Berlin (BER) → Frankfurt (FRA)](/docs/network/latency/pairs/ber-fra-rtt), averaging **6.1 ms** RTT (Ultra-Low). **How well connected is Berlin to the Hats Network backbone?** Berlin (BER) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Berlin (BER) → Sydney (SYD)](/docs/network/latency/pairs/ber-syd-rtt), averages **262.1 ms** RTT. ## Open Data Measured latency data for Berlin (BER) 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 Berlin is published as `ber-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [ber-fra.pings.csv](/opendata/latency/latest/pairs/ber-fra.pings.csv), the 50-probe ICMP echo round for [Berlin (BER) → Frankfurt (FRA)](/docs/network/latency/pairs/ber-fra-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/ber-berlin). - **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. # 🇩🇪 Frankfurt Ping & Network Latency (FRA) | AS203314 ## 🇩🇪 Frankfurt (FRA) Frankfurt is Europe's financial center and home to DE-CIX, the world's second-largest Internet Exchange. This PoP anchors Hats Network's dense European fiber ring. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Frankfurt (FRA)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Frankfurt, Germany (Europe) * **Region:** Europe * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 2925533](https://www.geonames.org/2925533) — 50.11552, 8.68417 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** FRA1 > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | --------------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇩🇪 Frankfurt (FRA) → 🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/fra-ams-rtt) (**5.9 ms**) — Ultra-Low | | Slowest Route | [🇩🇪 Frankfurt (FRA) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/fra-syd-rtt) (**256 ms**) | | Average RTT | **114.0 ms** | | Average Jitter | **0.95 ms** | | Average Packet Loss | **0.05%** | | Best Fiber Efficiency | **81.9%** | | Intra-Region Peers | 6 PoPs in Europe | | 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 Frankfurt sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **5.9 ms** (Amsterdam (AMS)) to **34.7 ms** (Moscow (MOW)). Frankfurt is the central switching point of the European fiber ring and home to DE-CIX, one of the world's largest Internet Exchanges. ## Outbound Latency from Frankfurt (FRA) Round-trip time in milliseconds **from Frankfurt** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇳🇱 Amsterdam (AMS) | **[5.9](/docs/network/latency/pairs/fra-ams-rtt)** | 3.57 ms | 60.6% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[6.1](/docs/network/latency/pairs/fra-ber-rtt)** | 4.16 ms | 68.2% | 0.12 ms | 0% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[7.6](/docs/network/latency/pairs/fra-par-rtt)** | 4.7 ms | 61.8% | 0.12 ms | 0% | Ultra-Low | | 🇬🇧 London (LON) | **[12.9](/docs/network/latency/pairs/fra-lon-rtt)** | 6.26 ms | 48.5% | 0.12 ms | 0% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[16.4](/docs/network/latency/pairs/fra-mrs-rtt)** | 7.82 ms | 47.7% | 0.19 ms | 0% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[34.7](/docs/network/latency/pairs/fra-mow-rtt)** | 19.85 ms | 57.2% | 0.25 ms | 0.13% | Excellent | | 🇺🇸 New York (NYC) | **[74.4](/docs/network/latency/pairs/fra-nyc-rtt)** | 60.9 ms | 81.9% | 0.73 ms | 0% | Excellent | | 🇺🇸 Ashburn (IAD) | **[80.7](/docs/network/latency/pairs/fra-iad-rtt)** | 64.3 ms | 79.7% | 0.91 ms | 0.04% | Good | | 🇺🇸 Miami (MIA) | **[112](/docs/network/latency/pairs/fra-mia-rtt)** | 76.17 ms | 68% | 1.27 ms | 0.07% | Good | | 🇺🇸 Seattle (SEA) | **[135.2](/docs/network/latency/pairs/fra-sea-rtt)** | 80.34 ms | 59.4% | 0.98 ms | 0.16% | Good | | 🇺🇸 Los Angeles (LAX) | **[141.8](/docs/network/latency/pairs/fra-lax-rtt)** | 91.31 ms | 64.4% | 1.06 ms | 0% | Good | | 🇸🇬 Singapore (SIN) | **[151.4](/docs/network/latency/pairs/fra-sin-rtt)** | 100.56 ms | 66.4% | 0.7 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[152](/docs/network/latency/pairs/fra-hkg-rtt)** | 89.87 ms | 59.1% | 1.18 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[163.8](/docs/network/latency/pairs/fra-tpe-rtt)** | 91.96 ms | 56.1% | 1.28 ms | 0.04% | Fair | | 🇧🇷 São Paulo (GRU) | **[181.3](/docs/network/latency/pairs/fra-gru-rtt)** | 96.04 ms | 53% | 2.02 ms | 0.04% | Fair | | 🇿🇦 Johannesburg (JNB) | **[188.4](/docs/network/latency/pairs/fra-jnb-rtt)** | 84.87 ms | 45% | 1.61 ms | 0.1% | Fair | | 🇯🇵 Tokyo (TYO) | **[194.5](/docs/network/latency/pairs/fra-tyo-rtt)** | 91.61 ms | 47.1% | 1.29 ms | 0.12% | Fair | | 🇦🇺 Melbourne (MEL) | **[250.1](/docs/network/latency/pairs/fra-mel-rtt)** | 159.77 ms | 63.9% | 2.57 ms | 0% | High | | 🇦🇺 Sydney (SYD) | **[256](/docs/network/latency/pairs/fra-syd-rtt)** | 161.37 ms | 63% | 1.5 ms | 0.16% | High | ## Fastest Routes to Frankfurt (FRA) The 10 fastest measured routes **to Frankfurt**, 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 | 🇳🇱 Amsterdam (AMS) | **[5.9 ms](/docs/network/latency/pairs/ams-fra-rtt)** | 5.67 ms | 7.15 ms | 0.23 ms | | 2 | 🇩🇪 Berlin (BER) | **[6.1 ms](/docs/network/latency/pairs/ber-fra-rtt)** | 5.9 ms | 6.73 ms | 0.18 ms | | 3 | 🇫🇷 Paris (PAR) | **[7.6 ms](/docs/network/latency/pairs/par-fra-rtt)** | 7.35 ms | 8.42 ms | 0.22 ms | | 4 | 🇬🇧 London (LON) | **[13.6 ms](/docs/network/latency/pairs/lon-fra-rtt)** | 13.18 ms | 15.43 ms | 0.42 ms | | 5 | 🇫🇷 Marseille (MRS) | **[16 ms](/docs/network/latency/pairs/mrs-fra-rtt)** | 15.12 ms | 18.91 ms | 0.79 ms | | 6 | 🇷🇺 Moscow (MOW) | **[35.9 ms](/docs/network/latency/pairs/mow-fra-rtt)** | 33.56 ms | 42.93 ms | 1.78 ms | | 7 | 🇺🇸 New York (NYC) | **[73.9 ms](/docs/network/latency/pairs/nyc-fra-rtt)** | 71.94 ms | 81.47 ms | 1.98 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[81.2 ms](/docs/network/latency/pairs/iad-fra-rtt)** | 79.1 ms | 86.57 ms | 1.81 ms | | 9 | 🇺🇸 Miami (MIA) | **[112.2 ms](/docs/network/latency/pairs/mia-fra-rtt)** | 108.19 ms | 121.5 ms | 3.61 ms | | 10 | 🇺🇸 Seattle (SEA) | **[133.2 ms](/docs/network/latency/pairs/sea-fra-rtt)** | 130.2 ms | 141.75 ms | 2.72 ms | ## Inbound Latency to Frankfurt (FRA) Round-trip time in milliseconds **from all other PoPs to Frankfurt**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇳🇱 Amsterdam (AMS) | **[5.9](/docs/network/latency/pairs/ams-fra-rtt)** | 3.57 ms | 60.6% | 0.12 ms | 0.05% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[6.1](/docs/network/latency/pairs/ber-fra-rtt)** | 4.16 ms | 68.2% | 0.12 ms | 0% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[7.6](/docs/network/latency/pairs/par-fra-rtt)** | 4.7 ms | 61.8% | 0.12 ms | 0.1% | Ultra-Low | | 🇬🇧 London (LON) | **[13.6](/docs/network/latency/pairs/lon-fra-rtt)** | 6.26 ms | 46.1% | 0.12 ms | 0.03% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[16](/docs/network/latency/pairs/mrs-fra-rtt)** | 7.82 ms | 48.9% | 0.18 ms | 0.15% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[35.9](/docs/network/latency/pairs/mow-fra-rtt)** | 19.85 ms | 55.3% | 0.3 ms | 0% | Excellent | | 🇺🇸 New York (NYC) | **[73.9](/docs/network/latency/pairs/nyc-fra-rtt)** | 60.9 ms | 82.4% | 0.74 ms | 0.09% | Excellent | | 🇺🇸 Ashburn (IAD) | **[81.2](/docs/network/latency/pairs/iad-fra-rtt)** | 64.3 ms | 79.2% | 0.95 ms | 0.1% | Good | | 🇺🇸 Miami (MIA) | **[112.2](/docs/network/latency/pairs/mia-fra-rtt)** | 76.17 ms | 67.9% | 0.83 ms | 0.06% | Good | | 🇺🇸 Seattle (SEA) | **[133.2](/docs/network/latency/pairs/sea-fra-rtt)** | 80.34 ms | 60.3% | 0.66 ms | 0.11% | Good | | 🇺🇸 Los Angeles (LAX) | **[142.3](/docs/network/latency/pairs/lax-fra-rtt)** | 91.31 ms | 64.2% | 0.71 ms | 0% | Good | | 🇭🇰 Hong Kong (HKG) | **[150.7](/docs/network/latency/pairs/hkg-fra-rtt)** | 89.87 ms | 59.6% | 1.66 ms | 0% | Fair | | 🇸🇬 Singapore (SIN) | **[151.6](/docs/network/latency/pairs/sin-fra-rtt)** | 100.56 ms | 66.3% | 0.77 ms | 0.04% | Fair | | 🇹🇼 Taipei (TPE) | **[166](/docs/network/latency/pairs/tpe-fra-rtt)** | 91.96 ms | 55.4% | 1.67 ms | 0.13% | Fair | | 🇿🇦 Johannesburg (JNB) | **[166](/docs/network/latency/pairs/jnb-fra-rtt)** | 84.87 ms | 51.1% | 1.86 ms | 0.11% | Fair | | 🇧🇷 São Paulo (GRU) | **[186.2](/docs/network/latency/pairs/gru-fra-rtt)** | 96.04 ms | 51.6% | 2 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[193.2](/docs/network/latency/pairs/tyo-fra-rtt)** | 91.61 ms | 47.4% | 2.16 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[248.6](/docs/network/latency/pairs/mel-fra-rtt)** | 159.77 ms | 64.3% | 2.09 ms | 0.16% | Fair | | 🇦🇺 Sydney (SYD) | **[254.4](/docs/network/latency/pairs/syd-fra-rtt)** | 161.37 ms | 63.4% | 2.54 ms | 0% | High | ## Europe Peers Frankfurt is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | --------------------------------------- | ---- | ----------- | -------- | --------- | | [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS | Netherlands | **5.9** | Ultra-Low | | [🇩🇪 Berlin (BER)](./ber-berlin) | BER | Germany | **6.1** | Ultra-Low | | [🇬🇧 London (LON)](./lon-london) | LON | UK | **12.9** | Ultra-Low | | [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS | France | **16.4** | Ultra-Low | | [🇷🇺 Moscow (MOW)](./mow-moscow) | MOW | Russia | **34.7** | Excellent | | [🇫🇷 Paris (PAR)](./par-paris) | PAR | France | **7.6** | Ultra-Low | ## Frequently Asked Questions **What is the fastest route to Frankfurt?** The fastest measured route to Frankfurt (FRA) is [Amsterdam (AMS) → Frankfurt (FRA)](/docs/network/latency/pairs/ams-fra-rtt), averaging **5.9 ms** RTT (Ultra-Low). **What is the fastest route from Frankfurt?** The fastest measured route from Frankfurt (FRA) is [Frankfurt (FRA) → Amsterdam (AMS)](/docs/network/latency/pairs/fra-ams-rtt), averaging **5.9 ms** RTT (Ultra-Low). **How well connected is Frankfurt to the Hats Network backbone?** Frankfurt (FRA) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Frankfurt (FRA) → Sydney (SYD)](/docs/network/latency/pairs/fra-syd-rtt), averages **256 ms** RTT. ## Open Data Measured latency data for Frankfurt (FRA) 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 Frankfurt is published as `fra-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [fra-ams.pings.csv](/opendata/latency/latest/pairs/fra-ams.pings.csv), the 50-probe ICMP echo round for [Frankfurt (FRA) → Amsterdam (AMS)](/docs/network/latency/pairs/fra-ams-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/fra-frankfurt). - **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. # 🇧🇷 São Paulo Ping & Network Latency (GRU) | AS203314 ## 🇧🇷 São Paulo (GRU) São Paulo is the internet capital of South America, hosting the region's largest peering ecosystem at PIX. Hats Network's only South American PoP connects the continent to the global backbone. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **São Paulo (GRU)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** São Paulo, Brazil (South America) * **Region:** South America * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 3448439](https://www.geonames.org/3448439) — -23.54750, -46.63611 * **Coverage:** RTT measurements to 19 other PoPs across 4 continents ### Facility & Interconnection * **Facility:** GRU1 * **Upstream transit:** NTT / Ascenty > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇧🇷 São Paulo (GRU) → 🇺🇸 Miami (MIA)](/docs/network/latency/pairs/gru-mia-rtt) (**74 ms**) — Excellent | | Slowest Route | [🇧🇷 São Paulo (GRU) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/gru-jnb-rtt) (**333.8 ms**) | | Average RTT | **203.4 ms** | | Average Jitter | **1.75 ms** | | Average Packet Loss | **0.05%** | | Best Fiber Efficiency | **86.6%** | | Intra-Region Peers | 0 PoP in South America | | 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 São Paulo is Hats Network's only PoP in **South America**. The nearest measured backbone PoP is Miami (MIA) at **74 ms** RTT. São Paulo is South America's internet capital, connecting the continent north to Miami and east across the Atlantic. ## Outbound Latency from São Paulo (GRU) Round-trip time in milliseconds **from São Paulo** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Miami (MIA) | **[74](/docs/network/latency/pairs/gru-mia-rtt)** | 64.11 ms | 86.6% | 0.62 ms | 0.16% | Excellent | | 🇺🇸 New York (NYC) | **[122](/docs/network/latency/pairs/gru-nyc-rtt)** | 74.99 ms | 61.5% | 1.29 ms | 0% | Good | | 🇺🇸 Ashburn (IAD) | **[128](/docs/network/latency/pairs/gru-iad-rtt)** | 74.79 ms | 58.4% | 0.6 ms | 0.09% | Good | | 🇺🇸 Los Angeles (LAX) | **[130.8](/docs/network/latency/pairs/gru-lax-rtt)** | 96.89 ms | 74.1% | 0.66 ms | 0% | Good | | 🇺🇸 Seattle (SEA) | **[155.9](/docs/network/latency/pairs/gru-sea-rtt)** | 106.76 ms | 68.5% | 1.54 ms | 0.19% | Fair | | 🇬🇧 London (LON) | **[175.8](/docs/network/latency/pairs/gru-lon-rtt)** | 92.76 ms | 52.8% | 1.62 ms | 0% | Fair | | 🇳🇱 Amsterdam (AMS) | **[180](/docs/network/latency/pairs/gru-ams-rtt)** | 95.79 ms | 53.2% | 1.53 ms | 0% | Fair | | 🇫🇷 Paris (PAR) | **[180.2](/docs/network/latency/pairs/gru-par-rtt)** | 91.83 ms | 51% | 1.95 ms | 0.14% | Fair | | 🇩🇪 Frankfurt (FRA) | **[186.2](/docs/network/latency/pairs/gru-fra-rtt)** | 96.04 ms | 51.6% | 2 ms | 0% | Fair | | 🇫🇷 Marseille (MRS) | **[187.7](/docs/network/latency/pairs/gru-mrs-rtt)** | 89.24 ms | 47.5% | 1.08 ms | 0.14% | Fair | | 🇩🇪 Berlin (BER) | **[191.3](/docs/network/latency/pairs/gru-ber-rtt)** | 100.2 ms | 52.4% | 2.12 ms | 0% | Fair | | 🇷🇺 Moscow (MOW) | **[219.5](/docs/network/latency/pairs/gru-mow-rtt)** | 115.47 ms | 52.6% | 1.57 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[230.3](/docs/network/latency/pairs/gru-tyo-rtt)** | 181.46 ms | 78.8% | 2.42 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[259.1](/docs/network/latency/pairs/gru-tpe-rtt)** | 184.29 ms | 71.1% | 3.01 ms | 0% | High | | 🇦🇺 Sydney (SYD) | **[265.5](/docs/network/latency/pairs/gru-syd-rtt)** | 131 ms | 49.3% | 1.66 ms | 0% | High | | 🇭🇰 Hong Kong (HKG) | **[273.5](/docs/network/latency/pairs/gru-hkg-rtt)** | 176.86 ms | 64.7% | 2.57 ms | 0% | High | | 🇦🇺 Melbourne (MEL) | **[274.7](/docs/network/latency/pairs/gru-mel-rtt)** | 128.34 ms | 46.7% | 1.71 ms | 0.08% | High | | 🇸🇬 Singapore (SIN) | **[297.1](/docs/network/latency/pairs/gru-sin-rtt)** | 156.67 ms | 52.7% | 2.14 ms | 0.08% | High | | 🇿🇦 Johannesburg (JNB) | **[333.8](/docs/network/latency/pairs/gru-jnb-rtt)** | 72.88 ms | 21.8% | 3.1 ms | 0.07% | High | ## Fastest Routes to São Paulo (GRU) The 10 fastest measured routes **to São Paulo**, 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 | 🇺🇸 Ashburn (IAD) | **[101.4 ms](/docs/network/latency/pairs/iad-gru-rtt)** | 98.16 ms | 107.74 ms | 2.31 ms | | 2 | 🇺🇸 New York (NYC) | **[106.9 ms](/docs/network/latency/pairs/nyc-gru-rtt)** | 104.25 ms | 117.31 ms | 2.21 ms | | 3 | 🇺🇸 Miami (MIA) | **[128.7 ms](/docs/network/latency/pairs/mia-gru-rtt)** | 126.78 ms | 136.62 ms | 1.96 ms | | 4 | 🇺🇸 Los Angeles (LAX) | **[131.3 ms](/docs/network/latency/pairs/lax-gru-rtt)** | 125.74 ms | 147.12 ms | 4.94 ms | | 5 | 🇺🇸 Seattle (SEA) | **[155.7 ms](/docs/network/latency/pairs/sea-gru-rtt)** | 152.75 ms | 163 ms | 2.37 ms | | 6 | 🇬🇧 London (LON) | **[170.7 ms](/docs/network/latency/pairs/lon-gru-rtt)** | 165.28 ms | 185.16 ms | 4.35 ms | | 7 | 🇳🇱 Amsterdam (AMS) | **[175.5 ms](/docs/network/latency/pairs/ams-gru-rtt)** | 166.82 ms | 195.11 ms | 6.86 ms | | 8 | 🇫🇷 Paris (PAR) | **[175.8 ms](/docs/network/latency/pairs/par-gru-rtt)** | 173.09 ms | 186.7 ms | 2.78 ms | | 9 | 🇩🇪 Frankfurt (FRA) | **[181.3 ms](/docs/network/latency/pairs/fra-gru-rtt)** | 176.28 ms | 197.75 ms | 3.73 ms | | 10 | 🇩🇪 Berlin (BER) | **[186.5 ms](/docs/network/latency/pairs/ber-gru-rtt)** | 179.2 ms | 206.69 ms | 6.78 ms | ## Inbound Latency to São Paulo (GRU) Round-trip time in milliseconds **from all other PoPs to São Paulo**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | ---- | | 🇺🇸 Ashburn (IAD) | **[101.4](/docs/network/latency/pairs/iad-gru-rtt)** | 74.79 ms | 73.8% | 1.02 ms | 0% | Good | | 🇺🇸 New York (NYC) | **[106.9](/docs/network/latency/pairs/nyc-gru-rtt)** | 74.99 ms | 70.1% | 0.74 ms | 0% | Good | | 🇺🇸 Miami (MIA) | **[128.7](/docs/network/latency/pairs/mia-gru-rtt)** | 64.11 ms | 49.8% | 0.81 ms | 0.16% | Good | | 🇺🇸 Los Angeles (LAX) | **[131.3](/docs/network/latency/pairs/lax-gru-rtt)** | 96.89 ms | 73.8% | 0.87 ms | 0% | Good | | 🇺🇸 Seattle (SEA) | **[155.7](/docs/network/latency/pairs/sea-gru-rtt)** | 106.76 ms | 68.6% | 1.76 ms | 0% | Fair | | 🇬🇧 London (LON) | **[170.7](/docs/network/latency/pairs/lon-gru-rtt)** | 92.76 ms | 54.3% | 1.06 ms | 0.02% | Fair | | 🇳🇱 Amsterdam (AMS) | **[175.5](/docs/network/latency/pairs/ams-gru-rtt)** | 95.79 ms | 54.6% | 1.53 ms | 0% | Fair | | 🇫🇷 Paris (PAR) | **[175.8](/docs/network/latency/pairs/par-gru-rtt)** | 91.83 ms | 52.2% | 1.26 ms | 0% | Fair | | 🇩🇪 Frankfurt (FRA) | **[181.3](/docs/network/latency/pairs/fra-gru-rtt)** | 96.04 ms | 53% | 2.02 ms | 0.04% | Fair | | 🇩🇪 Berlin (BER) | **[186.5](/docs/network/latency/pairs/ber-gru-rtt)** | 100.2 ms | 53.7% | 2.2 ms | 0.01% | Fair | | 🇫🇷 Marseille (MRS) | **[186.7](/docs/network/latency/pairs/mrs-gru-rtt)** | 89.24 ms | 47.8% | 1.4 ms | 0.05% | Fair | | 🇷🇺 Moscow (MOW) | **[214.4](/docs/network/latency/pairs/mow-gru-rtt)** | 115.47 ms | 53.9% | 1.47 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[230.5](/docs/network/latency/pairs/tyo-gru-rtt)** | 181.46 ms | 78.7% | 1.53 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[273](/docs/network/latency/pairs/tpe-gru-rtt)** | 184.29 ms | 67.5% | 2.95 ms | 0.03% | High | | 🇭🇰 Hong Kong (HKG) | **[287.6](/docs/network/latency/pairs/hkg-gru-rtt)** | 176.86 ms | 61.5% | 2.69 ms | 0.03% | High | | 🇦🇺 Sydney (SYD) | **[296.7](/docs/network/latency/pairs/syd-gru-rtt)** | 131 ms | 44.2% | 1.93 ms | 0% | High | | 🇦🇺 Melbourne (MEL) | **[305.3](/docs/network/latency/pairs/mel-gru-rtt)** | 128.34 ms | 42% | 1.69 ms | 0% | High | | 🇸🇬 Singapore (SIN) | **[311.4](/docs/network/latency/pairs/sin-gru-rtt)** | 156.67 ms | 50.3% | 2.4 ms | 0.1% | High | | 🇿🇦 Johannesburg (JNB) | **[328.7](/docs/network/latency/pairs/jnb-gru-rtt)** | 72.88 ms | 22.2% | 2.32 ms | 0.06% | High | ## Frequently Asked Questions **What is the fastest route to São Paulo?** The fastest measured route to São Paulo (GRU) is [Ashburn (IAD) → São Paulo (GRU)](/docs/network/latency/pairs/iad-gru-rtt), averaging **101.4 ms** RTT (Good). **What is the fastest route from São Paulo?** The fastest measured route from São Paulo (GRU) is [São Paulo (GRU) → Miami (MIA)](/docs/network/latency/pairs/gru-mia-rtt), averaging **74 ms** RTT (Excellent). **How well connected is São Paulo to the Hats Network backbone?** São Paulo (GRU) maintains measured routes to all 19 other PoPs across 4 continents. The slowest route, [São Paulo (GRU) → Johannesburg (JNB)](/docs/network/latency/pairs/gru-jnb-rtt), averages **333.8 ms** RTT. ## Open Data Measured latency data for São Paulo (GRU) 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 São Paulo is published as `gru-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [gru-mia.pings.csv](/opendata/latency/latest/pairs/gru-mia.pings.csv), the 50-probe ICMP echo round for [São Paulo (GRU) → Miami (MIA)](/docs/network/latency/pairs/gru-mia-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/gru-sao-paulo). - **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. # 🇭🇰 Hong Kong Ping & Network Latency (HKG) | AS203314 ## 🇭🇰 Hong Kong (HKG) Hong Kong is Asia's premier financial and interconnection hub, offering direct access to one of the world's densest fiber markets. Hats Network's HKG PoP is a cornerstone of the Asia-Pacific backbone. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Hong Kong (HKG)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Hong Kong, Hong Kong (Asia Pacific) * **Region:** Asia Pacific * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 1819729](https://www.geonames.org/1819729) — 22.27832, 114.17469 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** HKG3 * **Upstream transit:** HE / Cogent / CDN77 * **Peering / IX:** Equinix IX / HKIX > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ------------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇭🇰 Hong Kong (HKG) → 🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt) (**14.7 ms**) — Ultra-Low | | Slowest Route | [🇭🇰 Hong Kong (HKG) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/hkg-jnb-rtt) (**316.7 ms**) | | Average RTT | **151.1 ms** | | Average Jitter | **1.15 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **80.1%** | | 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 Hong Kong sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **14.7 ms** (Taipei (TPE)) to **138.4 ms** (Melbourne (MEL)). Hong Kong is a dense Asia-Pacific interconnection hub; regional submarine systems such as APG link it with Taiwan, Japan and Southeast Asia. ## Outbound Latency from Hong Kong (HKG) Round-trip time in milliseconds **from Hong Kong** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇹🇼 Taipei (TPE) | **[14.7](/docs/network/latency/pairs/hkg-tpe-rtt)** | 7.94 ms | 54% | 0.14 ms | 0.08% | Ultra-Low | | 🇸🇬 Singapore (SIN) | **[31.5](/docs/network/latency/pairs/hkg-sin-rtt)** | 25.24 ms | 80.1% | 0.33 ms | 0.05% | Excellent | | 🇯🇵 Tokyo (TYO) | **[44.9](/docs/network/latency/pairs/hkg-tyo-rtt)** | 28.24 ms | 62.9% | 0.23 ms | 0.08% | Excellent | | 🇷🇺 Moscow (MOW) | **[118.2](/docs/network/latency/pairs/hkg-mow-rtt)** | 70.05 ms | 59.3% | 1.17 ms | 0.11% | Good | | 🇺🇸 Seattle (SEA) | **[131.6](/docs/network/latency/pairs/hkg-sea-rtt)** | 102.2 ms | 77.7% | 0.82 ms | 0.05% | Good | | 🇦🇺 Sydney (SYD) | **[137.2](/docs/network/latency/pairs/hkg-syd-rtt)** | 71.97 ms | 52.5% | 0.86 ms | 0.17% | Good | | 🇦🇺 Melbourne (MEL) | **[138.4](/docs/network/latency/pairs/hkg-mel-rtt)** | 72.38 ms | 52.3% | 1.41 ms | 0% | Good | | 🇺🇸 Los Angeles (LAX) | **[145](/docs/network/latency/pairs/hkg-lax-rtt)** | 114.3 ms | 78.8% | 1.4 ms | 0.06% | Good | | 🇩🇪 Berlin (BER) | **[145.1](/docs/network/latency/pairs/hkg-ber-rtt)** | 85.85 ms | 59.2% | 0.83 ms | 0.18% | Good | | 🇩🇪 Frankfurt (FRA) | **[150.7](/docs/network/latency/pairs/hkg-fra-rtt)** | 89.87 ms | 59.6% | 1.66 ms | 0% | Fair | | 🇳🇱 Amsterdam (AMS) | **[154.4](/docs/network/latency/pairs/hkg-ams-rtt)** | 91.05 ms | 59% | 0.87 ms | 0% | Fair | | 🇬🇧 London (LON) | **[158.7](/docs/network/latency/pairs/hkg-lon-rtt)** | 94.44 ms | 59.5% | 0.8 ms | 0% | Fair | | 🇫🇷 Paris (PAR) | **[159.4](/docs/network/latency/pairs/hkg-par-rtt)** | 94.48 ms | 59.3% | 1.21 ms | 0.07% | Fair | | 🇫🇷 Marseille (MRS) | **[165.4](/docs/network/latency/pairs/hkg-mrs-rtt)** | 95.48 ms | 57.7% | 0.85 ms | 0.09% | Fair | | 🇺🇸 New York (NYC) | **[184.7](/docs/network/latency/pairs/hkg-nyc-rtt)** | 127.11 ms | 68.8% | 0.98 ms | 0% | Fair | | 🇺🇸 Ashburn (IAD) | **[186.2](/docs/network/latency/pairs/hkg-iad-rtt)** | 128.37 ms | 68.9% | 1.54 ms | 0.04% | Fair | | 🇺🇸 Miami (MIA) | **[201.1](/docs/network/latency/pairs/hkg-mia-rtt)** | 141.69 ms | 70.5% | 0.93 ms | 0.05% | Fair | | 🇧🇷 São Paulo (GRU) | **[287.6](/docs/network/latency/pairs/hkg-gru-rtt)** | 176.86 ms | 61.5% | 2.69 ms | 0.03% | High | | 🇿🇦 Johannesburg (JNB) | **[316.7](/docs/network/latency/pairs/hkg-jnb-rtt)** | 104.93 ms | 33.1% | 3.12 ms | 0% | High | ## Fastest Routes to Hong Kong (HKG) The 10 fastest measured routes **to Hong Kong**, 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 | 🇹🇼 Taipei (TPE) | **[15.5 ms](/docs/network/latency/pairs/tpe-hkg-rtt)** | 15.09 ms | 17.58 ms | 0.41 ms | | 2 | 🇸🇬 Singapore (SIN) | **[30.8 ms](/docs/network/latency/pairs/sin-hkg-rtt)** | 30.29 ms | 33.37 ms | 0.58 ms | | 3 | 🇯🇵 Tokyo (TYO) | **[44.8 ms](/docs/network/latency/pairs/tyo-hkg-rtt)** | 43.35 ms | 48.43 ms | 1.13 ms | | 4 | 🇷🇺 Moscow (MOW) | **[118.6 ms](/docs/network/latency/pairs/mow-hkg-rtt)** | 116.41 ms | 127.8 ms | 2.24 ms | | 5 | 🇺🇸 Seattle (SEA) | **[130.4 ms](/docs/network/latency/pairs/sea-hkg-rtt)** | 125.05 ms | 145.66 ms | 4.85 ms | | 6 | 🇦🇺 Sydney (SYD) | **[135.7 ms](/docs/network/latency/pairs/syd-hkg-rtt)** | 124.18 ms | 155.08 ms | 6.42 ms | | 7 | 🇦🇺 Melbourne (MEL) | **[138.5 ms](/docs/network/latency/pairs/mel-hkg-rtt)** | 133.73 ms | 150.99 ms | 4.36 ms | | 8 | 🇩🇪 Berlin (BER) | **[144.9 ms](/docs/network/latency/pairs/ber-hkg-rtt)** | 140.42 ms | 158.73 ms | 3.7 ms | | 9 | 🇺🇸 Los Angeles (LAX) | **[146.5 ms](/docs/network/latency/pairs/lax-hkg-rtt)** | 143.01 ms | 158.89 ms | 3.29 ms | | 10 | 🇩🇪 Frankfurt (FRA) | **[152 ms](/docs/network/latency/pairs/fra-hkg-rtt)** | 144.15 ms | 171.03 ms | 6.84 ms | ## Inbound Latency to Hong Kong (HKG) Round-trip time in milliseconds **from all other PoPs to Hong Kong**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇹🇼 Taipei (TPE) | **[15.5](/docs/network/latency/pairs/tpe-hkg-rtt)** | 7.94 ms | 51.2% | 0.16 ms | 0.02% | Ultra-Low | | 🇸🇬 Singapore (SIN) | **[30.8](/docs/network/latency/pairs/sin-hkg-rtt)** | 25.24 ms | 81.9% | 0.23 ms | 0.1% | Excellent | | 🇯🇵 Tokyo (TYO) | **[44.8](/docs/network/latency/pairs/tyo-hkg-rtt)** | 28.24 ms | 63% | 0.45 ms | 0.07% | Excellent | | 🇷🇺 Moscow (MOW) | **[118.6](/docs/network/latency/pairs/mow-hkg-rtt)** | 70.05 ms | 59.1% | 0.77 ms | 0.13% | Good | | 🇺🇸 Seattle (SEA) | **[130.4](/docs/network/latency/pairs/sea-hkg-rtt)** | 102.2 ms | 78.4% | 0.7 ms | 0% | Good | | 🇦🇺 Sydney (SYD) | **[135.7](/docs/network/latency/pairs/syd-hkg-rtt)** | 71.97 ms | 53% | 0.65 ms | 0.19% | Good | | 🇦🇺 Melbourne (MEL) | **[138.5](/docs/network/latency/pairs/mel-hkg-rtt)** | 72.38 ms | 52.3% | 1.39 ms | 0.19% | Good | | 🇩🇪 Berlin (BER) | **[144.9](/docs/network/latency/pairs/ber-hkg-rtt)** | 85.85 ms | 59.3% | 1.29 ms | 0.08% | Good | | 🇺🇸 Los Angeles (LAX) | **[146.5](/docs/network/latency/pairs/lax-hkg-rtt)** | 114.3 ms | 78% | 1.42 ms | 0% | Good | | 🇩🇪 Frankfurt (FRA) | **[152](/docs/network/latency/pairs/fra-hkg-rtt)** | 89.87 ms | 59.1% | 1.18 ms | 0% | Fair | | 🇳🇱 Amsterdam (AMS) | **[155.9](/docs/network/latency/pairs/ams-hkg-rtt)** | 91.05 ms | 58.4% | 1.21 ms | 0.05% | Fair | | 🇫🇷 Paris (PAR) | **[160.1](/docs/network/latency/pairs/par-hkg-rtt)** | 94.48 ms | 59% | 1.29 ms | 0.05% | Fair | | 🇬🇧 London (LON) | **[160.6](/docs/network/latency/pairs/lon-hkg-rtt)** | 94.44 ms | 58.8% | 0.84 ms | 0.07% | Fair | | 🇫🇷 Marseille (MRS) | **[166.4](/docs/network/latency/pairs/mrs-hkg-rtt)** | 95.48 ms | 57.4% | 1.49 ms | 0% | Fair | | 🇺🇸 New York (NYC) | **[187.1](/docs/network/latency/pairs/nyc-hkg-rtt)** | 127.11 ms | 67.9% | 1.76 ms | 0% | Fair | | 🇺🇸 Ashburn (IAD) | **[187.2](/docs/network/latency/pairs/iad-hkg-rtt)** | 128.37 ms | 68.6% | 1 ms | 0.05% | Fair | | 🇺🇸 Miami (MIA) | **[199.5](/docs/network/latency/pairs/mia-hkg-rtt)** | 141.69 ms | 71% | 2.35 ms | 0.06% | Fair | | 🇧🇷 São Paulo (GRU) | **[273.5](/docs/network/latency/pairs/gru-hkg-rtt)** | 176.86 ms | 64.7% | 2.57 ms | 0% | High | | 🇿🇦 Johannesburg (JNB) | **[318](/docs/network/latency/pairs/jnb-hkg-rtt)** | 104.93 ms | 33% | 3.32 ms | 0.19% | High | ## Asia Pacific Peers Hong Kong 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 | | --------------------------------------- | ---- | --------- | --------- | --------- | | [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL | Australia | **138.4** | Good | | [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN | Singapore | **31.5** | Excellent | | [🇦🇺 Sydney (SYD)](./syd-sydney) | SYD | Australia | **137.2** | Good | | [🇹🇼 Taipei (TPE)](./tpe-taipei) | TPE | Taiwan | **14.7** | Ultra-Low | | [🇯🇵 Tokyo (TYO)](./tyo-tokyo) | TYO | Japan | **44.9** | Excellent | ## Frequently Asked Questions **What is the fastest route to Hong Kong?** The fastest measured route to Hong Kong (HKG) is [Taipei (TPE) → Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt), averaging **15.5 ms** RTT (Ultra-Low). **What is the fastest route from Hong Kong?** The fastest measured route from Hong Kong (HKG) is [Hong Kong (HKG) → Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt), averaging **14.7 ms** RTT (Ultra-Low). **How well connected is Hong Kong to the Hats Network backbone?** Hong Kong (HKG) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Hong Kong (HKG) → Johannesburg (JNB)](/docs/network/latency/pairs/hkg-jnb-rtt), averages **316.7 ms** RTT. ## Open Data Measured latency data for Hong Kong (HKG) 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 Hong Kong is published as `hkg-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [hkg-tpe.pings.csv](/opendata/latency/latest/pairs/hkg-tpe.pings.csv), the 50-probe ICMP echo round for [Hong Kong (HKG) → Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-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/hkg-hong-kong). - **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. # 🇺🇸 Ashburn Ping & Network Latency (IAD) | AS203314 ## 🇺🇸 Ashburn (IAD) Ashburn, Virginia is the heart of "Data Center Alley" — the densest interconnection ecosystem on earth. Hats Network peers at multiple carrier hotels within the region. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Ashburn (IAD)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Ashburn, USA (North America) * **Region:** North America * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 4744870](https://www.geonames.org/4744870) — 39.04372, -77.48749 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** IAD1 * **Upstream transit:** HE / Telecom Italia / Comcast / GTT / Cogent > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇺🇸 Ashburn (IAD) → 🇺🇸 New York (NYC)](/docs/network/latency/pairs/iad-nyc-rtt) (**6 ms**) — Ultra-Low | | Slowest Route | [🇺🇸 Ashburn (IAD) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/iad-jnb-rtt) (**228.3 ms**) | | Average RTT | **115.0 ms** | | Average Jitter | **0.87 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **82.6%** | | Intra-Region Peers | 4 PoPs in North America | | 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 Ashburn sits on Hats Network's **North America** backbone. Measured round-trip times to its 4 intra-region peers range from **6 ms** (New York (NYC)) to **62.3 ms** (Seattle (SEA)). Ashburn anchors the US East Coast corridor — the 'Data Center Alley' concentration of carrier hotels and cloud on-ramps in Northern Virginia. ## Outbound Latency from Ashburn (IAD) Round-trip time in milliseconds **from Ashburn** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 New York (NYC) | **[6](/docs/network/latency/pairs/iad-nyc-rtt)** | 3.44 ms | 57.3% | 0.12 ms | 0.17% | Ultra-Low | | 🇺🇸 Miami (MIA) | **[27.4](/docs/network/latency/pairs/iad-mia-rtt)** | 14.62 ms | 53.4% | 0.15 ms | 0% | Ultra-Low | | 🇺🇸 Los Angeles (LAX) | **[60.7](/docs/network/latency/pairs/iad-lax-rtt)** | 35.84 ms | 59% | 0.32 ms | 0% | Excellent | | 🇺🇸 Seattle (SEA) | **[62.3](/docs/network/latency/pairs/iad-sea-rtt)** | 36.27 ms | 58.2% | 0.44 ms | 0.12% | Excellent | | 🇬🇧 London (LON) | **[70.3](/docs/network/latency/pairs/iad-lon-rtt)** | 58.1 ms | 82.6% | 0.81 ms | 0.19% | Excellent | | 🇳🇱 Amsterdam (AMS) | **[75.2](/docs/network/latency/pairs/iad-ams-rtt)** | 60.94 ms | 81% | 0.34 ms | 0.02% | Excellent | | 🇫🇷 Paris (PAR) | **[76.1](/docs/network/latency/pairs/iad-par-rtt)** | 60.73 ms | 79.8% | 0.7 ms | 0.03% | Excellent | | 🇩🇪 Frankfurt (FRA) | **[81.2](/docs/network/latency/pairs/iad-fra-rtt)** | 64.3 ms | 79.2% | 0.95 ms | 0.1% | Good | | 🇩🇪 Berlin (BER) | **[86.1](/docs/network/latency/pairs/iad-ber-rtt)** | 66.05 ms | 76.7% | 0.7 ms | 0% | Good | | 🇫🇷 Marseille (MRS) | **[86.5](/docs/network/latency/pairs/iad-mrs-rtt)** | 65.34 ms | 75.5% | 0.72 ms | 0% | Good | | 🇧🇷 São Paulo (GRU) | **[101.4](/docs/network/latency/pairs/iad-gru-rtt)** | 74.79 ms | 73.8% | 1.02 ms | 0% | Good | | 🇷🇺 Moscow (MOW) | **[112.8](/docs/network/latency/pairs/iad-mow-rtt)** | 76.88 ms | 68.2% | 0.79 ms | 0.13% | Good | | 🇯🇵 Tokyo (TYO) | **[141.9](/docs/network/latency/pairs/iad-tyo-rtt)** | 106.69 ms | 75.2% | 1.23 ms | 0.02% | Good | | 🇹🇼 Taipei (TPE) | **[172.3](/docs/network/latency/pairs/iad-tpe-rtt)** | 123.78 ms | 71.8% | 1.59 ms | 0.04% | Fair | | 🇭🇰 Hong Kong (HKG) | **[187.2](/docs/network/latency/pairs/iad-hkg-rtt)** | 128.37 ms | 68.6% | 1 ms | 0.05% | Fair | | 🇦🇺 Sydney (SYD) | **[193.6](/docs/network/latency/pairs/iad-syd-rtt)** | 153.48 ms | 79.3% | 1.68 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[203.9](/docs/network/latency/pairs/iad-mel-rtt)** | 160.09 ms | 78.5% | 1.06 ms | 0.15% | Fair | | 🇸🇬 Singapore (SIN) | **[211.5](/docs/network/latency/pairs/iad-sin-rtt)** | 152.14 ms | 71.9% | 1.77 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[228.3](/docs/network/latency/pairs/iad-jnb-rtt)** | 128.11 ms | 56.1% | 1.05 ms | 0.04% | Fair | ## Fastest Routes to Ashburn (IAD) The 10 fastest measured routes **to Ashburn**, 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 | 🇺🇸 New York (NYC) | **[6 ms](/docs/network/latency/pairs/nyc-iad-rtt)** | 5.58 ms | 7.18 ms | 0.3 ms | | 2 | 🇺🇸 Miami (MIA) | **[27.3 ms](/docs/network/latency/pairs/mia-iad-rtt)** | 26.26 ms | 30.45 ms | 1.02 ms | | 3 | 🇺🇸 Los Angeles (LAX) | **[60.4 ms](/docs/network/latency/pairs/lax-iad-rtt)** | 57.19 ms | 70.55 ms | 2.61 ms | | 4 | 🇺🇸 Seattle (SEA) | **[61.5 ms](/docs/network/latency/pairs/sea-iad-rtt)** | 57.92 ms | 70.85 ms | 2.96 ms | | 5 | 🇬🇧 London (LON) | **[71 ms](/docs/network/latency/pairs/lon-iad-rtt)** | 68.31 ms | 80.67 ms | 2.3 ms | | 6 | 🇫🇷 Paris (PAR) | **[75.5 ms](/docs/network/latency/pairs/par-iad-rtt)** | 72.75 ms | 85.2 ms | 2.46 ms | | 7 | 🇳🇱 Amsterdam (AMS) | **[75.7 ms](/docs/network/latency/pairs/ams-iad-rtt)** | 72.76 ms | 82.67 ms | 2.28 ms | | 8 | 🇩🇪 Frankfurt (FRA) | **[80.7 ms](/docs/network/latency/pairs/fra-iad-rtt)** | 79.19 ms | 87.49 ms | 1.42 ms | | 9 | 🇩🇪 Berlin (BER) | **[85.7 ms](/docs/network/latency/pairs/ber-iad-rtt)** | 83.7 ms | 92.94 ms | 2.12 ms | | 10 | 🇫🇷 Marseille (MRS) | **[85.7 ms](/docs/network/latency/pairs/mrs-iad-rtt)** | 82.1 ms | 94.47 ms | 2.63 ms | ## Inbound Latency to Ashburn (IAD) Round-trip time in milliseconds **from all other PoPs to Ashburn**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 New York (NYC) | **[6](/docs/network/latency/pairs/nyc-iad-rtt)** | 3.44 ms | 57.3% | 0.12 ms | 0.01% | Ultra-Low | | 🇺🇸 Miami (MIA) | **[27.3](/docs/network/latency/pairs/mia-iad-rtt)** | 14.62 ms | 53.6% | 0.15 ms | 0% | Ultra-Low | | 🇺🇸 Los Angeles (LAX) | **[60.4](/docs/network/latency/pairs/lax-iad-rtt)** | 35.84 ms | 59.3% | 0.64 ms | 0.06% | Excellent | | 🇺🇸 Seattle (SEA) | **[61.5](/docs/network/latency/pairs/sea-iad-rtt)** | 36.27 ms | 59% | 0.55 ms | 0% | Excellent | | 🇬🇧 London (LON) | **[71](/docs/network/latency/pairs/lon-iad-rtt)** | 58.1 ms | 81.8% | 0.52 ms | 0.13% | Excellent | | 🇫🇷 Paris (PAR) | **[75.5](/docs/network/latency/pairs/par-iad-rtt)** | 60.73 ms | 80.4% | 0.86 ms | 0.02% | Excellent | | 🇳🇱 Amsterdam (AMS) | **[75.7](/docs/network/latency/pairs/ams-iad-rtt)** | 60.94 ms | 80.5% | 0.75 ms | 0.05% | Excellent | | 🇩🇪 Frankfurt (FRA) | **[80.7](/docs/network/latency/pairs/fra-iad-rtt)** | 64.3 ms | 79.7% | 0.91 ms | 0.04% | Good | | 🇩🇪 Berlin (BER) | **[85.7](/docs/network/latency/pairs/ber-iad-rtt)** | 66.05 ms | 77.1% | 0.79 ms | 0% | Good | | 🇫🇷 Marseille (MRS) | **[85.7](/docs/network/latency/pairs/mrs-iad-rtt)** | 65.34 ms | 76.2% | 0.46 ms | 0.05% | Good | | 🇷🇺 Moscow (MOW) | **[113.9](/docs/network/latency/pairs/mow-iad-rtt)** | 76.88 ms | 67.5% | 1 ms | 0.08% | Good | | 🇧🇷 São Paulo (GRU) | **[128](/docs/network/latency/pairs/gru-iad-rtt)** | 74.79 ms | 58.4% | 0.6 ms | 0.09% | Good | | 🇯🇵 Tokyo (TYO) | **[142.9](/docs/network/latency/pairs/tyo-iad-rtt)** | 106.69 ms | 74.7% | 0.69 ms | 0% | Good | | 🇹🇼 Taipei (TPE) | **[171.6](/docs/network/latency/pairs/tpe-iad-rtt)** | 123.78 ms | 72.1% | 1.7 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[186.2](/docs/network/latency/pairs/hkg-iad-rtt)** | 128.37 ms | 68.9% | 1.54 ms | 0.04% | Fair | | 🇦🇺 Sydney (SYD) | **[195.3](/docs/network/latency/pairs/syd-iad-rtt)** | 153.48 ms | 78.6% | 1.26 ms | 0.15% | Fair | | 🇦🇺 Melbourne (MEL) | **[203.9](/docs/network/latency/pairs/mel-iad-rtt)** | 160.09 ms | 78.5% | 2.45 ms | 0.02% | Fair | | 🇸🇬 Singapore (SIN) | **[210](/docs/network/latency/pairs/sin-iad-rtt)** | 152.14 ms | 72.4% | 2.32 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[229](/docs/network/latency/pairs/jnb-iad-rtt)** | 128.11 ms | 55.9% | 1.29 ms | 0% | Fair | ## North America Peers Ashburn is one of 5 Hats Network PoPs in **North America**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | ------------------------------------------- | ---- | ------- | -------- | --------- | | [🇺🇸 Los Angeles (LAX)](./lax-los-angeles) | LAX | USA | **60.7** | Excellent | | [🇺🇸 Miami (MIA)](./mia-miami) | MIA | USA | **27.4** | Ultra-Low | | [🇺🇸 New York (NYC)](./nyc-new-york) | NYC | USA | **6** | Ultra-Low | | [🇺🇸 Seattle (SEA)](./sea-seattle) | SEA | USA | **62.3** | Excellent | ## Frequently Asked Questions **What is the fastest route to Ashburn?** The fastest measured route to Ashburn (IAD) is [New York (NYC) → Ashburn (IAD)](/docs/network/latency/pairs/nyc-iad-rtt), averaging **6 ms** RTT (Ultra-Low). **What is the fastest route from Ashburn?** The fastest measured route from Ashburn (IAD) is [Ashburn (IAD) → New York (NYC)](/docs/network/latency/pairs/iad-nyc-rtt), averaging **6 ms** RTT (Ultra-Low). **How well connected is Ashburn to the Hats Network backbone?** Ashburn (IAD) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Ashburn (IAD) → Johannesburg (JNB)](/docs/network/latency/pairs/iad-jnb-rtt), averages **228.3 ms** RTT. ## Open Data Measured latency data for Ashburn (IAD) 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 Ashburn is published as `iad-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [iad-nyc.pings.csv](/opendata/latency/latest/pairs/iad-nyc.pings.csv), the 50-probe ICMP echo round for [Ashburn (IAD) → New York (NYC)](/docs/network/latency/pairs/iad-nyc-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/iad-ashburn). - **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. # Global Ping & RTT Latency Matrix | AS203314 > **Auto-Generated Data** > > This page is automatically regenerated daily. Last updated: **August 16, 2026**. Data is sourced > from our internal measurements across all backbone PoPs. See [Methodology & Data > Sources](#methodology--data-sources) for details and limitations. Measurement round: `2026-08-16T04:07:28Z`. ## Overview This page publishes a global **round-trip time (RTT)** matrix (milliseconds) between Hats Network (AS203314) backbone PoPs. Use it to compare inter-city latency tiers and identify the best-case paths between regions. ### Key facts (for citations) * **Nodes:** 20 * **Directed routes:** 380 / 380 (100.0% coverage) > **Important:** RTT is *not* one-way latency. Values represent backbone PoP-to-PoP paths, not last-mile end-user performance. ## Methodology & Data Sources ### Data sources We aggregate latency data from our internal measurements (Update Frequency: daily). For every city pair, we also calculate WGS-84 distance, vacuum and silica propagation floors, attenuation-driven optical span counts, and measured-to-physical efficiency. Review the [coordinate and model inputs](/docs/network/latency/theoretical-fiber-latency), then reproduce the calculation on the [formula verification page](/docs/network/latency/theoretical-latency-verification). ### Limitations * This dataset is **not an SLA** and should be treated as *indicative best-case backbone RTT*. * End-user latency depends on local access networks, congestion, routing policy, and traffic engineering. > Interactive content is available on the canonical HTML page. ## Full RTT Matrix Round-trip times in milliseconds (RTT). Rows = source, columns = destination. Color-coded by latency tier; **bold** = column minimum (best-case for that destination). An accessible, print-friendly static view of the same data is available below. > Interactive content is available on the canonical HTML page. View raw RTT table (accessible / printable) | Source | AMS | BER | FRA | LON | MRS | MOW | PAR | IAD | LAX | MIA | NYC | SEA | GRU | HKG | MEL | SIN | SYD | TPE | TYO | JNB | | ------- | ------- | ------- | ------- | ------- | ------- | -------- | ------- | ----- | -------- | -------- | ----- | -------- | --------- | -------- | ------- | -------- | ------- | -------- | -------- | --------- | | **AMS** | — | 7.2 | **5.9** | **5.2** | 19.6 | 38.1 | 7 | 75.7 | 133.7 | 106 | 68.6 | 130.2 | 175.5 | 155.9 | 252.5 | 157.6 | 258 | 168.7 | 198.2 | **171.9** | | **BER** | 7.2 | — | 6.1 | 15.2 | 20.2 | **28.6** | 15.6 | 85.7 | 140.9 | 118.3 | 79.6 | 139.7 | 186.5 | 144.9 | 256.2 | 158.3 | 262.1 | 156.8 | 187.5 | 172.1 | | **FRA** | 5.9 | **6.1** | — | 12.9 | 16.4 | 34.7 | 7.6 | 80.7 | 141.8 | 112 | 74.4 | 135.2 | 181.3 | 152 | 250.1 | 151.4 | 256 | 163.8 | 194.5 | 188.4 | | **LON** | **5.2** | 16.2 | 13.6 | — | 17.9 | 43.5 | **6.4** | 71 | 127.5 | 101.9 | 63.8 | 123.2 | 170.7 | 160.6 | 249.6 | 156.5 | 258.1 | 173.8 | 202.9 | 179.6 | | **MRS** | 20.3 | 20.6 | 16 | 18.9 | — | 49.6 | 8.9 | 85.7 | 144.5 | 112.4 | 79.8 | 141.7 | 186.7 | 166.4 | 234.2 | 139.6 | 240.6 | 180.9 | 203.8 | 198.5 | | **MOW** | 37.6 | 27.5 | 35.9 | 42.4 | 49.9 | — | 44 | 113.9 | 177.7 | 144.5 | 107.5 | 164.8 | 214.4 | 118.6 | 235.9 | 147.3 | 241.8 | 132.1 | 162.2 | 201.9 | | **PAR** | 7 | 15.5 | 7.6 | 6.4 | **8.9** | 44.7 | — | 75.5 | 136.5 | 106.8 | 68.9 | 128 | 175.8 | 160.1 | 246.4 | 150.3 | 249.7 | 171.9 | 204.7 | 180.9 | | **IAD** | 75.2 | 86.1 | 81.2 | 70.3 | 86.5 | 112.8 | 76.1 | — | 60.7 | **27.4** | **6** | 62.3 | **101.4** | 187.2 | 203.9 | 211.5 | 193.6 | 172.3 | 141.9 | 228.3 | | **LAX** | 132.1 | 139.3 | 142.3 | 129.2 | 143.9 | 177 | 135.9 | 60.4 | — | 57.3 | 57.9 | **26.9** | 131.3 | 146.5 | 148.2 | 167.7 | 137.6 | 132.9 | 101.2 | 287.2 | | **MIA** | 106 | 117.3 | 112.2 | 101.8 | 113.7 | 145.5 | 106.2 | 27.3 | 56.8 | — | 33.3 | 81.9 | 128.7 | 199.5 | 200.7 | 223.1 | 191.5 | 185.1 | 156.3 | 259.8 | | **NYC** | 68.7 | 78.8 | 73.9 | 63.5 | 80.2 | 107 | 68.9 | **6** | 58.9 | 32.9 | — | 58.7 | 106.9 | 187.1 | 205.1 | 208.7 | 192.6 | 173.4 | 143.1 | 221.5 | | **SEA** | 128.6 | 140.9 | 133.2 | 124.1 | 141.2 | 164.6 | 129.2 | 61.5 | **25.9** | 81.7 | 59.5 | — | 155.7 | 130.4 | 170.1 | 151.1 | 161.3 | 114.7 | 85 | 282.1 | | **GRU** | 180 | 191.3 | 186.2 | 175.8 | 187.7 | 219.5 | 180.2 | 128 | 130.8 | 74 | 122 | 155.9 | — | 273.5 | 274.7 | 297.1 | 265.5 | 259.1 | 230.3 | 333.8 | | **HKG** | 154.4 | 145.1 | 150.7 | 158.7 | 165.4 | 118.2 | 159.4 | 186.2 | 145 | 201.1 | 184.7 | 131.6 | 287.6 | — | 138.4 | **31.5** | 137.2 | **14.7** | 44.9 | 316.7 | | **MEL** | 252.8 | 254.7 | 248.6 | 252 | 233.5 | 236.1 | 246.5 | 203.9 | 148.4 | 201 | 204.2 | 172.1 | 305.3 | 138.5 | — | 88.4 | **9.8** | 143.2 | 112 | 405.5 | | **SIN** | 155.8 | 160.3 | 151.6 | 155.4 | 140.6 | 147.7 | 151.4 | 210 | 168.2 | 221.7 | 209.3 | 151.5 | 311.4 | 30.8 | 88.6 | — | 94.5 | 45.8 | 68.9 | 312.6 | | **SYD** | 258.9 | 260.5 | 254.4 | 256.5 | 240.5 | 242.2 | 250.3 | 195.3 | 136.5 | 191.5 | 191.9 | 161.9 | 296.7 | 135.7 | **9.8** | 94.5 | — | 131.7 | 101.3 | 412.5 | | **TPE** | 166.5 | 158.6 | 166 | 173 | 179.5 | 132.7 | 173.8 | 171.6 | 132 | 185.7 | 174.2 | 115.8 | 273 | **15.5** | 142 | 44.3 | 133.2 | — | **31.9** | 331 | | **TYO** | 197.4 | 186.1 | 193.2 | 202.7 | 205.6 | 161.7 | 204.8 | 142.9 | 101.2 | 156.5 | 144.6 | 84.8 | 230.5 | 44.8 | 113.9 | 69.4 | 101.9 | 32.3 | — | 359.2 | | **JNB** | 163.2 | 172.1 | 166 | 158 | 172 | 200.7 | 164.4 | 229 | 285.5 | 259.9 | 221.8 | 281.2 | 328.7 | 318 | 406.2 | 311.6 | 412.6 | 329.8 | 360.5 | — | ## Regional Breakdown ### Europe #### Intra-Region Routes | Route | RTT (ms) | | --------------------------------- | -------- | | Amsterdam (AMS) ↔ London (LON) | 5.2 | | Amsterdam (AMS) ↔ Frankfurt (FRA) | 5.9 | | Berlin (BER) ↔ Frankfurt (FRA) | 6.1 | | London (LON) ↔ Paris (PAR) | 6.4 | | Amsterdam (AMS) ↔ Paris (PAR) | 7 | | Amsterdam (AMS) ↔ Berlin (BER) | 7.2 | | Frankfurt (FRA) ↔ Paris (PAR) | 7.6 | | Marseille (MRS) ↔ Paris (PAR) | 8.9 | | Frankfurt (FRA) ↔ London (LON) | 12.9 | | Berlin (BER) ↔ London (LON) | 15.2 | | Berlin (BER) ↔ Paris (PAR) | 15.6 | | Frankfurt (FRA) ↔ Marseille (MRS) | 16.4 | | London (LON) ↔ Marseille (MRS) | 17.9 | | Amsterdam (AMS) ↔ Marseille (MRS) | 19.6 | | Berlin (BER) ↔ Marseille (MRS) | 20.2 | | Berlin (BER) ↔ Moscow (MOW) | 28.6 | | Frankfurt (FRA) ↔ Moscow (MOW) | 34.7 | | Amsterdam (AMS) ↔ Moscow (MOW) | 38.1 | | London (LON) ↔ Moscow (MOW) | 43.5 | | Moscow (MOW) ↔ Paris (PAR) | 44 | | Marseille (MRS) ↔ Moscow (MOW) | 49.6 | #### Key Cross-Region Routes | Route | RTT (ms) | Far Region | | -------------------------------- | -------- | ------------- | | London (LON) ↔ New York (NYC) | 63.8 | North America | | Amsterdam (AMS) ↔ New York (NYC) | 68.6 | North America | | Paris (PAR) ↔ New York (NYC) | 68.9 | North America | | London (LON) ↔ Ashburn (IAD) | 71 | North America | | Frankfurt (FRA) ↔ New York (NYC) | 74.4 | North America | | Paris (PAR) ↔ Ashburn (IAD) | 75.5 | North America | | Amsterdam (AMS) ↔ Ashburn (IAD) | 75.7 | North America | | Berlin (BER) ↔ New York (NYC) | 79.6 | North America | ### North America #### Intra-Region Routes | Route | RTT (ms) | | ---------------------------------- | -------- | | Ashburn (IAD) ↔ New York (NYC) | 6 | | Los Angeles (LAX) ↔ Seattle (SEA) | 26.9 | | Ashburn (IAD) ↔ Miami (MIA) | 27.4 | | Miami (MIA) ↔ New York (NYC) | 33.3 | | Los Angeles (LAX) ↔ Miami (MIA) | 57.3 | | Los Angeles (LAX) ↔ New York (NYC) | 57.9 | | New York (NYC) ↔ Seattle (SEA) | 58.7 | | Ashburn (IAD) ↔ Los Angeles (LAX) | 60.7 | | Ashburn (IAD) ↔ Seattle (SEA) | 62.3 | | Miami (MIA) ↔ Seattle (SEA) | 81.9 | #### Key Cross-Region Routes | Route | RTT (ms) | Far Region | | -------------------------------- | -------- | ---------- | | New York (NYC) ↔ London (LON) | 63.5 | Europe | | New York (NYC) ↔ Amsterdam (AMS) | 68.7 | Europe | | New York (NYC) ↔ Paris (PAR) | 68.9 | Europe | | Ashburn (IAD) ↔ London (LON) | 70.3 | Europe | | New York (NYC) ↔ Frankfurt (FRA) | 73.9 | Europe | | Ashburn (IAD) ↔ Amsterdam (AMS) | 75.2 | Europe | | Ashburn (IAD) ↔ Paris (PAR) | 76.1 | Europe | | New York (NYC) ↔ Berlin (BER) | 78.8 | Europe | ### South America #### Key Cross-Region Routes | Route | RTT (ms) | Far Region | | ----------------------------------- | -------- | ------------- | | São Paulo (GRU) ↔ Miami (MIA) | 74 | North America | | São Paulo (GRU) ↔ New York (NYC) | 122 | North America | | São Paulo (GRU) ↔ Ashburn (IAD) | 128 | North America | | São Paulo (GRU) ↔ Los Angeles (LAX) | 130.8 | North America | | São Paulo (GRU) ↔ Seattle (SEA) | 155.9 | North America | | São Paulo (GRU) ↔ London (LON) | 175.8 | Europe | | São Paulo (GRU) ↔ Amsterdam (AMS) | 180 | Europe | | São Paulo (GRU) ↔ Paris (PAR) | 180.2 | Europe | ### Asia Pacific #### Intra-Region Routes | Route | RTT (ms) | | --------------------------------- | -------- | | Melbourne (MEL) ↔ Sydney (SYD) | 9.8 | | Hong Kong (HKG) ↔ Taipei (TPE) | 14.7 | | Hong Kong (HKG) ↔ Singapore (SIN) | 31.5 | | Taipei (TPE) ↔ Tokyo (TYO) | 31.9 | | Hong Kong (HKG) ↔ Tokyo (TYO) | 44.9 | | Singapore (SIN) ↔ Taipei (TPE) | 45.8 | | Singapore (SIN) ↔ Tokyo (TYO) | 68.9 | | Melbourne (MEL) ↔ Singapore (SIN) | 88.4 | | Singapore (SIN) ↔ Sydney (SYD) | 94.5 | | Sydney (SYD) ↔ Tokyo (TYO) | 101.3 | | Melbourne (MEL) ↔ Tokyo (TYO) | 112 | | Sydney (SYD) ↔ Taipei (TPE) | 131.7 | | Hong Kong (HKG) ↔ Sydney (SYD) | 137.2 | | Hong Kong (HKG) ↔ Melbourne (MEL) | 138.4 | | Melbourne (MEL) ↔ Taipei (TPE) | 143.2 | #### Key Cross-Region Routes | Route | RTT (ms) | Far Region | | -------------------------------- | -------- | ------------- | | Tokyo (TYO) ↔ Seattle (SEA) | 84.8 | North America | | Tokyo (TYO) ↔ Los Angeles (LAX) | 101.2 | North America | | Taipei (TPE) ↔ Seattle (SEA) | 115.8 | North America | | Hong Kong (HKG) ↔ Moscow (MOW) | 118.2 | Europe | | Hong Kong (HKG) ↔ Seattle (SEA) | 131.6 | North America | | Taipei (TPE) ↔ Los Angeles (LAX) | 132 | North America | | Taipei (TPE) ↔ Moscow (MOW) | 132.7 | Europe | | Sydney (SYD) ↔ Los Angeles (LAX) | 136.5 | North America | ### Africa #### Key Cross-Region Routes | Route | RTT (ms) | Far Region | | ------------------------------------ | -------- | ------------- | | Johannesburg (JNB) ↔ London (LON) | 158 | Europe | | Johannesburg (JNB) ↔ Amsterdam (AMS) | 163.2 | Europe | | Johannesburg (JNB) ↔ Paris (PAR) | 164.4 | Europe | | Johannesburg (JNB) ↔ Frankfurt (FRA) | 166 | Europe | | Johannesburg (JNB) ↔ Marseille (MRS) | 172 | Europe | | Johannesburg (JNB) ↔ Berlin (BER) | 172.1 | Europe | | Johannesburg (JNB) ↔ Moscow (MOW) | 200.7 | Europe | | Johannesburg (JNB) ↔ New York (NYC) | 221.8 | North America | ## Node Reference | Code | City | Country/Region | Continent | | ------- | ---------------------------------- | -------------- | ------------- | | **AMS** | [Amsterdam](./ams-amsterdam) | Netherlands | Europe | | **BER** | [Berlin](./ber-berlin) | Germany | Europe | | **FRA** | [Frankfurt](./fra-frankfurt) | Germany | Europe | | **LON** | [London](./lon-london) | UK | Europe | | **MRS** | [Marseille](./mrs-marseille) | France | Europe | | **MOW** | [Moscow](./mow-moscow) | Russia | Europe | | **PAR** | [Paris](./par-paris) | France | Europe | | **IAD** | [Ashburn](./iad-ashburn) | USA | North America | | **LAX** | [Los Angeles](./lax-los-angeles) | USA | North America | | **MIA** | [Miami](./mia-miami) | USA | North America | | **NYC** | [New York](./nyc-new-york) | USA | North America | | **SEA** | [Seattle](./sea-seattle) | USA | North America | | **GRU** | [São Paulo](./gru-sao-paulo) | Brazil | South America | | **HKG** | [Hong Kong](./hkg-hong-kong) | Hong Kong | Asia Pacific | | **MEL** | [Melbourne](./mel-melbourne) | Australia | Asia Pacific | | **SIN** | [Singapore](./sin-singapore) | Singapore | Asia Pacific | | **SYD** | [Sydney](./syd-sydney) | Australia | Asia Pacific | | **TPE** | [Taipei](./tpe-taipei) | Taiwan | Asia Pacific | | **TYO** | [Tokyo](./tyo-tokyo) | Japan | Asia Pacific | | **JNB** | [Johannesburg](./jnb-johannesburg) | South Africa | Africa | ## Browse Latency Data * [Latency Coordinates & Fiber Model Inputs](./theoretical-fiber-latency) — GeoNames resolution, physical constants, engineering assumptions, and source boundaries * [Theoretical Latency Formula Verification](./theoretical-latency-verification) — rendered equations, unit checks, boundary conditions, and a complete Tokyo-to-Sydney reconciliation * [By PoP](#node-reference) — per-node outbound/inbound RTT summaries * [By City Pair](./pairs) — individual source-to-destination RTT pages * [By Region & Corridor](./regions) — regional and inter-regional overviews *** *Data automatically generated on August 16, 2026 from our infrastructure.* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency). - **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. # 🇿🇦 Johannesburg Ping & Network Latency (JNB) | AS203314 ## 🇿🇦 Johannesburg (JNB) Johannesburg anchors Hats Network's African footprint, connecting Southern Africa to the global backbone via the Europe–Africa corridors through London, Marseille and Frankfurt. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Johannesburg (JNB)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Johannesburg, South Africa (Africa) * **Region:** Africa * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 993800](https://www.geonames.org/993800) — -26.20227, 28.04363 * **Coverage:** RTT measurements to 19 other PoPs across 4 continents ### Facility & Interconnection * **Facility:** JNB1 * **Upstream transit:** HE Only > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇿🇦 Johannesburg (JNB) → 🇬🇧 London (LON)](/docs/network/latency/pairs/jnb-lon-rtt) (**158 ms**) — Fair | | Slowest Route | [🇿🇦 Johannesburg (JNB) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/jnb-syd-rtt) (**412.6 ms**) | | Average RTT | **260.1 ms** | | Average Jitter | **2.18 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **57.5%** | | Intra-Region Peers | 0 PoP in Africa | | 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 Johannesburg is Hats Network's only PoP in **Africa**. The nearest measured backbone PoP is London (LON) at **158 ms** RTT. Johannesburg is Hats Network's African anchor, connecting Southern Africa to Europe and Asia via the continent's coastal submarine landings. ## Outbound Latency from Johannesburg (JNB) Round-trip time in milliseconds **from Johannesburg** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ---------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | ---- | | 🇬🇧 London (LON) | **[158](/docs/network/latency/pairs/jnb-lon-rtt)** | 88.52 ms | 56% | 0.77 ms | 0.12% | Fair | | 🇳🇱 Amsterdam (AMS) | **[163.2](/docs/network/latency/pairs/jnb-ams-rtt)** | 88.05 ms | 54% | 1.84 ms | 0% | Fair | | 🇫🇷 Paris (PAR) | **[164.4](/docs/network/latency/pairs/jnb-par-rtt)** | 85.17 ms | 51.8% | 1.05 ms | 0% | Fair | | 🇩🇪 Frankfurt (FRA) | **[166](/docs/network/latency/pairs/jnb-fra-rtt)** | 84.87 ms | 51.1% | 1.86 ms | 0.11% | Fair | | 🇫🇷 Marseille (MRS) | **[172](/docs/network/latency/pairs/jnb-mrs-rtt)** | 78.71 ms | 45.8% | 1.53 ms | 0% | Fair | | 🇩🇪 Berlin (BER) | **[172.1](/docs/network/latency/pairs/jnb-ber-rtt)** | 86.53 ms | 50.3% | 1.75 ms | 0.11% | Fair | | 🇷🇺 Moscow (MOW) | **[200.7](/docs/network/latency/pairs/jnb-mow-rtt)** | 89.37 ms | 44.5% | 2.17 ms | 0.16% | Fair | | 🇺🇸 New York (NYC) | **[221.8](/docs/network/latency/pairs/jnb-nyc-rtt)** | 125.67 ms | 56.7% | 2.01 ms | 0% | Fair | | 🇺🇸 Ashburn (IAD) | **[229](/docs/network/latency/pairs/jnb-iad-rtt)** | 128.11 ms | 55.9% | 1.29 ms | 0% | Fair | | 🇺🇸 Miami (MIA) | **[259.9](/docs/network/latency/pairs/jnb-mia-rtt)** | 126.78 ms | 48.8% | 3.06 ms | 0.1% | High | | 🇺🇸 Seattle (SEA) | **[281.2](/docs/network/latency/pairs/jnb-sea-rtt)** | 161.61 ms | 57.5% | 1.91 ms | 0.11% | High | | 🇺🇸 Los Angeles (LAX) | **[285.5](/docs/network/latency/pairs/jnb-lax-rtt)** | 163.35 ms | 57.2% | 2.14 ms | 0.01% | High | | 🇸🇬 Singapore (SIN) | **[311.6](/docs/network/latency/pairs/jnb-sin-rtt)** | 84.85 ms | 27.2% | 3.35 ms | 0% | High | | 🇭🇰 Hong Kong (HKG) | **[318](/docs/network/latency/pairs/jnb-hkg-rtt)** | 104.93 ms | 33% | 3.32 ms | 0.19% | High | | 🇧🇷 São Paulo (GRU) | **[328.7](/docs/network/latency/pairs/jnb-gru-rtt)** | 72.88 ms | 22.2% | 2.32 ms | 0.06% | High | | 🇹🇼 Taipei (TPE) | **[329.8](/docs/network/latency/pairs/jnb-tpe-rtt)** | 112.87 ms | 34.2% | 3.33 ms | 0% | High | | 🇯🇵 Tokyo (TYO) | **[360.5](/docs/network/latency/pairs/jnb-tyo-rtt)** | 132.57 ms | 36.8% | 2.79 ms | 0.06% | High | | 🇦🇺 Melbourne (MEL) | **[406.2](/docs/network/latency/pairs/jnb-mel-rtt)** | 101.33 ms | 24.9% | 2.56 ms | 0% | High | | 🇦🇺 Sydney (SYD) | **[412.6](/docs/network/latency/pairs/jnb-syd-rtt)** | 108.32 ms | 26.3% | 2.3 ms | 0.07% | High | ## Fastest Routes to Johannesburg (JNB) The 10 fastest measured routes **to Johannesburg**, 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 | 🇳🇱 Amsterdam (AMS) | **[171.9 ms](/docs/network/latency/pairs/ams-jnb-rtt)** | 163.56 ms | 197.47 ms | 6.53 ms | | 2 | 🇩🇪 Berlin (BER) | **[172.1 ms](/docs/network/latency/pairs/ber-jnb-rtt)** | 163.72 ms | 199.65 ms | 7.34 ms | | 3 | 🇬🇧 London (LON) | **[179.6 ms](/docs/network/latency/pairs/lon-jnb-rtt)** | 171.6 ms | 203.66 ms | 5.96 ms | | 4 | 🇫🇷 Paris (PAR) | **[180.9 ms](/docs/network/latency/pairs/par-jnb-rtt)** | 176.39 ms | 195.6 ms | 3.41 ms | | 5 | 🇩🇪 Frankfurt (FRA) | **[188.4 ms](/docs/network/latency/pairs/fra-jnb-rtt)** | 182.33 ms | 218.93 ms | 6.75 ms | | 6 | 🇫🇷 Marseille (MRS) | **[198.5 ms](/docs/network/latency/pairs/mrs-jnb-rtt)** | 194.33 ms | 207.86 ms | 3.18 ms | | 7 | 🇷🇺 Moscow (MOW) | **[201.9 ms](/docs/network/latency/pairs/mow-jnb-rtt)** | 192.01 ms | 232.17 ms | 7.94 ms | | 8 | 🇺🇸 New York (NYC) | **[221.5 ms](/docs/network/latency/pairs/nyc-jnb-rtt)** | 209.09 ms | 252.44 ms | 9.18 ms | | 9 | 🇺🇸 Ashburn (IAD) | **[228.3 ms](/docs/network/latency/pairs/iad-jnb-rtt)** | 216.38 ms | 264.39 ms | 10.74 ms | | 10 | 🇺🇸 Miami (MIA) | **[259.8 ms](/docs/network/latency/pairs/mia-jnb-rtt)** | 252.44 ms | 277.9 ms | 6.11 ms | ## Inbound Latency to Johannesburg (JNB) Round-trip time in milliseconds **from all other PoPs to Johannesburg**. 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 | | ---------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | ---- | | 🇳🇱 Amsterdam (AMS) | **[171.9](/docs/network/latency/pairs/ams-jnb-rtt)** | 88.05 ms | 51.2% | 1.1 ms | 0.1% | Fair | | 🇩🇪 Berlin (BER) | **[172.1](/docs/network/latency/pairs/ber-jnb-rtt)** | 86.53 ms | 50.3% | 1.56 ms | 0% | Fair | | 🇬🇧 London (LON) | **[179.6](/docs/network/latency/pairs/lon-jnb-rtt)** | 88.52 ms | 49.3% | 0.86 ms | 0% | Fair | | 🇫🇷 Paris (PAR) | **[180.9](/docs/network/latency/pairs/par-jnb-rtt)** | 85.17 ms | 47.1% | 0.94 ms | 0.17% | Fair | | 🇩🇪 Frankfurt (FRA) | **[188.4](/docs/network/latency/pairs/fra-jnb-rtt)** | 84.87 ms | 45% | 1.61 ms | 0.1% | Fair | | 🇫🇷 Marseille (MRS) | **[198.5](/docs/network/latency/pairs/mrs-jnb-rtt)** | 78.71 ms | 39.7% | 1.78 ms | 0% | Fair | | 🇷🇺 Moscow (MOW) | **[201.9](/docs/network/latency/pairs/mow-jnb-rtt)** | 89.37 ms | 44.3% | 1.29 ms | 0% | Fair | | 🇺🇸 New York (NYC) | **[221.5](/docs/network/latency/pairs/nyc-jnb-rtt)** | 125.67 ms | 56.7% | 2.09 ms | 0% | Fair | | 🇺🇸 Ashburn (IAD) | **[228.3](/docs/network/latency/pairs/iad-jnb-rtt)** | 128.11 ms | 56.1% | 1.05 ms | 0.04% | Fair | | 🇺🇸 Miami (MIA) | **[259.8](/docs/network/latency/pairs/mia-jnb-rtt)** | 126.78 ms | 48.8% | 1.51 ms | 0.19% | High | | 🇺🇸 Seattle (SEA) | **[282.1](/docs/network/latency/pairs/sea-jnb-rtt)** | 161.61 ms | 57.3% | 1.53 ms | 0.15% | High | | 🇺🇸 Los Angeles (LAX) | **[287.2](/docs/network/latency/pairs/lax-jnb-rtt)** | 163.35 ms | 56.9% | 1.6 ms | 0.08% | High | | 🇸🇬 Singapore (SIN) | **[312.6](/docs/network/latency/pairs/sin-jnb-rtt)** | 84.85 ms | 27.1% | 1.51 ms | 0.19% | High | | 🇭🇰 Hong Kong (HKG) | **[316.7](/docs/network/latency/pairs/hkg-jnb-rtt)** | 104.93 ms | 33.1% | 3.12 ms | 0% | High | | 🇹🇼 Taipei (TPE) | **[331](/docs/network/latency/pairs/tpe-jnb-rtt)** | 112.87 ms | 34.1% | 1.92 ms | 0% | High | | 🇧🇷 São Paulo (GRU) | **[333.8](/docs/network/latency/pairs/gru-jnb-rtt)** | 72.88 ms | 21.8% | 3.1 ms | 0.07% | High | | 🇯🇵 Tokyo (TYO) | **[359.2](/docs/network/latency/pairs/tyo-jnb-rtt)** | 132.57 ms | 36.9% | 2.19 ms | 0.05% | High | | 🇦🇺 Melbourne (MEL) | **[405.5](/docs/network/latency/pairs/mel-jnb-rtt)** | 101.33 ms | 25% | 3.75 ms | 0.06% | High | | 🇦🇺 Sydney (SYD) | **[412.5](/docs/network/latency/pairs/syd-jnb-rtt)** | 108.32 ms | 26.3% | 3.8 ms | 0% | High | ## Frequently Asked Questions **What is the fastest route to Johannesburg?** The fastest measured route to Johannesburg (JNB) is [Amsterdam (AMS) → Johannesburg (JNB)](/docs/network/latency/pairs/ams-jnb-rtt), averaging **171.9 ms** RTT (Fair). **What is the fastest route from Johannesburg?** The fastest measured route from Johannesburg (JNB) is [Johannesburg (JNB) → London (LON)](/docs/network/latency/pairs/jnb-lon-rtt), averaging **158 ms** RTT (Fair). **How well connected is Johannesburg to the Hats Network backbone?** Johannesburg (JNB) maintains measured routes to all 19 other PoPs across 4 continents. The slowest route, [Johannesburg (JNB) → Sydney (SYD)](/docs/network/latency/pairs/jnb-syd-rtt), averages **412.6 ms** RTT. ## Open Data Measured latency data for Johannesburg (JNB) 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 Johannesburg is published as `jnb-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [jnb-lon.pings.csv](/opendata/latency/latest/pairs/jnb-lon.pings.csv), the 50-probe ICMP echo round for [Johannesburg (JNB) → London (LON)](/docs/network/latency/pairs/jnb-lon-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/jnb-johannesburg). - **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. # 🇺🇸 Los Angeles Ping & Network Latency (LAX) | AS203314 ## 🇺🇸 Los Angeles (LAX) Los Angeles is the primary US West Coast gateway to the Asia-Pacific region, landing major trans-Pacific submarine cables. Hats Network's LA PoP provides the lowest-latency path to East Asia. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Los Angeles (LAX)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Los Angeles, USA (North America) * **Region:** North America * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 5368361](https://www.geonames.org/5368361) — 34.05223, -118.24368 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** LAX1 * **Upstream transit:** HE / Cogent / Comcast > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇺🇸 Los Angeles (LAX) → 🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/lax-sea-rtt) (**26.9 ms**) — Ultra-Low | | Slowest Route | [🇺🇸 Los Angeles (LAX) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/lax-jnb-rtt) (**287.2 ms**) | | Average RTT | **129.2 ms** | | Average Jitter | **1.03 ms** | | Average Packet Loss | **0.04%** | | Best Fiber Efficiency | **85.9%** | | Intra-Region Peers | 4 PoPs in North America | | 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 Los Angeles sits on Hats Network's **North America** backbone. Measured round-trip times to its 4 intra-region peers range from **26.9 ms** (Seattle (SEA)) to **60.4 ms** (Ashburn (IAD)). Los Angeles is the primary US West Coast landing point for trans-Pacific submarine cables, giving the backbone its shortest Pacific crossing toward East Asia. ## Outbound Latency from Los Angeles (LAX) Round-trip time in milliseconds **from Los Angeles** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Seattle (SEA) | **[26.9](/docs/network/latency/pairs/lax-sea-rtt)** | 15.12 ms | 56.2% | 0.3 ms | 0.13% | Ultra-Low | | 🇺🇸 Miami (MIA) | **[57.3](/docs/network/latency/pairs/lax-mia-rtt)** | 36.86 ms | 64.3% | 0.34 ms | 0% | Excellent | | 🇺🇸 New York (NYC) | **[57.9](/docs/network/latency/pairs/lax-nyc-rtt)** | 38.63 ms | 66.7% | 0.34 ms | 0.09% | Excellent | | 🇺🇸 Ashburn (IAD) | **[60.4](/docs/network/latency/pairs/lax-iad-rtt)** | 35.84 ms | 59.3% | 0.64 ms | 0.06% | Excellent | | 🇯🇵 Tokyo (TYO) | **[101.2](/docs/network/latency/pairs/lax-tyo-rtt)** | 86.51 ms | 85.5% | 0.82 ms | 0% | Good | | 🇬🇧 London (LON) | **[129.2](/docs/network/latency/pairs/lax-lon-rtt)** | 85.95 ms | 66.5% | 1.17 ms | 0% | Good | | 🇧🇷 São Paulo (GRU) | **[131.3](/docs/network/latency/pairs/lax-gru-rtt)** | 96.89 ms | 73.8% | 0.87 ms | 0% | Good | | 🇳🇱 Amsterdam (AMS) | **[132.1](/docs/network/latency/pairs/lax-ams-rtt)** | 87.74 ms | 66.4% | 0.78 ms | 0% | Good | | 🇹🇼 Taipei (TPE) | **[132.9](/docs/network/latency/pairs/lax-tpe-rtt)** | 107 ms | 80.5% | 0.87 ms | 0.08% | Good | | 🇫🇷 Paris (PAR) | **[135.9](/docs/network/latency/pairs/lax-par-rtt)** | 89.18 ms | 65.6% | 0.62 ms | 0% | Good | | 🇦🇺 Sydney (SYD) | **[137.6](/docs/network/latency/pairs/lax-syd-rtt)** | 118.13 ms | 85.9% | 1.65 ms | 0% | Good | | 🇩🇪 Berlin (BER) | **[139.3](/docs/network/latency/pairs/lax-ber-rtt)** | 91.39 ms | 65.6% | 1.58 ms | 0.12% | Good | | 🇩🇪 Frankfurt (FRA) | **[142.3](/docs/network/latency/pairs/lax-fra-rtt)** | 91.31 ms | 64.2% | 0.71 ms | 0% | Good | | 🇫🇷 Marseille (MRS) | **[143.9](/docs/network/latency/pairs/lax-mrs-rtt)** | 95.09 ms | 66.1% | 1.05 ms | 0.16% | Good | | 🇭🇰 Hong Kong (HKG) | **[146.5](/docs/network/latency/pairs/lax-hkg-rtt)** | 114.3 ms | 78% | 1.42 ms | 0% | Good | | 🇦🇺 Melbourne (MEL) | **[148.2](/docs/network/latency/pairs/lax-mel-rtt)** | 125 ms | 84.3% | 1.74 ms | 0.06% | Good | | 🇸🇬 Singapore (SIN) | **[167.7](/docs/network/latency/pairs/lax-sin-rtt)** | 138.43 ms | 82.5% | 1.33 ms | 0% | Fair | | 🇷🇺 Moscow (MOW) | **[177](/docs/network/latency/pairs/lax-mow-rtt)** | 95.9 ms | 54.2% | 1.7 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[287.2](/docs/network/latency/pairs/lax-jnb-rtt)** | 163.35 ms | 56.9% | 1.6 ms | 0.08% | High | ## Fastest Routes to Los Angeles (LAX) The 10 fastest measured routes **to Los Angeles**, 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 | 🇺🇸 Seattle (SEA) | **[25.9 ms](/docs/network/latency/pairs/sea-lax-rtt)** | 25.44 ms | 27.56 ms | 0.42 ms | | 2 | 🇺🇸 Miami (MIA) | **[56.8 ms](/docs/network/latency/pairs/mia-lax-rtt)** | 54.44 ms | 64.31 ms | 2.11 ms | | 3 | 🇺🇸 New York (NYC) | **[58.9 ms](/docs/network/latency/pairs/nyc-lax-rtt)** | 56.67 ms | 64.24 ms | 2.02 ms | | 4 | 🇺🇸 Ashburn (IAD) | **[60.7 ms](/docs/network/latency/pairs/iad-lax-rtt)** | 58.56 ms | 67.73 ms | 1.84 ms | | 5 | 🇯🇵 Tokyo (TYO) | **[101.2 ms](/docs/network/latency/pairs/tyo-lax-rtt)** | 98.89 ms | 105.47 ms | 1.62 ms | | 6 | 🇬🇧 London (LON) | **[127.5 ms](/docs/network/latency/pairs/lon-lax-rtt)** | 123.84 ms | 138.75 ms | 3.03 ms | | 7 | 🇧🇷 São Paulo (GRU) | **[130.8 ms](/docs/network/latency/pairs/gru-lax-rtt)** | 125.52 ms | 141.14 ms | 3.75 ms | | 8 | 🇹🇼 Taipei (TPE) | **[132 ms](/docs/network/latency/pairs/tpe-lax-rtt)** | 129.33 ms | 144.07 ms | 2.56 ms | | 9 | 🇳🇱 Amsterdam (AMS) | **[133.7 ms](/docs/network/latency/pairs/ams-lax-rtt)** | 130.58 ms | 141.4 ms | 2.49 ms | | 10 | 🇫🇷 Paris (PAR) | **[136.5 ms](/docs/network/latency/pairs/par-lax-rtt)** | 130.92 ms | 152.23 ms | 5.13 ms | ## Inbound Latency to Los Angeles (LAX) Round-trip time in milliseconds **from all other PoPs to Los Angeles**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Seattle (SEA) | **[25.9](/docs/network/latency/pairs/sea-lax-rtt)** | 15.12 ms | 58.4% | 0.24 ms | 0% | Ultra-Low | | 🇺🇸 Miami (MIA) | **[56.8](/docs/network/latency/pairs/mia-lax-rtt)** | 36.86 ms | 64.9% | 0.59 ms | 0% | Excellent | | 🇺🇸 New York (NYC) | **[58.9](/docs/network/latency/pairs/nyc-lax-rtt)** | 38.63 ms | 65.6% | 0.46 ms | 0% | Excellent | | 🇺🇸 Ashburn (IAD) | **[60.7](/docs/network/latency/pairs/iad-lax-rtt)** | 35.84 ms | 59% | 0.32 ms | 0% | Excellent | | 🇯🇵 Tokyo (TYO) | **[101.2](/docs/network/latency/pairs/tyo-lax-rtt)** | 86.51 ms | 85.5% | 0.97 ms | 0.02% | Good | | 🇬🇧 London (LON) | **[127.5](/docs/network/latency/pairs/lon-lax-rtt)** | 85.95 ms | 67.4% | 0.86 ms | 0.17% | Good | | 🇧🇷 São Paulo (GRU) | **[130.8](/docs/network/latency/pairs/gru-lax-rtt)** | 96.89 ms | 74.1% | 0.66 ms | 0% | Good | | 🇹🇼 Taipei (TPE) | **[132](/docs/network/latency/pairs/tpe-lax-rtt)** | 107 ms | 81.1% | 1.31 ms | 0% | Good | | 🇳🇱 Amsterdam (AMS) | **[133.7](/docs/network/latency/pairs/ams-lax-rtt)** | 87.74 ms | 65.6% | 0.65 ms | 0% | Good | | 🇫🇷 Paris (PAR) | **[136.5](/docs/network/latency/pairs/par-lax-rtt)** | 89.18 ms | 65.3% | 1.58 ms | 0.11% | Good | | 🇦🇺 Sydney (SYD) | **[136.5](/docs/network/latency/pairs/syd-lax-rtt)** | 118.13 ms | 86.5% | 1.54 ms | 0.12% | Good | | 🇩🇪 Berlin (BER) | **[140.9](/docs/network/latency/pairs/ber-lax-rtt)** | 91.39 ms | 64.9% | 1.62 ms | 0.1% | Good | | 🇩🇪 Frankfurt (FRA) | **[141.8](/docs/network/latency/pairs/fra-lax-rtt)** | 91.31 ms | 64.4% | 1.06 ms | 0% | Good | | 🇫🇷 Marseille (MRS) | **[144.5](/docs/network/latency/pairs/mrs-lax-rtt)** | 95.09 ms | 65.8% | 0.78 ms | 0% | Good | | 🇭🇰 Hong Kong (HKG) | **[145](/docs/network/latency/pairs/hkg-lax-rtt)** | 114.3 ms | 78.8% | 1.4 ms | 0.06% | Good | | 🇦🇺 Melbourne (MEL) | **[148.4](/docs/network/latency/pairs/mel-lax-rtt)** | 125 ms | 84.2% | 1.28 ms | 0.07% | Good | | 🇸🇬 Singapore (SIN) | **[168.2](/docs/network/latency/pairs/sin-lax-rtt)** | 138.43 ms | 82.3% | 1.78 ms | 0.03% | Fair | | 🇷🇺 Moscow (MOW) | **[177.7](/docs/network/latency/pairs/mow-lax-rtt)** | 95.9 ms | 54% | 1.55 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[285.5](/docs/network/latency/pairs/jnb-lax-rtt)** | 163.35 ms | 57.2% | 2.14 ms | 0.01% | High | ## North America Peers Los Angeles is one of 5 Hats Network PoPs in **North America**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | ------------------------------------- | ---- | ------- | -------- | --------- | | [🇺🇸 Ashburn (IAD)](./iad-ashburn) | IAD | USA | **60.4** | Excellent | | [🇺🇸 Miami (MIA)](./mia-miami) | MIA | USA | **57.3** | Excellent | | [🇺🇸 New York (NYC)](./nyc-new-york) | NYC | USA | **57.9** | Excellent | | [🇺🇸 Seattle (SEA)](./sea-seattle) | SEA | USA | **26.9** | Ultra-Low | ## Frequently Asked Questions **What is the fastest route to Los Angeles?** The fastest measured route to Los Angeles (LAX) is [Seattle (SEA) → Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-rtt), averaging **25.9 ms** RTT (Ultra-Low). **What is the fastest route from Los Angeles?** The fastest measured route from Los Angeles (LAX) is [Los Angeles (LAX) → Seattle (SEA)](/docs/network/latency/pairs/lax-sea-rtt), averaging **26.9 ms** RTT (Ultra-Low). **How well connected is Los Angeles to the Hats Network backbone?** Los Angeles (LAX) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Los Angeles (LAX) → Johannesburg (JNB)](/docs/network/latency/pairs/lax-jnb-rtt), averages **287.2 ms** RTT. ## Open Data Measured latency data for Los Angeles (LAX) 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 Los Angeles is published as `lax-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [lax-sea.pings.csv](/opendata/latency/latest/pairs/lax-sea.pings.csv), the 50-probe ICMP echo round for [Los Angeles (LAX) → Seattle (SEA)](/docs/network/latency/pairs/lax-sea-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/lax-los-angeles). - **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. # 🇬🇧 London Ping & Network Latency (LON) | AS203314 ## 🇬🇧 London (LON) London is Europe's transatlantic gateway, connecting European networks to North America. Hats Network's London PoP provides low-latency paths to both continents. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **London (LON)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** London, UK (Europe) * **Region:** Europe * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 2643743](https://www.geonames.org/2643743) — 51.50853, -0.12574 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** LON1 * **Upstream transit:** HE / Cogent / LINX * **Peering / IX:** LINX / DE-CIX London > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ------------------------------------------------------------------------------------------------------------ | | Fastest Route | [🇬🇧 London (LON) → 🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-rtt) (**5.2 ms**) — Ultra-Low | | Slowest Route | [🇬🇧 London (LON) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/lon-syd-rtt) (**258.1 ms**) | | Average RTT | **112.7 ms** | | Average Jitter | **0.83 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **85.7%** | | Intra-Region Peers | 6 PoPs in Europe | | 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 London sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **5.2 ms** (Amsterdam (AMS)) to **43.5 ms** (Moscow (MOW)). London is the western anchor of the Northwest European corridor and Europe's traditional transatlantic gateway. ## Outbound Latency from London (LON) Round-trip time in milliseconds **from London** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇳🇱 Amsterdam (AMS) | **[5.2](/docs/network/latency/pairs/lon-ams-rtt)** | 3.51 ms | 67.4% | 0.12 ms | 0% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[6.4](/docs/network/latency/pairs/lon-par-rtt)** | 3.37 ms | 52.7% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[13.6](/docs/network/latency/pairs/lon-fra-rtt)** | 6.26 ms | 46.1% | 0.12 ms | 0.03% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[16.2](/docs/network/latency/pairs/lon-ber-rtt)** | 9.15 ms | 56.5% | 0.12 ms | 0.02% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[17.9](/docs/network/latency/pairs/lon-mrs-rtt)** | 9.82 ms | 54.8% | 0.16 ms | 0.14% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[43.5](/docs/network/latency/pairs/lon-mow-rtt)** | 24.56 ms | 56.5% | 0.2 ms | 0.06% | Excellent | | 🇺🇸 New York (NYC) | **[63.8](/docs/network/latency/pairs/lon-nyc-rtt)** | 54.69 ms | 85.7% | 0.42 ms | 0.12% | Excellent | | 🇺🇸 Ashburn (IAD) | **[71](/docs/network/latency/pairs/lon-iad-rtt)** | 58.1 ms | 81.8% | 0.52 ms | 0.13% | Excellent | | 🇺🇸 Miami (MIA) | **[101.9](/docs/network/latency/pairs/lon-mia-rtt)** | 69.9 ms | 68.6% | 0.83 ms | 0.1% | Good | | 🇺🇸 Seattle (SEA) | **[123.2](/docs/network/latency/pairs/lon-sea-rtt)** | 75.63 ms | 61.4% | 0.95 ms | 0% | Good | | 🇺🇸 Los Angeles (LAX) | **[127.5](/docs/network/latency/pairs/lon-lax-rtt)** | 85.95 ms | 67.4% | 0.86 ms | 0.17% | Good | | 🇸🇬 Singapore (SIN) | **[156.5](/docs/network/latency/pairs/lon-sin-rtt)** | 106.35 ms | 68% | 1.57 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[160.6](/docs/network/latency/pairs/lon-hkg-rtt)** | 94.44 ms | 58.8% | 0.84 ms | 0.07% | Fair | | 🇧🇷 São Paulo (GRU) | **[170.7](/docs/network/latency/pairs/lon-gru-rtt)** | 92.76 ms | 54.3% | 1.06 ms | 0.02% | Fair | | 🇹🇼 Taipei (TPE) | **[173.8](/docs/network/latency/pairs/lon-tpe-rtt)** | 95.97 ms | 55.2% | 1.58 ms | 0.09% | Fair | | 🇿🇦 Johannesburg (JNB) | **[179.6](/docs/network/latency/pairs/lon-jnb-rtt)** | 88.52 ms | 49.3% | 0.86 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[202.9](/docs/network/latency/pairs/lon-tyo-rtt)** | 93.84 ms | 46.2% | 1.61 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[249.6](/docs/network/latency/pairs/lon-mel-rtt)** | 165.48 ms | 66.3% | 2.17 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[258.1](/docs/network/latency/pairs/lon-syd-rtt)** | 166.37 ms | 64.5% | 1.58 ms | 0.18% | High | ## Fastest Routes to London (LON) The 10 fastest measured routes **to London**, 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 | 🇳🇱 Amsterdam (AMS) | **[5.2 ms](/docs/network/latency/pairs/ams-lon-rtt)** | 4.89 ms | 5.85 ms | 0.25 ms | | 2 | 🇫🇷 Paris (PAR) | **[6.4 ms](/docs/network/latency/pairs/par-lon-rtt)** | 6.03 ms | 7.35 ms | 0.26 ms | | 3 | 🇩🇪 Frankfurt (FRA) | **[12.9 ms](/docs/network/latency/pairs/fra-lon-rtt)** | 12.38 ms | 14.46 ms | 0.43 ms | | 4 | 🇩🇪 Berlin (BER) | **[15.2 ms](/docs/network/latency/pairs/ber-lon-rtt)** | 14.57 ms | 16.96 ms | 0.49 ms | | 5 | 🇫🇷 Marseille (MRS) | **[18.9 ms](/docs/network/latency/pairs/mrs-lon-rtt)** | 18.41 ms | 20.09 ms | 0.42 ms | | 6 | 🇷🇺 Moscow (MOW) | **[42.4 ms](/docs/network/latency/pairs/mow-lon-rtt)** | 40.38 ms | 48.72 ms | 1.83 ms | | 7 | 🇺🇸 New York (NYC) | **[63.5 ms](/docs/network/latency/pairs/nyc-lon-rtt)** | 61.91 ms | 68.19 ms | 1.32 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[70.3 ms](/docs/network/latency/pairs/iad-lon-rtt)** | 68.79 ms | 73.78 ms | 1.22 ms | | 9 | 🇺🇸 Miami (MIA) | **[101.8 ms](/docs/network/latency/pairs/mia-lon-rtt)** | 96.22 ms | 114.36 ms | 3.81 ms | | 10 | 🇺🇸 Seattle (SEA) | **[124.1 ms](/docs/network/latency/pairs/sea-lon-rtt)** | 118.94 ms | 137.2 ms | 3.96 ms | ## Inbound Latency to London (LON) Round-trip time in milliseconds **from all other PoPs to London**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇳🇱 Amsterdam (AMS) | **[5.2](/docs/network/latency/pairs/ams-lon-rtt)** | 3.51 ms | 67.4% | 0.12 ms | 0.09% | Ultra-Low | | 🇫🇷 Paris (PAR) | **[6.4](/docs/network/latency/pairs/par-lon-rtt)** | 3.37 ms | 52.7% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[12.9](/docs/network/latency/pairs/fra-lon-rtt)** | 6.26 ms | 48.5% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[15.2](/docs/network/latency/pairs/ber-lon-rtt)** | 9.15 ms | 60.2% | 0.15 ms | 0.14% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[18.9](/docs/network/latency/pairs/mrs-lon-rtt)** | 9.82 ms | 51.9% | 0.15 ms | 0.09% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[42.4](/docs/network/latency/pairs/mow-lon-rtt)** | 24.56 ms | 57.9% | 0.46 ms | 0.18% | Excellent | | 🇺🇸 New York (NYC) | **[63.5](/docs/network/latency/pairs/nyc-lon-rtt)** | 54.69 ms | 86.1% | 0.7 ms | 0.01% | Excellent | | 🇺🇸 Ashburn (IAD) | **[70.3](/docs/network/latency/pairs/iad-lon-rtt)** | 58.1 ms | 82.6% | 0.81 ms | 0.19% | Excellent | | 🇺🇸 Miami (MIA) | **[101.8](/docs/network/latency/pairs/mia-lon-rtt)** | 69.9 ms | 68.7% | 0.73 ms | 0% | Good | | 🇺🇸 Seattle (SEA) | **[124.1](/docs/network/latency/pairs/sea-lon-rtt)** | 75.63 ms | 60.9% | 1.38 ms | 0% | Good | | 🇺🇸 Los Angeles (LAX) | **[129.2](/docs/network/latency/pairs/lax-lon-rtt)** | 85.95 ms | 66.5% | 1.17 ms | 0% | Good | | 🇸🇬 Singapore (SIN) | **[155.4](/docs/network/latency/pairs/sin-lon-rtt)** | 106.35 ms | 68.4% | 1.17 ms | 0.06% | Fair | | 🇿🇦 Johannesburg (JNB) | **[158](/docs/network/latency/pairs/jnb-lon-rtt)** | 88.52 ms | 56% | 0.77 ms | 0.12% | Fair | | 🇭🇰 Hong Kong (HKG) | **[158.7](/docs/network/latency/pairs/hkg-lon-rtt)** | 94.44 ms | 59.5% | 0.8 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[173](/docs/network/latency/pairs/tpe-lon-rtt)** | 95.97 ms | 55.5% | 1.51 ms | 0.16% | Fair | | 🇧🇷 São Paulo (GRU) | **[175.8](/docs/network/latency/pairs/gru-lon-rtt)** | 92.76 ms | 52.8% | 1.62 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[202.7](/docs/network/latency/pairs/tyo-lon-rtt)** | 93.84 ms | 46.3% | 0.93 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[252](/docs/network/latency/pairs/mel-lon-rtt)** | 165.48 ms | 65.7% | 2.3 ms | 0.04% | High | | 🇦🇺 Sydney (SYD) | **[256.5](/docs/network/latency/pairs/syd-lon-rtt)** | 166.37 ms | 64.9% | 2.97 ms | 0.09% | High | ## Europe Peers London is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | --------------------------------------- | ---- | ----------- | -------- | --------- | | [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS | Netherlands | **5.2** | Ultra-Low | | [🇩🇪 Berlin (BER)](./ber-berlin) | BER | Germany | **16.2** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA | Germany | **13.6** | Ultra-Low | | [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS | France | **17.9** | Ultra-Low | | [🇷🇺 Moscow (MOW)](./mow-moscow) | MOW | Russia | **43.5** | Excellent | | [🇫🇷 Paris (PAR)](./par-paris) | PAR | France | **6.4** | Ultra-Low | ## Frequently Asked Questions **What is the fastest route to London?** The fastest measured route to London (LON) is [Amsterdam (AMS) → London (LON)](/docs/network/latency/pairs/ams-lon-rtt), averaging **5.2 ms** RTT (Ultra-Low). **What is the fastest route from London?** The fastest measured route from London (LON) is [London (LON) → Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-rtt), averaging **5.2 ms** RTT (Ultra-Low). **How well connected is London to the Hats Network backbone?** London (LON) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [London (LON) → Sydney (SYD)](/docs/network/latency/pairs/lon-syd-rtt), averages **258.1 ms** RTT. ## Open Data Measured latency data for London (LON) 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 London is published as `lon-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [lon-ams.pings.csv](/opendata/latency/latest/pairs/lon-ams.pings.csv), the 50-probe ICMP echo round for [London (LON) → Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-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/lon-london). - **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. # 🇦🇺 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-.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. # 🇺🇸 Miami Ping & Network Latency (MIA) | AS203314 ## 🇺🇸 Miami (MIA) Miami is the digital gateway between North and South America, hosting the NAP of the Americas. Hats Network's Miami PoP offers the fastest routes into Latin America. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Miami (MIA)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Miami, USA (North America) * **Region:** North America * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 4164138](https://www.geonames.org/4164138) — 25.77427, -80.19366 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** MIA1 * **Upstream transit:** Cogent / GTT * **Peering / IX:** NAP of the Americas / Equinix MI > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇺🇸 Miami (MIA) → 🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/mia-iad-rtt) (**27.3 ms**) — Ultra-Low | | Slowest Route | [🇺🇸 Miami (MIA) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/mia-jnb-rtt) (**259.8 ms**) | | Average RTT | **134.0 ms** | | Average Jitter | **1.06 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **76.9%** | | Intra-Region Peers | 4 PoPs in North America | | 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 Miami sits on Hats Network's **North America** backbone. Measured round-trip times to its 4 intra-region peers range from **27.3 ms** (Ashburn (IAD)) to **81.9 ms** (Seattle (SEA)). Miami is the digital gateway between North and South America, hosting the NAP of the Americas where Latin American routes converge. ## Outbound Latency from Miami (MIA) Round-trip time in milliseconds **from Miami** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Ashburn (IAD) | **[27.3](/docs/network/latency/pairs/mia-iad-rtt)** | 14.62 ms | 53.6% | 0.15 ms | 0% | Ultra-Low | | 🇺🇸 New York (NYC) | **[33.3](/docs/network/latency/pairs/mia-nyc-rtt)** | 17.17 ms | 51.6% | 0.33 ms | 0.08% | Excellent | | 🇺🇸 Los Angeles (LAX) | **[56.8](/docs/network/latency/pairs/mia-lax-rtt)** | 36.86 ms | 64.9% | 0.59 ms | 0% | Excellent | | 🇺🇸 Seattle (SEA) | **[81.9](/docs/network/latency/pairs/mia-sea-rtt)** | 43.08 ms | 52.6% | 0.47 ms | 0.1% | Good | | 🇬🇧 London (LON) | **[101.8](/docs/network/latency/pairs/mia-lon-rtt)** | 69.9 ms | 68.7% | 0.73 ms | 0% | Good | | 🇳🇱 Amsterdam (AMS) | **[106](/docs/network/latency/pairs/mia-ams-rtt)** | 73.03 ms | 68.9% | 0.87 ms | 0.08% | Good | | 🇫🇷 Paris (PAR) | **[106.2](/docs/network/latency/pairs/mia-par-rtt)** | 72.16 ms | 67.9% | 1.07 ms | 0% | Good | | 🇩🇪 Frankfurt (FRA) | **[112.2](/docs/network/latency/pairs/mia-fra-rtt)** | 76.17 ms | 67.9% | 0.83 ms | 0.06% | Good | | 🇫🇷 Marseille (MRS) | **[113.7](/docs/network/latency/pairs/mia-mrs-rtt)** | 75.92 ms | 66.8% | 1.23 ms | 0.14% | Good | | 🇩🇪 Berlin (BER) | **[117.3](/docs/network/latency/pairs/mia-ber-rtt)** | 78.44 ms | 66.9% | 1.4 ms | 0% | Good | | 🇧🇷 São Paulo (GRU) | **[128.7](/docs/network/latency/pairs/mia-gru-rtt)** | 64.11 ms | 49.8% | 0.81 ms | 0.16% | Good | | 🇷🇺 Moscow (MOW) | **[145.5](/docs/network/latency/pairs/mia-mow-rtt)** | 90.48 ms | 62.2% | 1.67 ms | 0.13% | Good | | 🇯🇵 Tokyo (TYO) | **[156.3](/docs/network/latency/pairs/mia-tyo-rtt)** | 117.71 ms | 75.3% | 0.95 ms | 0.03% | Fair | | 🇹🇼 Taipei (TPE) | **[185.1](/docs/network/latency/pairs/mia-tpe-rtt)** | 136.3 ms | 73.6% | 1.17 ms | 0.09% | Fair | | 🇦🇺 Sydney (SYD) | **[191.5](/docs/network/latency/pairs/mia-syd-rtt)** | 147.18 ms | 76.9% | 0.88 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[199.5](/docs/network/latency/pairs/mia-hkg-rtt)** | 141.69 ms | 71% | 2.35 ms | 0.06% | Fair | | 🇦🇺 Melbourne (MEL) | **[200.7](/docs/network/latency/pairs/mia-mel-rtt)** | 152.69 ms | 76.1% | 1.72 ms | 0% | Fair | | 🇸🇬 Singapore (SIN) | **[223.1](/docs/network/latency/pairs/mia-sin-rtt)** | 166.27 ms | 74.5% | 1.42 ms | 0.08% | Fair | | 🇿🇦 Johannesburg (JNB) | **[259.8](/docs/network/latency/pairs/mia-jnb-rtt)** | 126.78 ms | 48.8% | 1.51 ms | 0.19% | High | ## Fastest Routes to Miami (MIA) The 10 fastest measured routes **to Miami**, 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 | 🇺🇸 Ashburn (IAD) | **[27.4 ms](/docs/network/latency/pairs/iad-mia-rtt)** | 26.09 ms | 30.01 ms | 1.06 ms | | 2 | 🇺🇸 New York (NYC) | **[32.9 ms](/docs/network/latency/pairs/nyc-mia-rtt)** | 31.54 ms | 39.09 ms | 1.24 ms | | 3 | 🇺🇸 Los Angeles (LAX) | **[57.3 ms](/docs/network/latency/pairs/lax-mia-rtt)** | 55.45 ms | 63.93 ms | 1.73 ms | | 4 | 🇧🇷 São Paulo (GRU) | **[74 ms](/docs/network/latency/pairs/gru-mia-rtt)** | 70.55 ms | 83.79 ms | 3.07 ms | | 5 | 🇺🇸 Seattle (SEA) | **[81.7 ms](/docs/network/latency/pairs/sea-mia-rtt)** | 79.89 ms | 89.57 ms | 1.94 ms | | 6 | 🇬🇧 London (LON) | **[101.9 ms](/docs/network/latency/pairs/lon-mia-rtt)** | 97.83 ms | 115.14 ms | 3.85 ms | | 7 | 🇳🇱 Amsterdam (AMS) | **[106 ms](/docs/network/latency/pairs/ams-mia-rtt)** | 99.94 ms | 119.16 ms | 4.46 ms | | 8 | 🇫🇷 Paris (PAR) | **[106.8 ms](/docs/network/latency/pairs/par-mia-rtt)** | 101.15 ms | 125.38 ms | 5.28 ms | | 9 | 🇩🇪 Frankfurt (FRA) | **[112 ms](/docs/network/latency/pairs/fra-mia-rtt)** | 110.01 ms | 117.35 ms | 1.8 ms | | 10 | 🇫🇷 Marseille (MRS) | **[112.4 ms](/docs/network/latency/pairs/mrs-mia-rtt)** | 105.38 ms | 129.43 ms | 5.13 ms | ## Inbound Latency to Miami (MIA) Round-trip time in milliseconds **from all other PoPs to Miami**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Ashburn (IAD) | **[27.4](/docs/network/latency/pairs/iad-mia-rtt)** | 14.62 ms | 53.4% | 0.15 ms | 0% | Ultra-Low | | 🇺🇸 New York (NYC) | **[32.9](/docs/network/latency/pairs/nyc-mia-rtt)** | 17.17 ms | 52.2% | 0.39 ms | 0.15% | Excellent | | 🇺🇸 Los Angeles (LAX) | **[57.3](/docs/network/latency/pairs/lax-mia-rtt)** | 36.86 ms | 64.3% | 0.34 ms | 0% | Excellent | | 🇧🇷 São Paulo (GRU) | **[74](/docs/network/latency/pairs/gru-mia-rtt)** | 64.11 ms | 86.6% | 0.62 ms | 0.16% | Excellent | | 🇺🇸 Seattle (SEA) | **[81.7](/docs/network/latency/pairs/sea-mia-rtt)** | 43.08 ms | 52.7% | 0.84 ms | 0% | Good | | 🇬🇧 London (LON) | **[101.9](/docs/network/latency/pairs/lon-mia-rtt)** | 69.9 ms | 68.6% | 0.83 ms | 0.1% | Good | | 🇳🇱 Amsterdam (AMS) | **[106](/docs/network/latency/pairs/ams-mia-rtt)** | 73.03 ms | 68.9% | 1.03 ms | 0.01% | Good | | 🇫🇷 Paris (PAR) | **[106.8](/docs/network/latency/pairs/par-mia-rtt)** | 72.16 ms | 67.6% | 0.65 ms | 0.05% | Good | | 🇩🇪 Frankfurt (FRA) | **[112](/docs/network/latency/pairs/fra-mia-rtt)** | 76.17 ms | 68% | 1.27 ms | 0.07% | Good | | 🇫🇷 Marseille (MRS) | **[112.4](/docs/network/latency/pairs/mrs-mia-rtt)** | 75.92 ms | 67.5% | 0.96 ms | 0.1% | Good | | 🇩🇪 Berlin (BER) | **[118.3](/docs/network/latency/pairs/ber-mia-rtt)** | 78.44 ms | 66.3% | 0.76 ms | 0% | Good | | 🇷🇺 Moscow (MOW) | **[144.5](/docs/network/latency/pairs/mow-mia-rtt)** | 90.48 ms | 62.6% | 1.25 ms | 0.07% | Good | | 🇯🇵 Tokyo (TYO) | **[156.5](/docs/network/latency/pairs/tyo-mia-rtt)** | 117.71 ms | 75.2% | 1.36 ms | 0.14% | Fair | | 🇹🇼 Taipei (TPE) | **[185.7](/docs/network/latency/pairs/tpe-mia-rtt)** | 136.3 ms | 73.4% | 1.27 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[191.5](/docs/network/latency/pairs/syd-mia-rtt)** | 147.18 ms | 76.9% | 0.95 ms | 0.12% | Fair | | 🇦🇺 Melbourne (MEL) | **[201](/docs/network/latency/pairs/mel-mia-rtt)** | 152.69 ms | 76% | 1.83 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[201.1](/docs/network/latency/pairs/hkg-mia-rtt)** | 141.69 ms | 70.5% | 0.93 ms | 0.05% | Fair | | 🇸🇬 Singapore (SIN) | **[221.7](/docs/network/latency/pairs/sin-mia-rtt)** | 166.27 ms | 75% | 1.1 ms | 0.19% | Fair | | 🇿🇦 Johannesburg (JNB) | **[259.9](/docs/network/latency/pairs/jnb-mia-rtt)** | 126.78 ms | 48.8% | 3.06 ms | 0.1% | High | ## North America Peers Miami is one of 5 Hats Network PoPs in **North America**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | ------------------------------------------- | ---- | ------- | -------- | --------- | | [🇺🇸 Ashburn (IAD)](./iad-ashburn) | IAD | USA | **27.3** | Ultra-Low | | [🇺🇸 Los Angeles (LAX)](./lax-los-angeles) | LAX | USA | **56.8** | Excellent | | [🇺🇸 New York (NYC)](./nyc-new-york) | NYC | USA | **33.3** | Excellent | | [🇺🇸 Seattle (SEA)](./sea-seattle) | SEA | USA | **81.9** | Good | ## Frequently Asked Questions **What is the fastest route to Miami?** The fastest measured route to Miami (MIA) is [Ashburn (IAD) → Miami (MIA)](/docs/network/latency/pairs/iad-mia-rtt), averaging **27.4 ms** RTT (Ultra-Low). **What is the fastest route from Miami?** The fastest measured route from Miami (MIA) is [Miami (MIA) → Ashburn (IAD)](/docs/network/latency/pairs/mia-iad-rtt), averaging **27.3 ms** RTT (Ultra-Low). **How well connected is Miami to the Hats Network backbone?** Miami (MIA) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Miami (MIA) → Johannesburg (JNB)](/docs/network/latency/pairs/mia-jnb-rtt), averages **259.8 ms** RTT. ## Open Data Measured latency data for Miami (MIA) 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 Miami is published as `mia-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [mia-iad.pings.csv](/opendata/latency/latest/pairs/mia-iad.pings.csv), the 50-probe ICMP echo round for [Miami (MIA) → Ashburn (IAD)](/docs/network/latency/pairs/mia-iad-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/mia-miami). - **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. # 🇷🇺 Moscow Ping & Network Latency (MOW) | AS203314 ## 🇷🇺 Moscow (MOW) Moscow anchors Hats Network's reach into Eastern Europe and Central Asia, providing a critical transit corridor between European and Asia-Pacific networks. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Moscow (MOW)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Moscow, Russia (Europe) * **Region:** Europe * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 524901](https://www.geonames.org/524901) — 55.75204, 37.61781 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** MOW1 * **Upstream transit:** RETN / Melbicom > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇷🇺 Moscow (MOW) → 🇩🇪 Berlin (BER)](/docs/network/latency/pairs/mow-ber-rtt) (**27.5 ms**) — Ultra-Low | | Slowest Route | [🇷🇺 Moscow (MOW) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mow-syd-rtt) (**241.8 ms**) | | Average RTT | **126.3 ms** | | Average Jitter | **1.03 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **68.6%** | | Intra-Region Peers | 6 PoPs in Europe | | 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 Moscow sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **27.5 ms** (Berlin (BER)) to **49.9 ms** (Marseille (MRS)). Moscow extends the backbone eastward, providing a transit corridor between European and Asia-Pacific networks. ## Outbound Latency from Moscow (MOW) Round-trip time in milliseconds **from Moscow** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇩🇪 Berlin (BER) | **[27.5](/docs/network/latency/pairs/mow-ber-rtt)** | 15.8 ms | 57.5% | 0.3 ms | 0.13% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[35.9](/docs/network/latency/pairs/mow-fra-rtt)** | 19.85 ms | 55.3% | 0.3 ms | 0% | Excellent | | 🇳🇱 Amsterdam (AMS) | **[37.6](/docs/network/latency/pairs/mow-ams-rtt)** | 21.1 ms | 56.1% | 0.28 ms | 0.17% | Excellent | | 🇬🇧 London (LON) | **[42.4](/docs/network/latency/pairs/mow-lon-rtt)** | 24.56 ms | 57.9% | 0.46 ms | 0.18% | Excellent | | 🇫🇷 Paris (PAR) | **[44](/docs/network/latency/pairs/mow-par-rtt)** | 24.42 ms | 55.5% | 0.29 ms | 0% | Excellent | | 🇫🇷 Marseille (MRS) | **[49.9](/docs/network/latency/pairs/mow-mrs-rtt)** | 26.23 ms | 52.6% | 0.4 ms | 0.05% | Excellent | | 🇺🇸 New York (NYC) | **[107.5](/docs/network/latency/pairs/mow-nyc-rtt)** | 73.75 ms | 68.6% | 1 ms | 0% | Good | | 🇺🇸 Ashburn (IAD) | **[113.9](/docs/network/latency/pairs/mow-iad-rtt)** | 76.88 ms | 67.5% | 1 ms | 0.08% | Good | | 🇭🇰 Hong Kong (HKG) | **[118.6](/docs/network/latency/pairs/mow-hkg-rtt)** | 70.05 ms | 59.1% | 0.77 ms | 0.13% | Good | | 🇹🇼 Taipei (TPE) | **[132.1](/docs/network/latency/pairs/mow-tpe-rtt)** | 72.16 ms | 54.6% | 1.49 ms | 0% | Good | | 🇺🇸 Miami (MIA) | **[144.5](/docs/network/latency/pairs/mow-mia-rtt)** | 90.48 ms | 62.6% | 1.25 ms | 0.07% | Good | | 🇸🇬 Singapore (SIN) | **[147.3](/docs/network/latency/pairs/mow-sin-rtt)** | 82.49 ms | 56% | 1.11 ms | 0.17% | Good | | 🇯🇵 Tokyo (TYO) | **[162.2](/docs/network/latency/pairs/mow-tyo-rtt)** | 73.42 ms | 45.3% | 1.92 ms | 0.08% | Fair | | 🇺🇸 Seattle (SEA) | **[164.8](/docs/network/latency/pairs/mow-sea-rtt)** | 82.23 ms | 49.9% | 0.99 ms | 0% | Fair | | 🇺🇸 Los Angeles (LAX) | **[177.7](/docs/network/latency/pairs/mow-lax-rtt)** | 95.9 ms | 54% | 1.55 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[201.9](/docs/network/latency/pairs/mow-jnb-rtt)** | 89.37 ms | 44.3% | 1.29 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[214.4](/docs/network/latency/pairs/mow-gru-rtt)** | 115.47 ms | 53.9% | 1.47 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[235.9](/docs/network/latency/pairs/mow-mel-rtt)** | 141.13 ms | 59.8% | 1.11 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[241.8](/docs/network/latency/pairs/mow-syd-rtt)** | 141.84 ms | 58.7% | 2.66 ms | 0% | Fair | ## Fastest Routes to Moscow (MOW) The 10 fastest measured routes **to Moscow**, 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 | 🇩🇪 Berlin (BER) | **[28.6 ms](/docs/network/latency/pairs/ber-mow-rtt)** | 27.35 ms | 31.58 ms | 1.1 ms | | 2 | 🇩🇪 Frankfurt (FRA) | **[34.7 ms](/docs/network/latency/pairs/fra-mow-rtt)** | 32.66 ms | 40.02 ms | 1.68 ms | | 3 | 🇳🇱 Amsterdam (AMS) | **[38.1 ms](/docs/network/latency/pairs/ams-mow-rtt)** | 35.69 ms | 44.57 ms | 1.9 ms | | 4 | 🇬🇧 London (LON) | **[43.5 ms](/docs/network/latency/pairs/lon-mow-rtt)** | 41.81 ms | 48.52 ms | 1.38 ms | | 5 | 🇫🇷 Paris (PAR) | **[44.7 ms](/docs/network/latency/pairs/par-mow-rtt)** | 43.04 ms | 51.46 ms | 1.56 ms | | 6 | 🇫🇷 Marseille (MRS) | **[49.6 ms](/docs/network/latency/pairs/mrs-mow-rtt)** | 47.26 ms | 58 ms | 2.18 ms | | 7 | 🇺🇸 New York (NYC) | **[107 ms](/docs/network/latency/pairs/nyc-mow-rtt)** | 101.46 ms | 119.28 ms | 4.26 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[112.8 ms](/docs/network/latency/pairs/iad-mow-rtt)** | 109.18 ms | 122.64 ms | 3.63 ms | | 9 | 🇭🇰 Hong Kong (HKG) | **[118.2 ms](/docs/network/latency/pairs/hkg-mow-rtt)** | 115.72 ms | 128.25 ms | 2.23 ms | | 10 | 🇹🇼 Taipei (TPE) | **[132.7 ms](/docs/network/latency/pairs/tpe-mow-rtt)** | 127.77 ms | 145.28 ms | 3.91 ms | ## Inbound Latency to Moscow (MOW) Round-trip time in milliseconds **from all other PoPs to Moscow**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇩🇪 Berlin (BER) | **[28.6](/docs/network/latency/pairs/ber-mow-rtt)** | 15.8 ms | 55.2% | 0.33 ms | 0% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[34.7](/docs/network/latency/pairs/fra-mow-rtt)** | 19.85 ms | 57.2% | 0.25 ms | 0.13% | Excellent | | 🇳🇱 Amsterdam (AMS) | **[38.1](/docs/network/latency/pairs/ams-mow-rtt)** | 21.1 ms | 55.4% | 0.38 ms | 0% | Excellent | | 🇬🇧 London (LON) | **[43.5](/docs/network/latency/pairs/lon-mow-rtt)** | 24.56 ms | 56.5% | 0.2 ms | 0.06% | Excellent | | 🇫🇷 Paris (PAR) | **[44.7](/docs/network/latency/pairs/par-mow-rtt)** | 24.42 ms | 54.6% | 0.23 ms | 0.2% | Excellent | | 🇫🇷 Marseille (MRS) | **[49.6](/docs/network/latency/pairs/mrs-mow-rtt)** | 26.23 ms | 52.9% | 0.45 ms | 0.07% | Excellent | | 🇺🇸 New York (NYC) | **[107](/docs/network/latency/pairs/nyc-mow-rtt)** | 73.75 ms | 68.9% | 1.08 ms | 0.06% | Good | | 🇺🇸 Ashburn (IAD) | **[112.8](/docs/network/latency/pairs/iad-mow-rtt)** | 76.88 ms | 68.2% | 0.79 ms | 0.13% | Good | | 🇭🇰 Hong Kong (HKG) | **[118.2](/docs/network/latency/pairs/hkg-mow-rtt)** | 70.05 ms | 59.3% | 1.17 ms | 0.11% | Good | | 🇹🇼 Taipei (TPE) | **[132.7](/docs/network/latency/pairs/tpe-mow-rtt)** | 72.16 ms | 54.4% | 0.68 ms | 0.09% | Good | | 🇺🇸 Miami (MIA) | **[145.5](/docs/network/latency/pairs/mia-mow-rtt)** | 90.48 ms | 62.2% | 1.67 ms | 0.13% | Good | | 🇸🇬 Singapore (SIN) | **[147.7](/docs/network/latency/pairs/sin-mow-rtt)** | 82.49 ms | 55.8% | 0.99 ms | 0.11% | Good | | 🇯🇵 Tokyo (TYO) | **[161.7](/docs/network/latency/pairs/tyo-mow-rtt)** | 73.42 ms | 45.4% | 1.62 ms | 0.09% | Fair | | 🇺🇸 Seattle (SEA) | **[164.6](/docs/network/latency/pairs/sea-mow-rtt)** | 82.23 ms | 50% | 1.42 ms | 0% | Fair | | 🇺🇸 Los Angeles (LAX) | **[177](/docs/network/latency/pairs/lax-mow-rtt)** | 95.9 ms | 54.2% | 1.7 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[200.7](/docs/network/latency/pairs/jnb-mow-rtt)** | 89.37 ms | 44.5% | 2.17 ms | 0.16% | Fair | | 🇧🇷 São Paulo (GRU) | **[219.5](/docs/network/latency/pairs/gru-mow-rtt)** | 115.47 ms | 52.6% | 1.57 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[236.1](/docs/network/latency/pairs/mel-mow-rtt)** | 141.13 ms | 59.8% | 2.48 ms | 0.05% | Fair | | 🇦🇺 Sydney (SYD) | **[242.2](/docs/network/latency/pairs/syd-mow-rtt)** | 141.84 ms | 58.6% | 1.9 ms | 0.11% | Fair | ## Europe Peers Moscow is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | --------------------------------------- | ---- | ----------- | -------- | --------- | | [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS | Netherlands | **37.6** | Excellent | | [🇩🇪 Berlin (BER)](./ber-berlin) | BER | Germany | **27.5** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA | Germany | **35.9** | Excellent | | [🇬🇧 London (LON)](./lon-london) | LON | UK | **42.4** | Excellent | | [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS | France | **49.9** | Excellent | | [🇫🇷 Paris (PAR)](./par-paris) | PAR | France | **44** | Excellent | ## Frequently Asked Questions **What is the fastest route to Moscow?** The fastest measured route to Moscow (MOW) is [Berlin (BER) → Moscow (MOW)](/docs/network/latency/pairs/ber-mow-rtt), averaging **28.6 ms** RTT (Ultra-Low). **What is the fastest route from Moscow?** The fastest measured route from Moscow (MOW) is [Moscow (MOW) → Berlin (BER)](/docs/network/latency/pairs/mow-ber-rtt), averaging **27.5 ms** RTT (Ultra-Low). **How well connected is Moscow to the Hats Network backbone?** Moscow (MOW) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Moscow (MOW) → Sydney (SYD)](/docs/network/latency/pairs/mow-syd-rtt), averages **241.8 ms** RTT. ## Open Data Measured latency data for Moscow (MOW) 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 Moscow is published as `mow-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [mow-ber.pings.csv](/opendata/latency/latest/pairs/mow-ber.pings.csv), the 50-probe ICMP echo round for [Moscow (MOW) → Berlin (BER)](/docs/network/latency/pairs/mow-ber-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/mow-moscow). - **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. # 🇫🇷 Marseille Ping & Network Latency (MRS) | AS203314 ## 🇫🇷 Marseille (MRS) Marseille serves as the strategic submarine cable landing hub bridging Europe to Africa, the Middle East, and Asia. Hats Network's PoP offers diverse path options via multiple cable systems. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Marseille (MRS)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Marseille, France (Europe) * **Region:** Europe * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 2995469](https://www.geonames.org/2995469) — 43.29695, 5.38107 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** MRS1 > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ----------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇫🇷 Marseille (MRS) → 🇫🇷 Paris (PAR)](/docs/network/latency/pairs/mrs-par-rtt) (**8.9 ms**) — Ultra-Low | | Slowest Route | [🇫🇷 Marseille (MRS) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mrs-syd-rtt) (**240.6 ms**) | | Average RTT | **118.4 ms** | | Average Jitter | **0.97 ms** | | Average Packet Loss | **0.05%** | | Best Fiber Efficiency | **77.6%** | | Intra-Region Peers | 6 PoPs in Europe | | 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 Marseille sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **8.9 ms** (Paris (PAR)) to **49.6 ms** (Moscow (MOW)). Marseille is France's Mediterranean submarine cable landing hub, where systems from Africa, the Middle East and Asia come ashore. ## Outbound Latency from Marseille (MRS) Round-trip time in milliseconds **from Marseille** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇫🇷 Paris (PAR) | **[8.9](/docs/network/latency/pairs/mrs-par-rtt)** | 6.47 ms | 72.7% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[16](/docs/network/latency/pairs/mrs-fra-rtt)** | 7.82 ms | 48.9% | 0.18 ms | 0.15% | Ultra-Low | | 🇬🇧 London (LON) | **[18.9](/docs/network/latency/pairs/mrs-lon-rtt)** | 9.82 ms | 51.9% | 0.15 ms | 0.09% | Ultra-Low | | 🇳🇱 Amsterdam (AMS) | **[20.3](/docs/network/latency/pairs/mrs-ams-rtt)** | 9.89 ms | 48.7% | 0.17 ms | 0.16% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[20.6](/docs/network/latency/pairs/mrs-ber-rtt)** | 11.62 ms | 56.4% | 0.24 ms | 0% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[49.6](/docs/network/latency/pairs/mrs-mow-rtt)** | 26.23 ms | 52.9% | 0.45 ms | 0.07% | Excellent | | 🇺🇸 New York (NYC) | **[79.8](/docs/network/latency/pairs/mrs-nyc-rtt)** | 61.91 ms | 77.6% | 0.78 ms | 0% | Excellent | | 🇺🇸 Ashburn (IAD) | **[85.7](/docs/network/latency/pairs/mrs-iad-rtt)** | 65.34 ms | 76.2% | 0.46 ms | 0.05% | Good | | 🇺🇸 Miami (MIA) | **[112.4](/docs/network/latency/pairs/mrs-mia-rtt)** | 75.92 ms | 67.5% | 0.96 ms | 0.1% | Good | | 🇸🇬 Singapore (SIN) | **[139.6](/docs/network/latency/pairs/mrs-sin-rtt)** | 103.79 ms | 74.3% | 1.19 ms | 0% | Good | | 🇺🇸 Seattle (SEA) | **[141.7](/docs/network/latency/pairs/mrs-sea-rtt)** | 85.27 ms | 60.2% | 1.19 ms | 0.12% | Good | | 🇺🇸 Los Angeles (LAX) | **[144.5](/docs/network/latency/pairs/mrs-lax-rtt)** | 95.09 ms | 65.8% | 0.78 ms | 0% | Good | | 🇭🇰 Hong Kong (HKG) | **[166.4](/docs/network/latency/pairs/mrs-hkg-rtt)** | 95.48 ms | 57.4% | 1.49 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[180.9](/docs/network/latency/pairs/mrs-tpe-rtt)** | 98.2 ms | 54.3% | 1.86 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[186.7](/docs/network/latency/pairs/mrs-gru-rtt)** | 89.24 ms | 47.8% | 1.4 ms | 0.05% | Fair | | 🇿🇦 Johannesburg (JNB) | **[198.5](/docs/network/latency/pairs/mrs-jnb-rtt)** | 78.71 ms | 39.7% | 1.78 ms | 0% | Fair | | 🇯🇵 Tokyo (TYO) | **[203.8](/docs/network/latency/pairs/mrs-tyo-rtt)** | 99.03 ms | 48.6% | 2.03 ms | 0.18% | Fair | | 🇦🇺 Melbourne (MEL) | **[234.2](/docs/network/latency/pairs/mrs-mel-rtt)** | 162.36 ms | 69.3% | 1.1 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[240.6](/docs/network/latency/pairs/mrs-syd-rtt)** | 165.41 ms | 68.7% | 2.14 ms | 0% | Fair | ## Fastest Routes to Marseille (MRS) The 10 fastest measured routes **to Marseille**, 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 | 🇫🇷 Paris (PAR) | **[8.9 ms](/docs/network/latency/pairs/par-mrs-rtt)** | 8.59 ms | 9.69 ms | 0.26 ms | | 2 | 🇩🇪 Frankfurt (FRA) | **[16.4 ms](/docs/network/latency/pairs/fra-mrs-rtt)** | 15.96 ms | 17.74 ms | 0.37 ms | | 3 | 🇬🇧 London (LON) | **[17.9 ms](/docs/network/latency/pairs/lon-mrs-rtt)** | 17.02 ms | 21.69 ms | 0.84 ms | | 4 | 🇳🇱 Amsterdam (AMS) | **[19.6 ms](/docs/network/latency/pairs/ams-mrs-rtt)** | 19.03 ms | 20.95 ms | 0.5 ms | | 5 | 🇩🇪 Berlin (BER) | **[20.2 ms](/docs/network/latency/pairs/ber-mrs-rtt)** | 19.92 ms | 21.65 ms | 0.31 ms | | 6 | 🇷🇺 Moscow (MOW) | **[49.9 ms](/docs/network/latency/pairs/mow-mrs-rtt)** | 47.94 ms | 53.35 ms | 1.46 ms | | 7 | 🇺🇸 New York (NYC) | **[80.2 ms](/docs/network/latency/pairs/nyc-mrs-rtt)** | 78.94 ms | 85.06 ms | 1.32 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[86.5 ms](/docs/network/latency/pairs/iad-mrs-rtt)** | 81.69 ms | 97.62 ms | 3.63 ms | | 9 | 🇺🇸 Miami (MIA) | **[113.7 ms](/docs/network/latency/pairs/mia-mrs-rtt)** | 110.36 ms | 126.2 ms | 3.72 ms | | 10 | 🇸🇬 Singapore (SIN) | **[140.6 ms](/docs/network/latency/pairs/sin-mrs-rtt)** | 138.21 ms | 150.15 ms | 2.29 ms | ## Inbound Latency to Marseille (MRS) Round-trip time in milliseconds **from all other PoPs to Marseille**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇫🇷 Paris (PAR) | **[8.9](/docs/network/latency/pairs/par-mrs-rtt)** | 6.47 ms | 72.7% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[16.4](/docs/network/latency/pairs/fra-mrs-rtt)** | 7.82 ms | 47.7% | 0.19 ms | 0% | Ultra-Low | | 🇬🇧 London (LON) | **[17.9](/docs/network/latency/pairs/lon-mrs-rtt)** | 9.82 ms | 54.8% | 0.16 ms | 0.14% | Ultra-Low | | 🇳🇱 Amsterdam (AMS) | **[19.6](/docs/network/latency/pairs/ams-mrs-rtt)** | 9.89 ms | 50.5% | 0.12 ms | 0.03% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[20.2](/docs/network/latency/pairs/ber-mrs-rtt)** | 11.62 ms | 57.5% | 0.16 ms | 0.06% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[49.9](/docs/network/latency/pairs/mow-mrs-rtt)** | 26.23 ms | 52.6% | 0.4 ms | 0.05% | Excellent | | 🇺🇸 New York (NYC) | **[80.2](/docs/network/latency/pairs/nyc-mrs-rtt)** | 61.91 ms | 77.2% | 0.53 ms | 0% | Good | | 🇺🇸 Ashburn (IAD) | **[86.5](/docs/network/latency/pairs/iad-mrs-rtt)** | 65.34 ms | 75.5% | 0.72 ms | 0% | Good | | 🇺🇸 Miami (MIA) | **[113.7](/docs/network/latency/pairs/mia-mrs-rtt)** | 75.92 ms | 66.8% | 1.23 ms | 0.14% | Good | | 🇸🇬 Singapore (SIN) | **[140.6](/docs/network/latency/pairs/sin-mrs-rtt)** | 103.79 ms | 73.8% | 1.48 ms | 0.2% | Good | | 🇺🇸 Seattle (SEA) | **[141.2](/docs/network/latency/pairs/sea-mrs-rtt)** | 85.27 ms | 60.4% | 1.25 ms | 0.04% | Good | | 🇺🇸 Los Angeles (LAX) | **[143.9](/docs/network/latency/pairs/lax-mrs-rtt)** | 95.09 ms | 66.1% | 1.05 ms | 0.16% | Good | | 🇭🇰 Hong Kong (HKG) | **[165.4](/docs/network/latency/pairs/hkg-mrs-rtt)** | 95.48 ms | 57.7% | 0.85 ms | 0.09% | Fair | | 🇿🇦 Johannesburg (JNB) | **[172](/docs/network/latency/pairs/jnb-mrs-rtt)** | 78.71 ms | 45.8% | 1.53 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[179.5](/docs/network/latency/pairs/tpe-mrs-rtt)** | 98.2 ms | 54.7% | 1.4 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[187.7](/docs/network/latency/pairs/gru-mrs-rtt)** | 89.24 ms | 47.5% | 1.08 ms | 0.14% | Fair | | 🇯🇵 Tokyo (TYO) | **[205.6](/docs/network/latency/pairs/tyo-mrs-rtt)** | 99.03 ms | 48.2% | 1.86 ms | 0.14% | Fair | | 🇦🇺 Melbourne (MEL) | **[233.5](/docs/network/latency/pairs/mel-mrs-rtt)** | 162.36 ms | 69.5% | 2.54 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[240.5](/docs/network/latency/pairs/syd-mrs-rtt)** | 165.41 ms | 68.8% | 2.18 ms | 0% | Fair | ## Europe Peers Marseille is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | --------------------------------------- | ---- | ----------- | -------- | --------- | | [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS | Netherlands | **20.3** | Ultra-Low | | [🇩🇪 Berlin (BER)](./ber-berlin) | BER | Germany | **20.6** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA | Germany | **16** | Ultra-Low | | [🇬🇧 London (LON)](./lon-london) | LON | UK | **18.9** | Ultra-Low | | [🇷🇺 Moscow (MOW)](./mow-moscow) | MOW | Russia | **49.6** | Excellent | | [🇫🇷 Paris (PAR)](./par-paris) | PAR | France | **8.9** | Ultra-Low | ## Frequently Asked Questions **What is the fastest route to Marseille?** The fastest measured route to Marseille (MRS) is [Paris (PAR) → Marseille (MRS)](/docs/network/latency/pairs/par-mrs-rtt), averaging **8.9 ms** RTT (Ultra-Low). **What is the fastest route from Marseille?** The fastest measured route from Marseille (MRS) is [Marseille (MRS) → Paris (PAR)](/docs/network/latency/pairs/mrs-par-rtt), averaging **8.9 ms** RTT (Ultra-Low). **How well connected is Marseille to the Hats Network backbone?** Marseille (MRS) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Marseille (MRS) → Sydney (SYD)](/docs/network/latency/pairs/mrs-syd-rtt), averages **240.6 ms** RTT. ## Open Data Measured latency data for Marseille (MRS) 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 Marseille is published as `mrs-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [mrs-par.pings.csv](/opendata/latency/latest/pairs/mrs-par.pings.csv), the 50-probe ICMP echo round for [Marseille (MRS) → Paris (PAR)](/docs/network/latency/pairs/mrs-par-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/mrs-marseille). - **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. # 🇺🇸 New York Ping & Network Latency (NYC) | AS203314 ## 🇺🇸 New York (NYC) New York City is a top-tier global internet hub, home to major carrier hotels at 60 Hudson Street. Hats Network's NYC PoP anchors the transatlantic corridor to Europe. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **New York (NYC)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** New York, USA (North America) * **Region:** North America * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 5128581](https://www.geonames.org/5128581) — 40.71427, -74.00597 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** NYC1 > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇺🇸 New York (NYC) → 🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/nyc-iad-rtt) (**6 ms**) — Ultra-Low | | Slowest Route | [🇺🇸 New York (NYC) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/nyc-jnb-rtt) (**221.5 ms**) | | Average RTT | **112.4 ms** | | Average Jitter | **0.89 ms** | | Average Packet Loss | **0.03%** | | Best Fiber Efficiency | **86.1%** | | Intra-Region Peers | 4 PoPs in North America | | 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 New York sits on Hats Network's **North America** backbone. Measured round-trip times to its 4 intra-region peers range from **6 ms** (Ashburn (IAD)) to **58.9 ms** (Los Angeles (LAX)). New York anchors the US end of the transatlantic corridor to Europe, centered on carrier hotels such as 60 Hudson Street. ## Outbound Latency from New York (NYC) Round-trip time in milliseconds **from New York** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Ashburn (IAD) | **[6](/docs/network/latency/pairs/nyc-iad-rtt)** | 3.44 ms | 57.3% | 0.12 ms | 0.01% | Ultra-Low | | 🇺🇸 Miami (MIA) | **[32.9](/docs/network/latency/pairs/nyc-mia-rtt)** | 17.17 ms | 52.2% | 0.39 ms | 0.15% | Excellent | | 🇺🇸 Seattle (SEA) | **[58.7](/docs/network/latency/pairs/nyc-sea-rtt)** | 37.95 ms | 64.7% | 0.35 ms | 0.11% | Excellent | | 🇺🇸 Los Angeles (LAX) | **[58.9](/docs/network/latency/pairs/nyc-lax-rtt)** | 38.63 ms | 65.6% | 0.46 ms | 0% | Excellent | | 🇬🇧 London (LON) | **[63.5](/docs/network/latency/pairs/nyc-lon-rtt)** | 54.69 ms | 86.1% | 0.7 ms | 0.01% | Excellent | | 🇳🇱 Amsterdam (AMS) | **[68.7](/docs/network/latency/pairs/nyc-ams-rtt)** | 57.56 ms | 83.8% | 0.33 ms | 0.03% | Excellent | | 🇫🇷 Paris (PAR) | **[68.9](/docs/network/latency/pairs/nyc-par-rtt)** | 57.31 ms | 83.2% | 0.43 ms | 0.15% | Excellent | | 🇩🇪 Frankfurt (FRA) | **[73.9](/docs/network/latency/pairs/nyc-fra-rtt)** | 60.9 ms | 82.4% | 0.74 ms | 0.09% | Excellent | | 🇩🇪 Berlin (BER) | **[78.8](/docs/network/latency/pairs/nyc-ber-rtt)** | 62.7 ms | 79.6% | 0.67 ms | 0% | Excellent | | 🇫🇷 Marseille (MRS) | **[80.2](/docs/network/latency/pairs/nyc-mrs-rtt)** | 61.91 ms | 77.2% | 0.53 ms | 0% | Good | | 🇧🇷 São Paulo (GRU) | **[106.9](/docs/network/latency/pairs/nyc-gru-rtt)** | 74.99 ms | 70.1% | 0.74 ms | 0% | Good | | 🇷🇺 Moscow (MOW) | **[107](/docs/network/latency/pairs/nyc-mow-rtt)** | 73.75 ms | 68.9% | 1.08 ms | 0.06% | Good | | 🇯🇵 Tokyo (TYO) | **[143.1](/docs/network/latency/pairs/nyc-tyo-rtt)** | 106.47 ms | 74.4% | 0.8 ms | 0% | Good | | 🇹🇼 Taipei (TPE) | **[173.4](/docs/network/latency/pairs/nyc-tpe-rtt)** | 122.89 ms | 70.9% | 1.21 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[187.1](/docs/network/latency/pairs/nyc-hkg-rtt)** | 127.11 ms | 67.9% | 1.76 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[192.6](/docs/network/latency/pairs/nyc-syd-rtt)** | 156.57 ms | 81.3% | 0.91 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[205.1](/docs/network/latency/pairs/nyc-mel-rtt)** | 163.27 ms | 79.6% | 1.79 ms | 0.04% | Fair | | 🇸🇬 Singapore (SIN) | **[208.7](/docs/network/latency/pairs/nyc-sin-rtt)** | 150.29 ms | 72% | 1.83 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[221.5](/docs/network/latency/pairs/nyc-jnb-rtt)** | 125.67 ms | 56.7% | 2.09 ms | 0% | Fair | ## Fastest Routes to New York (NYC) The 10 fastest measured routes **to New York**, 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 | 🇺🇸 Ashburn (IAD) | **[6 ms](/docs/network/latency/pairs/iad-nyc-rtt)** | 5.77 ms | 6.79 ms | 0.2 ms | | 2 | 🇺🇸 Miami (MIA) | **[33.3 ms](/docs/network/latency/pairs/mia-nyc-rtt)** | 31.68 ms | 39.04 ms | 1.51 ms | | 3 | 🇺🇸 Los Angeles (LAX) | **[57.9 ms](/docs/network/latency/pairs/lax-nyc-rtt)** | 55.78 ms | 62.74 ms | 1.33 ms | | 4 | 🇺🇸 Seattle (SEA) | **[59.5 ms](/docs/network/latency/pairs/sea-nyc-rtt)** | 57.58 ms | 64.42 ms | 1.48 ms | | 5 | 🇬🇧 London (LON) | **[63.8 ms](/docs/network/latency/pairs/lon-nyc-rtt)** | 60.82 ms | 74.75 ms | 2.78 ms | | 6 | 🇳🇱 Amsterdam (AMS) | **[68.6 ms](/docs/network/latency/pairs/ams-nyc-rtt)** | 67.28 ms | 73 ms | 1.16 ms | | 7 | 🇫🇷 Paris (PAR) | **[68.9 ms](/docs/network/latency/pairs/par-nyc-rtt)** | 66.76 ms | 73.07 ms | 1.55 ms | | 8 | 🇩🇪 Frankfurt (FRA) | **[74.4 ms](/docs/network/latency/pairs/fra-nyc-rtt)** | 72.04 ms | 80.52 ms | 2.09 ms | | 9 | 🇩🇪 Berlin (BER) | **[79.6 ms](/docs/network/latency/pairs/ber-nyc-rtt)** | 78.03 ms | 83.78 ms | 1.28 ms | | 10 | 🇫🇷 Marseille (MRS) | **[79.8 ms](/docs/network/latency/pairs/mrs-nyc-rtt)** | 75.53 ms | 89.73 ms | 3.65 ms | ## Inbound Latency to New York (NYC) Round-trip time in milliseconds **from all other PoPs to New York**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Ashburn (IAD) | **[6](/docs/network/latency/pairs/iad-nyc-rtt)** | 3.44 ms | 57.3% | 0.12 ms | 0.17% | Ultra-Low | | 🇺🇸 Miami (MIA) | **[33.3](/docs/network/latency/pairs/mia-nyc-rtt)** | 17.17 ms | 51.6% | 0.33 ms | 0.08% | Excellent | | 🇺🇸 Los Angeles (LAX) | **[57.9](/docs/network/latency/pairs/lax-nyc-rtt)** | 38.63 ms | 66.7% | 0.34 ms | 0.09% | Excellent | | 🇺🇸 Seattle (SEA) | **[59.5](/docs/network/latency/pairs/sea-nyc-rtt)** | 37.95 ms | 63.8% | 0.66 ms | 0.16% | Excellent | | 🇬🇧 London (LON) | **[63.8](/docs/network/latency/pairs/lon-nyc-rtt)** | 54.69 ms | 85.7% | 0.42 ms | 0.12% | Excellent | | 🇳🇱 Amsterdam (AMS) | **[68.6](/docs/network/latency/pairs/ams-nyc-rtt)** | 57.56 ms | 83.9% | 0.31 ms | 0% | Excellent | | 🇫🇷 Paris (PAR) | **[68.9](/docs/network/latency/pairs/par-nyc-rtt)** | 57.31 ms | 83.2% | 0.71 ms | 0.05% | Excellent | | 🇩🇪 Frankfurt (FRA) | **[74.4](/docs/network/latency/pairs/fra-nyc-rtt)** | 60.9 ms | 81.9% | 0.73 ms | 0% | Excellent | | 🇩🇪 Berlin (BER) | **[79.6](/docs/network/latency/pairs/ber-nyc-rtt)** | 62.7 ms | 78.8% | 0.5 ms | 0.08% | Excellent | | 🇫🇷 Marseille (MRS) | **[79.8](/docs/network/latency/pairs/mrs-nyc-rtt)** | 61.91 ms | 77.6% | 0.78 ms | 0% | Excellent | | 🇷🇺 Moscow (MOW) | **[107.5](/docs/network/latency/pairs/mow-nyc-rtt)** | 73.75 ms | 68.6% | 1 ms | 0% | Good | | 🇧🇷 São Paulo (GRU) | **[122](/docs/network/latency/pairs/gru-nyc-rtt)** | 74.99 ms | 61.5% | 1.29 ms | 0% | Good | | 🇯🇵 Tokyo (TYO) | **[144.6](/docs/network/latency/pairs/tyo-nyc-rtt)** | 106.47 ms | 73.6% | 1.33 ms | 0.17% | Good | | 🇹🇼 Taipei (TPE) | **[174.2](/docs/network/latency/pairs/tpe-nyc-rtt)** | 122.89 ms | 70.5% | 1.24 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[184.7](/docs/network/latency/pairs/hkg-nyc-rtt)** | 127.11 ms | 68.8% | 0.98 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[191.9](/docs/network/latency/pairs/syd-nyc-rtt)** | 156.57 ms | 81.6% | 2.06 ms | 0.07% | Fair | | 🇦🇺 Melbourne (MEL) | **[204.2](/docs/network/latency/pairs/mel-nyc-rtt)** | 163.27 ms | 80% | 2.1 ms | 0% | Fair | | 🇸🇬 Singapore (SIN) | **[209.3](/docs/network/latency/pairs/sin-nyc-rtt)** | 150.29 ms | 71.8% | 1.38 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[221.8](/docs/network/latency/pairs/jnb-nyc-rtt)** | 125.67 ms | 56.7% | 2.01 ms | 0% | Fair | ## North America Peers New York is one of 5 Hats Network PoPs in **North America**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | ------------------------------------------- | ---- | ------- | -------- | --------- | | [🇺🇸 Ashburn (IAD)](./iad-ashburn) | IAD | USA | **6** | Ultra-Low | | [🇺🇸 Los Angeles (LAX)](./lax-los-angeles) | LAX | USA | **58.9** | Excellent | | [🇺🇸 Miami (MIA)](./mia-miami) | MIA | USA | **32.9** | Excellent | | [🇺🇸 Seattle (SEA)](./sea-seattle) | SEA | USA | **58.7** | Excellent | ## Frequently Asked Questions **What is the fastest route to New York?** The fastest measured route to New York (NYC) is [Ashburn (IAD) → New York (NYC)](/docs/network/latency/pairs/iad-nyc-rtt), averaging **6 ms** RTT (Ultra-Low). **What is the fastest route from New York?** The fastest measured route from New York (NYC) is [New York (NYC) → Ashburn (IAD)](/docs/network/latency/pairs/nyc-iad-rtt), averaging **6 ms** RTT (Ultra-Low). **How well connected is New York to the Hats Network backbone?** New York (NYC) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [New York (NYC) → Johannesburg (JNB)](/docs/network/latency/pairs/nyc-jnb-rtt), averages **221.5 ms** RTT. ## Open Data Measured latency data for New York (NYC) 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 New York is published as `nyc-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [nyc-iad.pings.csv](/opendata/latency/latest/pairs/nyc-iad.pings.csv), the 50-probe ICMP echo round for [New York (NYC) → Ashburn (IAD)](/docs/network/latency/pairs/nyc-iad-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/nyc-new-york). - **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. # 🇫🇷 Paris Ping & Network Latency (PAR) | AS203314 ## 🇫🇷 Paris (PAR) Paris is a major French interconnection market, providing direct access to France-IX Paris and NL-IX Paris alongside diverse national and European transit paths. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Paris (PAR)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Paris, France (Europe) * **Region:** Europe * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 2988507](https://www.geonames.org/2988507) — 48.85341, 2.34880 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** PAR1 > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | -------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇫🇷 Paris (PAR) → 🇬🇧 London (LON)](/docs/network/latency/pairs/par-lon-rtt) (**6.4 ms**) — Ultra-Low | | Slowest Route | [🇫🇷 Paris (PAR) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/par-syd-rtt) (**249.7 ms**) | | Average RTT | **112.9 ms** | | Average Jitter | **0.85 ms** | | Average Packet Loss | **0.05%** | | Best Fiber Efficiency | **83.2%** | | Intra-Region Peers | 6 PoPs in Europe | | 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 Paris sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **6.4 ms** (London (LON)) to **44.7 ms** (Moscow (MOW)). Paris is a major French interconnection market on the Northwest European corridor, with dense national and pan-European fiber paths. ## Outbound Latency from Paris (PAR) Round-trip time in milliseconds **from Paris** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇬🇧 London (LON) | **[6.4](/docs/network/latency/pairs/par-lon-rtt)** | 3.37 ms | 52.7% | 0.12 ms | 0% | Ultra-Low | | 🇳🇱 Amsterdam (AMS) | **[7](/docs/network/latency/pairs/par-ams-rtt)** | 4.22 ms | 60.3% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[7.6](/docs/network/latency/pairs/par-fra-rtt)** | 4.7 ms | 61.8% | 0.12 ms | 0.1% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[8.9](/docs/network/latency/pairs/par-mrs-rtt)** | 6.47 ms | 72.7% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[15.5](/docs/network/latency/pairs/par-ber-rtt)** | 8.62 ms | 55.6% | 0.13 ms | 0% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[44.7](/docs/network/latency/pairs/par-mow-rtt)** | 24.42 ms | 54.6% | 0.23 ms | 0.2% | Excellent | | 🇺🇸 New York (NYC) | **[68.9](/docs/network/latency/pairs/par-nyc-rtt)** | 57.31 ms | 83.2% | 0.71 ms | 0.05% | Excellent | | 🇺🇸 Ashburn (IAD) | **[75.5](/docs/network/latency/pairs/par-iad-rtt)** | 60.73 ms | 80.4% | 0.86 ms | 0.02% | Excellent | | 🇺🇸 Miami (MIA) | **[106.8](/docs/network/latency/pairs/par-mia-rtt)** | 72.16 ms | 67.6% | 0.65 ms | 0.05% | Good | | 🇺🇸 Seattle (SEA) | **[128](/docs/network/latency/pairs/par-sea-rtt)** | 78.98 ms | 61.7% | 0.85 ms | 0.07% | Good | | 🇺🇸 Los Angeles (LAX) | **[136.5](/docs/network/latency/pairs/par-lax-rtt)** | 89.18 ms | 65.3% | 1.58 ms | 0.11% | Good | | 🇸🇬 Singapore (SIN) | **[150.3](/docs/network/latency/pairs/par-sin-rtt)** | 105.19 ms | 70% | 1.32 ms | 0% | Fair | | 🇭🇰 Hong Kong (HKG) | **[160.1](/docs/network/latency/pairs/par-hkg-rtt)** | 94.48 ms | 59% | 1.29 ms | 0.05% | Fair | | 🇹🇼 Taipei (TPE) | **[171.9](/docs/network/latency/pairs/par-tpe-rtt)** | 96.42 ms | 56.1% | 0.85 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[175.8](/docs/network/latency/pairs/par-gru-rtt)** | 91.83 ms | 52.2% | 1.26 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[180.9](/docs/network/latency/pairs/par-jnb-rtt)** | 85.17 ms | 47.1% | 0.94 ms | 0.17% | Fair | | 🇯🇵 Tokyo (TYO) | **[204.7](/docs/network/latency/pairs/par-tyo-rtt)** | 95.34 ms | 46.6% | 2.17 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[246.4](/docs/network/latency/pairs/par-mel-rtt)** | 164.4 ms | 66.7% | 1.59 ms | 0.17% | Fair | | 🇦🇺 Sydney (SYD) | **[249.7](/docs/network/latency/pairs/par-syd-rtt)** | 166.06 ms | 66.5% | 1.18 ms | 0% | Fair | ## Fastest Routes to Paris (PAR) The 10 fastest measured routes **to Paris**, 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 | 🇬🇧 London (LON) | **[6.4 ms](/docs/network/latency/pairs/lon-par-rtt)** | 6.23 ms | 6.9 ms | 0.15 ms | | 2 | 🇳🇱 Amsterdam (AMS) | **[7 ms](/docs/network/latency/pairs/ams-par-rtt)** | 6.61 ms | 8.02 ms | 0.32 ms | | 3 | 🇩🇪 Frankfurt (FRA) | **[7.6 ms](/docs/network/latency/pairs/fra-par-rtt)** | 7.34 ms | 8.24 ms | 0.23 ms | | 4 | 🇫🇷 Marseille (MRS) | **[8.9 ms](/docs/network/latency/pairs/mrs-par-rtt)** | 8.72 ms | 9.67 ms | 0.16 ms | | 5 | 🇩🇪 Berlin (BER) | **[15.6 ms](/docs/network/latency/pairs/ber-par-rtt)** | 14.9 ms | 17.81 ms | 0.63 ms | | 6 | 🇷🇺 Moscow (MOW) | **[44 ms](/docs/network/latency/pairs/mow-par-rtt)** | 42.02 ms | 49.11 ms | 1.64 ms | | 7 | 🇺🇸 New York (NYC) | **[68.9 ms](/docs/network/latency/pairs/nyc-par-rtt)** | 67.48 ms | 73.26 ms | 1.31 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[76.1 ms](/docs/network/latency/pairs/iad-par-rtt)** | 74.36 ms | 85 ms | 1.76 ms | | 9 | 🇺🇸 Miami (MIA) | **[106.2 ms](/docs/network/latency/pairs/mia-par-rtt)** | 104.35 ms | 111.43 ms | 1.69 ms | | 10 | 🇺🇸 Seattle (SEA) | **[129.2 ms](/docs/network/latency/pairs/sea-par-rtt)** | 126.7 ms | 135.02 ms | 2.13 ms | ## Inbound Latency to Paris (PAR) Round-trip time in milliseconds **from all other PoPs to Paris**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇬🇧 London (LON) | **[6.4](/docs/network/latency/pairs/lon-par-rtt)** | 3.37 ms | 52.7% | 0.12 ms | 0% | Ultra-Low | | 🇳🇱 Amsterdam (AMS) | **[7](/docs/network/latency/pairs/ams-par-rtt)** | 4.22 ms | 60.3% | 0.12 ms | 0.03% | Ultra-Low | | 🇩🇪 Frankfurt (FRA) | **[7.6](/docs/network/latency/pairs/fra-par-rtt)** | 4.7 ms | 61.8% | 0.12 ms | 0% | Ultra-Low | | 🇫🇷 Marseille (MRS) | **[8.9](/docs/network/latency/pairs/mrs-par-rtt)** | 6.47 ms | 72.7% | 0.12 ms | 0% | Ultra-Low | | 🇩🇪 Berlin (BER) | **[15.6](/docs/network/latency/pairs/ber-par-rtt)** | 8.62 ms | 55.3% | 0.16 ms | 0% | Ultra-Low | | 🇷🇺 Moscow (MOW) | **[44](/docs/network/latency/pairs/mow-par-rtt)** | 24.42 ms | 55.5% | 0.29 ms | 0% | Excellent | | 🇺🇸 New York (NYC) | **[68.9](/docs/network/latency/pairs/nyc-par-rtt)** | 57.31 ms | 83.2% | 0.43 ms | 0.15% | Excellent | | 🇺🇸 Ashburn (IAD) | **[76.1](/docs/network/latency/pairs/iad-par-rtt)** | 60.73 ms | 79.8% | 0.7 ms | 0.03% | Excellent | | 🇺🇸 Miami (MIA) | **[106.2](/docs/network/latency/pairs/mia-par-rtt)** | 72.16 ms | 67.9% | 1.07 ms | 0% | Good | | 🇺🇸 Seattle (SEA) | **[129.2](/docs/network/latency/pairs/sea-par-rtt)** | 78.98 ms | 61.1% | 1.22 ms | 0.02% | Good | | 🇺🇸 Los Angeles (LAX) | **[135.9](/docs/network/latency/pairs/lax-par-rtt)** | 89.18 ms | 65.6% | 0.62 ms | 0% | Good | | 🇸🇬 Singapore (SIN) | **[151.4](/docs/network/latency/pairs/sin-par-rtt)** | 105.19 ms | 69.5% | 1.07 ms | 0.12% | Fair | | 🇭🇰 Hong Kong (HKG) | **[159.4](/docs/network/latency/pairs/hkg-par-rtt)** | 94.48 ms | 59.3% | 1.21 ms | 0.07% | Fair | | 🇿🇦 Johannesburg (JNB) | **[164.4](/docs/network/latency/pairs/jnb-par-rtt)** | 85.17 ms | 51.8% | 1.05 ms | 0% | Fair | | 🇹🇼 Taipei (TPE) | **[173.8](/docs/network/latency/pairs/tpe-par-rtt)** | 96.42 ms | 55.5% | 1.13 ms | 0.13% | Fair | | 🇧🇷 São Paulo (GRU) | **[180.2](/docs/network/latency/pairs/gru-par-rtt)** | 91.83 ms | 51% | 1.95 ms | 0.14% | Fair | | 🇯🇵 Tokyo (TYO) | **[204.8](/docs/network/latency/pairs/tyo-par-rtt)** | 95.34 ms | 46.6% | 2.06 ms | 0.03% | Fair | | 🇦🇺 Melbourne (MEL) | **[246.5](/docs/network/latency/pairs/mel-par-rtt)** | 164.4 ms | 66.7% | 1.53 ms | 0.13% | Fair | | 🇦🇺 Sydney (SYD) | **[250.3](/docs/network/latency/pairs/syd-par-rtt)** | 166.06 ms | 66.3% | 2.41 ms | 0% | High | ## Europe Peers Paris is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | --------------------------------------- | ---- | ----------- | -------- | --------- | | [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS | Netherlands | **7** | Ultra-Low | | [🇩🇪 Berlin (BER)](./ber-berlin) | BER | Germany | **15.5** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA | Germany | **7.6** | Ultra-Low | | [🇬🇧 London (LON)](./lon-london) | LON | UK | **6.4** | Ultra-Low | | [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS | France | **8.9** | Ultra-Low | | [🇷🇺 Moscow (MOW)](./mow-moscow) | MOW | Russia | **44.7** | Excellent | ## Frequently Asked Questions **What is the fastest route to Paris?** The fastest measured route to Paris (PAR) is [London (LON) → Paris (PAR)](/docs/network/latency/pairs/lon-par-rtt), averaging **6.4 ms** RTT (Ultra-Low). **What is the fastest route from Paris?** The fastest measured route from Paris (PAR) is [Paris (PAR) → London (LON)](/docs/network/latency/pairs/par-lon-rtt), averaging **6.4 ms** RTT (Ultra-Low). **How well connected is Paris to the Hats Network backbone?** Paris (PAR) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Paris (PAR) → Sydney (SYD)](/docs/network/latency/pairs/par-syd-rtt), averages **249.7 ms** RTT. ## Open Data Measured latency data for Paris (PAR) 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 Paris is published as `par-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [par-lon.pings.csv](/opendata/latency/latest/pairs/par-lon.pings.csv), the 50-probe ICMP echo round for [Paris (PAR) → London (LON)](/docs/network/latency/pairs/par-lon-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/par-paris). - **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. # 🇺🇸 Seattle Ping & Network Latency (SEA) | AS203314 ## 🇺🇸 Seattle (SEA) Seattle is the US Pacific Northwest's primary interconnection hub and a key landing point for trans-Pacific submarine cables to Japan and East Asia. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Seattle (SEA)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Seattle, USA (North America) * **Region:** North America * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 5809844](https://www.geonames.org/5809844) — 47.60621, -122.33207 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** SEA1 * **Upstream transit:** HE / Cogent > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ---------------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇺🇸 Seattle (SEA) → 🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-rtt) (**25.9 ms**) — Ultra-Low | | Slowest Route | [🇺🇸 Seattle (SEA) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/sea-jnb-rtt) (**282.1 ms**) | | Average RTT | **128.5 ms** | | Average Jitter | **1.09 ms** | | Average Packet Loss | **0.03%** | | Best Fiber Efficiency | **88.9%** | | Intra-Region Peers | 4 PoPs in North America | | 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 Seattle sits on Hats Network's **North America** backbone. Measured round-trip times to its 4 intra-region peers range from **25.9 ms** (Los Angeles (LAX)) to **81.7 ms** (Miami (MIA)). Seattle is the Pacific Northwest's primary interconnection hub and a landing point for trans-Pacific cables toward Japan and East Asia. ## Outbound Latency from Seattle (SEA) Round-trip time in milliseconds **from Seattle** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Los Angeles (LAX) | **[25.9](/docs/network/latency/pairs/sea-lax-rtt)** | 15.12 ms | 58.4% | 0.24 ms | 0% | Ultra-Low | | 🇺🇸 New York (NYC) | **[59.5](/docs/network/latency/pairs/sea-nyc-rtt)** | 37.95 ms | 63.8% | 0.66 ms | 0.16% | Excellent | | 🇺🇸 Ashburn (IAD) | **[61.5](/docs/network/latency/pairs/sea-iad-rtt)** | 36.27 ms | 59% | 0.55 ms | 0% | Excellent | | 🇺🇸 Miami (MIA) | **[81.7](/docs/network/latency/pairs/sea-mia-rtt)** | 43.08 ms | 52.7% | 0.84 ms | 0% | Good | | 🇯🇵 Tokyo (TYO) | **[85](/docs/network/latency/pairs/sea-tyo-rtt)** | 75.55 ms | 88.9% | 0.39 ms | 0% | Good | | 🇹🇼 Taipei (TPE) | **[114.7](/docs/network/latency/pairs/sea-tpe-rtt)** | 95.46 ms | 83.2% | 1.36 ms | 0% | Good | | 🇬🇧 London (LON) | **[124.1](/docs/network/latency/pairs/sea-lon-rtt)** | 75.63 ms | 60.9% | 1.38 ms | 0% | Good | | 🇳🇱 Amsterdam (AMS) | **[128.6](/docs/network/latency/pairs/sea-ams-rtt)** | 76.86 ms | 59.8% | 1.46 ms | 0.13% | Good | | 🇫🇷 Paris (PAR) | **[129.2](/docs/network/latency/pairs/sea-par-rtt)** | 78.98 ms | 61.1% | 1.22 ms | 0.02% | Good | | 🇭🇰 Hong Kong (HKG) | **[130.4](/docs/network/latency/pairs/sea-hkg-rtt)** | 102.2 ms | 78.4% | 0.7 ms | 0% | Good | | 🇩🇪 Frankfurt (FRA) | **[133.2](/docs/network/latency/pairs/sea-fra-rtt)** | 80.34 ms | 60.3% | 0.66 ms | 0.11% | Good | | 🇩🇪 Berlin (BER) | **[140.9](/docs/network/latency/pairs/sea-ber-rtt)** | 79.73 ms | 56.6% | 1.36 ms | 0.01% | Good | | 🇫🇷 Marseille (MRS) | **[141.2](/docs/network/latency/pairs/sea-mrs-rtt)** | 85.27 ms | 60.4% | 1.25 ms | 0.04% | Good | | 🇸🇬 Singapore (SIN) | **[151.1](/docs/network/latency/pairs/sea-sin-rtt)** | 127.22 ms | 84.2% | 1.4 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[155.7](/docs/network/latency/pairs/sea-gru-rtt)** | 106.76 ms | 68.6% | 1.76 ms | 0% | Fair | | 🇦🇺 Sydney (SYD) | **[161.3](/docs/network/latency/pairs/sea-syd-rtt)** | 121.96 ms | 75.6% | 1.49 ms | 0% | Fair | | 🇷🇺 Moscow (MOW) | **[164.6](/docs/network/latency/pairs/sea-mow-rtt)** | 82.23 ms | 50% | 1.42 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[170.1](/docs/network/latency/pairs/sea-mel-rtt)** | 128.93 ms | 75.8% | 0.98 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[282.1](/docs/network/latency/pairs/sea-jnb-rtt)** | 161.61 ms | 57.3% | 1.53 ms | 0.15% | High | ## Fastest Routes to Seattle (SEA) The 10 fastest measured routes **to Seattle**, 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 | 🇺🇸 Los Angeles (LAX) | **[26.9 ms](/docs/network/latency/pairs/lax-sea-rtt)** | 25.5 ms | 29.88 ms | 1.13 ms | | 2 | 🇺🇸 New York (NYC) | **[58.7 ms](/docs/network/latency/pairs/nyc-sea-rtt)** | 56.64 ms | 67.85 ms | 2.09 ms | | 3 | 🇺🇸 Ashburn (IAD) | **[62.3 ms](/docs/network/latency/pairs/iad-sea-rtt)** | 59.37 ms | 75.24 ms | 2.67 ms | | 4 | 🇺🇸 Miami (MIA) | **[81.9 ms](/docs/network/latency/pairs/mia-sea-rtt)** | 78.54 ms | 93.5 ms | 3.48 ms | | 5 | 🇯🇵 Tokyo (TYO) | **[84.8 ms](/docs/network/latency/pairs/tyo-sea-rtt)** | 81.06 ms | 94.31 ms | 2.93 ms | | 6 | 🇹🇼 Taipei (TPE) | **[115.8 ms](/docs/network/latency/pairs/tpe-sea-rtt)** | 111.75 ms | 128.63 ms | 4.07 ms | | 7 | 🇬🇧 London (LON) | **[123.2 ms](/docs/network/latency/pairs/lon-sea-rtt)** | 121.09 ms | 129.68 ms | 1.95 ms | | 8 | 🇫🇷 Paris (PAR) | **[128 ms](/docs/network/latency/pairs/par-sea-rtt)** | 123.76 ms | 137.5 ms | 3.51 ms | | 9 | 🇳🇱 Amsterdam (AMS) | **[130.2 ms](/docs/network/latency/pairs/ams-sea-rtt)** | 123.59 ms | 144.11 ms | 5.22 ms | | 10 | 🇭🇰 Hong Kong (HKG) | **[131.6 ms](/docs/network/latency/pairs/hkg-sea-rtt)** | 125.78 ms | 162.34 ms | 6.2 ms | ## Inbound Latency to Seattle (SEA) Round-trip time in milliseconds **from all other PoPs to Seattle**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇺🇸 Los Angeles (LAX) | **[26.9](/docs/network/latency/pairs/lax-sea-rtt)** | 15.12 ms | 56.2% | 0.3 ms | 0.13% | Ultra-Low | | 🇺🇸 New York (NYC) | **[58.7](/docs/network/latency/pairs/nyc-sea-rtt)** | 37.95 ms | 64.7% | 0.35 ms | 0.11% | Excellent | | 🇺🇸 Ashburn (IAD) | **[62.3](/docs/network/latency/pairs/iad-sea-rtt)** | 36.27 ms | 58.2% | 0.44 ms | 0.12% | Excellent | | 🇺🇸 Miami (MIA) | **[81.9](/docs/network/latency/pairs/mia-sea-rtt)** | 43.08 ms | 52.6% | 0.47 ms | 0.1% | Good | | 🇯🇵 Tokyo (TYO) | **[84.8](/docs/network/latency/pairs/tyo-sea-rtt)** | 75.55 ms | 89.1% | 0.77 ms | 0.06% | Good | | 🇹🇼 Taipei (TPE) | **[115.8](/docs/network/latency/pairs/tpe-sea-rtt)** | 95.46 ms | 82.4% | 0.97 ms | 0.15% | Good | | 🇬🇧 London (LON) | **[123.2](/docs/network/latency/pairs/lon-sea-rtt)** | 75.63 ms | 61.4% | 0.95 ms | 0% | Good | | 🇫🇷 Paris (PAR) | **[128](/docs/network/latency/pairs/par-sea-rtt)** | 78.98 ms | 61.7% | 0.85 ms | 0.07% | Good | | 🇳🇱 Amsterdam (AMS) | **[130.2](/docs/network/latency/pairs/ams-sea-rtt)** | 76.86 ms | 59% | 1.26 ms | 0.04% | Good | | 🇭🇰 Hong Kong (HKG) | **[131.6](/docs/network/latency/pairs/hkg-sea-rtt)** | 102.2 ms | 77.7% | 0.82 ms | 0.05% | Good | | 🇩🇪 Frankfurt (FRA) | **[135.2](/docs/network/latency/pairs/fra-sea-rtt)** | 80.34 ms | 59.4% | 0.98 ms | 0.16% | Good | | 🇩🇪 Berlin (BER) | **[139.7](/docs/network/latency/pairs/ber-sea-rtt)** | 79.73 ms | 57.1% | 1.63 ms | 0.2% | Good | | 🇫🇷 Marseille (MRS) | **[141.7](/docs/network/latency/pairs/mrs-sea-rtt)** | 85.27 ms | 60.2% | 1.19 ms | 0.12% | Good | | 🇸🇬 Singapore (SIN) | **[151.5](/docs/network/latency/pairs/sin-sea-rtt)** | 127.22 ms | 84% | 1.11 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[155.9](/docs/network/latency/pairs/gru-sea-rtt)** | 106.76 ms | 68.5% | 1.54 ms | 0.19% | Fair | | 🇦🇺 Sydney (SYD) | **[161.9](/docs/network/latency/pairs/syd-sea-rtt)** | 121.96 ms | 75.3% | 1.74 ms | 0.03% | Fair | | 🇷🇺 Moscow (MOW) | **[164.8](/docs/network/latency/pairs/mow-sea-rtt)** | 82.23 ms | 49.9% | 0.99 ms | 0% | Fair | | 🇦🇺 Melbourne (MEL) | **[172.1](/docs/network/latency/pairs/mel-sea-rtt)** | 128.93 ms | 74.9% | 1.49 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[281.2](/docs/network/latency/pairs/jnb-sea-rtt)** | 161.61 ms | 57.5% | 1.91 ms | 0.11% | High | ## North America Peers Seattle is one of 5 Hats Network PoPs in **North America**. Intra-region routes offer the lowest latency and highest path diversity. | PoP | Code | Country | RTT (ms) | Tier | | ------------------------------------------- | ---- | ------- | -------- | --------- | | [🇺🇸 Ashburn (IAD)](./iad-ashburn) | IAD | USA | **61.5** | Excellent | | [🇺🇸 Los Angeles (LAX)](./lax-los-angeles) | LAX | USA | **25.9** | Ultra-Low | | [🇺🇸 Miami (MIA)](./mia-miami) | MIA | USA | **81.7** | Good | | [🇺🇸 New York (NYC)](./nyc-new-york) | NYC | USA | **59.5** | Excellent | ## Frequently Asked Questions **What is the fastest route to Seattle?** The fastest measured route to Seattle (SEA) is [Los Angeles (LAX) → Seattle (SEA)](/docs/network/latency/pairs/lax-sea-rtt), averaging **26.9 ms** RTT (Ultra-Low). **What is the fastest route from Seattle?** The fastest measured route from Seattle (SEA) is [Seattle (SEA) → Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-rtt), averaging **25.9 ms** RTT (Ultra-Low). **How well connected is Seattle to the Hats Network backbone?** Seattle (SEA) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Seattle (SEA) → Johannesburg (JNB)](/docs/network/latency/pairs/sea-jnb-rtt), averages **282.1 ms** RTT. ## Open Data Measured latency data for Seattle (SEA) 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 Seattle is published as `sea-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [sea-lax.pings.csv](/opendata/latency/latest/pairs/sea-lax.pings.csv), the 50-probe ICMP echo round for [Seattle (SEA) → Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-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/sea-seattle). - **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. # 🇸🇬 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-.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. # 🇦🇺 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-.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. # Latency Coordinates & Fiber Model Inputs This document defines the geographic inputs, physical constants, engineering assumptions, and evidence boundaries used by the Hats Network latency model. The complete equation derivation and numerical reconciliation are maintained separately on the [theoretical latency formula verification page](/docs/network/latency/theoretical-latency-verification). > **A city reference, not a facility address** > > Published coordinates identify the GeoNames city centre. They deliberately do not reveal a router, > carrier hotel, cable landing station, or other private infrastructure location. The resulting > value is a city-to-city physical reference, not a reconstruction of the production fiber route. ## 1. Resolving the theoretical physical location Each PoP already has a public city name and ISO 3166-1 alpha-2 country code. Our coordinate refresh process sends those two values to the [GeoNames Search Webservice](https://www.geonames.org/export/geonames-search.html) with the following constraints: | Parameter | Value | Purpose | | -------------- | -------------------- | --------------------------------------------------------- | | `name_equals` | Public PoP city name | Prefer an exact toponym or alternate-name match | | `country` | ISO country code | Prevent collisions such as Paris, France vs. Paris, Texas | | `featureClass` | `P` | Restrict results to populated places | | `style` | `FULL` | Return identity and location fields needed for validation | | `maxRows` | `20` | Permit local disambiguation when names are shared | If an exact query returns no result, the resolver retries a required-name search. It then normalizes diacritics, verifies the country and populated-place class, and chooses the highest-population exact name or alternate-name match. This handles examples such as **São Paulo**, **Frankfurt → Frankfurt am Main**, and **New York → New York City** without using a private datacenter address. The resolved snapshot stores the GeoNames identifier, canonical place name, feature code, latitude, longitude, source, date, and attribution. It can be refreshed with `pnpm --filter @hatsnet/docs geonames:refresh` when `GEONAMES_USERNAME` is available. Normal builds consume the checked snapshot, so an external rate limit cannot make latency pages non-reproducible. > Interactive content is available on the canonical HTML page. GeoNames data is published under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). The coordinate snapshot is a public geographic reference and is kept separate from operational topology data. ## 2. Model inputs and engineering evidence The model keeps measured constants, published material properties, and explicit engineering assumptions separate: | Input | Model value | Role and evidence | | -------------------------- | ---------------: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Earth model | WGS-84 ellipsoid | The inverse geodesic uses Charles F. F. Karney's robust [Algorithms for geodesics](https://doi.org/10.1007/s00190-012-0578-z) | | Vacuum light speed | 299,792.458km/s | Exact physical constant used for the absolute propagation floor | | Standard fiber group index | 1.4679 | Conventional single-mode reference from Corning's [fiber latency white paper](https://www.corning.com/media/worldwide/coc/documents/Fiber/white-paper/WP8080_03-11.pdf) | | Low-latency group index | 1.4620 | Optimistic SMF-28 ULL material comparison from the same Corning paper | | Optical path allowance | 1.05× | Transparent engineering reference for slack and small route deviations | | Attenuation reference | 0.20dB/km | Conservative long-haul single-mode planning value | | Optical span | 80km | Lower edge of the 80–120km range in [Cisco's long-haul design guide](https://www.cisco.com/c/en/us/td/docs/optical/ron/4-0/solution/guide/ron-solution-guide-40/deployment-topologies/r-long-haul-topology.html) | | Amplifier transit delay | 0.05µs per pass | Rounded from the roughly 10m equivalent fiber length described by the [GÉANT transport report](https://www.geant3.archive.geant.org/Media%20Library/GN3-13-109_DJ1-1-3_Transport-Network-Technologies-and-Operations.pdf) | | Mapped-fiber reference | 1.33× | Median conduit-to-geodesic comparison reported in [Dissecting Latency in the Internet's Fiber Infrastructure](https://arxiv.org/abs/1811.10737) | [ITU-T G.652](https://www.itu.int/rec/T-REC-G.652/) defines the relevant characteristics of standard single-mode fiber. The broader distinction between the speed-of-light baseline and routed-network path inflation is also discussed in [cISP: A Speed-of-Light Internet Service Provider](https://www.usenix.org/conference/nsdi22/presentation/bhattacherjee). > **Formula derivation and numerical verification** > > See [Theoretical Fiber Latency Formula > Verification](/docs/network/latency/theoretical-latency-verification) for the rendered equations, > unit conversions, boundary checks, and the complete Tokyo (TYO) to Sydney (SYD) worked example. ## 3. Separation of model layers * The **geographic layer** resolves city-centre coordinates and the shortest WGS-84 surface distance. * The **physical layer** compares vacuum, conventional silica, and low-latency silica propagation. * The **engineering layer** adds a 5% path allowance and idealized inline-amplifier transit time. * The **research layer** provides a 1.33× mapped-fiber comparison without treating it as a universal route prediction. * The **comparison layer** relates the published RTT to the standard-fiber physical floor. Attenuation does not directly reduce propagation speed. It determines optical power loss and the resulting span and amplifier count. Vendor-specific transponder, FEC, OTN switching, router, serialization, and queueing delays remain outside the universal lower-bound model. ## 4. Estimated stability indicators Route pages also show estimated jitter, packet-loss, percentile, and 24-hour/7-day/30-day trend indicators. They follow the latency matrix publication cycle and provide a consistent basis for comparing relative route stability. These indicators are suitable for route comparison and planning context. They are not an outage record or an SLA measurement. ## 5. Interpretation checklist * Use **vacuum RTT** only as an absolute law-of-physics reference. * Use **fiber RTT** as the shortest possible RTT through standard silica along the WGS-84 geodesic. * Use **engineering floor** as a transparent low-latency optical design reference with small cable and amplifier allowances. * Use **1.33× mapped-fiber RTT** as a research comparison, not as a universal route prediction. * Compare **efficiency** across routes only after considering city-centre coordinates, submarine cable geography, routing policy, and normal measurement variation. * Do not interpret any value on these pages as an SLA or as disclosure of a production facility or cable path. For the complete calculation, open the [formula verification page](/docs/network/latency/theoretical-latency-verification). For current values, return to the [global backbone latency matrix](/docs/network/latency), browse [latency by PoP](/docs/network/latency), or compare individual [city-pair ping and RTT pages](/docs/network/latency/pairs). --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/theoretical-fiber-latency). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # Theoretical Fiber Latency Formula Verification This page independently reconciles the equations used by the latency-page generator with a worked **Tokyo (TYO) → Sydney (SYD)** example. It starts with GeoNames city-centre coordinates, carries units through every calculation, and uses a fixed 101.7ms RTT fixture captured on July 18, 2026. Keeping the fixture fixed separates mathematical regression checks from routine latency-matrix refreshes. > **Verification scope** > > This is a reproducibility check for the public theoretical model. It verifies the mathematics and > implementation outputs; it does not attempt to reconstruct a deployed cable path. Read [Latency > Coordinates & Fiber Model Inputs](/docs/network/latency/theoretical-fiber-latency) for coordinate > resolution, source selection, and engineering assumptions. ## Symbols and reference inputs | Symbol | Meaning | Verification value | | --------- | ---------------------------------- | ----------------------------------: | | $A$ | Tokyo GeoNames city centre | $35.68950^\circ,\ 139.69171^\circ$ | | $B$ | Sydney GeoNames city centre | $-33.86785^\circ,\ 151.20732^\circ$ | | $d_g$ | WGS-84 inverse-geodesic distance | $7\,792.8\ \mathrm{km}$ | | $c$ | Speed of light in vacuum | $299\,792.458\ \mathrm{km\,s^{-1}}$ | | $n_s$ | Standard-fiber group index | $1.4679$ | | $n_u$ | Low-latency-fiber group index | $1.4620$ | | $\lambda$ | Engineering path multiplier | $1.05$ | | $\alpha$ | Attenuation reference | $0.20\ \mathrm{dB\,km^{-1}}$ | | $S$ | Maximum modeled optical span | $80\ \mathrm{km}$ | | $\tau_a$ | One-pass amplifier transit delay | $0.05\ \mathrm{\mu s}$ | | $RTT_p$ | Reference RTT fixture (2026-07-18) | $101.7\ \mathrm{ms}$ | ## 1. WGS-84 geodesic verification The implementation solves the inverse geodesic on the WGS-84 ellipsoid: $$ d_g = \operatorname{InverseGeodesic}_{\mathrm{WGS84}}(A,B) = 7\,792.8\ \mathrm{km} $$ This avoids the distance error introduced by treating Earth as a perfect sphere. The returned surface distance is the geographic lower-bound input for every later step. ## 2. Vacuum propagation floor Round-trip propagation traverses the distance twice. Multiplying by $10^3$ converts seconds to milliseconds: $$ \begin{aligned} RTT_{\mathrm{vac}} &= \frac{2d_g}{c} \times 10^3 \\ &= \frac{2(7\,792.8\ \mathrm{km})} {299\,792.458\ \mathrm{km\,s^{-1}}} \times 10^3\ \mathrm{ms\,s^{-1}} \\ &= 51.99\ \mathrm{ms} \end{aligned} $$ The kilometer units cancel, leaving seconds before the final conversion to milliseconds. ## 3. Silica propagation floors The group velocity of light in fiber is: $$ v_g = \frac{c}{n_g} $$ For standard single-mode fiber: $$ \begin{aligned} RTT_{\mathrm{fiber}} &= \frac{2d_g n_s}{c} \times 10^3 \\ &= \frac{2(7\,792.8)(1.4679)} {299\,792.458} \times 10^3 \\ &= 76.31\ \mathrm{ms} \end{aligned} $$ For the optimistic low-latency material comparison: $$ \begin{aligned} RTT_{\mathrm{ULL}} &= \frac{2d_g n_u}{c} \times 10^3 \\ &= \frac{2(7\,792.8)(1.4620)} {299\,792.458} \times 10^3 \\ &= 76.01\ \mathrm{ms} \end{aligned} $$ The required physical ordering is therefore: $$ RTT_{\mathrm{vac}} < RTT_{\mathrm{ULL}} < RTT_{\mathrm{fiber}} $$ ## 4. Engineering path, attenuation, and amplifiers The transparent engineering reference applies the explicit path multiplier: $$ \begin{aligned} d_e &= \lambda d_g \\ &= 1.05(7\,792.8) \\ &= 8\,182.5\ \mathrm{km} \end{aligned} $$ Attenuation determines optical power loss: $$ \begin{aligned} L_{\mathrm{dB}} &= \alpha d_e \\ &= (0.20\ \mathrm{dB\,km^{-1}}) (8\,182.5\ \mathrm{km}) \\ &= 1\,636.5\ \mathrm{dB} \end{aligned} $$ The span and inline-amplifier counts are: $$ \begin{aligned} N_{\mathrm{span}} &= \left\lceil \frac{d_e}{S} \right\rceil = \left\lceil \frac{8\,182.5}{80} \right\rceil = 103 \\ N_{\mathrm{amp}} &= \max(0,N_{\mathrm{span}}-1) = 102 \end{aligned} $$ The amplifier contribution must be converted from microseconds to milliseconds: $$ \begin{aligned} RTT_{\mathrm{amp}} &= 2N_{\mathrm{amp}}\tau_a \\ &= 2(102)(0.05\ \mathrm{\mu s}) \\ &= 10.2\ \mathrm{\mu s} = 0.0102\ \mathrm{ms} \end{aligned} $$ The complete engineering floor is: $$ \begin{aligned} RTT_{\mathrm{eng}} &= \frac{2d_e n_s}{c} \times 10^3 + RTT_{\mathrm{amp}} \\ &= \frac{2(8\,182.5)(1.4679)} {299\,792.458} \times 10^3 + 0.0102 \\ &= 80.14\ \mathrm{ms} \end{aligned} $$ Attenuation is absent from the propagation-speed term. It affects the model through $N_{\mathrm{span}}$ and $N_{\mathrm{amp}}$, which is dimensionally and physically distinct from group velocity. ## 5. Mapped-fiber research reference The separate 1.33× research comparison is: $$ \begin{aligned} RTT_{\mathrm{mapped}} &= 1.33RTT_{\mathrm{fiber}} \\ &= 1.33(76.31\ \mathrm{ms}) \\ &= 101.50\ \mathrm{ms} \end{aligned} $$ This reference is close to the fixed Tokyo-to-Sydney RTT fixture, but it remains a comparison factor rather than a claimed cable length. ## 6. Efficiency and latency inflation Using the fixed $101.7\ \mathrm{ms}$ verification RTT: $$ \begin{aligned} \eta &= 100\frac{RTT_{\mathrm{fiber}}}{RTT_p} \\ &= 100\frac{76.31}{101.7} \\ &= 75.03\% \approx 75.0\% \end{aligned} $$ $$ \begin{aligned} I &= \frac{RTT_p}{RTT_{\mathrm{fiber}}} \\ &= \frac{101.7}{76.31} \\ &= 1.3327 \approx 1.33 \end{aligned} $$ The two comparison metrics are reciprocal after converting efficiency from percent to a ratio: $$ \frac{\eta}{100} = \frac{1}{I} $$ ## 7. Implementation reconciliation | Output | Formula result | Expected implementation output | Difference | | ---------------------- | -------------: | -----------------------------: | ---------: | | WGS-84 distance | 7,792.8km | 7,792.8km | 0.0km | | Vacuum RTT | 51.99ms | 51.99ms | 0.00ms | | Standard-fiber RTT | 76.31ms | 76.31ms | 0.00ms | | Low-latency-fiber RTT | 76.01ms | 76.01ms | 0.00ms | | Engineering distance | 8,182.5km | 8,182.5km | 0.0km | | Engineering RTT | 80.14ms | 80.14ms | 0.00ms | | Mapped-fiber reference | 101.50ms | 101.50ms | 0.00ms | | Inline amplifiers | 102 | 102 | 0 | | Amplifier RTT | 0.0102ms | 0.0102ms | 0.0000ms | | Fiber efficiency | 75.0% | 75.0% | 0.0pp | | Latency inflation | 1.33× | 1.33× | 0.00× | ## 8. Boundary checks The implementation and its automated tests enforce these invariants: $$ d_g \ge 0 $$ $$ RTT_{\mathrm{vac}} < RTT_{\mathrm{ULL}} < RTT_{\mathrm{fiber}} < RTT_{\mathrm{eng}} $$ $$ N_{\mathrm{span}} \ge 1, \qquad N_{\mathrm{amp}} = N_{\mathrm{span}} - 1 $$ $$ RTT_{\mathrm{amp}} \ge 0, \qquad \eta > 0, \qquad I > 0 $$ If a future constant, coordinate, or rounding rule changes, the reconciliation test must change with it. This prevents the rendered explanation from silently diverging from the generator implementation. Continue to [Latency Coordinates & Fiber Model Inputs](/docs/network/latency/theoretical-fiber-latency), compare the live [Tokyo (TYO) → Sydney (SYD) route](/docs/network/latency/pairs/tyo-syd-rtt), or return to the [global latency matrix](/docs/network/latency). --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/theoretical-latency-verification). - **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/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. # 🇹🇼 Taipei Ping & Network Latency (TPE) | AS203314 ## 🇹🇼 Taipei (TPE) Taipei is Taiwan's primary internet hub, providing strategic connectivity between East and Southeast Asia on Hats Network's regional backbone. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Taipei (TPE)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Taipei, Taiwan (Asia Pacific) * **Region:** Asia Pacific * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 1668341](https://www.geonames.org/1668341) — 25.05306, 121.52639 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** TPE2 * **Upstream transit:** HE Only * **Peering / IX:** STUIX - Taipei > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | ------------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇹🇼 Taipei (TPE) → 🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt) (**15.5 ms**) — Ultra-Low | | Slowest Route | [🇹🇼 Taipei (TPE) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/tpe-jnb-rtt) (**331 ms**) | | Average RTT | **152.6 ms** | | Average Jitter | **1.24 ms** | | Average Packet Loss | **0.06%** | | Best Fiber Efficiency | **82.4%** | | 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 Taipei sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **15.5 ms** (Hong Kong (HKG)) to **142 ms** (Melbourne (MEL)). Taipei sits on the East Asia corridor between Tokyo, Hong Kong and Singapore; intra-Asia systems such as APG and FASTER connect Taiwan with Japan and Hong Kong. ## Outbound Latency from Taipei (TPE) Round-trip time in milliseconds **from Taipei** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇭🇰 Hong Kong (HKG) | **[15.5](/docs/network/latency/pairs/tpe-hkg-rtt)** | 7.94 ms | 51.2% | 0.16 ms | 0.02% | Ultra-Low | | 🇯🇵 Tokyo (TYO) | **[31.9](/docs/network/latency/pairs/tpe-tyo-rtt)** | 20.58 ms | 64.5% | 0.23 ms | 0.08% | Excellent | | 🇸🇬 Singapore (SIN) | **[44.3](/docs/network/latency/pairs/tpe-sin-rtt)** | 31.77 ms | 71.7% | 0.22 ms | 0.11% | Excellent | | 🇺🇸 Seattle (SEA) | **[115.8](/docs/network/latency/pairs/tpe-sea-rtt)** | 95.46 ms | 82.4% | 0.97 ms | 0.15% | Good | | 🇺🇸 Los Angeles (LAX) | **[132](/docs/network/latency/pairs/tpe-lax-rtt)** | 107 ms | 81.1% | 1.31 ms | 0% | Good | | 🇷🇺 Moscow (MOW) | **[132.7](/docs/network/latency/pairs/tpe-mow-rtt)** | 72.16 ms | 54.4% | 0.68 ms | 0.09% | Good | | 🇦🇺 Sydney (SYD) | **[133.2](/docs/network/latency/pairs/tpe-syd-rtt)** | 70.88 ms | 53.2% | 1.48 ms | 0% | Good | | 🇦🇺 Melbourne (MEL) | **[142](/docs/network/latency/pairs/tpe-mel-rtt)** | 72.25 ms | 50.9% | 1.12 ms | 0.08% | Good | | 🇩🇪 Berlin (BER) | **[158.6](/docs/network/latency/pairs/tpe-ber-rtt)** | 87.84 ms | 55.4% | 1.84 ms | 0.09% | Fair | | 🇩🇪 Frankfurt (FRA) | **[166](/docs/network/latency/pairs/tpe-fra-rtt)** | 91.96 ms | 55.4% | 1.67 ms | 0.13% | Fair | | 🇳🇱 Amsterdam (AMS) | **[166.5](/docs/network/latency/pairs/tpe-ams-rtt)** | 92.72 ms | 55.7% | 0.78 ms | 0% | Fair | | 🇺🇸 Ashburn (IAD) | **[171.6](/docs/network/latency/pairs/tpe-iad-rtt)** | 123.78 ms | 72.1% | 1.7 ms | 0% | Fair | | 🇬🇧 London (LON) | **[173](/docs/network/latency/pairs/tpe-lon-rtt)** | 95.97 ms | 55.5% | 1.51 ms | 0.16% | Fair | | 🇫🇷 Paris (PAR) | **[173.8](/docs/network/latency/pairs/tpe-par-rtt)** | 96.42 ms | 55.5% | 1.13 ms | 0.13% | Fair | | 🇺🇸 New York (NYC) | **[174.2](/docs/network/latency/pairs/tpe-nyc-rtt)** | 122.89 ms | 70.5% | 1.24 ms | 0% | Fair | | 🇫🇷 Marseille (MRS) | **[179.5](/docs/network/latency/pairs/tpe-mrs-rtt)** | 98.2 ms | 54.7% | 1.4 ms | 0% | Fair | | 🇺🇸 Miami (MIA) | **[185.7](/docs/network/latency/pairs/tpe-mia-rtt)** | 136.3 ms | 73.4% | 1.27 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[273](/docs/network/latency/pairs/tpe-gru-rtt)** | 184.29 ms | 67.5% | 2.95 ms | 0.03% | High | | 🇿🇦 Johannesburg (JNB) | **[331](/docs/network/latency/pairs/tpe-jnb-rtt)** | 112.87 ms | 34.1% | 1.92 ms | 0% | High | ## Fastest Routes to Taipei (TPE) The 10 fastest measured routes **to Taipei**, 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) | **[14.7 ms](/docs/network/latency/pairs/hkg-tpe-rtt)** | 13.95 ms | 17.24 ms | 0.72 ms | | 2 | 🇯🇵 Tokyo (TYO) | **[32.3 ms](/docs/network/latency/pairs/tyo-tpe-rtt)** | 31.1 ms | 36.28 ms | 0.96 ms | | 3 | 🇸🇬 Singapore (SIN) | **[45.8 ms](/docs/network/latency/pairs/sin-tpe-rtt)** | 43.12 ms | 50.4 ms | 1.72 ms | | 4 | 🇺🇸 Seattle (SEA) | **[114.7 ms](/docs/network/latency/pairs/sea-tpe-rtt)** | 109.75 ms | 137.83 ms | 5.07 ms | | 5 | 🇦🇺 Sydney (SYD) | **[131.7 ms](/docs/network/latency/pairs/syd-tpe-rtt)** | 126.36 ms | 151.94 ms | 4.46 ms | | 6 | 🇷🇺 Moscow (MOW) | **[132.1 ms](/docs/network/latency/pairs/mow-tpe-rtt)** | 126.75 ms | 145.67 ms | 4.52 ms | | 7 | 🇺🇸 Los Angeles (LAX) | **[132.9 ms](/docs/network/latency/pairs/lax-tpe-rtt)** | 128.75 ms | 148.78 ms | 4.24 ms | | 8 | 🇦🇺 Melbourne (MEL) | **[143.2 ms](/docs/network/latency/pairs/mel-tpe-rtt)** | 135 ms | 166.26 ms | 7.11 ms | | 9 | 🇩🇪 Berlin (BER) | **[156.8 ms](/docs/network/latency/pairs/ber-tpe-rtt)** | 150.23 ms | 174.22 ms | 5.07 ms | | 10 | 🇩🇪 Frankfurt (FRA) | **[163.8 ms](/docs/network/latency/pairs/fra-tpe-rtt)** | 159.37 ms | 176 ms | 3.63 ms | ## Inbound Latency to Taipei (TPE) Round-trip time in milliseconds **from all other PoPs to Taipei**. 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) | **[14.7](/docs/network/latency/pairs/hkg-tpe-rtt)** | 7.94 ms | 54% | 0.14 ms | 0.08% | Ultra-Low | | 🇯🇵 Tokyo (TYO) | **[32.3](/docs/network/latency/pairs/tyo-tpe-rtt)** | 20.58 ms | 63.7% | 0.34 ms | 0% | Excellent | | 🇸🇬 Singapore (SIN) | **[45.8](/docs/network/latency/pairs/sin-tpe-rtt)** | 31.77 ms | 69.4% | 0.25 ms | 0% | Excellent | | 🇺🇸 Seattle (SEA) | **[114.7](/docs/network/latency/pairs/sea-tpe-rtt)** | 95.46 ms | 83.2% | 1.36 ms | 0% | Good | | 🇦🇺 Sydney (SYD) | **[131.7](/docs/network/latency/pairs/syd-tpe-rtt)** | 70.88 ms | 53.8% | 1.51 ms | 0% | Good | | 🇷🇺 Moscow (MOW) | **[132.1](/docs/network/latency/pairs/mow-tpe-rtt)** | 72.16 ms | 54.6% | 1.49 ms | 0% | Good | | 🇺🇸 Los Angeles (LAX) | **[132.9](/docs/network/latency/pairs/lax-tpe-rtt)** | 107 ms | 80.5% | 0.87 ms | 0.08% | Good | | 🇦🇺 Melbourne (MEL) | **[143.2](/docs/network/latency/pairs/mel-tpe-rtt)** | 72.25 ms | 50.5% | 0.65 ms | 0% | Good | | 🇩🇪 Berlin (BER) | **[156.8](/docs/network/latency/pairs/ber-tpe-rtt)** | 87.84 ms | 56% | 1.45 ms | 0.17% | Fair | | 🇩🇪 Frankfurt (FRA) | **[163.8](/docs/network/latency/pairs/fra-tpe-rtt)** | 91.96 ms | 56.1% | 1.28 ms | 0.04% | Fair | | 🇳🇱 Amsterdam (AMS) | **[168.7](/docs/network/latency/pairs/ams-tpe-rtt)** | 92.72 ms | 55% | 1.29 ms | 0.11% | Fair | | 🇫🇷 Paris (PAR) | **[171.9](/docs/network/latency/pairs/par-tpe-rtt)** | 96.42 ms | 56.1% | 0.85 ms | 0% | Fair | | 🇺🇸 Ashburn (IAD) | **[172.3](/docs/network/latency/pairs/iad-tpe-rtt)** | 123.78 ms | 71.8% | 1.59 ms | 0.04% | Fair | | 🇺🇸 New York (NYC) | **[173.4](/docs/network/latency/pairs/nyc-tpe-rtt)** | 122.89 ms | 70.9% | 1.21 ms | 0% | Fair | | 🇬🇧 London (LON) | **[173.8](/docs/network/latency/pairs/lon-tpe-rtt)** | 95.97 ms | 55.2% | 1.58 ms | 0.09% | Fair | | 🇫🇷 Marseille (MRS) | **[180.9](/docs/network/latency/pairs/mrs-tpe-rtt)** | 98.2 ms | 54.3% | 1.86 ms | 0% | Fair | | 🇺🇸 Miami (MIA) | **[185.1](/docs/network/latency/pairs/mia-tpe-rtt)** | 136.3 ms | 73.6% | 1.17 ms | 0.09% | Fair | | 🇧🇷 São Paulo (GRU) | **[259.1](/docs/network/latency/pairs/gru-tpe-rtt)** | 184.29 ms | 71.1% | 3.01 ms | 0% | High | | 🇿🇦 Johannesburg (JNB) | **[329.8](/docs/network/latency/pairs/jnb-tpe-rtt)** | 112.87 ms | 34.2% | 3.33 ms | 0% | High | ## Asia Pacific Peers Taipei 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 | **15.5** | Ultra-Low | | [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL | Australia | **142** | Good | | [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN | Singapore | **44.3** | Excellent | | [🇦🇺 Sydney (SYD)](./syd-sydney) | SYD | Australia | **133.2** | Good | | [🇯🇵 Tokyo (TYO)](./tyo-tokyo) | TYO | Japan | **31.9** | Excellent | ## Frequently Asked Questions **What is the fastest route to Taipei?** The fastest measured route to Taipei (TPE) is [Hong Kong (HKG) → Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt), averaging **14.7 ms** RTT (Ultra-Low). **What is the fastest route from Taipei?** The fastest measured route from Taipei (TPE) is [Taipei (TPE) → Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt), averaging **15.5 ms** RTT (Ultra-Low). **How well connected is Taipei to the Hats Network backbone?** Taipei (TPE) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Taipei (TPE) → Johannesburg (JNB)](/docs/network/latency/pairs/tpe-jnb-rtt), averages **331 ms** RTT. ## Open Data Measured latency data for Taipei (TPE) 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 Taipei is published as `tpe-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [tpe-hkg.pings.csv](/opendata/latency/latest/pairs/tpe-hkg.pings.csv), the 50-probe ICMP echo round for [Taipei (TPE) → Hong Kong (HKG)](/docs/network/latency/pairs/tpe-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/tpe-taipei). - **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. # 🇯🇵 Tokyo Ping & Network Latency (TYO) | AS203314 ## 🇯🇵 Tokyo (TYO) Tokyo is East Asia's premier internet exchange hub, home to JPNAP and JPIX. Hats Network's Tokyo PoP provides ultra-low latency across the Pacific to North America. Measurement round: `2026-08-16T04:07:28Z`. This page provides round-trip time (RTT) latency metrics between the **Tokyo (TYO)** PoP and every other node on the Hats Network (AS203314) global backbone. ### PoP Highlights * **Location:** Tokyo, Japan (Asia Pacific) * **Region:** Asia Pacific * **Role:** Backbone interconnection point for Hats Network (AS203314) * **Public city reference:** [GeoNames 1850147](https://www.geonames.org/1850147) — 35.68950, 139.69171 * **Coverage:** RTT measurements to 19 other PoPs across 5 continents ### Facility & Interconnection * **Facility:** TYO2 > Interactive content is available on the canonical HTML page. ### Latency Summary | Metric | Value | | --------------------- | --------------------------------------------------------------------------------------------------------- | | Fastest Route | [🇯🇵 Tokyo (TYO) → 🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/tyo-tpe-rtt) (**32.3 ms**) — Excellent | | Slowest Route | [🇯🇵 Tokyo (TYO) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/tyo-jnb-rtt) (**359.2 ms**) | | Average RTT | **154.4 ms** | | Average Jitter | **1.25 ms** | | Average Packet Loss | **0.05%** | | Best Fiber Efficiency | **89.1%** | | 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 Tokyo sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **32.3 ms** (Taipei (TPE)) to **113.9 ms** (Melbourne (MEL)). Tokyo is East Asia's premier exchange hub and a landing point for trans-Pacific systems; within the region, FASTER links Japan with Taiwan. ## Outbound Latency from Tokyo (TYO) Round-trip time in milliseconds **from Tokyo** to all other backbone PoPs, sorted fastest to slowest. | Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇹🇼 Taipei (TPE) | **[32.3](/docs/network/latency/pairs/tyo-tpe-rtt)** | 20.58 ms | 63.7% | 0.34 ms | 0% | Excellent | | 🇭🇰 Hong Kong (HKG) | **[44.8](/docs/network/latency/pairs/tyo-hkg-rtt)** | 28.24 ms | 63% | 0.45 ms | 0.07% | Excellent | | 🇸🇬 Singapore (SIN) | **[69.4](/docs/network/latency/pairs/tyo-sin-rtt)** | 52 ms | 74.9% | 0.62 ms | 0% | Excellent | | 🇺🇸 Seattle (SEA) | **[84.8](/docs/network/latency/pairs/tyo-sea-rtt)** | 75.55 ms | 89.1% | 0.77 ms | 0.06% | Good | | 🇺🇸 Los Angeles (LAX) | **[101.2](/docs/network/latency/pairs/tyo-lax-rtt)** | 86.51 ms | 85.5% | 0.97 ms | 0.02% | Good | | 🇦🇺 Sydney (SYD) | **[101.9](/docs/network/latency/pairs/tyo-syd-rtt)** | 76.31 ms | 74.9% | 0.92 ms | 0.2% | Good | | 🇦🇺 Melbourne (MEL) | **[113.9](/docs/network/latency/pairs/tyo-mel-rtt)** | 79.87 ms | 70.1% | 1.25 ms | 0.05% | Good | | 🇺🇸 Ashburn (IAD) | **[142.9](/docs/network/latency/pairs/tyo-iad-rtt)** | 106.69 ms | 74.7% | 0.69 ms | 0% | Good | | 🇺🇸 New York (NYC) | **[144.6](/docs/network/latency/pairs/tyo-nyc-rtt)** | 106.47 ms | 73.6% | 1.33 ms | 0.17% | Good | | 🇺🇸 Miami (MIA) | **[156.5](/docs/network/latency/pairs/tyo-mia-rtt)** | 117.71 ms | 75.2% | 1.36 ms | 0.14% | Fair | | 🇷🇺 Moscow (MOW) | **[161.7](/docs/network/latency/pairs/tyo-mow-rtt)** | 73.42 ms | 45.4% | 1.62 ms | 0.09% | Fair | | 🇩🇪 Berlin (BER) | **[186.1](/docs/network/latency/pairs/tyo-ber-rtt)** | 87.53 ms | 47% | 1.64 ms | 0% | Fair | | 🇩🇪 Frankfurt (FRA) | **[193.2](/docs/network/latency/pairs/tyo-fra-rtt)** | 91.61 ms | 47.4% | 2.16 ms | 0% | Fair | | 🇳🇱 Amsterdam (AMS) | **[197.4](/docs/network/latency/pairs/tyo-ams-rtt)** | 91.18 ms | 46.2% | 1.09 ms | 0% | Fair | | 🇬🇧 London (LON) | **[202.7](/docs/network/latency/pairs/tyo-lon-rtt)** | 93.84 ms | 46.3% | 0.93 ms | 0% | Fair | | 🇫🇷 Paris (PAR) | **[204.8](/docs/network/latency/pairs/tyo-par-rtt)** | 95.34 ms | 46.6% | 2.06 ms | 0.03% | Fair | | 🇫🇷 Marseille (MRS) | **[205.6](/docs/network/latency/pairs/tyo-mrs-rtt)** | 99.03 ms | 48.2% | 1.86 ms | 0.14% | Fair | | 🇧🇷 São Paulo (GRU) | **[230.5](/docs/network/latency/pairs/tyo-gru-rtt)** | 181.46 ms | 78.7% | 1.53 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[359.2](/docs/network/latency/pairs/tyo-jnb-rtt)** | 132.57 ms | 36.9% | 2.19 ms | 0.05% | High | ## Fastest Routes to Tokyo (TYO) The 10 fastest measured routes **to Tokyo**, 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 | 🇹🇼 Taipei (TPE) | **[31.9 ms](/docs/network/latency/pairs/tpe-tyo-rtt)** | 30.57 ms | 35.67 ms | 1.12 ms | | 2 | 🇭🇰 Hong Kong (HKG) | **[44.9 ms](/docs/network/latency/pairs/hkg-tyo-rtt)** | 42.32 ms | 50.91 ms | 1.82 ms | | 3 | 🇸🇬 Singapore (SIN) | **[68.9 ms](/docs/network/latency/pairs/sin-tyo-rtt)** | 65.47 ms | 78.16 ms | 2.72 ms | | 4 | 🇺🇸 Seattle (SEA) | **[85 ms](/docs/network/latency/pairs/sea-tyo-rtt)** | 81.03 ms | 97.43 ms | 3.15 ms | | 5 | 🇺🇸 Los Angeles (LAX) | **[101.2 ms](/docs/network/latency/pairs/lax-tyo-rtt)** | 97.1 ms | 112.57 ms | 3.72 ms | | 6 | 🇦🇺 Sydney (SYD) | **[101.3 ms](/docs/network/latency/pairs/syd-tyo-rtt)** | 99.25 ms | 108.62 ms | 2.05 ms | | 7 | 🇦🇺 Melbourne (MEL) | **[112 ms](/docs/network/latency/pairs/mel-tyo-rtt)** | 105.34 ms | 140.34 ms | 5.58 ms | | 8 | 🇺🇸 Ashburn (IAD) | **[141.9 ms](/docs/network/latency/pairs/iad-tyo-rtt)** | 136.1 ms | 154.55 ms | 4.32 ms | | 9 | 🇺🇸 New York (NYC) | **[143.1 ms](/docs/network/latency/pairs/nyc-tyo-rtt)** | 136.69 ms | 171.34 ms | 6.58 ms | | 10 | 🇺🇸 Miami (MIA) | **[156.3 ms](/docs/network/latency/pairs/mia-tyo-rtt)** | 149.17 ms | 178.72 ms | 6.19 ms | ## Inbound Latency to Tokyo (TYO) Round-trip time in milliseconds **from all other PoPs to Tokyo**. 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 | | ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- | | 🇹🇼 Taipei (TPE) | **[31.9](/docs/network/latency/pairs/tpe-tyo-rtt)** | 20.58 ms | 64.5% | 0.23 ms | 0.08% | Excellent | | 🇭🇰 Hong Kong (HKG) | **[44.9](/docs/network/latency/pairs/hkg-tyo-rtt)** | 28.24 ms | 62.9% | 0.23 ms | 0.08% | Excellent | | 🇸🇬 Singapore (SIN) | **[68.9](/docs/network/latency/pairs/sin-tyo-rtt)** | 52 ms | 75.5% | 0.41 ms | 0% | Excellent | | 🇺🇸 Seattle (SEA) | **[85](/docs/network/latency/pairs/sea-tyo-rtt)** | 75.55 ms | 88.9% | 0.39 ms | 0% | Good | | 🇺🇸 Los Angeles (LAX) | **[101.2](/docs/network/latency/pairs/lax-tyo-rtt)** | 86.51 ms | 85.5% | 0.82 ms | 0% | Good | | 🇦🇺 Sydney (SYD) | **[101.3](/docs/network/latency/pairs/syd-tyo-rtt)** | 76.31 ms | 75.3% | 0.74 ms | 0% | Good | | 🇦🇺 Melbourne (MEL) | **[112](/docs/network/latency/pairs/mel-tyo-rtt)** | 79.87 ms | 71.3% | 0.86 ms | 0% | Good | | 🇺🇸 Ashburn (IAD) | **[141.9](/docs/network/latency/pairs/iad-tyo-rtt)** | 106.69 ms | 75.2% | 1.23 ms | 0.02% | Good | | 🇺🇸 New York (NYC) | **[143.1](/docs/network/latency/pairs/nyc-tyo-rtt)** | 106.47 ms | 74.4% | 0.8 ms | 0% | Good | | 🇺🇸 Miami (MIA) | **[156.3](/docs/network/latency/pairs/mia-tyo-rtt)** | 117.71 ms | 75.3% | 0.95 ms | 0.03% | Fair | | 🇷🇺 Moscow (MOW) | **[162.2](/docs/network/latency/pairs/mow-tyo-rtt)** | 73.42 ms | 45.3% | 1.92 ms | 0.08% | Fair | | 🇩🇪 Berlin (BER) | **[187.5](/docs/network/latency/pairs/ber-tyo-rtt)** | 87.53 ms | 46.7% | 1.21 ms | 0% | Fair | | 🇩🇪 Frankfurt (FRA) | **[194.5](/docs/network/latency/pairs/fra-tyo-rtt)** | 91.61 ms | 47.1% | 1.29 ms | 0.12% | Fair | | 🇳🇱 Amsterdam (AMS) | **[198.2](/docs/network/latency/pairs/ams-tyo-rtt)** | 91.18 ms | 46% | 1.27 ms | 0.14% | Fair | | 🇬🇧 London (LON) | **[202.9](/docs/network/latency/pairs/lon-tyo-rtt)** | 93.84 ms | 46.2% | 1.61 ms | 0% | Fair | | 🇫🇷 Marseille (MRS) | **[203.8](/docs/network/latency/pairs/mrs-tyo-rtt)** | 99.03 ms | 48.6% | 2.03 ms | 0.18% | Fair | | 🇫🇷 Paris (PAR) | **[204.7](/docs/network/latency/pairs/par-tyo-rtt)** | 95.34 ms | 46.6% | 2.17 ms | 0% | Fair | | 🇧🇷 São Paulo (GRU) | **[230.3](/docs/network/latency/pairs/gru-tyo-rtt)** | 181.46 ms | 78.8% | 2.42 ms | 0% | Fair | | 🇿🇦 Johannesburg (JNB) | **[360.5](/docs/network/latency/pairs/jnb-tyo-rtt)** | 132.57 ms | 36.8% | 2.79 ms | 0.06% | High | ## Asia Pacific Peers Tokyo 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 | **44.8** | Excellent | | [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL | Australia | **113.9** | Good | | [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN | Singapore | **69.4** | Excellent | | [🇦🇺 Sydney (SYD)](./syd-sydney) | SYD | Australia | **101.9** | Good | | [🇹🇼 Taipei (TPE)](./tpe-taipei) | TPE | Taiwan | **32.3** | Excellent | ## Frequently Asked Questions **What is the fastest route to Tokyo?** The fastest measured route to Tokyo (TYO) is [Taipei (TPE) → Tokyo (TYO)](/docs/network/latency/pairs/tpe-tyo-rtt), averaging **31.9 ms** RTT (Excellent). **What is the fastest route from Tokyo?** The fastest measured route from Tokyo (TYO) is [Tokyo (TYO) → Taipei (TPE)](/docs/network/latency/pairs/tyo-tpe-rtt), averaging **32.3 ms** RTT (Excellent). **How well connected is Tokyo to the Hats Network backbone?** Tokyo (TYO) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Tokyo (TYO) → Johannesburg (JNB)](/docs/network/latency/pairs/tyo-jnb-rtt), averages **359.2 ms** RTT. ## Open Data Measured latency data for Tokyo (TYO) 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 Tokyo is published as `tyo-.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [tyo-tpe.pings.csv](/opendata/latency/latest/pairs/tyo-tpe.pings.csv), the 50-probe ICMP echo round for [Tokyo (TYO) → Taipei (TPE)](/docs/network/latency/pairs/tyo-tpe-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/tyo-tokyo). - **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. # Africa Ping & RTT Latency | AS203314 Africa is served by Hats Network's Johannesburg PoP, anchoring Southern African connectivity to the global backbone with the lowest-latency paths via European submarine cable landings. Measurement round: `2026-08-16T04:07:28Z`. ## Africa to Other Regions Lowest-latency paths from this region to every other region. ### To Europe | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇬🇧 [London (LON)](/docs/network/latency/lon-london) | **158** | Fair | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) | **163.2** | Fair | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) | **164.4** | Fair | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) | **166** | Fair | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) | **172** | Fair | ### To North America | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **221.8** | Fair | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **229** | Fair | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **259.9** | High | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **281.2** | High | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **285.5** | High | ### To South America | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **328.7** | High | ### To Asia Pacific | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **311.6** | High | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **318** | High | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **329.8** | High | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **360.5** | High | | 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **406.2** | High | ## PoPs in this Region | PoP | City | Country | | ------------------------------------------------- | ----------------- | ------------ | | **[JNB](/docs/network/latency/jnb-johannesburg)** | 🇿🇦 Johannesburg | South Africa | *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency) or browse by [city pair](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/africa). - **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. # Asia Pacific to South America Ping & RTT | AS203314 The Asia Pacific to South America corridor is the longest on Hats Network's backbone, typically routed via North America or Europe. Sydney, Los Angeles, and São Paulo form key waypoints. Measurement round: `2026-08-16T04:07:28Z`. ## Quick Stats | Metric | Value | | ------------------- | ------------------------------------------------------------------------------------------- | | Fastest Route | **[Tokyo (TYO) → São Paulo (GRU)](/docs/network/latency/pairs/tyo-gru-rtt)** — 230.5 ms | | Slowest Route | **[Singapore (SIN) → São Paulo (GRU)](/docs/network/latency/pairs/sin-gru-rtt)** — 311.4 ms | | Average RTT | **284.1 ms** | | City Pairs Measured | 6 | ## Asia Pacific to South America City-Pair RTT | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ---- | | 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[230.5](/docs/network/latency/pairs/tyo-gru-rtt)** | Fair | | 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[273](/docs/network/latency/pairs/tpe-gru-rtt)** | High | | 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[287.6](/docs/network/latency/pairs/hkg-gru-rtt)** | High | | 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[296.7](/docs/network/latency/pairs/syd-gru-rtt)** | High | | 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[305.3](/docs/network/latency/pairs/mel-gru-rtt)** | High | | 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[311.4](/docs/network/latency/pairs/sin-gru-rtt)** | High | ## Related Regions * [Asia Pacific backbone latency](./asia-pacific) * [South America backbone latency](./south-america) *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/asia-pacific-to-south-america). - **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. # Asia Pacific Ping & RTT Latency | AS203314 Asia Pacific spans Hats Network PoPs in Hong Kong, Singapore, Taipei, Tokyo, Sydney, and Melbourne, covering East Asia, Southeast Asia, and Oceania with dense submarine cable connectivity. Measurement round: `2026-08-16T04:07:28Z`. ## Intra-Asia Pacific RTT Matrix Round-trip times in milliseconds between PoPs within the region. | Route | HKG | MEL | SIN | SYD | TPE | TYO | | ----------------------------------------------------------- | ----- | ----- | ---- | ----- | ----- | ----- | | 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | — | 138.4 | 31.5 | 137.2 | 14.7 | 44.9 | | 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | 138.5 | — | 88.4 | 9.8 | 143.2 | 112 | | 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | 30.8 | 88.6 | — | 94.5 | 45.8 | 68.9 | | 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | 135.7 | 9.8 | 94.5 | — | 131.7 | 101.3 | | 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | 15.5 | 142 | 44.3 | 133.2 | — | 31.9 | | 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | 44.8 | 113.9 | 69.4 | 101.9 | 32.3 | — | ## Asia Pacific to Other Regions Lowest-latency paths from this region to every other region. ### To Europe | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) → 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) | **118.2** | Good | | 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) → 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) | **132.7** | Good | | 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) → 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) | **140.6** | Good | | 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) → 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) | **145.1** | Good | | 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) → 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) | **147.7** | Good | ### To North America | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **84.8** | Good | | 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **101.2** | Good | | 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **115.8** | Good | | 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **131.6** | Good | | 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **132** | Good | ### To South America | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **230.5** | Fair | | 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **273** | High | | 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **287.6** | High | | 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **296.7** | High | | 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **305.3** | High | ### To Africa | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **312.6** | High | | 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **316.7** | High | | 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **331** | High | | 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **359.2** | High | | 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **405.5** | High | ## PoPs in this Region | PoP | City | Country | | ---------------------------------------------- | -------------- | --------- | | **[HKG](/docs/network/latency/hkg-hong-kong)** | 🇭🇰 Hong Kong | Hong Kong | | **[MEL](/docs/network/latency/mel-melbourne)** | 🇦🇺 Melbourne | Australia | | **[SIN](/docs/network/latency/sin-singapore)** | 🇸🇬 Singapore | Singapore | | **[SYD](/docs/network/latency/syd-sydney)** | 🇦🇺 Sydney | Australia | | **[TPE](/docs/network/latency/tpe-taipei)** | 🇹🇼 Taipei | Taiwan | | **[TYO](/docs/network/latency/tyo-tokyo)** | 🇯🇵 Tokyo | Japan | *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency) or browse by [city pair](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/asia-pacific). - **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. # Europe to Asia Pacific Ping & RTT | AS203314 The Europe to Asia Pacific corridor spans the Eurasian landmass and submarine cable systems via the Mediterranean, Red Sea, and Indian Ocean. Marseille and Amsterdam serve as primary departure points for Singapore, Hong Kong, and Tokyo. Measurement round: `2026-08-16T04:07:28Z`. ## Quick Stats | Metric | Value | | ------------------- | ---------------------------------------------------------------------------------------- | | Fastest Route | **[Moscow (MOW) → Hong Kong (HKG)](/docs/network/latency/pairs/mow-hkg-rtt)** — 118.6 ms | | Slowest Route | **[Berlin (BER) → Sydney (SYD)](/docs/network/latency/pairs/ber-syd-rtt)** — 262.1 ms | | Average RTT | **193.2 ms** | | City Pairs Measured | 42 | ## Europe to Asia Pacific City-Pair RTT | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ---- | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[118.6](/docs/network/latency/pairs/mow-hkg-rtt)** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[132.1](/docs/network/latency/pairs/mow-tpe-rtt)** | Good | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[139.6](/docs/network/latency/pairs/mrs-sin-rtt)** | Good | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[144.9](/docs/network/latency/pairs/ber-hkg-rtt)** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[147.3](/docs/network/latency/pairs/mow-sin-rtt)** | Good | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[150.3](/docs/network/latency/pairs/par-sin-rtt)** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[151.4](/docs/network/latency/pairs/fra-sin-rtt)** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[152](/docs/network/latency/pairs/fra-hkg-rtt)** | Fair | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[155.9](/docs/network/latency/pairs/ams-hkg-rtt)** | Fair | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[156.5](/docs/network/latency/pairs/lon-sin-rtt)** | Fair | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[156.8](/docs/network/latency/pairs/ber-tpe-rtt)** | Fair | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[157.6](/docs/network/latency/pairs/ams-sin-rtt)** | Fair | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[158.3](/docs/network/latency/pairs/ber-sin-rtt)** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[160.1](/docs/network/latency/pairs/par-hkg-rtt)** | Fair | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[160.6](/docs/network/latency/pairs/lon-hkg-rtt)** | Fair | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[162.2](/docs/network/latency/pairs/mow-tyo-rtt)** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[163.8](/docs/network/latency/pairs/fra-tpe-rtt)** | Fair | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[166.4](/docs/network/latency/pairs/mrs-hkg-rtt)** | Fair | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[168.7](/docs/network/latency/pairs/ams-tpe-rtt)** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[171.9](/docs/network/latency/pairs/par-tpe-rtt)** | Fair | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[173.8](/docs/network/latency/pairs/lon-tpe-rtt)** | Fair | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[180.9](/docs/network/latency/pairs/mrs-tpe-rtt)** | Fair | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[187.5](/docs/network/latency/pairs/ber-tyo-rtt)** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[194.5](/docs/network/latency/pairs/fra-tyo-rtt)** | Fair | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[198.2](/docs/network/latency/pairs/ams-tyo-rtt)** | Fair | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[202.9](/docs/network/latency/pairs/lon-tyo-rtt)** | Fair | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[203.8](/docs/network/latency/pairs/mrs-tyo-rtt)** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[204.7](/docs/network/latency/pairs/par-tyo-rtt)** | Fair | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[234.2](/docs/network/latency/pairs/mrs-mel-rtt)** | Fair | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[235.9](/docs/network/latency/pairs/mow-mel-rtt)** | Fair | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[240.6](/docs/network/latency/pairs/mrs-syd-rtt)** | Fair | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[241.8](/docs/network/latency/pairs/mow-syd-rtt)** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[246.4](/docs/network/latency/pairs/par-mel-rtt)** | Fair | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[249.6](/docs/network/latency/pairs/lon-mel-rtt)** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[249.7](/docs/network/latency/pairs/par-syd-rtt)** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[250.1](/docs/network/latency/pairs/fra-mel-rtt)** | High | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[252.5](/docs/network/latency/pairs/ams-mel-rtt)** | High | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[256](/docs/network/latency/pairs/fra-syd-rtt)** | High | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[256.2](/docs/network/latency/pairs/ber-mel-rtt)** | High | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[258](/docs/network/latency/pairs/ams-syd-rtt)** | High | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[258.1](/docs/network/latency/pairs/lon-syd-rtt)** | High | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[262.1](/docs/network/latency/pairs/ber-syd-rtt)** | High | ## Related Regions * [Europe backbone latency](./europe) * [Asia Pacific backbone latency](./asia-pacific) *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/europe-to-asia-pacific). - **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. # Europe to North America Ping & RTT | AS203314 The transatlantic corridor connects Hats Network's European ring to North American hubs. Traffic typically crosses submarine cables such as TAT-14, Amitié, or MAREA, with lowest-latency paths between London/Amsterdam and New York/Ashburn. Measurement round: `2026-08-16T04:07:28Z`. ## Quick Stats | Metric | Value | | ------------------- | ------------------------------------------------------------------------------------------ | | Fastest Route | **[London (LON) → New York (NYC)](/docs/network/latency/pairs/lon-nyc-rtt)** — 63.8 ms | | Slowest Route | **[Moscow (MOW) → Los Angeles (LAX)](/docs/network/latency/pairs/mow-lax-rtt)** — 177.7 ms | | Average RTT | **111.4 ms** | | City Pairs Measured | 35 | ## Europe to North America City-Pair RTT | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | --------- | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **[63.8](/docs/network/latency/pairs/lon-nyc-rtt)** | Excellent | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **[68.6](/docs/network/latency/pairs/ams-nyc-rtt)** | Excellent | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **[68.9](/docs/network/latency/pairs/par-nyc-rtt)** | Excellent | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **[71](/docs/network/latency/pairs/lon-iad-rtt)** | Excellent | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **[74.4](/docs/network/latency/pairs/fra-nyc-rtt)** | Excellent | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **[75.5](/docs/network/latency/pairs/par-iad-rtt)** | Excellent | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **[75.7](/docs/network/latency/pairs/ams-iad-rtt)** | Excellent | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **[79.6](/docs/network/latency/pairs/ber-nyc-rtt)** | Excellent | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **[79.8](/docs/network/latency/pairs/mrs-nyc-rtt)** | Excellent | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **[80.7](/docs/network/latency/pairs/fra-iad-rtt)** | Good | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **[85.7](/docs/network/latency/pairs/ber-iad-rtt)** | Good | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **[85.7](/docs/network/latency/pairs/mrs-iad-rtt)** | Good | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **[101.9](/docs/network/latency/pairs/lon-mia-rtt)** | Good | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **[106](/docs/network/latency/pairs/ams-mia-rtt)** | Good | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **[106.8](/docs/network/latency/pairs/par-mia-rtt)** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **[107.5](/docs/network/latency/pairs/mow-nyc-rtt)** | Good | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **[112](/docs/network/latency/pairs/fra-mia-rtt)** | Good | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **[112.4](/docs/network/latency/pairs/mrs-mia-rtt)** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **[113.9](/docs/network/latency/pairs/mow-iad-rtt)** | Good | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **[118.3](/docs/network/latency/pairs/ber-mia-rtt)** | Good | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **[123.2](/docs/network/latency/pairs/lon-sea-rtt)** | Good | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **[127.5](/docs/network/latency/pairs/lon-lax-rtt)** | Good | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **[128](/docs/network/latency/pairs/par-sea-rtt)** | Good | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **[130.2](/docs/network/latency/pairs/ams-sea-rtt)** | Good | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **[133.7](/docs/network/latency/pairs/ams-lax-rtt)** | Good | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **[135.2](/docs/network/latency/pairs/fra-sea-rtt)** | Good | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **[136.5](/docs/network/latency/pairs/par-lax-rtt)** | Good | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **[139.7](/docs/network/latency/pairs/ber-sea-rtt)** | Good | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **[140.9](/docs/network/latency/pairs/ber-lax-rtt)** | Good | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **[141.7](/docs/network/latency/pairs/mrs-sea-rtt)** | Good | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **[141.8](/docs/network/latency/pairs/fra-lax-rtt)** | Good | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **[144.5](/docs/network/latency/pairs/mrs-lax-rtt)** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **[144.5](/docs/network/latency/pairs/mow-mia-rtt)** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **[164.8](/docs/network/latency/pairs/mow-sea-rtt)** | Fair | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **[177.7](/docs/network/latency/pairs/mow-lax-rtt)** | Fair | ## Related Regions * [Europe backbone latency](./europe) * [North America backbone latency](./north-america) *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/europe-to-north-america). - **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. # Europe to South America Ping & RTT | AS203314 The Europe to South America corridor crosses the South Atlantic via cables such as EllaLink and SABR, landing in Fortaleza and extending to São Paulo. Marseille and Lisbon are the natural European departure points. Measurement round: `2026-08-16T04:07:28Z`. ## Quick Stats | Metric | Value | | ------------------- | ---------------------------------------------------------------------------------------- | | Fastest Route | **[London (LON) → São Paulo (GRU)](/docs/network/latency/pairs/lon-gru-rtt)** — 170.7 ms | | Slowest Route | **[Moscow (MOW) → São Paulo (GRU)](/docs/network/latency/pairs/mow-gru-rtt)** — 214.4 ms | | Average RTT | **184.4 ms** | | City Pairs Measured | 7 | ## Europe to South America City-Pair RTT | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ---- | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[170.7](/docs/network/latency/pairs/lon-gru-rtt)** | Fair | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[175.5](/docs/network/latency/pairs/ams-gru-rtt)** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[175.8](/docs/network/latency/pairs/par-gru-rtt)** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[181.3](/docs/network/latency/pairs/fra-gru-rtt)** | Fair | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[186.5](/docs/network/latency/pairs/ber-gru-rtt)** | Fair | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[186.7](/docs/network/latency/pairs/mrs-gru-rtt)** | Fair | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[214.4](/docs/network/latency/pairs/mow-gru-rtt)** | Fair | ## Related Regions * [Europe backbone latency](./europe) * [South America backbone latency](./south-america) *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/europe-to-south-america). - **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. # Europe Ping & RTT Latency | AS203314 Europe hosts the densest interconnection ecosystem on Hats Network's backbone, with PoPs in Amsterdam, Berlin, Frankfurt, London, Marseille, and Moscow. These nodes form a low-latency ring connecting Western, Central, and Eastern Europe. Measurement round: `2026-08-16T04:07:28Z`. ## Intra-Europe RTT Matrix Round-trip times in milliseconds between PoPs within the region. | Route | AMS | BER | FRA | LON | MRS | MOW | PAR | | ----------------------------------------------------------- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) | — | 7.2 | 5.9 | 5.2 | 19.6 | 38.1 | 7 | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) | 7.2 | — | 6.1 | 15.2 | 20.2 | 28.6 | 15.6 | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) | 5.9 | 6.1 | — | 12.9 | 16.4 | 34.7 | 7.6 | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) | 5.2 | 16.2 | 13.6 | — | 17.9 | 43.5 | 6.4 | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) | 20.3 | 20.6 | 16 | 18.9 | — | 49.6 | 8.9 | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) | 37.6 | 27.5 | 35.9 | 42.4 | 49.9 | — | 44 | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) | 7 | 15.5 | 7.6 | 6.4 | 8.9 | 44.7 | — | ## Europe to Other Regions Lowest-latency paths from this region to every other region. ### To North America | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------- | -------- | --------- | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **63.8** | Excellent | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **68.6** | Excellent | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **68.9** | Excellent | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **71** | Excellent | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **74.4** | Excellent | ### To South America | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **170.7** | Fair | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **175.5** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **175.8** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **181.3** | Fair | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **186.5** | Fair | ### To Asia Pacific | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **118.6** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **132.1** | Good | | 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **139.6** | Good | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **144.9** | Good | | 🇷🇺 [Moscow (MOW)](/docs/network/latency/mow-moscow) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **147.3** | Good | ### To Africa | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **171.9** | Fair | | 🇩🇪 [Berlin (BER)](/docs/network/latency/ber-berlin) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **172.1** | Fair | | 🇬🇧 [London (LON)](/docs/network/latency/lon-london) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **179.6** | Fair | | 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **180.9** | Fair | | 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **188.4** | Fair | ## PoPs in this Region | PoP | City | Country | | ---------------------------------------------- | -------------- | ----------- | | **[AMS](/docs/network/latency/ams-amsterdam)** | 🇳🇱 Amsterdam | Netherlands | | **[BER](/docs/network/latency/ber-berlin)** | 🇩🇪 Berlin | Germany | | **[FRA](/docs/network/latency/fra-frankfurt)** | 🇩🇪 Frankfurt | Germany | | **[LON](/docs/network/latency/lon-london)** | 🇬🇧 London | UK | | **[MRS](/docs/network/latency/mrs-marseille)** | 🇫🇷 Marseille | France | | **[MOW](/docs/network/latency/mow-moscow)** | 🇷🇺 Moscow | Russia | | **[PAR](/docs/network/latency/par-paris)** | 🇫🇷 Paris | France | *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency) or browse by [city pair](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/europe). - **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. # Regional Ping & RTT Corridors | AS203314 This section breaks down Hats Network backbone RTT by geographic region and by major inter-regional corridors. Use these pages to compare intra-region performance and find the best cross-region paths. Measurement round: `2026-08-16T04:07:28Z`. ## Regions | Region | PoPs | Description | | -------------------------------- | ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Europe](./europe) | 7 | Europe hosts the densest interconnection ecosystem on Hats Network's backbone, with PoPs in Amsterdam, Berlin, Frankfurt, London, Marseille, and Moscow. These nodes form a low-latency ring connecting Western, Central, and Eastern Europe. | | [North America](./north-america) | 5 | North America is anchored by Hats Network PoPs across the United States, covering Data Center Alley in Ashburn, the transatlantic gateway in New York, the West Coast hubs in Los Angeles and Seattle, and the Latin America bridge in Miami. | | [South America](./south-america) | 1 | South America is served by Hats Network's São Paulo PoP, the continent's largest peering and interconnection hub, providing diverse paths to North America, Europe, and Asia Pacific. | | [Asia Pacific](./asia-pacific) | 6 | Asia Pacific spans Hats Network PoPs in Hong Kong, Singapore, Taipei, Tokyo, Sydney, and Melbourne, covering East Asia, Southeast Asia, and Oceania with dense submarine cable connectivity. | | [Africa](./africa) | 1 | Africa is served by Hats Network's Johannesburg PoP, anchoring Southern African connectivity to the global backbone with the lowest-latency paths via European submarine cable landings. | ## Corridors | Corridor | Description | | ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Europe → North America](./europe-to-north-america) | The transatlantic corridor connects Hats Network's European ring to North American hubs. Traffic typically crosses submarine cables such as TAT-14, Amitié, or MAREA, with lowest-latency paths between London/Amsterdam and New York/Ashburn. | | [Europe → Asia Pacific](./europe-to-asia-pacific) | The Europe to Asia Pacific corridor spans the Eurasian landmass and submarine cable systems via the Mediterranean, Red Sea, and Indian Ocean. Marseille and Amsterdam serve as primary departure points for Singapore, Hong Kong, and Tokyo. | | [North America → Asia Pacific](./north-america-to-asia-pacific) | The North America to Asia Pacific corridor is dominated by trans-Pacific submarine cables. Los Angeles, Seattle, and Ashburn provide the lowest-latency paths to Tokyo, Hong Kong, and Singapore. | | [Europe → South America](./europe-to-south-america) | The Europe to South America corridor crosses the South Atlantic via cables such as EllaLink and SABR, landing in Fortaleza and extending to São Paulo. Marseille and Lisbon are the natural European departure points. | | [North America → South America](./north-america-to-south-america) | The North America to South America corridor bridges the continents via submarine cables landing in Florida, Brazil, and the Caribbean. Miami is the primary North American gateway to São Paulo. | | [Asia Pacific → South America](./asia-pacific-to-south-america) | The Asia Pacific to South America corridor is the longest on Hats Network's backbone, typically routed via North America or Europe. Sydney, Los Angeles, and São Paulo form key waypoints. | *** *Data auto-generated on August 16, 2026. Return to the [full global latency matrix](/docs/network/latency) or browse individual [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions). - **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. # North America to Asia Pacific Ping & RTT | AS203314 The North America to Asia Pacific corridor is dominated by trans-Pacific submarine cables. Los Angeles, Seattle, and Ashburn provide the lowest-latency paths to Tokyo, Hong Kong, and Singapore. Measurement round: `2026-08-16T04:07:28Z`. ## Quick Stats | Metric | Value | | ------------------- | --------------------------------------------------------------------------------------- | | Fastest Route | **[Seattle (SEA) → Tokyo (TYO)](/docs/network/latency/pairs/sea-tyo-rtt)** — 85 ms | | Slowest Route | **[Miami (MIA) → Singapore (SIN)](/docs/network/latency/pairs/mia-sin-rtt)** — 223.1 ms | | Average RTT | **167.4 ms** | | City Pairs Measured | 30 | ## North America to Asia Pacific City-Pair RTT | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ---- | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[85](/docs/network/latency/pairs/sea-tyo-rtt)** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[101.2](/docs/network/latency/pairs/lax-tyo-rtt)** | Good | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[114.7](/docs/network/latency/pairs/sea-tpe-rtt)** | Good | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[130.4](/docs/network/latency/pairs/sea-hkg-rtt)** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[132.9](/docs/network/latency/pairs/lax-tpe-rtt)** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[137.6](/docs/network/latency/pairs/lax-syd-rtt)** | Good | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[141.9](/docs/network/latency/pairs/iad-tyo-rtt)** | Good | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[143.1](/docs/network/latency/pairs/nyc-tyo-rtt)** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[146.5](/docs/network/latency/pairs/lax-hkg-rtt)** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[148.2](/docs/network/latency/pairs/lax-mel-rtt)** | Good | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[151.1](/docs/network/latency/pairs/sea-sin-rtt)** | Fair | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **[156.3](/docs/network/latency/pairs/mia-tyo-rtt)** | Fair | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[161.3](/docs/network/latency/pairs/sea-syd-rtt)** | Fair | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[167.7](/docs/network/latency/pairs/lax-sin-rtt)** | Fair | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[170.1](/docs/network/latency/pairs/sea-mel-rtt)** | Fair | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[172.3](/docs/network/latency/pairs/iad-tpe-rtt)** | Fair | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[173.4](/docs/network/latency/pairs/nyc-tpe-rtt)** | Fair | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **[185.1](/docs/network/latency/pairs/mia-tpe-rtt)** | Fair | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[187.1](/docs/network/latency/pairs/nyc-hkg-rtt)** | Fair | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[187.2](/docs/network/latency/pairs/iad-hkg-rtt)** | Fair | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[191.5](/docs/network/latency/pairs/mia-syd-rtt)** | Fair | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[192.6](/docs/network/latency/pairs/nyc-syd-rtt)** | Fair | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **[193.6](/docs/network/latency/pairs/iad-syd-rtt)** | Fair | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **[199.5](/docs/network/latency/pairs/mia-hkg-rtt)** | Fair | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[200.7](/docs/network/latency/pairs/mia-mel-rtt)** | Fair | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[203.9](/docs/network/latency/pairs/iad-mel-rtt)** | Fair | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **[205.1](/docs/network/latency/pairs/nyc-mel-rtt)** | Fair | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[208.7](/docs/network/latency/pairs/nyc-sin-rtt)** | Fair | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[211.5](/docs/network/latency/pairs/iad-sin-rtt)** | Fair | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇸🇬 [Singapore (SIN)](/docs/network/latency/sin-singapore) | **[223.1](/docs/network/latency/pairs/mia-sin-rtt)** | Fair | ## Related Regions * [North America backbone latency](./north-america) * [Asia Pacific backbone latency](./asia-pacific) *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/north-america-to-asia-pacific). - **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. # North America to South America Ping & RTT | AS203314 The North America to South America corridor bridges the continents via submarine cables landing in Florida, Brazil, and the Caribbean. Miami is the primary North American gateway to São Paulo. Measurement round: `2026-08-16T04:07:28Z`. ## Quick Stats | Metric | Value | | ------------------- | ----------------------------------------------------------------------------------------- | | Fastest Route | **[Ashburn (IAD) → São Paulo (GRU)](/docs/network/latency/pairs/iad-gru-rtt)** — 101.4 ms | | Slowest Route | **[Seattle (SEA) → São Paulo (GRU)](/docs/network/latency/pairs/sea-gru-rtt)** — 155.7 ms | | Average RTT | **124.8 ms** | | City Pairs Measured | 5 | ## North America to South America City-Pair RTT | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ---- | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[101.4](/docs/network/latency/pairs/iad-gru-rtt)** | Good | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[106.9](/docs/network/latency/pairs/nyc-gru-rtt)** | Good | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[128.7](/docs/network/latency/pairs/mia-gru-rtt)** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[131.3](/docs/network/latency/pairs/lax-gru-rtt)** | Good | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **[155.7](/docs/network/latency/pairs/sea-gru-rtt)** | Fair | ## Related Regions * [North America backbone latency](./north-america) * [South America backbone latency](./south-america) *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/north-america-to-south-america). - **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. # North America Ping & RTT Latency | AS203314 North America is anchored by Hats Network PoPs across the United States, covering Data Center Alley in Ashburn, the transatlantic gateway in New York, the West Coast hubs in Los Angeles and Seattle, and the Latin America bridge in Miami. Measurement round: `2026-08-16T04:07:28Z`. ## Intra-North America RTT Matrix Round-trip times in milliseconds between PoPs within the region. | Route | IAD | LAX | MIA | NYC | SEA | | --------------------------------------------------------------- | ---- | ---- | ---- | ---- | ---- | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | — | 60.7 | 27.4 | 6 | 62.3 | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | 60.4 | — | 57.3 | 57.9 | 26.9 | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | 27.3 | 56.8 | — | 33.3 | 81.9 | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | 6 | 58.9 | 32.9 | — | 58.7 | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | 61.5 | 25.9 | 81.7 | 59.5 | — | ## North America to Other Regions Lowest-latency paths from this region to every other region. ### To Europe | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------- | -------- | --------- | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇬🇧 [London (LON)](/docs/network/latency/lon-london) | **63.5** | Excellent | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) | **68.7** | Excellent | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) | **68.9** | Excellent | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇬🇧 [London (LON)](/docs/network/latency/lon-london) | **70.3** | Excellent | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) | **73.9** | Excellent | ### To South America | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **101.4** | Good | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **106.9** | Good | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **128.7** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **131.3** | Good | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | **155.7** | Fair | ### To Asia Pacific | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **85** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **101.2** | Good | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **114.7** | Good | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **130.4** | Good | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **132.9** | Good | ### To Africa | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **221.5** | Fair | | 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **228.3** | Fair | | 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **259.8** | High | | 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **282.1** | High | | 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **287.2** | High | ## PoPs in this Region | PoP | City | Country | | ------------------------------------------------ | ---------------- | ------- | | **[IAD](/docs/network/latency/iad-ashburn)** | 🇺🇸 Ashburn | USA | | **[LAX](/docs/network/latency/lax-los-angeles)** | 🇺🇸 Los Angeles | USA | | **[MIA](/docs/network/latency/mia-miami)** | 🇺🇸 Miami | USA | | **[NYC](/docs/network/latency/nyc-new-york)** | 🇺🇸 New York | USA | | **[SEA](/docs/network/latency/sea-seattle)** | 🇺🇸 Seattle | USA | *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency) or browse by [city pair](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/north-america). - **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. # South America Ping & RTT Latency | AS203314 South America is served by Hats Network's São Paulo PoP, the continent's largest peering and interconnection hub, providing diverse paths to North America, Europe, and Asia Pacific. Measurement round: `2026-08-16T04:07:28Z`. ## South America to Other Regions Lowest-latency paths from this region to every other region. ### To Europe | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇬🇧 [London (LON)](/docs/network/latency/lon-london) | **175.8** | Fair | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇳🇱 [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) | **180** | Fair | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇫🇷 [Paris (PAR)](/docs/network/latency/par-paris) | **180.2** | Fair | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇩🇪 [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) | **186.2** | Fair | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇫🇷 [Marseille (MRS)](/docs/network/latency/mrs-marseille) | **187.7** | Fair | ### To North America | Route | RTT (ms) | Tier | | ----------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇺🇸 [Miami (MIA)](/docs/network/latency/mia-miami) | **74** | Excellent | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇺🇸 [New York (NYC)](/docs/network/latency/nyc-new-york) | **122** | Good | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇺🇸 [Ashburn (IAD)](/docs/network/latency/iad-ashburn) | **128** | Good | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇺🇸 [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | **130.8** | Good | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇺🇸 [Seattle (SEA)](/docs/network/latency/sea-seattle) | **155.9** | Fair | ### To Asia Pacific | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇯🇵 [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | **230.3** | Fair | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇹🇼 [Taipei (TPE)](/docs/network/latency/tpe-taipei) | **259.1** | High | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇦🇺 [Sydney (SYD)](/docs/network/latency/syd-sydney) | **265.5** | High | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇭🇰 [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | **273.5** | High | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇦🇺 [Melbourne (MEL)](/docs/network/latency/mel-melbourne) | **274.7** | High | ### To Africa | Route | RTT (ms) | Tier | | ------------------------------------------------------------------------------------------------------------------------------- | --------- | ---- | | 🇧🇷 [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) → 🇿🇦 [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | **333.8** | High | ## PoPs in this Region | PoP | City | Country | | ---------------------------------------------- | -------------- | ------- | | **[GRU](/docs/network/latency/gru-sao-paulo)** | 🇧🇷 São Paulo | Brazil | *** *Data auto-generated on August 16, 2026. Explore the [full global latency matrix](/docs/network/latency) or browse by [city pair](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/regions/south-america). - **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. # Amsterdam, Netherlands → Berlin, Germany RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo probes between Amsterdam, Netherlands and Berlin, Germany averaged 7.2 ms over 50 samples, with a minimum of 6.88 ms and a maximum of 8.21 ms. No packets were lost, and jitter held at 0.23 ms, so the route was both fast and stable during the test window. The physical reference for this 579.2 km great-circle route is a vacuum transit floor of 3.86 ms and a realistic fiber floor of 5.67 ms. The observed average latency is only 1.27 times the fiber floor, corresponding to 78.8% fiber efficiency and leaving little additional latency over the theoretical fiber minimum. This path ranks fourth in a field of 19 outbound routes measured from Amsterdam in the same round. Its 0.31 ms standard deviation is about 4.3% of the 7.2 ms average, a touch above the 3.28% median standard-deviation-to-average ratio across the route set, but the absolute spread stays under a third of a millisecond. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **7.2 ms** | | Jitter | **0.23 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **5.67 ms** | | Fiber Efficiency | **78.8%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **579.2 km** | | Vacuum RTT floor | **3.86 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **5.67 ms** | | Low-latency fiber material floor | **5.65 ms** | | Engineering floor (5% path allowance) | **5.96 ms** | | Research 1.33× mapped-fiber reference | **7.54 ms** | | Estimated unamplified path loss | **121.6 dB** | | Transparent optical spans / inline amplifiers | **8 / 7** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **6.88 ms** | | Average RTT | **7.2 ms** | | Maximum RTT | **8.21 ms** | | Standard deviation | **0.31 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-ber-rtt). - **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. # Amsterdam, Netherlands → Frankfurt, Germany RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from Amsterdam, Netherlands to Frankfurt, Germany returned an average of 5.9 ms across 50 samples, with a minimum of 5.67 ms and a maximum of 7.15 ms. Packet loss was zero and jitter was 0.17 ms, making the measurement window consistently quiet. The geodesic span is 365.1 km, with a theoretical vacuum floor of 2.44 ms and a fiber floor of 3.57 ms. The 5.9 ms average is 1.65 times the fiber floor, putting fiber efficiency at 60.6% and leaving roughly 2.3 ms of additional latency to account for in the path overhead. Within the same round, this route comes second among 19 outbound paths measured from Amsterdam. Its standard deviation of 0.23 ms is about 3.9% of the 5.9 ms average, close to the 3.28% median standard-deviation-to-average ratio for the route set, while jitter stays at just 0.17 ms. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **5.9 ms** | | Jitter | **0.17 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.57 ms** | | Fiber Efficiency | **60.6%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **365.1 km** | | Vacuum RTT floor | **2.44 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.57 ms** | | Low-latency fiber material floor | **3.56 ms** | | Engineering floor (5% path allowance) | **3.75 ms** | | Research 1.33× mapped-fiber reference | **4.75 ms** | | Estimated unamplified path loss | **76.7 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.65×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **5.67 ms** | | Average RTT | **5.9 ms** | | Maximum RTT | **7.15 ms** | | Standard deviation | **0.23 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms **Fastest routes arriving at Frankfurt (FRA)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-fra-rtt). - **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. # Amsterdam, Netherlands → São Paulo, Brazil RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. At round 2026-08-16T04:07:28Z, ICMP echo requests from Amsterdam, Netherlands to São Paulo, Brazil spent an average of 175.5 ms in round-trip transit across 50 samples, with a minimum of 166.82 ms and a maximum of 195.11 ms. There was no packet loss, but the route's standard deviation was 6.86 ms and jitter was 6.92 ms, so the largest observed round-trip time exceeded the smallest by more than 28 ms. Within the 19 outbound routes from Amsterdam measured in this round, this route ranked 16th by average latency, placing it near the slower end of the set; its standard deviation is about 3.9% of its average, close to but above the median route's 3.28% ratio. The physical reference is a geodesic distance of 9,781.6 km, with a vacuum floor of 65.26 ms and a fiber floor of 95.79 ms. The measured average sits at 1.83 times the fiber floor, equivalent to 54.6% fiber efficiency, indicating that the path carries substantial additional round-trip time beyond the ideal fiber estimate. With zero loss but jitter near 7 ms, the route remained available throughout the sample window while individual round-trip values varied noticeably; treat the 166.82–195.11 ms range as this route's observed envelope. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **175.5 ms** | | Jitter | **6.92 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.79 ms** | | Fiber Efficiency | **54.6%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,781.6 km** | | Vacuum RTT floor | **65.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.79 ms** | | Low-latency fiber material floor | **95.4 ms** | | Engineering floor (5% path allowance) | **100.59 ms** | | Research 1.33× mapped-fiber reference | **127.4 ms** | | Estimated unamplified path loss | **2054.1 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.83×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **166.82 ms** | | Average RTT | **175.5 ms** | | Maximum RTT | **195.11 ms** | | Standard deviation | **6.86 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Europe → South America)** * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms * [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 ms * [Frankfurt to São Paulo latency and RTT](/docs/network/latency/pairs/fra-gru-rtt) — 181.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-gru-rtt). - **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. # Amsterdam, Netherlands → Hong Kong RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Amsterdam to Hong Kong averaged 155.9 ms, with a minimum of 149.39 ms and a maximum of 177.73 ms. All 50 probes were answered, so the zero packet loss and 4.48 ms jitter describe a stable sample rather than a lossy path. The great-circle distance of 9,297.6 km gives a vacuum light-time floor of 62.03 ms and a realistic fiber floor of 91.05 ms. The observed average is 1.71 times that fiber floor, which translates to a fiber efficiency of 58.4%; the extra time over the floor is the route's real-world distance penalty. This route ranks 12th among the 19 outbound routes measured from Amsterdam in this round. Its standard deviation of 5.82 ms is about 3.7% of the average, slightly above the 3.28% median variability for the 19-route set, so the path is consistent but a touch more variable than the midpoint of the group. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **155.9 ms** | | Jitter | **4.48 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.05 ms** | | Fiber Efficiency | **58.4%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,297.6 km** | | Vacuum RTT floor | **62.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.05 ms** | | Low-latency fiber material floor | **90.68 ms** | | Engineering floor (5% path allowance) | **95.61 ms** | | Research 1.33× mapped-fiber reference | **121.1 ms** | | Estimated unamplified path loss | **1952.5 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **1.71×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **149.39 ms** | | Average RTT | **155.9 ms** | | Maximum RTT | **177.73 ms** | | Standard deviation | **5.82 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Amsterdam latency and RTT](/docs/network/latency/pairs/hkg-ams-rtt) — 154.4 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-hkg-rtt). - **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. # Amsterdam, Netherlands → Ashburn, USA RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo RTT from Amsterdam, Netherlands to Ashburn, USA averaged 75.7 ms across 50 samples, with a minimum of 72.76 ms and a maximum of 82.67 ms. Zero packet loss and a 2.14 ms jitter figure accompany a tight 2.28 ms standard deviation, placing this measurement in the excellent latency tier. The average is 1.24 times the calculated fiber floor of 60.94 ms for the 6,223.2 km great-circle distance, or 80.5% in straight-line fiber efficiency, against a 41.52 ms vacuum floor. That closeness to the theoretical straight-line limit is the route's standout feature. In the Amsterdam outbound set of 19 routes, this destination ranks 8th by average RTT. Its variability of about 3.0% is below the 3.28% median variability across the route set, reinforcing the stable, low-loss profile of the measurement. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **75.7 ms** | | Jitter | **2.14 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **60.94 ms** | | Fiber Efficiency | **80.5%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,223.2 km** | | Vacuum RTT floor | **41.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **60.94 ms** | | Low-latency fiber material floor | **60.7 ms** | | Engineering floor (5% path allowance) | **64 ms** | | Research 1.33× mapped-fiber reference | **81.05 ms** | | Estimated unamplified path loss | **1306.9 dB** | | Transparent optical spans / inline amplifiers | **82 / 81** | | Published RTT inflation over fiber floor | **1.24×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **72.76 ms** | | Average RTT | **75.7 ms** | | Maximum RTT | **82.67 ms** | | Standard deviation | **2.28 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Amsterdam latency and RTT](/docs/network/latency/pairs/iad-ams-rtt) — 75.2 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-iad-rtt). - **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. # Amsterdam, Netherlands → Johannesburg, South Africa RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round used 50 ICMP echo probes from Amsterdam, Netherlands to Johannesburg, South Africa and measured an average round-trip time of 171.9 ms, with a minimum of 163.56 ms and a maximum of 197.47 ms. Packet loss was 0%, and the 6.53 ms standard deviation indicates the path stayed in a tight band across the 8,991.8 km geodesic distance. That RTT is 1.95 times the fiber floor of 88.05 ms for the same span, putting fiber efficiency at 51.2%. Jitter of 5.46 ms reinforces the stability picture: the route was loss-free and showed no large swings between consecutive replies. In the 19-route measurement set for this network, this path ranked 15th, placing it near the slower end. Its standard deviation is about 3.8% of the average, just above the 3.28% median spread-to-average ratio across the set, so the added distance did not translate into disproportionate variability. The useful takeaway is that the intercontinental cost is visible mainly in the 171.9 ms average, while loss and jitter stayed contained. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **171.9 ms** | | Jitter | **5.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **88.05 ms** | | Fiber Efficiency | **51.2%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,991.8 km** | | Vacuum RTT floor | **59.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **88.05 ms** | | Low-latency fiber material floor | **87.7 ms** | | Engineering floor (5% path allowance) | **92.47 ms** | | Research 1.33× mapped-fiber reference | **117.11 ms** | | Estimated unamplified path loss | **1888.3 dB** | | Transparent optical spans / inline amplifiers | **119 / 118** | | Published RTT inflation over fiber floor | **1.95×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **163.56 ms** | | Average RTT | **171.9 ms** | | Maximum RTT | **197.47 ms** | | Standard deviation | **6.53 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Johannesburg (JNB)** * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms * [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt) — 198.5 ms **Same corridor (Europe → Africa)** * [Moscow to Johannesburg latency and RTT](/docs/network/latency/pairs/mow-jnb-rtt) — 201.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-jnb-rtt). - **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. # Amsterdam, Netherlands → Los Angeles, USA RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo RTT from Amsterdam, Netherlands to Los Angeles, USA averaged 133.7 ms over 50 samples; the minimum was 130.58 ms and the maximum was 141.4 ms. No packets were lost, and the 2.49 ms standard deviation produced 2.11 ms jitter, so the long distance did not translate into erratic round-trip times. At 1.52 times the 87.74 ms fiber floor for the 8,960 km great-circle distance, the route has 65.6% straight-line fiber efficiency and a 59.77 ms vacuum floor. The measured RTT stays within a 10.8 ms band even though the destination is nearly 9,000 km away, making the tight spread the most distinctive feature of this route. Average latency ranks 11th among the 19 outbound routes measured from Amsterdam. Variability of about 1.9% is much lower than the 3.28% median variability across the route set, which makes the 133.7 ms average a dependable reference for this coastal destination. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **133.7 ms** | | Jitter | **2.11 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **87.74 ms** | | Fiber Efficiency | **65.6%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **8,960 km** | | Vacuum RTT floor | **59.77 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **87.74 ms** | | Low-latency fiber material floor | **87.39 ms** | | Engineering floor (5% path allowance) | **92.14 ms** | | Research 1.33× mapped-fiber reference | **116.7 ms** | | Estimated unamplified path loss | **1881.6 dB** | | Transparent optical spans / inline amplifiers | **118 / 117** | | Published RTT inflation over fiber floor | **1.52×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **130.58 ms** | | Average RTT | **133.7 ms** | | Maximum RTT | **141.4 ms** | | Standard deviation | **2.49 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Amsterdam latency and RTT](/docs/network/latency/pairs/lax-ams-rtt) — 132.1 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-lax-rtt). - **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. # Amsterdam, Netherlands → London, UK RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Amsterdam, Netherlands to London, UK averaged 5.2 ms across 50 samples, with a minimum of 4.89 ms and a maximum of 5.85 ms. Zero packet loss and 0.22 ms jitter kept the route stable for the duration of the test. The 358 km geodesic distance has a vacuum floor of 2.39 ms and a fiber floor of 3.51 ms. At 5.2 ms average, the route sits 1.48 times above the fiber floor and reaches 67.4% fiber efficiency, a solid result over a relatively short cross-border span. This route ranks first among 19 outbound paths measured from Amsterdam in the same round. Its 0.25 ms standard deviation is about 4.8% of the 5.2 ms average, above the 3.28% route-set median standard-deviation-to-average ratio, yet with zero loss and a sub-millisecond spread the route remained consistent throughout the measurement window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **5.2 ms** | | Jitter | **0.22 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.51 ms** | | Fiber Efficiency | **67.4%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ----------- | | WGS-84 geodesic distance | **358 km** | | Vacuum RTT floor | **2.39 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.51 ms** | | Low-latency fiber material floor | **3.49 ms** | | Engineering floor (5% path allowance) | **3.68 ms** | | Research 1.33× mapped-fiber reference | **4.66 ms** | | Estimated unamplified path loss | **75.2 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.48×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **4.89 ms** | | Average RTT | **5.2 ms** | | Maximum RTT | **5.85 ms** | | Standard deviation | **0.25 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms **Fastest routes arriving at London (LON)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms **Same corridor (Europe → Europe)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-lon-rtt). - **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. # Amsterdam, Netherlands → Melbourne, Australia RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Amsterdam to Melbourne averaged 252.5 ms across 50 samples, with a low of 235.69 ms and a high of 297.33 ms. Despite the high latency tier, packet loss was 0%, so this is a long-distance path with no dropped probes in the sample. The geodesic distance of 16,540.5 km sets a vacuum floor of 110.35 ms and a fiber floor of 161.98 ms. The measured average is 1.56 times the fiber floor, equivalent to a fiber efficiency of 64.1%; the 12.24 ms standard deviation and 10.79 ms jitter are modest in absolute terms and small relative to the 252.5 ms average. This route ranks 18th among the 19 outbound routes measured from Amsterdam in this round, placing it near the high end of that latency range. Its standard deviation is about 4.8% of the average, noticeably above the 3.28% median variability for the 19-route set, so the combination of high latency and above-median variability is the main thing to watch on this path. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **252.5 ms** | | Jitter | **10.79 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **161.98 ms** | | Fiber Efficiency | **64.1%** | | Latency Tier | High | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,540.5 km** | | Vacuum RTT floor | **110.35 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **161.98 ms** | | Low-latency fiber material floor | **161.33 ms** | | Engineering floor (5% path allowance) | **170.1 ms** | | Research 1.33× mapped-fiber reference | **215.43 ms** | | Estimated unamplified path loss | **3473.5 dB** | | Transparent optical spans / inline amplifiers | **218 / 217** | | Published RTT inflation over fiber floor | **1.56×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **235.69 ms** | | Average RTT | **252.5 ms** | | Maximum RTT | **297.33 ms** | | Standard deviation | **12.24 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Amsterdam latency and RTT](/docs/network/latency/pairs/mel-ams-rtt) — 252.8 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-mel-rtt). - **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. # Amsterdam, Netherlands → Miami, USA RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo RTT from Amsterdam, Netherlands to Miami, USA averaged 106 ms over 50 samples, with a minimum of 99.94 ms and a maximum of 119.16 ms. The route saw zero packet loss, but the 4.46 ms standard deviation and 4.12 ms jitter show a relatively uneven round-trip profile. The average is 1.45 times the calculated fiber floor of 73.03 ms for the 7,457.8 km great-circle distance, corresponding to 68.9% straight-line fiber efficiency and a 49.75 ms vacuum floor. The 19.22 ms difference between minimum and maximum RTT is a notable feature of this measurement. This destination ranks 9th of 19 outbound routes from Amsterdam by average RTT. Its variability of about 4.2% is above the 3.28% median variability across the route set, making the elevated jitter the key distinction in this round. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **106 ms** | | Jitter | **4.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **73.03 ms** | | Fiber Efficiency | **68.9%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,457.8 km** | | Vacuum RTT floor | **49.75 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **73.03 ms** | | Low-latency fiber material floor | **72.74 ms** | | Engineering floor (5% path allowance) | **76.69 ms** | | Research 1.33× mapped-fiber reference | **97.13 ms** | | Estimated unamplified path loss | **1566.1 dB** | | Transparent optical spans / inline amplifiers | **98 / 97** | | Published RTT inflation over fiber floor | **1.45×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **99.94 ms** | | Average RTT | **106 ms** | | Maximum RTT | **119.16 ms** | | Standard deviation | **4.46 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Amsterdam latency and RTT](/docs/network/latency/pairs/mia-ams-rtt) — 106 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-mia-rtt). - **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. # Amsterdam, Netherlands → Moscow, Russia RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, the Amsterdam–Moscow path measured 38.1 ms average ICMP echo RTT from 50 samples, with min 35.69 ms, max 44.57 ms, and no packet loss. Standard deviation of 1.9 ms and jitter of 1.52 ms indicate a stable but not perfectly uniform sample. The geodesic distance of 2,154.6 km gives a theoretical fiber floor of 21.1 ms, so the observed RTT is 1.81x above that floor, or 55.4% fiber efficiency. Moscow's role as a European–Asia transit corridor is consistent with a long-haul path that still holds average latency in the excellent tier. Relative to the 19 routes in this round, this route ranked 6th; its variability of about 5.0% of the average exceeded the 3.28% median variability seen across routes. Despite that, zero loss and a maximum of 44.57 ms keep the path dependable for cross-border ICMP testing. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **38.1 ms** | | Jitter | **1.52 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **21.1 ms** | | Fiber Efficiency | **55.4%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,154.6 km** | | Vacuum RTT floor | **14.37 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **21.1 ms** | | Low-latency fiber material floor | **21.02 ms** | | Engineering floor (5% path allowance) | **22.16 ms** | | Research 1.33× mapped-fiber reference | **28.06 ms** | | Estimated unamplified path loss | **452.5 dB** | | Transparent optical spans / inline amplifiers | **29 / 28** | | Published RTT inflation over fiber floor | **1.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **35.69 ms** | | Average RTT | **38.1 ms** | | Maximum RTT | **44.57 ms** | | Standard deviation | **1.9 ms** | | Stdev / average | **5.0%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-mow-rtt). - **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. # Amsterdam, Netherlands → Marseille, France RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, the Amsterdam–Marseille path returned an average ICMP echo RTT of 19.6 ms across 50 samples, with a minimum of 19.03 ms, a maximum of 20.95 ms, and zero packet loss. Standard deviation was 0.5 ms and jitter 0.41 ms, so the path was consistently tight. The 1,009.9 km geodesic separation has a theoretical fiber floor near 9.89 ms; the observed RTT lands about 1.98x above that floor, implying 50.5% fiber efficiency. This is a reasonable directness result for a route terminating at Marseille's Mediterranean cable-landing ecosystem, where subsea systems add last-mile context without necessarily inflating spread. This route ranked 5th among the 19 routes in the same round, while its relative variability of about 2.6% of the average sat below the 3.28% median variability recorded across routes. For operators watching Amsterdam-to-Marseille reachability, the combination of no loss, sub-millisecond jitter, and stable RTT is the headline. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **19.6 ms** | | Jitter | **0.41 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **9.89 ms** | | Fiber Efficiency | **50.5%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,009.9 km** | | Vacuum RTT floor | **6.74 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **9.89 ms** | | Low-latency fiber material floor | **9.85 ms** | | Engineering floor (5% path allowance) | **10.39 ms** | | Research 1.33× mapped-fiber reference | **13.15 ms** | | Estimated unamplified path loss | **212.1 dB** | | Transparent optical spans / inline amplifiers | **14 / 13** | | Published RTT inflation over fiber floor | **1.98×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **19.03 ms** | | Average RTT | **19.6 ms** | | Maximum RTT | **20.95 ms** | | Standard deviation | **0.5 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-mrs-rtt). - **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. # Amsterdam, Netherlands → New York, USA RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. For the ICMP RTT round at 2026-08-16T04:07:28Z, 50 echo requests from Amsterdam, Netherlands to New York, USA returned an average round-trip time of 68.6 ms, with a minimum of 67.28 ms and a maximum of 73 ms. The path was very stable: standard deviation was 1.16 ms, jitter was 1.05 ms, and every packet arrived, so no packet loss was observed. In the context of the 19 outbound routes measured from Amsterdam in this round, this route ranked 7th by average latency. Its standard deviation is about 1.7% of its average, tighter than the median route's 3.28% ratio, confirming that the transatlantic connection is not only quick but also consistent. The physical reference for this route is a geodesic distance of 5,877.8 km, giving a vacuum floor of 39.21 ms and a fiber floor of 57.56 ms. The measured 68.6 ms average sits 1.19 times above the fiber floor, or about 83.9% fiber efficiency, meaning the path adds roughly 11 ms beyond the best-case fiber transit time. With no loss and a 1.05 ms jitter, this route provides a clean network-layer reference for repeated ICMP round-trip checks across the Atlantic. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **68.6 ms** | | Jitter | **1.05 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **57.56 ms** | | Fiber Efficiency | **83.9%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,877.8 km** | | Vacuum RTT floor | **39.21 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **57.56 ms** | | Low-latency fiber material floor | **57.33 ms** | | Engineering floor (5% path allowance) | **60.45 ms** | | Research 1.33× mapped-fiber reference | **76.56 ms** | | Estimated unamplified path loss | **1234.3 dB** | | Transparent optical spans / inline amplifiers | **78 / 77** | | Published RTT inflation over fiber floor | **1.19×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **67.28 ms** | | Average RTT | **68.6 ms** | | Maximum RTT | **73 ms** | | Standard deviation | **1.16 ms** | | Stdev / average | **1.7%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Europe → North America)** * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms * [Frankfurt to New York latency and RTT](/docs/network/latency/pairs/fra-nyc-rtt) — 74.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-nyc-rtt). - **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. # Amsterdam, Netherlands → Paris, France RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, the Amsterdam–Paris path averaged 7 ms ICMP echo RTT across 50 samples, with min 6.61 ms, max 8.02 ms, standard deviation 0.32 ms, jitter 0.27 ms, and zero packet loss. The 430.9 km geodesic distance corresponds to a theoretical fiber floor of 4.22 ms; the measured RTT is 1.66x that floor, or 60.3% fiber efficiency. That efficiency is a strong result for a corridor connecting two dense interconnection markets in Northwest Europe. This route ranked 3rd among the 19 routes in the round, while its relative variability of about 4.6% of the average was above the 3.28% median variability across routes. The absolute spread is still tiny, so the route offers a very stable, ultra-low-latency baseline for Amsterdam–Paris ICMP measurements. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **7 ms** | | Jitter | **0.27 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **4.22 ms** | | Fiber Efficiency | **60.3%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **430.9 km** | | Vacuum RTT floor | **2.87 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **4.22 ms** | | Low-latency fiber material floor | **4.2 ms** | | Engineering floor (5% path allowance) | **4.43 ms** | | Research 1.33× mapped-fiber reference | **5.61 ms** | | Estimated unamplified path loss | **90.5 dB** | | Transparent optical spans / inline amplifiers | **6 / 5** | | Published RTT inflation over fiber floor | **1.66×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **6.61 ms** | | Average RTT | **7 ms** | | Maximum RTT | **8.02 ms** | | Standard deviation | **0.32 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-par-rtt). - **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. # Amsterdam, Netherlands → Seattle, USA RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. The ICMP RTT round 2026-08-16T04:07:28Z sampled Amsterdam, Netherlands to Seattle, USA with 50 echo requests at 100 ms intervals; the average round-trip time was 130.2 ms, with a minimum of 123.59 ms and a maximum of 144.11 ms. All 50 packets were returned, so packet loss was 0%, but the path showed more variability: the standard deviation was 5.22 ms and jitter was 4.46 ms, producing a spread of about 20.5 ms between the fastest and slowest samples. In the set of 19 outbound routes measured from Amsterdam for this round, this route ranked 10th by average latency; its standard deviation is about 4.0% of its average, slightly above the median route's 3.28% ratio. The geodesic distance is 7,848.5 km, corresponding to a vacuum floor of 52.36 ms and a fiber floor of 76.86 ms. The measured average is 1.69 times the fiber floor, or about 59% fiber efficiency, meaning the actual round-trip time is markedly above the ideal fiber transit estimate. With zero packet loss and a 20.5 ms spread between the fastest and slowest samples, this route's ICMP behavior is stable in availability but variable in value; a single ping may land near either end of the observed range. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **130.2 ms** | | Jitter | **4.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.86 ms** | | Fiber Efficiency | **59%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,848.5 km** | | Vacuum RTT floor | **52.36 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.86 ms** | | Low-latency fiber material floor | **76.55 ms** | | Engineering floor (5% path allowance) | **80.71 ms** | | Research 1.33× mapped-fiber reference | **102.22 ms** | | Estimated unamplified path loss | **1648.2 dB** | | Transparent optical spans / inline amplifiers | **104 / 103** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **123.59 ms** | | Average RTT | **130.2 ms** | | Maximum RTT | **144.11 ms** | | Standard deviation | **5.22 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Amsterdam latency and RTT](/docs/network/latency/pairs/sea-ams-rtt) — 128.6 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-sea-rtt). - **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. # Amsterdam, Netherlands → Singapore RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Amsterdam to Singapore averaged 157.6 ms, with observed values ranging from 150.92 ms to 175.59 ms. All 50 probes succeeded, and the 4.44 ms jitter points to a steady fair-latency path. At 10,503.4 km apart, the two cities have a vacuum light-time floor of 70.07 ms and a fiber floor of 102.86 ms. The average sits 1.53 times above the fiber floor, giving a fiber efficiency of 65.3%; the extra 54.7 ms over the floor is the route's real-world distance penalty. This Amsterdam outbound route ranks 13th among the 19 routes in the same measurement set. Its standard deviation of 6.2 ms is about 3.9% of the average, slightly above the 3.28% median variability for the set, so the route is stable but not the quietest in the set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **157.6 ms** | | Jitter | **4.44 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **102.86 ms** | | Fiber Efficiency | **65.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,503.4 km** | | Vacuum RTT floor | **70.07 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **102.86 ms** | | Low-latency fiber material floor | **102.44 ms** | | Engineering floor (5% path allowance) | **108.01 ms** | | Research 1.33× mapped-fiber reference | **136.8 ms** | | Estimated unamplified path loss | **2205.7 dB** | | Transparent optical spans / inline amplifiers | **138 / 137** | | Published RTT inflation over fiber floor | **1.53×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **150.92 ms** | | Average RTT | **157.6 ms** | | Maximum RTT | **175.59 ms** | | Standard deviation | **6.2 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Amsterdam latency and RTT](/docs/network/latency/pairs/sin-ams-rtt) — 155.8 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-sin-rtt). - **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. # Amsterdam, Netherlands → Sydney, Australia RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo probes from Amsterdam to Sydney averaged 258 ms, ranging from 246.95 ms to 290.31 ms across 50 samples, with no packet loss. The 16,638.1 km geodesic separation puts the vacuum one-way floor at 111 ms and a realistic fiber floor at 162.93 ms, so the observed average is 1.58 times that fiber floor. That equates to 63.2% fiber efficiency, a reasonable result for a path that cannot travel along a straight great-circle line. This path ranked 19th out of 19 measured outbound routes from Amsterdam in the round, reflecting the highest latency tier in that set. Its 9.9 ms standard deviation is about 3.8% of the average, just above the 3.28% median variation across the network's outbound route set, while jitter of 7.93 ms remains modest for a high-latency route. The practical signal for this round is predictability: Sydney is far in absolute RTT terms, but zero packet loss and a tightly clustered 246.95–290.31 ms envelope mean the route is delivering stable transit rather than loss-induced spikes. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **258 ms** | | Jitter | **7.93 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **162.93 ms** | | Fiber Efficiency | **63.2%** | | Latency Tier | High | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,638.1 km** | | Vacuum RTT floor | **111 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **162.93 ms** | | Low-latency fiber material floor | **162.28 ms** | | Engineering floor (5% path allowance) | **171.1 ms** | | Research 1.33× mapped-fiber reference | **216.7 ms** | | Estimated unamplified path loss | **3494 dB** | | Transparent optical spans / inline amplifiers | **219 / 218** | | Published RTT inflation over fiber floor | **1.58×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **246.95 ms** | | Average RTT | **258 ms** | | Maximum RTT | **290.31 ms** | | Standard deviation | **9.9 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Amsterdam latency and RTT](/docs/network/latency/pairs/syd-ams-rtt) — 258.9 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-syd-rtt). - **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. # Amsterdam, Netherlands → Taipei, Taiwan RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo probes from Amsterdam to Taipei averaged 168.7 ms, with a minimum of 163.09 ms and a maximum of 184.23 ms over 50 samples and zero packet loss. The 9,467.8 km geodesic distance sets a vacuum floor of 63.16 ms and a fiber floor of 92.72 ms. At 168.7 ms, the average is 1.82 times the fiber floor, which puts the route at 55% fiber efficiency and indicates more overhead than a direct straight-line fiber path would allow. Within the round's 19 outbound routes from Amsterdam, this path ranked 14th. Its standard deviation of 4.36 ms is about 2.6% of the average—lower than the 3.28% median variation across the network's outbound route set—so the latency profile is more consistent than typical for this peer group. The useful takeaway is that Amsterdam-Taipei RTTs are moderate and stable rather than extreme: the 168.7 ms baseline is driven mainly by distance and route overhead, while jitter of 3.84 ms and the zero-loss result reinforce that the path is steady in this round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **168.7 ms** | | Jitter | **3.84 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **92.72 ms** | | Fiber Efficiency | **55%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,467.8 km** | | Vacuum RTT floor | **63.16 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **92.72 ms** | | Low-latency fiber material floor | **92.34 ms** | | Engineering floor (5% path allowance) | **97.36 ms** | | Research 1.33× mapped-fiber reference | **123.31 ms** | | Estimated unamplified path loss | **1988.2 dB** | | Transparent optical spans / inline amplifiers | **125 / 124** | | Published RTT inflation over fiber floor | **1.82×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **163.09 ms** | | Average RTT | **168.7 ms** | | Maximum RTT | **184.23 ms** | | Standard deviation | **4.36 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Amsterdam latency and RTT](/docs/network/latency/pairs/tpe-ams-rtt) — 166.5 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-tpe-rtt). - **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. # Amsterdam, Netherlands → Tokyo, Japan RTT 🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo probes from Amsterdam to Tokyo averaged 198.2 ms, with a minimum of 194.91 ms and a maximum of 216.11 ms across 50 samples and no packet loss. The geodesic distance of 9,311.4 km corresponds to a vacuum floor of 62.12 ms and a fiber floor of 91.18 ms. The observed average is 2.17 times that fiber floor, so the route operates at 46% fiber efficiency—a lower ratio than the raw distance alone would suggest. Tokyo ranked 17th out of the 19 outbound routes measured from Amsterdam in this round. Its standard deviation of 3.99 ms is just 2.0% of the average, below the 3.28% median variation across the network's outbound route set, so the elevated latency is very evenly paced. The route-specific insight is that Tokyo's delay from Amsterdam is less about variability than about a consistently high baseline; zero loss and 2.6 ms jitter make the path predictable, while the 2.17 inflation over the fiber floor points to substantial non-ideal overhead in this measurement round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **198.2 ms** | | Jitter | **2.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.18 ms** | | Fiber Efficiency | **46%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,311.4 km** | | Vacuum RTT floor | **62.12 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.18 ms** | | Low-latency fiber material floor | **90.82 ms** | | Engineering floor (5% path allowance) | **95.76 ms** | | Research 1.33× mapped-fiber reference | **121.28 ms** | | Estimated unamplified path loss | **1955.4 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **2.17×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **194.91 ms** | | Average RTT | **198.2 ms** | | Maximum RTT | **216.11 ms** | | Standard deviation | **3.99 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Amsterdam latency and RTT](/docs/network/latency/pairs/tyo-ams-rtt) — 197.4 ms **Fastest routes departing Amsterdam (AMS)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-tyo-rtt). - **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. # Berlin, Germany → Amsterdam, Netherlands RTT 🇩🇪 **Berlin, Germany (BER)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP probes from Berlin, Germany to Amsterdam, Netherlands averaged 7.2 ms round-trip time, with all 50 samples between 6.91 ms and 7.91 ms. The 0.23 ms standard deviation, 0.22 ms jitter, and 0% packet loss together define an Ultra-Low latency path that stayed consistent throughout the window. Relative to the 579.2 km geodesic distance, the measured average is 1.27 times the fiber floor of 5.67 ms, for a fiber efficiency of 78.8%. The gap between the measured RTT and the fiber floor is 1.53 ms, leaving a short international route with a small absolute overhead while staying close to the theoretical propagation budget. This route ranked 2nd in the 19-route measurement set for this network, placing it in the fastest tier. Its own spread-to-average ratio is about 3.2%, close to the 3.28% median across the set, so the low average was not achieved at the expense of stability. The route-specific value is an Ultra-Low RTT with near-floor efficiency and no packet loss. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **7.2 ms** | | Jitter | **0.22 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **5.67 ms** | | Fiber Efficiency | **78.8%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **579.2 km** | | Vacuum RTT floor | **3.86 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **5.67 ms** | | Low-latency fiber material floor | **5.65 ms** | | Engineering floor (5% path allowance) | **5.96 ms** | | Research 1.33× mapped-fiber reference | **7.54 ms** | | Estimated unamplified path loss | **121.6 dB** | | Transparent optical spans / inline amplifiers | **8 / 7** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **6.91 ms** | | Average RTT | **7.2 ms** | | Maximum RTT | **7.91 ms** | | Standard deviation | **0.23 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-ams-rtt). - **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. # Berlin, Germany → Frankfurt, Germany RTT 🇩🇪 **Berlin, Germany (BER)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round captured 50 ICMP echo probes from Berlin, Germany to Frankfurt, Germany and returned an average round-trip time of 6.1 ms, with a minimum of 5.9 ms and a maximum of 6.73 ms. No packets were lost, and the 0.18 ms standard deviation with 0.15 ms jitter marked a highly consistent sample. Relative to the 424.6 km geodesic distance, the measured average is 1.47 times the fiber floor of 4.16 ms, for a fiber efficiency of 68.2%. The 1.94 ms gap above the floor is more visible in proportional terms than the raw speed might imply, yet every reply stayed in the 5.9 ms to 6.73 ms range. This route held the top rank in the 19-route measurement set for this network. Its spread-to-average ratio is about 3.0%, below the 3.28% median across the set, so the fastest measured route was also one of the steadier ones. The practical signal is that this corridor combined the best observed RTT with 0% loss and sub-0.2 ms jitter. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **6.1 ms** | | Jitter | **0.15 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **4.16 ms** | | Fiber Efficiency | **68.2%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **424.6 km** | | Vacuum RTT floor | **2.83 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **4.16 ms** | | Low-latency fiber material floor | **4.14 ms** | | Engineering floor (5% path allowance) | **4.37 ms** | | Research 1.33× mapped-fiber reference | **5.53 ms** | | Estimated unamplified path loss | **89.2 dB** | | Transparent optical spans / inline amplifiers | **6 / 5** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **5.9 ms** | | Average RTT | **6.1 ms** | | Maximum RTT | **6.73 ms** | | Standard deviation | **0.18 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms **Fastest routes departing Berlin (BER)** * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-fra-rtt). - **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. # Berlin, Germany → São Paulo, Brazil RTT 🇩🇪 **Berlin, Germany (BER)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. During round 2026-08-16T04:07:28Z, 50 ICMP echo samples from Berlin, Germany to São Paulo, Brazil averaged 186.5 ms, with a minimum of 179.2 ms, a maximum of 206.69 ms, and zero packet loss. Jitter of 5.27 ms and a standard deviation of 6.78 ms keep the path in the fair latency tier. At 1.86 times the 100.2 ms fiber-floor estimate for the 10,232 km separation, the measured average translates to 53.7% fiber efficiency. The spread is about 3.6% of the average, which sits close to the 3.28% median variability seen across the 19 routes in this round. Ranked 16th of those 19, the route's absolute RTT is the main constraint; its loss-free, moderately jittered profile suggests a stable path whose cost is distance rather than erratic behavior. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **186.5 ms** | | Jitter | **5.27 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **100.2 ms** | | Fiber Efficiency | **53.7%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,232.3 km** | | Vacuum RTT floor | **68.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **100.2 ms** | | Low-latency fiber material floor | **99.8 ms** | | Engineering floor (5% path allowance) | **105.23 ms** | | Research 1.33× mapped-fiber reference | **133.27 ms** | | Estimated unamplified path loss | **2148.8 dB** | | Transparent optical spans / inline amplifiers | **135 / 134** | | Published RTT inflation over fiber floor | **1.86×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **179.2 ms** | | Average RTT | **186.5 ms** | | Maximum RTT | **206.69 ms** | | Standard deviation | **6.78 ms** | | Stdev / average | **3.6%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Berlin latency and RTT](/docs/network/latency/pairs/gru-ber-rtt) — 191.3 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Europe → South America)** * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms * [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms * [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-gru-rtt). - **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. # Berlin, Germany → Hong Kong RTT 🇩🇪 **Berlin, Germany (BER)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. During round 2026-08-16T04:07:28Z, 50 ICMP echo samples from Berlin, Germany to Hong Kong averaged 144.9 ms, with a minimum of 140.42 ms, a maximum of 158.73 ms, and zero packet loss. Jitter of 2.94 ms and a standard deviation of 3.7 ms place this route in the good latency tier. Measured against the 85.85 ms fiber floor for the 8,767 km geodesic, the average is 1.69 times that floor, or 59.3% fiber efficiency. The route's variability is about 2.6% of the average, below the 3.28% median variability across the 19 routes in this round. Ranked 12th of those 19, this route combines a good RTT with notably tight dispersion. The low jitter and zero loss indicate that the good tier is a result of absolute distance, rather than inconsistent network behavior. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **144.9 ms** | | Jitter | **2.94 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.85 ms** | | Fiber Efficiency | **59.3%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,767.1 km** | | Vacuum RTT floor | **58.49 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.85 ms** | | Low-latency fiber material floor | **85.51 ms** | | Engineering floor (5% path allowance) | **90.16 ms** | | Research 1.33× mapped-fiber reference | **114.19 ms** | | Estimated unamplified path loss | **1841.1 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **140.42 ms** | | Average RTT | **144.9 ms** | | Maximum RTT | **158.73 ms** | | Standard deviation | **3.7 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Moscow to Singapore latency and RTT](/docs/network/latency/pairs/mow-sin-rtt) — 147.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-hkg-rtt). - **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. # Berlin, Germany → Ashburn, USA RTT 🇩🇪 **Berlin, Germany (BER)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round recorded an average ICMP RTT of 85.7ms from Berlin to Ashburn, with 50 samples ranging from 83.7ms to 92.94ms and zero packet loss. Jitter was 1.62ms. This path ranks 8th in the set of 19 outbound routes from Berlin for this round. Its 2.12ms standard deviation is about 2.5% of the average, more stable than the 3.28% median standard-deviation-to-average ratio across the route set. Across a 6,744.5km great-circle span, the measured RTT is only 1.3 times the theoretical fiber-floor estimate of 66.05ms, yielding 77.1% fiber efficiency. The spread between best and worst samples is under 10ms, reinforcing the route's consistency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **85.7 ms** | | Jitter | **1.62 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **66.05 ms** | | Fiber Efficiency | **77.1%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,744.5 km** | | Vacuum RTT floor | **44.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **66.05 ms** | | Low-latency fiber material floor | **65.78 ms** | | Engineering floor (5% path allowance) | **69.36 ms** | | Research 1.33× mapped-fiber reference | **87.84 ms** | | Estimated unamplified path loss | **1416.4 dB** | | Transparent optical spans / inline amplifiers | **89 / 88** | | Published RTT inflation over fiber floor | **1.3×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **83.7 ms** | | Average RTT | **85.7 ms** | | Maximum RTT | **92.94 ms** | | Standard deviation | **2.12 ms** | | Stdev / average | **2.5%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Berlin latency and RTT](/docs/network/latency/pairs/iad-ber-rtt) — 86.1 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-iad-rtt). - **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. # Berlin, Germany → Johannesburg, South Africa RTT 🇩🇪 **Berlin, Germany (BER)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from Berlin, Germany to Johannesburg, South Africa averaged 172.1 ms over 50 samples at 100 ms intervals, with a minimum of 163.72 ms, a maximum of 199.65 ms, and no packet loss. Against an 8,836.6 km great-circle distance and a fiber-floor estimate of 86.53 ms, the measured RTT is 1.99 times the floor, yielding 50.3% fiber efficiency and a fair latency tier. The 7.34 ms standard deviation and 6.16 ms jitter show moderate probe-to-probe variation, with the maximum about 27.5 ms above the minimum. Among the 19 outbound routes measured from Berlin, this route ranks 15th, placing it in the slower half of the set, and its standard deviation equals about 4.3% of the average, above the 3.28% median variability seen across the network's measured routes. Despite the wider spread, zero packet loss and a sub-200 ms maximum make the route consistent enough for round-trip trend checks. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **172.1 ms** | | Jitter | **6.16 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **86.53 ms** | | Fiber Efficiency | **50.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,836.6 km** | | Vacuum RTT floor | **58.95 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **86.53 ms** | | Low-latency fiber material floor | **86.19 ms** | | Engineering floor (5% path allowance) | **90.87 ms** | | Research 1.33× mapped-fiber reference | **115.09 ms** | | Estimated unamplified path loss | **1855.7 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.99×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **163.72 ms** | | Average RTT | **172.1 ms** | | Maximum RTT | **199.65 ms** | | Standard deviation | **7.34 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Berlin latency and RTT](/docs/network/latency/pairs/jnb-ber-rtt) — 172.1 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms * [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt) — 198.5 ms **Same corridor (Europe → Africa)** * [Moscow to Johannesburg latency and RTT](/docs/network/latency/pairs/mow-jnb-rtt) — 201.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-jnb-rtt). - **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. # Berlin, Germany → Los Angeles, USA RTT 🇩🇪 **Berlin, Germany (BER)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, the Berlin-to-Los Angeles ICMP echo route averaged 140.9ms, with all 50 samples between 133.87ms and 162.61ms and zero packet loss. This route ranks 11th among the 19 outbound paths from Berlin in the same round. Its 5.85ms standard deviation is approximately 4.2% of the average, above the 3.28% median standard-deviation-to-average ratio, making it one of the more variable routes in the set. Given a great-circle distance of 9,331.9km, the RTT is 1.54 times above the theoretical fiber-floor estimate of 91.39ms, corresponding to 64.9% fiber efficiency. The 28.74ms gap between minimum and maximum samples is worth noting for a route that otherwise completed every probe without loss. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **140.9 ms** | | Jitter | **4.81 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.39 ms** | | Fiber Efficiency | **64.9%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,331.9 km** | | Vacuum RTT floor | **62.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.39 ms** | | Low-latency fiber material floor | **91.02 ms** | | Engineering floor (5% path allowance) | **95.97 ms** | | Research 1.33× mapped-fiber reference | **121.54 ms** | | Estimated unamplified path loss | **1959.7 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **1.54×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **133.87 ms** | | Average RTT | **140.9 ms** | | Maximum RTT | **162.61 ms** | | Standard deviation | **5.85 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Berlin latency and RTT](/docs/network/latency/pairs/lax-ber-rtt) — 139.3 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-lax-rtt). - **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. # Berlin, Germany → London, UK RTT 🇩🇪 **Berlin, Germany (BER)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, Berlin-to-London ICMP echo RTT averaged 15.2 ms over 50 samples, with a 14.57 ms minimum and 16.96 ms maximum. The 0.49 ms standard deviation and 0.4 ms jitter point to a very stable path, and zero packet loss was recorded. This link ranked third among the 19 routes measured in the same round. Its standard-deviation-to-average ratio is about 3.22%, essentially matching the 3.28% median ratio for that set, so the 15.2 ms average is a representative figure rather than an outlier pulled by a few slow samples. At a geodesic distance of 934.7 km, the theoretical fiber floor is 9.15 ms; the measured average of 15.2 ms is 1.66 times that floor, or 60.2% fiber efficiency. The tight 2.39 ms spread between minimum and maximum suggests the remaining overhead is consistent across the sample window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **15.2 ms** | | Jitter | **0.4 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **9.15 ms** | | Fiber Efficiency | **60.2%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **934.7 km** | | Vacuum RTT floor | **6.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **9.15 ms** | | Low-latency fiber material floor | **9.12 ms** | | Engineering floor (5% path allowance) | **9.61 ms** | | Research 1.33× mapped-fiber reference | **12.17 ms** | | Estimated unamplified path loss | **196.3 dB** | | Transparent optical spans / inline amplifiers | **13 / 12** | | Published RTT inflation over fiber floor | **1.66×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **14.57 ms** | | Average RTT | **15.2 ms** | | Maximum RTT | **16.96 ms** | | Standard deviation | **0.49 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-lon-rtt). - **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. # Berlin, Germany → Melbourne, Australia RTT 🇩🇪 **Berlin, Germany (BER)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. During round 2026-08-16T04:07:28Z, 50 ICMP echo samples from Berlin, Germany to Melbourne, Australia averaged 256.2 ms, with a minimum of 246.67 ms, a maximum of 285.1 ms, and zero packet loss. Jitter of 5.78 ms and a standard deviation of 7.82 ms place this route in the high latency tier. Relative to the 156.34 ms fiber floor for the 15,965 km geodesic, the measured average is 1.64 times that floor, or 61% fiber efficiency. The route's variability is about 3.05% of the average, just below the 3.28% median variability across the 19 routes in this round. Ranked 18th of those 19, this is a high-latency route, but it is not an erratic one: zero packet loss and a jitter below 6 ms keep the connection consistent despite the long distance. Its fiber efficiency is reasonably good for a path of this length, meaning the extra milliseconds are largely explained by geography. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **256.2 ms** | | Jitter | **5.78 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **156.34 ms** | | Fiber Efficiency | **61%** | | Latency Tier | High | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,965.1 km** | | Vacuum RTT floor | **106.51 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **156.34 ms** | | Low-latency fiber material floor | **155.71 ms** | | Engineering floor (5% path allowance) | **164.18 ms** | | Research 1.33× mapped-fiber reference | **207.94 ms** | | Estimated unamplified path loss | **3352.7 dB** | | Transparent optical spans / inline amplifiers | **210 / 209** | | Published RTT inflation over fiber floor | **1.64×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **246.67 ms** | | Average RTT | **256.2 ms** | | Maximum RTT | **285.1 ms** | | Standard deviation | **7.82 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Berlin latency and RTT](/docs/network/latency/pairs/mel-ber-rtt) — 254.7 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-mel-rtt). - **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. # Berlin, Germany → Miami, USA RTT 🇩🇪 **Berlin, Germany (BER)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. In the measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Berlin to Miami averaged 118.3 ms, with a minimum of 115.44 ms, a maximum of 127.36 ms, and zero packet loss. The route's jitter of 2.21 ms and standard deviation of 2.6 ms kept the round-trip times tightly grouped around the average. The observed 118.3 ms average is 1.51 times the 78.44 ms fiber-floor reference for the 8,009.8 km geodesic separation, giving a fiber efficiency of 66.3 percent. This places the pair in the good latency tier while leaving room above the speed-of-light-in-fiber minimum. Within the set of 19 outbound routes measured in the same cycle, Berlin-Miami is ranked 9th, and its standard deviation is about 2.2 percent of the average RTT, below the 3.28 percent median across the route set. With no packet loss and tight jitter, the measurement offers a dependable RTT baseline for traffic destined toward Miami's North-South American gateway. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **118.3 ms** | | Jitter | **2.21 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **78.44 ms** | | Fiber Efficiency | **66.3%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,009.8 km** | | Vacuum RTT floor | **53.44 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **78.44 ms** | | Low-latency fiber material floor | **78.12 ms** | | Engineering floor (5% path allowance) | **82.37 ms** | | Research 1.33× mapped-fiber reference | **104.32 ms** | | Estimated unamplified path loss | **1682.1 dB** | | Transparent optical spans / inline amplifiers | **106 / 105** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **115.44 ms** | | Average RTT | **118.3 ms** | | Maximum RTT | **127.36 ms** | | Standard deviation | **2.6 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Berlin latency and RTT](/docs/network/latency/pairs/mia-ber-rtt) — 117.3 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-mia-rtt). - **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. # Berlin, Germany → Moscow, Russia RTT 🇩🇪 **Berlin, Germany (BER)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, Berlin-to-Moscow ICMP echo RTT averaged 28.6 ms over 50 samples, with replies spanning 27.35 ms to 31.58 ms. The 1.1 ms standard deviation and 0.83 ms jitter are moderate in absolute terms, and all probes completed with zero packet loss. The 19-route set measured in the same round places this link sixth, and its standard-deviation-to-average ratio is about 3.85% versus the set's 3.28% median. The 28.6 ms average is therefore valid, but it sits on a path with more sample-to-sample movement than the set's typical route. At a geodesic distance of 1,613.5 km, the fiber floor is 15.8 ms, making the 28.6 ms average 1.81 times that floor, or 55.2% fiber efficiency. The 1.1 ms standard deviation is the most relevant caveat: individual round trips can sit roughly a millisecond or more away from the average, even though loss remained at zero. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **28.6 ms** | | Jitter | **0.83 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **15.8 ms** | | Fiber Efficiency | **55.2%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,613.5 km** | | Vacuum RTT floor | **10.76 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **15.8 ms** | | Low-latency fiber material floor | **15.74 ms** | | Engineering floor (5% path allowance) | **16.59 ms** | | Research 1.33× mapped-fiber reference | **21.01 ms** | | Estimated unamplified path loss | **338.8 dB** | | Transparent optical spans / inline amplifiers | **22 / 21** | | Published RTT inflation over fiber floor | **1.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **27.35 ms** | | Average RTT | **28.6 ms** | | Maximum RTT | **31.58 ms** | | Standard deviation | **1.1 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Moscow (MOW)** * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-mow-rtt). - **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. # Berlin, Germany → Marseille, France RTT 🇩🇪 **Berlin, Germany (BER)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, Berlin-to-Marseille ICMP echo RTT averaged 20.2 ms over 50 samples, with every reply between 19.92 ms and 21.65 ms. The 0.31 ms standard deviation and 0.22 ms jitter show the round-trip time stayed tightly grouped, and none of the samples were lost. This link ranked fifth among the 19 routes measured in the same round. Its standard-deviation-to-average ratio comes to about 1.53%, well below the 3.28% median ratio for that set, so the 20.2 ms average is a stable central value rather than a product of uneven samples. Covering 1,187 km geodesic distance, the route's theoretical fiber floor is 11.62 ms; the measured average of 20.2 ms equates to 1.74 times that floor, or 57.5% fiber efficiency. With a maximum-to-minimum spread of just 1.73 ms, the path's overhead is consistent enough that the average is a meaningful round-trip timing reference. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **20.2 ms** | | Jitter | **0.22 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **11.62 ms** | | Fiber Efficiency | **57.5%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **1,187 km** | | Vacuum RTT floor | **7.92 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **11.62 ms** | | Low-latency fiber material floor | **11.58 ms** | | Engineering floor (5% path allowance) | **12.21 ms** | | Research 1.33× mapped-fiber reference | **15.46 ms** | | Estimated unamplified path loss | **249.3 dB** | | Transparent optical spans / inline amplifiers | **16 / 15** | | Published RTT inflation over fiber floor | **1.74×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **19.92 ms** | | Average RTT | **20.2 ms** | | Maximum RTT | **21.65 ms** | | Standard deviation | **0.31 ms** | | Stdev / average | **1.5%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-mrs-rtt). - **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. # Berlin, Germany → New York, USA RTT 🇩🇪 **Berlin, Germany (BER)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. In measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Berlin to New York produced an average RTT of 79.6 ms, a minimum of 78.03 ms, a maximum of 83.78 ms, and no packet loss. Jitter of 1.07 ms and a standard deviation of 1.28 ms put the data in the excellent latency tier. The average is 1.27 times the 62.7 ms fiber floor for the 6,402.4 km geodesic distance, corresponding to 78.8 percent fiber efficiency. The measured RTT stays close to the physical reference, with a narrow spread across all 50 samples. Among the 19 outbound routes in this cycle, Berlin-New York ranks 7th, and its standard deviation is about 1.6 percent of the average RTT, comfortably below the 3.28 percent median across the route set. For a corridor anchored at New York's carrier hotels, the zero-loss result and low jitter make this a clean reference point for ICMP RTT expectations. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **79.6 ms** | | Jitter | **1.07 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **62.7 ms** | | Fiber Efficiency | **78.8%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,402.4 km** | | Vacuum RTT floor | **42.71 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **62.7 ms** | | Low-latency fiber material floor | **62.45 ms** | | Engineering floor (5% path allowance) | **65.84 ms** | | Research 1.33× mapped-fiber reference | **83.39 ms** | | Estimated unamplified path loss | **1344.5 dB** | | Transparent optical spans / inline amplifiers | **85 / 84** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **78.03 ms** | | Average RTT | **79.6 ms** | | Maximum RTT | **83.78 ms** | | Standard deviation | **1.28 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Berlin latency and RTT](/docs/network/latency/pairs/nyc-ber-rtt) — 78.8 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Europe → North America)** * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-nyc-rtt). - **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. # Berlin, Germany → Paris, France RTT 🇩🇪 **Berlin, Germany (BER)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, the Berlin-to-Paris ICMP echo measurements averaged 15.6ms across 50 samples, with the full run between 14.9ms and 17.81ms and no packet loss. This route sits 4th among the 19 outbound paths measured from Berlin in the same round. Its standard deviation of 0.63ms is about 4% of the average, slightly above the 3.28% median standard-deviation-to-average ratio across the route set, so the path is stable but not the steadiest in the group. Against the 880.6km great-circle distance, the observed RTT is 1.81 times the theoretical fiber-floor estimate of 8.62ms, equating to 55.3% fiber efficiency. For an ultra-low-latency route, the jitter of 0.52ms and zero loss leave little to fault. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **15.6 ms** | | Jitter | **0.52 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **8.62 ms** | | Fiber Efficiency | **55.3%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **880.6 km** | | Vacuum RTT floor | **5.87 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **8.62 ms** | | Low-latency fiber material floor | **8.59 ms** | | Engineering floor (5% path allowance) | **9.06 ms** | | Research 1.33× mapped-fiber reference | **11.47 ms** | | Estimated unamplified path loss | **184.9 dB** | | Transparent optical spans / inline amplifiers | **12 / 11** | | Published RTT inflation over fiber floor | **1.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **14.9 ms** | | Average RTT | **15.6 ms** | | Maximum RTT | **17.81 ms** | | Standard deviation | **0.63 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-par-rtt). - **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. # Berlin, Germany → Seattle, USA RTT 🇩🇪 **Berlin, Germany (BER)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. During the measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Berlin to Seattle produced an average RTT of 139.7 ms, with a minimum of 135.21 ms, a maximum of 156.43 ms, and no packet loss. Jitter of 3.54 ms and a standard deviation of 4.65 ms place the route in the good latency tier. The 139.7 ms average is 1.75 times the 79.73 ms fiber floor for an 8,142.2 km geodesic distance, yielding 57.1 percent fiber efficiency. The distribution is wider in absolute terms, yet the route remains loss-free across all probes. Among the 19 outbound routes in this cycle, Berlin-Seattle is ranked 10th, and its standard deviation is about 3.3 percent of the average RTT, essentially matching the 3.28 percent median across the route set. For a Pacific Northwest interconnection hub, this consistency gives network teams a reliable RTT baseline toward Seattle. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **139.7 ms** | | Jitter | **3.54 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **79.73 ms** | | Fiber Efficiency | **57.1%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,142.2 km** | | Vacuum RTT floor | **54.32 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **79.73 ms** | | Low-latency fiber material floor | **79.41 ms** | | Engineering floor (5% path allowance) | **83.73 ms** | | Research 1.33× mapped-fiber reference | **106.05 ms** | | Estimated unamplified path loss | **1709.9 dB** | | Transparent optical spans / inline amplifiers | **107 / 106** | | Published RTT inflation over fiber floor | **1.75×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **135.21 ms** | | Average RTT | **139.7 ms** | | Maximum RTT | **156.43 ms** | | Standard deviation | **4.65 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Berlin latency and RTT](/docs/network/latency/pairs/sea-ber-rtt) — 140.9 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-sea-rtt). - **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. # Berlin, Germany → Singapore RTT 🇩🇪 **Berlin, Germany (BER)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo round-trip time from Berlin, Germany to Singapore, Singapore averaged 158.3ms, with a 154.42ms minimum and 169.59ms maximum over 50 samples. Zero packets were lost and jitter was 2.74ms, so the path was stable for the full window. The measured average is 1.63 times the 97.19ms fiber-floor estimate for the 9,925km geodesic, an overhead of about 61ms above the theoretical minimum. Fiber efficiency of 61.4% puts that gap in context for an intercontinental route and aligns with the Fair latency tier. Berlin–Singapore is ranked 14th among the 19 outbound routes in this round, while the network-wide median variability relative to the average is 3.28%. The route's own standard deviation of 3.09ms works out to about 1.95% of the average, so its consistency is better than the network median. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **158.3 ms** | | Jitter | **2.74 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **97.19 ms** | | Fiber Efficiency | **61.4%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **9,925 km** | | Vacuum RTT floor | **66.21 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **97.19 ms** | | Low-latency fiber material floor | **96.8 ms** | | Engineering floor (5% path allowance) | **102.07 ms** | | Research 1.33× mapped-fiber reference | **129.27 ms** | | Estimated unamplified path loss | **2084.3 dB** | | Transparent optical spans / inline amplifiers | **131 / 130** | | Published RTT inflation over fiber floor | **1.63×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **154.42 ms** | | Average RTT | **158.3 ms** | | Maximum RTT | **169.59 ms** | | Standard deviation | **3.09 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Berlin latency and RTT](/docs/network/latency/pairs/sin-ber-rtt) — 160.3 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-sin-rtt). - **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. # Berlin, Germany → Sydney, Australia RTT 🇩🇪 **Berlin, Germany (BER)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Berlin, Germany to Sydney, Australia averaged 262.1ms, with a minimum of 255.96ms and a maximum of 280.93ms over 50 samples. Packet loss was 0% and jitter was 4.49ms, indicating the path stayed continuous even at high raw latency. The measured average is 1.66 times the 157.54ms fiber-floor estimate for the 16,087.7km geodesic, or about 104.6ms above the theoretical minimum. Fiber efficiency of 60.1% makes clear that most of the delay is tied to the distance itself rather than to unstable behavior. Berlin–Sydney sits 19th among the 19 outbound routes in this round, and the network-wide median variability relative to the average is 3.28%. Its standard deviation of 5.08ms is about 1.94% of the average, so the route is more consistent than the network median despite being in the High latency tier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **262.1 ms** | | Jitter | **4.49 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **157.54 ms** | | Fiber Efficiency | **60.1%** | | Latency Tier | High | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,087.7 km** | | Vacuum RTT floor | **107.33 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **157.54 ms** | | Low-latency fiber material floor | **156.91 ms** | | Engineering floor (5% path allowance) | **165.44 ms** | | Research 1.33× mapped-fiber reference | **209.53 ms** | | Estimated unamplified path loss | **3378.4 dB** | | Transparent optical spans / inline amplifiers | **212 / 211** | | Published RTT inflation over fiber floor | **1.66×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **255.96 ms** | | Average RTT | **262.1 ms** | | Maximum RTT | **280.93 ms** | | Standard deviation | **5.08 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Berlin latency and RTT](/docs/network/latency/pairs/syd-ber-rtt) — 260.5 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-syd-rtt). - **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. # Berlin, Germany → Taipei, Taiwan RTT 🇩🇪 **Berlin, Germany (BER)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo round-trip time from Berlin, Germany to Taipei, Taiwan in the 2026-08-16T04:07:28Z round averaged 156.8ms, with a minimum of 150.23ms and a maximum of 174.22ms from 50 samples. Jitter was 4.24ms and packet loss was 0%, so the path was both moderate in latency and clean during the window. The measured average is 1.78 times the 87.84ms fiber-floor estimate for the 8,970.4km geodesic, adding about 68.9ms of overhead above the theoretical minimum. With fiber efficiency at 56%, the route sits in the Fair latency tier while carrying a noticeable gap from the theoretical floor. This route is 13th among the 19 outbound routes in the round, while the network-wide median variability relative to the average is 3.28%. The route's own standard deviation of 5.07ms is about 3.23% of the average, placing its variability almost exactly in line with the network median. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **156.8 ms** | | Jitter | **4.24 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **87.84 ms** | | Fiber Efficiency | **56%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,970.4 km** | | Vacuum RTT floor | **59.84 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **87.84 ms** | | Low-latency fiber material floor | **87.49 ms** | | Engineering floor (5% path allowance) | **92.25 ms** | | Research 1.33× mapped-fiber reference | **116.83 ms** | | Estimated unamplified path loss | **1883.8 dB** | | Transparent optical spans / inline amplifiers | **118 / 117** | | Published RTT inflation over fiber floor | **1.78×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **150.23 ms** | | Average RTT | **156.8 ms** | | Maximum RTT | **174.22 ms** | | Standard deviation | **5.07 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Berlin latency and RTT](/docs/network/latency/pairs/tpe-ber-rtt) — 158.6 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-tpe-rtt). - **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. # Berlin, Germany → Tokyo, Japan RTT 🇩🇪 **Berlin, Germany (BER)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Berlin, Germany to Tokyo, Japan produced an average RTT of 187.5 ms across 50 samples at 100 ms intervals, with a minimum of 181.19 ms, a maximum of 200.11 ms, and zero packet loss. The 8,937.7 km great-circle distance implies a fiber-floor RTT of 87.53 ms, so the measured average is 2.14 times that floor, translating to 46.7% fiber efficiency and a fair latency tier. Jitter of 3.12 ms and a standard deviation of 4.64 ms point to a stable path despite the long distance. This route ranks 17th among the 19 outbound routes measured from Berlin, placing it near the slower end of the city's set, while its standard deviation is about 2.5% of the average, below the 3.28% median variability seen across the network's measured routes. The main operational takeaway is that absolute RTT is high but consistent, with no loss observed during the round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **187.5 ms** | | Jitter | **3.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **87.53 ms** | | Fiber Efficiency | **46.7%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,937.7 km** | | Vacuum RTT floor | **59.63 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **87.53 ms** | | Low-latency fiber material floor | **87.17 ms** | | Engineering floor (5% path allowance) | **91.91 ms** | | Research 1.33× mapped-fiber reference | **116.41 ms** | | Estimated unamplified path loss | **1876.9 dB** | | Transparent optical spans / inline amplifiers | **118 / 117** | | Published RTT inflation over fiber floor | **2.14×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **181.19 ms** | | Average RTT | **187.5 ms** | | Maximum RTT | **200.11 ms** | | Standard deviation | **4.64 ms** | | Stdev / average | **2.5%** | ## Route Context * Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Berlin latency and RTT](/docs/network/latency/pairs/tyo-ber-rtt) — 186.1 ms **Fastest routes departing Berlin (BER)** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-tyo-rtt). - **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. # Frankfurt, Germany → Amsterdam, Netherlands RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round shows ICMP echo RTT from Frankfurt, Germany to Amsterdam, Netherlands averaging 5.9 ms across 50 samples at 100 ms intervals, with a minimum of 5.62 ms, a maximum of 6.84 ms, and zero packet loss. For the 365.1 km great-circle distance, the fiber-floor RTT is 3.57 ms, so the measured average is 1.65 times that floor, an efficiency of 60.6% and an ultra-low latency tier. The tiny standard deviation of 0.25 ms and jitter of 0.17 ms indicate an exceptionally consistent path. This is the fastest of the 19 outbound routes measured from Frankfurt, and the standard deviation is about 4.2% of the average, slightly above the 3.28% median variability seen across the network's measured routes. In practical terms, the route's round-trip time rarely moves by more than a fraction of a millisecond, so it can serve as a stable reference point for regional measurements. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **5.9 ms** | | Jitter | **0.17 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.57 ms** | | Fiber Efficiency | **60.6%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **365.1 km** | | Vacuum RTT floor | **2.44 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.57 ms** | | Low-latency fiber material floor | **3.56 ms** | | Engineering floor (5% path allowance) | **3.75 ms** | | Research 1.33× mapped-fiber reference | **4.75 ms** | | Estimated unamplified path loss | **76.7 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.65×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **5.62 ms** | | Average RTT | **5.9 ms** | | Maximum RTT | **6.84 ms** | | Standard deviation | **0.25 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-ams-rtt). - **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. # Frankfurt, Germany → Berlin, Germany RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT measurements from Frankfurt to Berlin in round 2026-08-16T04:07:28Z averaged 6.1 ms across 50 samples, with a minimum of 5.91 ms, a maximum of 6.79 ms, and 0% packet loss. The 424.6 km geodesic path has a vacuum floor of 2.83 ms and a fiber floor of 4.16 ms; the measured RTT is 1.47 times that fiber floor, which translates to 68.2% fiber efficiency. This domestic route is already operating close to the optical limit for the straight-line distance, leaving only limited headroom. Within a route set of 19 measured paths, this route ranked second, and the corresponding network median variability was 3.28% of average RTT. Frankfurt–Berlin recorded a standard deviation of 0.18 ms and jitter of 0.16 ms, or about 2.9% of the mean, so its stability is tighter than the network median. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **6.1 ms** | | Jitter | **0.16 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **4.16 ms** | | Fiber Efficiency | **68.2%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **424.6 km** | | Vacuum RTT floor | **2.83 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **4.16 ms** | | Low-latency fiber material floor | **4.14 ms** | | Engineering floor (5% path allowance) | **4.37 ms** | | Research 1.33× mapped-fiber reference | **5.53 ms** | | Estimated unamplified path loss | **89.2 dB** | | Transparent optical spans / inline amplifiers | **6 / 5** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **5.91 ms** | | Average RTT | **6.1 ms** | | Maximum RTT | **6.79 ms** | | Standard deviation | **0.18 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms **Fastest routes arriving at Berlin (BER)** * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-ber-rtt). - **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. # Frankfurt, Germany → São Paulo, Brazil RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo requests from Frankfurt to São Paulo averaged 181.3 ms over 50 samples, with a minimum of 176.28 ms, a maximum of 197.75 ms and zero packet loss. A 3.73 ms standard deviation and 3.34 ms jitter keep the route's variability at about 2.1% of the average, tighter than the 3.28% median for the 19-route set. Ranked 15th of 19 outbound routes by average RTT, this path is among the slower half of the set, consistent with a great-circle distance of 9,807.7 km. Its average is 1.89 times the theoretical fiber floor of 96.04 ms, giving a fiber efficiency of 53%. The notable feature is consistency: 50 consecutive probes with no loss and a standard deviation below 4 ms mean the high latency is steady rather than erratic. The Fair latency tier reflects the high absolute RTT, not instability, making the 181.3 ms average a stable reference point for this long-haul route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **181.3 ms** | | Jitter | **3.34 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **96.04 ms** | | Fiber Efficiency | **53%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,807.7 km** | | Vacuum RTT floor | **65.43 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **96.04 ms** | | Low-latency fiber material floor | **95.66 ms** | | Engineering floor (5% path allowance) | **100.86 ms** | | Research 1.33× mapped-fiber reference | **127.74 ms** | | Estimated unamplified path loss | **2059.6 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.89×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **176.28 ms** | | Average RTT | **181.3 ms** | | Maximum RTT | **197.75 ms** | | Standard deviation | **3.73 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Frankfurt latency and RTT](/docs/network/latency/pairs/gru-fra-rtt) — 186.2 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Europe → South America)** * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms * [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms * [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-gru-rtt). - **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. # Frankfurt, Germany → Hong Kong RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo RTT from Frankfurt to Hong Kong averaged 152 ms across 50 samples, with a minimum of 144.15 ms and a maximum of 171.03 ms. Packet loss was zero, but the 6.84 ms standard deviation and 4.6 ms jitter yield variability of about 4.5% of the average, above the 3.28% median variability of the 19-route set. Ranked 13th of 19 outbound routes by average RTT, this route sits in the lower-middle of the measured set. The 152 ms average is 1.69 times the theoretical fiber floor of 89.87 ms for the 9,177.1 km great-circle distance, corresponding to a fiber efficiency of 59.1%. With no loss but a wider spread than the route set's median, this connection shows stable average latency with occasional larger excursions. The round's Fair latency tier captures that combination of moderate delay and above-median variability. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **152 ms** | | Jitter | **4.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.87 ms** | | Fiber Efficiency | **59.1%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,177.1 km** | | Vacuum RTT floor | **61.22 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.87 ms** | | Low-latency fiber material floor | **89.51 ms** | | Engineering floor (5% path allowance) | **94.37 ms** | | Research 1.33× mapped-fiber reference | **119.53 ms** | | Estimated unamplified path loss | **1927.2 dB** | | Transparent optical spans / inline amplifiers | **121 / 120** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **144.15 ms** | | Average RTT | **152 ms** | | Maximum RTT | **171.03 ms** | | Standard deviation | **6.84 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Frankfurt latency and RTT](/docs/network/latency/pairs/hkg-fra-rtt) — 150.7 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-hkg-rtt). - **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. # Frankfurt, Germany → Ashburn, USA RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo round from Frankfurt, Germany to Ashburn, USA recorded an average RTT of 80.7 ms across 50 samples, with a minimum of 79.19 ms, a maximum of 87.49 ms, and zero packet loss. At 6,566 km, this is a long-haul transatlantic pair, and the measured average is only 1.26 times the theoretical fiber floor of 64.3 ms - a strong efficiency result at 79.7%. The 1.42 ms standard deviation and 1.11 ms jitter keep the sample tightly grouped despite the distance. The same round covers 19 routes from this network, with Frankfurt-Ashburn ranking eighth. Its variability is about 1.8% of the average RTT, well below the network's median variability of 3.28%, making this an efficient and comparatively stable long-distance route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **80.7 ms** | | Jitter | **1.11 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **64.3 ms** | | Fiber Efficiency | **79.7%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **6,566 km** | | Vacuum RTT floor | **43.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **64.3 ms** | | Low-latency fiber material floor | **64.04 ms** | | Engineering floor (5% path allowance) | **67.52 ms** | | Research 1.33× mapped-fiber reference | **85.52 ms** | | Estimated unamplified path loss | **1378.9 dB** | | Transparent optical spans / inline amplifiers | **87 / 86** | | Published RTT inflation over fiber floor | **1.26×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **79.19 ms** | | Average RTT | **80.7 ms** | | Maximum RTT | **87.49 ms** | | Standard deviation | **1.42 ms** | | Stdev / average | **1.8%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Frankfurt latency and RTT](/docs/network/latency/pairs/iad-fra-rtt) — 81.2 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-iad-rtt). - **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. # Frankfurt, Germany → Johannesburg, South Africa RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round used 50 ICMP echo probes from Frankfurt to Johannesburg at 100 ms intervals; the average round-trip time was 188.4 ms, with replies from 182.33 ms to 218.93 ms. All 50 probes returned, so packet loss was 0%. Johannesburg's role as an African anchor connecting Southern Africa with Europe and Asia is visible in the route's 2.22 times inflation over the 84.87 ms fiber floor for 8,666.9 km, or about 45% fiber efficiency. The 6.75 ms standard deviation is 3.6% of the average, slightly above the 3.28% median variation across the route set. This route ranks 16th among the 19 outbound routes from Frankfurt. The 36.6 ms gap between the fastest and slowest replies is wider than the average would suggest, so occasional slower answers drive the spread, even though the minimum and average stay close and no packets are lost. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **188.4 ms** | | Jitter | **4.87 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **84.87 ms** | | Fiber Efficiency | **45%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,666.9 km** | | Vacuum RTT floor | **57.82 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **84.87 ms** | | Low-latency fiber material floor | **84.53 ms** | | Engineering floor (5% path allowance) | **89.13 ms** | | Research 1.33× mapped-fiber reference | **112.88 ms** | | Estimated unamplified path loss | **1820.1 dB** | | Transparent optical spans / inline amplifiers | **114 / 113** | | Published RTT inflation over fiber floor | **2.22×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **182.33 ms** | | Average RTT | **188.4 ms** | | Maximum RTT | **218.93 ms** | | Standard deviation | **6.75 ms** | | Stdev / average | **3.6%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt) — 198.5 ms **Same corridor (Europe → Africa)** * [Moscow to Johannesburg latency and RTT](/docs/network/latency/pairs/mow-jnb-rtt) — 201.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-jnb-rtt). - **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. # Frankfurt, Germany → Los Angeles, USA RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo probes from Frankfurt, Germany to Los Angeles, USA averaged 141.8 ms across 50 samples sent every 100 ms, with a minimum of 135.2 ms, a maximum of 158.63 ms, and no packet loss. The 9,324.5 km great-circle path has a theoretical vacuum floor of 62.21 ms and a straight-fiber floor of 91.31 ms, so the measured average is 1.55 times the fiber floor and reaches 64.4% fiber efficiency. The route's 5.99 ms standard deviation and 5.12 ms jitter place it in the good latency tier with only modest variation. In the 19-route Frankfurt set for this round, the route ranked 11th, and the median standard-deviation-to-average ratio for the set was 3.28%; this route's deviation of about 4.2% of its average sits slightly above that midpoint. Because Los Angeles is the primary US West Coast landing point for trans-Pacific cables, this no-loss, moderately stable RTT offers a useful baseline for traffic that continues toward East Asia from the US West Coast. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **141.8 ms** | | Jitter | **5.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.31 ms** | | Fiber Efficiency | **64.4%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,324.5 km** | | Vacuum RTT floor | **62.21 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.31 ms** | | Low-latency fiber material floor | **90.95 ms** | | Engineering floor (5% path allowance) | **95.89 ms** | | Research 1.33× mapped-fiber reference | **121.45 ms** | | Estimated unamplified path loss | **1958.1 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **1.55×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **135.2 ms** | | Average RTT | **141.8 ms** | | Maximum RTT | **158.63 ms** | | Standard deviation | **5.99 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Frankfurt latency and RTT](/docs/network/latency/pairs/lax-fra-rtt) — 142.3 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-lax-rtt). - **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. # Frankfurt, Germany → London, UK RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT measurements from Frankfurt to London in round 2026-08-16T04:07:28Z averaged 12.9 ms over 50 samples, with a minimum of 12.38 ms, a maximum of 14.46 ms, and 0% packet loss. Given a geodesic distance of 639.5 km, the vacuum floor is 4.27 ms and the fiber floor is 6.26 ms. The measured RTT is 2.06 times the fiber floor, or 48.5% fiber efficiency, showing that this cross-border route carries more overhead above the optical straight-line bound than the tightest possible path. Within a route set of 19 measured paths, this route ranked fourth, while the network median variability was 3.28% of average RTT. Here the standard deviation was 0.43 ms and jitter was 0.33 ms, approximately 3.3% of the mean, placing stability near the network median. Zero packet loss and ultra-low tier latency still make this a consistent reference for Frankfurt–London RTT, though the lower fiber efficiency hints at more headroom for path optimization than the raw distance alone implies. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **12.9 ms** | | Jitter | **0.33 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **6.26 ms** | | Fiber Efficiency | **48.5%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **639.5 km** | | Vacuum RTT floor | **4.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **6.26 ms** | | Low-latency fiber material floor | **6.24 ms** | | Engineering floor (5% path allowance) | **6.58 ms** | | Research 1.33× mapped-fiber reference | **8.33 ms** | | Estimated unamplified path loss | **134.3 dB** | | Transparent optical spans / inline amplifiers | **9 / 8** | | Published RTT inflation over fiber floor | **2.06×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **12.38 ms** | | Average RTT | **12.9 ms** | | Maximum RTT | **14.46 ms** | | Standard deviation | **0.43 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-lon-rtt). - **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. # Frankfurt, Germany → Melbourne, Australia RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo round-trip run from Frankfurt, Germany to Melbourne, Australia produced an average RTT of 250.1 ms across 50 samples, with a minimum of 236.31 ms and a maximum of 287.22 ms. No packets were lost, yet a standard deviation of 11.19 ms and jitter of 9.69 ms make the timing spread more meaningful than the average alone. The measured average is 1.57 times the theoretical fiber-floor time, so the observed fiber efficiency is 63.9% over a 16,315.5 km geodesic distance. Ranked 18th out of 19 routes leaving this origin, the route has a stdev-to-average ratio of roughly 4.5%, above the 3.28% median for the set. The useful signal is the wide sample range: even with no loss, round-trip time can swing by about 51 ms between the best and worst probes. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **250.1 ms** | | Jitter | **9.69 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **159.77 ms** | | Fiber Efficiency | **63.9%** | | Latency Tier | High | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,315.5 km** | | Vacuum RTT floor | **108.85 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **159.77 ms** | | Low-latency fiber material floor | **159.13 ms** | | Engineering floor (5% path allowance) | **167.78 ms** | | Research 1.33× mapped-fiber reference | **212.5 ms** | | Estimated unamplified path loss | **3426.2 dB** | | Transparent optical spans / inline amplifiers | **215 / 214** | | Published RTT inflation over fiber floor | **1.57×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **236.31 ms** | | Average RTT | **250.1 ms** | | Maximum RTT | **287.22 ms** | | Standard deviation | **11.19 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Frankfurt latency and RTT](/docs/network/latency/pairs/mel-fra-rtt) — 248.6 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-mel-rtt). - **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. # Frankfurt, Germany → Miami, USA RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo probes from Frankfurt, Germany to Miami, USA averaged 112 ms over 50 samples at 100 ms intervals, with a narrow range of 110.01 ms to 117.35 ms and zero packet loss. The 7,777.9 km great-circle route has a vacuum floor of 51.89 ms and a straight-fiber floor of 76.17 ms, making the measured average 1.47 times the fiber floor with 68% fiber efficiency. Variability is a standout feature: standard deviation is just 1.8 ms and jitter 1.53 ms, or about 1.6% of the average RTT. Among the 19 routes measured out of Frankfurt in this round, the median relative deviation was 3.28%, so this route is considerably steadier than the midpoint and earned its good latency tier. As Miami hosts the NAP of the Americas and serves as the digital gateway between North and South America, a stable Frankfurt-to-Miami RTT is especially useful for baseline checks of traffic entering that hub. The zero packet loss and low jitter seen in this round make the route a dependable point of reference for the Latin American convergence corridor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **112 ms** | | Jitter | **1.53 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.17 ms** | | Fiber Efficiency | **68%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,777.9 km** | | Vacuum RTT floor | **51.89 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.17 ms** | | Low-latency fiber material floor | **75.86 ms** | | Engineering floor (5% path allowance) | **79.99 ms** | | Research 1.33× mapped-fiber reference | **101.3 ms** | | Estimated unamplified path loss | **1633.4 dB** | | Transparent optical spans / inline amplifiers | **103 / 102** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **110.01 ms** | | Average RTT | **112 ms** | | Maximum RTT | **117.35 ms** | | Standard deviation | **1.8 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Frankfurt latency and RTT](/docs/network/latency/pairs/mia-fra-rtt) — 112.2 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-mia-rtt). - **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. # Frankfurt, Germany → Moscow, Russia RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo round from Frankfurt, Germany to Moscow, Russia recorded an average RTT of 34.7 ms across 50 samples, with a minimum of 32.66 ms, a maximum of 40.02 ms, and zero packet loss. That average is 1.75 times the theoretical fiber-floor time of 19.85 ms for a 2,026.8 km straight-line distance, leaving the route at 57.2% efficiency relative to that floor. With a 1.68 ms standard deviation and 1.68 ms jitter, the distribution is compact; the overhead over the fiber floor is the more notable feature for anyone measuring this route. The same round covers 19 routes from this network, with Frankfurt-Moscow ranking sixth. Its variability equals about 4.8% of the average RTT, higher than the network's median variability of 3.28%, so the path is generally stable but not the tightest in the set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **34.7 ms** | | Jitter | **1.68 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **19.85 ms** | | Fiber Efficiency | **57.2%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,026.8 km** | | Vacuum RTT floor | **13.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **19.85 ms** | | Low-latency fiber material floor | **19.77 ms** | | Engineering floor (5% path allowance) | **20.84 ms** | | Research 1.33× mapped-fiber reference | **26.4 ms** | | Estimated unamplified path loss | **425.6 dB** | | Transparent optical spans / inline amplifiers | **27 / 26** | | Published RTT inflation over fiber floor | **1.75×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **32.66 ms** | | Average RTT | **34.7 ms** | | Maximum RTT | **40.02 ms** | | Standard deviation | **1.68 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-mow-rtt). - **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. # Frankfurt, Germany → Marseille, France RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT measurements from Frankfurt to Marseille in round 2026-08-16T04:07:28Z averaged 16.4 ms across 50 samples, with a minimum of 15.96 ms, a maximum of 17.74 ms, and no packet loss. The geodesic distance is 798.8 km, setting a vacuum floor of 5.33 ms and a fiber floor of 7.82 ms. At 2.1 times the fiber floor and 47.7% fiber efficiency, the measured RTT carries meaningful overhead beyond the optical ideal for such a long separation. With 19 measured paths in the route set, this route ranked fifth, and the network median variability was 3.28% of average RTT. Frankfurt–Marseille had a standard deviation of 0.37 ms and jitter of 0.31 ms, about 2.3% of the mean, so its latency dispersion is tighter than the network median while covering a multi-hundred-kilometer span. Zero loss and stable dispersion make this a dependable RTT reference on the Frankfurt–Marseille route, even though the average latency sits higher than on shorter European routes. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **16.4 ms** | | Jitter | **0.31 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **7.82 ms** | | Fiber Efficiency | **47.7%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **798.8 km** | | Vacuum RTT floor | **5.33 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **7.82 ms** | | Low-latency fiber material floor | **7.79 ms** | | Engineering floor (5% path allowance) | **8.21 ms** | | Research 1.33× mapped-fiber reference | **10.4 ms** | | Estimated unamplified path loss | **167.7 dB** | | Transparent optical spans / inline amplifiers | **11 / 10** | | Published RTT inflation over fiber floor | **2.1×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **15.96 ms** | | Average RTT | **16.4 ms** | | Maximum RTT | **17.74 ms** | | Standard deviation | **0.37 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-mrs-rtt). - **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. # Frankfurt, Germany → New York, USA RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo probes from Frankfurt, Germany to New York, USA averaged 74.4 ms across 50 samples at 100 ms intervals, with a minimum of 72.04 ms, a maximum of 80.52 ms, and no packet loss. The 6,219.3 km great-circle route has a vacuum floor of 41.49 ms and a straight-fiber floor of 60.9 ms, placing the average 1.22 times the fiber floor with 81.9% fiber efficiency. That efficiency means only 13.5 ms of overhead separate the measured average from the theoretical straight-fiber floor. It ranked 7th among the 19 Frankfurt-origin routes measured this round, while the set's median relative deviation was 3.28%; the route's 2.09 ms standard deviation is about 2.8% of its average, slightly below that midpoint. New York anchors the US end of the transatlantic corridor, with carrier hotels such as 60 Hudson Street central to that role. The excellent-tier result from Frankfurt to New York is therefore a strong baseline for the core Europe-to-US pathway, with near-theoretical efficiency and no loss in this sample. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **74.4 ms** | | Jitter | **1.69 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **60.9 ms** | | Fiber Efficiency | **81.9%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,219.3 km** | | Vacuum RTT floor | **41.49 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **60.9 ms** | | Low-latency fiber material floor | **60.66 ms** | | Engineering floor (5% path allowance) | **63.96 ms** | | Research 1.33× mapped-fiber reference | **81 ms** | | Estimated unamplified path loss | **1306 dB** | | Transparent optical spans / inline amplifiers | **82 / 81** | | Published RTT inflation over fiber floor | **1.22×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **72.04 ms** | | Average RTT | **74.4 ms** | | Maximum RTT | **80.52 ms** | | Standard deviation | **2.09 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Frankfurt latency and RTT](/docs/network/latency/pairs/nyc-fra-rtt) — 73.9 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Europe → North America)** * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-nyc-rtt). - **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. # Frankfurt, Germany → Paris, France RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo round from Frankfurt, Germany to Paris, France recorded an average RTT of 7.6 ms across 50 samples, with a minimum of 7.34 ms, a maximum of 8.24 ms, and zero packet loss. With 0.15 ms jitter and a 0.23 ms standard deviation, the measurements cluster tightly around the average. The observed RTT is 1.62 times the theoretical fiber floor of 4.7 ms for the 479.9 km distance, so the route sits close to the lower bound of what a straight fiber path would allow. The same round covers 19 routes from this network, with Frankfurt-Paris ranking third. Its variability is about 3.0% of the average RTT, just under the network's median variability of 3.28%, which aligns with an ultra-low-latency result and no packet loss. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **7.6 ms** | | Jitter | **0.15 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **4.7 ms** | | Fiber Efficiency | **61.8%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **479.9 km** | | Vacuum RTT floor | **3.2 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **4.7 ms** | | Low-latency fiber material floor | **4.68 ms** | | Engineering floor (5% path allowance) | **4.93 ms** | | Research 1.33× mapped-fiber reference | **6.25 ms** | | Estimated unamplified path loss | **100.8 dB** | | Transparent optical spans / inline amplifiers | **7 / 6** | | Published RTT inflation over fiber floor | **1.62×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **7.34 ms** | | Average RTT | **7.6 ms** | | Maximum RTT | **8.24 ms** | | Standard deviation | **0.23 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-par-rtt). - **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. # Frankfurt, Germany → Seattle, USA RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Frankfurt to Seattle averaged 135.2 ms across 50 samples, with a minimum of 129.14 ms, a maximum of 151.39 ms and no packet loss. A standard deviation of 5.97 ms and jitter of 4.05 ms put this route's variability above the 3.28% median variability for the 19-route set. Ranked 10th of 19 outbound routes by average RTT, this route sits near the middle of the set. The 135.2 ms average is 1.68 times the theoretical fiber floor of 80.34 ms for the 8,204 km great-circle distance, which corresponds to a fiber efficiency of 59.4%; the numbers show meaningful headroom relative to the idealized path. With zero loss and moderate jitter, the 135.2 ms average is a stable baseline for this intercontinental route, even though its variability is somewhat higher than the set's median. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **135.2 ms** | | Jitter | **4.05 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **80.34 ms** | | Fiber Efficiency | **59.4%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **8,204 km** | | Vacuum RTT floor | **54.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **80.34 ms** | | Low-latency fiber material floor | **80.02 ms** | | Engineering floor (5% path allowance) | **84.37 ms** | | Research 1.33× mapped-fiber reference | **106.85 ms** | | Estimated unamplified path loss | **1722.8 dB** | | Transparent optical spans / inline amplifiers | **108 / 107** | | Published RTT inflation over fiber floor | **1.68×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **129.14 ms** | | Average RTT | **135.2 ms** | | Maximum RTT | **151.39 ms** | | Standard deviation | **5.97 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Frankfurt latency and RTT](/docs/network/latency/pairs/sea-fra-rtt) — 133.2 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-sea-rtt). - **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. # Frankfurt, Germany → Singapore RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement, ICMP echo round trips from Frankfurt, Germany to Singapore averaged 151.4 ms across 50 samples, with all samples between 148.19 ms and 159.42 ms and no packet loss. The geodesic distance is 10,268.5 km, and the average sits 1.51 times the theoretical fiber-floor time, equal to an observed fiber efficiency of 66.4%. The narrow min-max band and low jitter mean the round-trip timing is predictable despite the intercontinental distance. This route is positioned 12th among 19 routes from the same origin, while its stdev-to-average ratio of about 1.6% is well below the 3.28% median for the set. The low variability is the standout result; even the worst sample in the run was only about 8 ms above the average. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **151.4 ms** | | Jitter | **2.17 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **100.56 ms** | | Fiber Efficiency | **66.4%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,268.5 km** | | Vacuum RTT floor | **68.5 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **100.56 ms** | | Low-latency fiber material floor | **100.15 ms** | | Engineering floor (5% path allowance) | **105.6 ms** | | Research 1.33× mapped-fiber reference | **133.74 ms** | | Estimated unamplified path loss | **2156.4 dB** | | Transparent optical spans / inline amplifiers | **135 / 134** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **148.19 ms** | | Average RTT | **151.4 ms** | | Maximum RTT | **159.42 ms** | | Standard deviation | **2.49 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Frankfurt latency and RTT](/docs/network/latency/pairs/sin-fra-rtt) — 151.6 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-sin-rtt). - **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. # Frankfurt, Germany → Sydney, Australia RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo measurement from Frankfurt, Germany to Sydney, Australia posted an average RTT of 256 ms over 50 samples, with a minimum of 251.25 ms and a maximum of 274.41 ms, and zero packet loss. At 16,478.2 km on the geodesic line, the average is 1.59 times the theoretical fiber-floor time, leaving observed fiber efficiency at 63.0%. The sample spread is small for such a long route: a standard deviation of 4.51 ms and jitter of 3.47 ms keep most round-trip times tightly clustered near the average. Despite holding the 19th position in a 19-route outbound set, this route shows less relative timing variation than the 3.28% median for the same set. Its observed stdev-to-average ratio is about 1.8%, which is a useful counterpoint to the high absolute latency. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **256 ms** | | Jitter | **3.47 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **161.37 ms** | | Fiber Efficiency | **63%** | | Latency Tier | High | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,478.2 km** | | Vacuum RTT floor | **109.93 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **161.37 ms** | | Low-latency fiber material floor | **160.72 ms** | | Engineering floor (5% path allowance) | **169.46 ms** | | Research 1.33× mapped-fiber reference | **214.62 ms** | | Estimated unamplified path loss | **3460.4 dB** | | Transparent optical spans / inline amplifiers | **217 / 216** | | Published RTT inflation over fiber floor | **1.59×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **251.25 ms** | | Average RTT | **256 ms** | | Maximum RTT | **274.41 ms** | | Standard deviation | **4.51 ms** | | Stdev / average | **1.8%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Frankfurt latency and RTT](/docs/network/latency/pairs/syd-fra-rtt) — 254.4 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-syd-rtt). - **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. # Frankfurt, Germany → Taipei, Taiwan RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes left Frankfurt for Taipei at 100 ms intervals; the average round-trip time was 163.8 ms, with a minimum of 159.37 ms and a maximum of 176 ms. No probe was lost. The 9,390.8 km great-circle distance implies a fiber-floor estimate of about 91.96 ms, so the observed average is 1.78 times that floor, equivalent to 56.1% fiber efficiency. The 3.63 ms standard deviation and 3.43 ms jitter keep the path consistent despite the long-haul crossing. This route ranks 14th among the 19 outbound routes from Frankfurt by average round-trip time. Its standard deviation is only 2.2% of the average, below the 3.28% median variation across the broader route set, and the 16.6 ms gap between fastest and slowest replies suggests latency stays fairly predictable. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **163.8 ms** | | Jitter | **3.43 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.96 ms** | | Fiber Efficiency | **56.1%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,390.8 km** | | Vacuum RTT floor | **62.65 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.96 ms** | | Low-latency fiber material floor | **91.59 ms** | | Engineering floor (5% path allowance) | **96.57 ms** | | Research 1.33× mapped-fiber reference | **122.31 ms** | | Estimated unamplified path loss | **1972.1 dB** | | Transparent optical spans / inline amplifiers | **124 / 123** | | Published RTT inflation over fiber floor | **1.78×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **159.37 ms** | | Average RTT | **163.8 ms** | | Maximum RTT | **176 ms** | | Standard deviation | **3.63 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Frankfurt latency and RTT](/docs/network/latency/pairs/tpe-fra-rtt) — 166 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-tpe-rtt). - **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. # Frankfurt, Germany → Tokyo, Japan RTT 🇩🇪 **Frankfurt, Germany (FRA)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Frankfurt to Tokyo averaged 194.5 ms, returning replies between 189.69 ms and 207.25 ms. There was no packet loss. Tokyo's East Asian exchange role sits behind a route that spans 9,354.4 km; the fiber-floor estimate is about 91.61 ms, making the observed average 2.12 times the floor, or 47.1% fiber efficiency. The 4.7 ms standard deviation and 4.78 ms jitter are moderate for a near-200 ms path. Among the 19 outbound routes from Frankfurt, this route ranks 17th by average round-trip time. Its standard deviation is 2.4% of the average, below the 3.28% median variation across the route set, so the path is stable even though the absolute latency is relatively high; the min-to-max range of 17.56 ms confirms that stability. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **194.5 ms** | | Jitter | **4.78 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.61 ms** | | Fiber Efficiency | **47.1%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,354.4 km** | | Vacuum RTT floor | **62.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.61 ms** | | Low-latency fiber material floor | **91.24 ms** | | Engineering floor (5% path allowance) | **96.2 ms** | | Research 1.33× mapped-fiber reference | **121.84 ms** | | Estimated unamplified path loss | **1964.4 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **2.12×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **189.69 ms** | | Average RTT | **194.5 ms** | | Maximum RTT | **207.25 ms** | | Standard deviation | **4.7 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Frankfurt latency and RTT](/docs/network/latency/pairs/tyo-fra-rtt) — 193.2 ms **Fastest routes departing Frankfurt (FRA)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/fra-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-tyo-rtt). - **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. # São Paulo, Brazil → Amsterdam, Netherlands RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from São Paulo, Brazil to Amsterdam, Netherlands averaged 180 ms across 50 samples, with a minimum of 172.52 ms, a maximum of 196.27 ms, and no packet loss. Average RTT places the route in the Fair latency tier, while the 6.11 ms standard deviation and 5.36 ms jitter define its consistency. It ranks 7th among the 19 outbound routes from São Paulo in this measurement round. The average sits 1.88 times above the fiber-floor estimate of 95.79 ms, giving a 53.2% fiber-efficiency figure. Relative to the median variability of 3.28% for the outbound route set, the route's 3.39% stdev-to-average ratio is closely in line, so the delay is dominated by the transatlantic distance rather than by packet loss. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **180 ms** | | Jitter | **5.36 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.79 ms** | | Fiber Efficiency | **53.2%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,781.6 km** | | Vacuum RTT floor | **65.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.79 ms** | | Low-latency fiber material floor | **95.4 ms** | | Engineering floor (5% path allowance) | **100.59 ms** | | Research 1.33× mapped-fiber reference | **127.4 ms** | | Estimated unamplified path loss | **2054.1 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.88×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **172.52 ms** | | Average RTT | **180 ms** | | Maximum RTT | **196.27 ms** | | Standard deviation | **6.11 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (South America → Europe)** * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms * [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms * [São Paulo to Frankfurt latency and RTT](/docs/network/latency/pairs/gru-fra-rtt) — 186.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-ams-rtt). - **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. # São Paulo, Brazil → Berlin, Germany RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from São Paulo, Brazil to Berlin, Germany averaged 191.3 ms over 50 samples, with a minimum of 185.86 ms, a maximum of 210.68 ms, and zero packet loss. The 4.6 ms standard deviation and 3.74 ms jitter show a fairly steady signal, even though the average places the route in the Fair latency tier. It ranks 11th among the 19 outbound routes from São Paulo, putting it on the slower side of the set. At 1.91 times the fiber-floor estimate of 100.2 ms, the route's 52.4% fiber efficiency reflects the additional overhead beyond the great-circle distance. Its stdev-to-average ratio of 2.40% is well below the 3.28% median for the outbound route set, so this is a comparatively consistent round-trip time despite the higher absolute latency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **191.3 ms** | | Jitter | **3.74 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **100.2 ms** | | Fiber Efficiency | **52.4%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,232.3 km** | | Vacuum RTT floor | **68.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **100.2 ms** | | Low-latency fiber material floor | **99.8 ms** | | Engineering floor (5% path allowance) | **105.23 ms** | | Research 1.33× mapped-fiber reference | **133.27 ms** | | Estimated unamplified path loss | **2148.8 dB** | | Transparent optical spans / inline amplifiers | **135 / 134** | | Published RTT inflation over fiber floor | **1.91×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **185.86 ms** | | Average RTT | **191.3 ms** | | Maximum RTT | **210.68 ms** | | Standard deviation | **4.6 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to São Paulo latency and RTT](/docs/network/latency/pairs/ber-gru-rtt) — 186.5 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (South America → Europe)** * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms * [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms * [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-ber-rtt). - **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. # São Paulo, Brazil → Frankfurt, Germany RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from São Paulo, Brazil to Frankfurt, Germany averaged 186.2 ms across 50 samples, with a minimum of 180.59 ms, a maximum of 202.2 ms, and no packet loss. Average RTT keeps the route in the Fair latency tier, while the 5.01 ms standard deviation and 4.54 ms jitter indicate moderate variability. It ranks 9th among the 19 outbound routes from São Paulo in this round. The observed average is 1.94 times the fiber-floor estimate of 96.04 ms, equivalent to 51.6% fiber efficiency. With a stdev-to-average ratio of 2.69% versus the 3.28% median for the outbound route set, the route is steadier than the typical São Paulo outbound path, even though its absolute latency is in the Fair tier. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **186.2 ms** | | Jitter | **4.54 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **96.04 ms** | | Fiber Efficiency | **51.6%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,807.7 km** | | Vacuum RTT floor | **65.43 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **96.04 ms** | | Low-latency fiber material floor | **95.66 ms** | | Engineering floor (5% path allowance) | **100.86 ms** | | Research 1.33× mapped-fiber reference | **127.74 ms** | | Estimated unamplified path loss | **2059.6 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.94×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **180.59 ms** | | Average RTT | **186.2 ms** | | Maximum RTT | **202.2 ms** | | Standard deviation | **5.01 ms** | | Stdev / average | **2.7%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to São Paulo latency and RTT](/docs/network/latency/pairs/fra-gru-rtt) — 181.3 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (South America → Europe)** * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms * [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms * [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-fra-rtt). - **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. # São Paulo, Brazil → Hong Kong RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from São Paulo to Hong Kong averaged 273.5 ms, with a minimum of 267.18 ms and a maximum of 286.64 ms. The 50-sample run stayed tight: standard deviation was 4.57 ms, jitter was 4.53 ms, and packet loss was 0%. The great-circle distance between the two cities is 18,060 km, corresponding to a vacuum one-way floor of 120.48 ms and an approximate fiber floor of 176.86 ms. The observed round-trip time is 1.55 times that fiber floor, or about 64.7% fiber efficiency. This route ranked 16th of 19 outbound paths measured from São Paulo in this round, placing it in the higher-latency tier. Its standard deviation is about 1.7% of the average, below the 3.28% median stdev-to-average ratio for those 19 paths, so the path is stable despite the high baseline latency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **273.5 ms** | | Jitter | **4.53 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **176.86 ms** | | Fiber Efficiency | **64.7%** | | Latency Tier | High | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **18,060 km** | | Vacuum RTT floor | **120.48 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **176.86 ms** | | Low-latency fiber material floor | **176.15 ms** | | Engineering floor (5% path allowance) | **185.72 ms** | | Research 1.33× mapped-fiber reference | **235.22 ms** | | Estimated unamplified path loss | **3792.6 dB** | | Transparent optical spans / inline amplifiers | **238 / 237** | | Published RTT inflation over fiber floor | **1.55×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **267.18 ms** | | Average RTT | **273.5 ms** | | Maximum RTT | **286.64 ms** | | Standard deviation | **4.57 ms** | | Stdev / average | **1.7%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (South America → Asia Pacific)** * [São Paulo to Tokyo latency and RTT](/docs/network/latency/pairs/gru-tyo-rtt) — 230.3 ms * [São Paulo to Taipei latency and RTT](/docs/network/latency/pairs/gru-tpe-rtt) — 259.1 ms * [São Paulo to Sydney latency and RTT](/docs/network/latency/pairs/gru-syd-rtt) — 265.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-hkg-rtt). - **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. # São Paulo, Brazil → Ashburn, USA RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, the São Paulo-to-Ashburn ICMP path averaged 128 ms, with a minimum of 121.55 ms and maximum of 142 ms across 50 samples. Packet loss was zero and jitter was 4.04 ms. The observed RTT sits about 1.71 times above the theoretical fiber floor of roughly 74.8 ms for the 7,637.7 km distance, corresponding to 58.4% fiber efficiency. This route ranked third among the 19 outbound routes measured in the round, a strong standing for a North American destination. Although the average latency is steady, the standard deviation of 4.73 ms is about 3.7% of the average, slightly above the median variation of roughly 3.3% across those 19 routes. The combination of zero loss, low jitter, and a tight 121.55–142 ms range makes for a generally stable path with only modest variation near the upper bound. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **128 ms** | | Jitter | **4.04 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **74.79 ms** | | Fiber Efficiency | **58.4%** | | Latency Tier | Good | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,637.7 km** | | Vacuum RTT floor | **50.95 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **74.79 ms** | | Low-latency fiber material floor | **74.49 ms** | | Engineering floor (5% path allowance) | **78.54 ms** | | Research 1.33× mapped-fiber reference | **99.48 ms** | | Estimated unamplified path loss | **1603.9 dB** | | Transparent optical spans / inline amplifiers | **101 / 100** | | Published RTT inflation over fiber floor | **1.71×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **121.55 ms** | | Average RTT | **128 ms** | | Maximum RTT | **142 ms** | | Standard deviation | **4.73 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [South America](/docs/network/latency/regions/south-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-iad-rtt). - **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. # São Paulo, Brazil → Johannesburg, South Africa RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from São Paulo, Brazil to Johannesburg, South Africa averaged 333.8 ms, with a minimum of 321.14 ms and a maximum of 369.06 ms; all 50 probes returned, so packet loss was 0%, and jitter was 9.28 ms. The great-circle distance is 7,441.9 km, placing the ideal fiber floor at 72.88 ms, so the measured average is 4.58 times that floor and fiber efficiency is 21.8%. Ranked 19th among the 19 outbound routes in this round, the route sits at the high-latency end of the set. Its standard deviation of 10.62 ms is about 3.18% of the average, slightly calmer than the network's median spread-to-average ratio of 3.28%, so the high RTT is consistent rather than erratic. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **333.8 ms** | | Jitter | **9.28 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.88 ms** | | Fiber Efficiency | **21.8%** | | Latency Tier | High | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,441.9 km** | | Vacuum RTT floor | **49.65 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.88 ms** | | Low-latency fiber material floor | **72.58 ms** | | Engineering floor (5% path allowance) | **76.53 ms** | | Research 1.33× mapped-fiber reference | **96.93 ms** | | Estimated unamplified path loss | **1562.8 dB** | | Transparent optical spans / inline amplifiers | **98 / 97** | | Published RTT inflation over fiber floor | **4.58×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **321.14 ms** | | Average RTT | **333.8 ms** | | Maximum RTT | **369.06 ms** | | Standard deviation | **10.62 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to São Paulo latency and RTT](/docs/network/latency/pairs/jnb-gru-rtt) — 328.7 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-jnb-rtt). - **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. # São Paulo, Brazil → Los Angeles, USA RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement between São Paulo, Brazil and Los Angeles, USA produced an average ICMP RTT of 130.8 ms, a minimum of 125.52 ms, and a maximum of 141.14 ms over 50 samples, with no packet loss and jitter of 3.38 ms. The path covers a geodesic distance of 9,894.5 km, yet its RTT is only 1.35 times the theoretical fiber floor of about 96.9 ms, an efficiency of 74.1%. That is the standout characteristic of this route: a long-haul crossing with unusually little excess delay. It ranked fourth among the 19 outbound routes in the round, and its sample spread was narrower than the network's median: a standard deviation of 3.75 ms is roughly 2.9% of the average, compared with a median of about 3.3%. The consistent 125.52–141.14 ms range and zero loss signal a stable path for round-trip time monitoring. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **130.8 ms** | | Jitter | **3.38 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **96.89 ms** | | Fiber Efficiency | **74.1%** | | Latency Tier | Good | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,894.5 km** | | Vacuum RTT floor | **66.01 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **96.89 ms** | | Low-latency fiber material floor | **96.51 ms** | | Engineering floor (5% path allowance) | **101.75 ms** | | Research 1.33× mapped-fiber reference | **128.87 ms** | | Estimated unamplified path loss | **2077.8 dB** | | Transparent optical spans / inline amplifiers | **130 / 129** | | Published RTT inflation over fiber floor | **1.35×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **125.52 ms** | | Average RTT | **130.8 ms** | | Maximum RTT | **141.14 ms** | | Standard deviation | **3.75 ms** | | Stdev / average | **2.9%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [South America](/docs/network/latency/regions/south-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-lax-rtt). - **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. # São Paulo, Brazil → London, UK RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo to London recorded an average RTT of 175.8 ms, with a minimum of 170.28 ms and a maximum of 196 ms. Packet loss was 0%, jitter was 3.82 ms, and the standard deviation was 5.34 ms. The measured average sits 1.9 times above the 92.76 ms fiber floor for the 9,472.8 km great-circle distance, putting the route at 52.8% fiber efficiency and in the “Fair” latency tier. Geographic distance alone cannot explain the delay; the inflation over the fiber floor shows how much of the ideal path remains unrealized. This route ranks 6th among the 19 outbound São Paulo routes in the round, while the median variability for those 19 paths is 3.28% of average RTT. At about 3.0% of its average, the route’s own standard deviation is slightly below that median, making London a steadier-than-typical transatlantic destination from São Paulo. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **175.8 ms** | | Jitter | **3.82 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **92.76 ms** | | Fiber Efficiency | **52.8%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,472.8 km** | | Vacuum RTT floor | **63.2 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **92.76 ms** | | Low-latency fiber material floor | **92.39 ms** | | Engineering floor (5% path allowance) | **97.42 ms** | | Research 1.33× mapped-fiber reference | **123.38 ms** | | Estimated unamplified path loss | **1989.3 dB** | | Transparent optical spans / inline amplifiers | **125 / 124** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **170.28 ms** | | Average RTT | **175.8 ms** | | Maximum RTT | **196 ms** | | Standard deviation | **5.34 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (South America → Europe)** * [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms * [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms * [São Paulo to Frankfurt latency and RTT](/docs/network/latency/pairs/gru-fra-rtt) — 186.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-lon-rtt). - **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. # São Paulo, Brazil → Melbourne, Australia RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from São Paulo to Melbourne averaged 274.7 ms, with a minimum of 268.04 ms and a maximum of 300.54 ms. The standard deviation was 5.82 ms, jitter was 4.86 ms, and the 50-sample run reported 0% packet loss. The great-circle distance is 13,105.1 km, giving a vacuum one-way floor of 87.43 ms and an approximate fiber floor of 128.34 ms. The observed RTT is 2.14 times that fiber floor, corresponding to 46.7% fiber efficiency, showing that the path overhead is substantial relative to the straight-line ideal. This route ranked 17th of 19 outbound paths measured from São Paulo in this round. Its standard deviation is about 2.1% of the average, below the 3.28% median stdev-to-average ratio for those 19 paths, though the maximum reading reached 300.54 ms against a 268.04 ms minimum, leaving a roughly 32 ms spread. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **274.7 ms** | | Jitter | **4.86 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.34 ms** | | Fiber Efficiency | **46.7%** | | Latency Tier | High | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,105.1 km** | | Vacuum RTT floor | **87.43 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.34 ms** | | Low-latency fiber material floor | **127.82 ms** | | Engineering floor (5% path allowance) | **134.77 ms** | | Research 1.33× mapped-fiber reference | **170.69 ms** | | Estimated unamplified path loss | **2752.1 dB** | | Transparent optical spans / inline amplifiers | **173 / 172** | | Published RTT inflation over fiber floor | **2.14×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **268.04 ms** | | Average RTT | **274.7 ms** | | Maximum RTT | **300.54 ms** | | Standard deviation | **5.82 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to São Paulo latency and RTT](/docs/network/latency/pairs/mel-gru-rtt) — 305.3 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (South America → Asia Pacific)** * [São Paulo to Tokyo latency and RTT](/docs/network/latency/pairs/gru-tyo-rtt) — 230.3 ms * [São Paulo to Taipei latency and RTT](/docs/network/latency/pairs/gru-tpe-rtt) — 259.1 ms * [São Paulo to Sydney latency and RTT](/docs/network/latency/pairs/gru-syd-rtt) — 265.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-mel-rtt). - **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. # São Paulo, Brazil → Miami, USA RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests between São Paulo, Brazil and Miami, USA averaged 74ms over 50 samples, with a minimum of 70.55ms and a maximum of 83.79ms. The 3.07ms standard deviation and 2.29ms jitter show a stable profile, and packet loss was zero. That 74ms average is only about 15% above the theoretical fiber floor of 64.11ms for the 6,546.4km great-circle distance, yielding an 86.6% fiber efficiency. The route is running close to the propagation limit for light in fiber, leaving little room for latency improvement on this geography. This path ranks first among the 19 outbound routes in the round, while its variability ratio of about 4.1% sits slightly above the network median of 3.28%. With an Excellent latency tier, no loss, and very low jitter, this is a strong reference for São Paulo-to-Miami connectivity. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **74 ms** | | Jitter | **2.29 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **64.11 ms** | | Fiber Efficiency | **86.6%** | | Latency Tier | Excellent | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,546.4 km** | | Vacuum RTT floor | **43.67 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **64.11 ms** | | Low-latency fiber material floor | **63.85 ms** | | Engineering floor (5% path allowance) | **67.32 ms** | | Research 1.33× mapped-fiber reference | **85.26 ms** | | Estimated unamplified path loss | **1374.7 dB** | | Transparent optical spans / inline amplifiers | **86 / 85** | | Published RTT inflation over fiber floor | **1.15×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **70.55 ms** | | Average RTT | **74 ms** | | Maximum RTT | **83.79 ms** | | Standard deviation | **3.07 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [South America](/docs/network/latency/regions/south-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-mia-rtt). - **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. # São Paulo, Brazil → Moscow, Russia RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo to Moscow produced an average RTT of 219.5 ms, with a minimum of 208.05 ms and a maximum of 246.05 ms. The path had zero packet loss, a 7.63 ms standard deviation, and 6.64 ms jitter. For the 11,791.1 km great-circle distance, the fiber floor is 115.47 ms; the observed average is 1.9 times that floor, giving a 52.6% fiber efficiency and a “Fair” latency tier. The 38 ms gap between the fastest and slowest probes indicates moderate variability over the long crossing. This route ranks 12th among the 19 outbound São Paulo routes, with the median variability for those 19 paths at 3.28% of average RTT. Moscow’s standard deviation equals about 3.5% of its average, so stability is close to the median but slightly looser, and the zero-loss result stands out for such a long haul. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **219.5 ms** | | Jitter | **6.64 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **115.47 ms** | | Fiber Efficiency | **52.6%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,791.1 km** | | Vacuum RTT floor | **78.66 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **115.47 ms** | | Low-latency fiber material floor | **115 ms** | | Engineering floor (5% path allowance) | **121.26 ms** | | Research 1.33× mapped-fiber reference | **153.57 ms** | | Estimated unamplified path loss | **2476.1 dB** | | Transparent optical spans / inline amplifiers | **155 / 154** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **208.05 ms** | | Average RTT | **219.5 ms** | | Maximum RTT | **246.05 ms** | | Standard deviation | **7.63 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to São Paulo latency and RTT](/docs/network/latency/pairs/mow-gru-rtt) — 214.4 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (South America → Europe)** * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms * [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms * [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-mow-rtt). - **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. # São Paulo, Brazil → Marseille, France RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo to Marseille averaged 187.7 ms, with readings between 176.81 ms and 212.03 ms. There was no packet loss, while jitter reached 7.15 ms and the standard deviation was 8.46 ms. The average is 2.1 times the 89.24 ms fiber floor for the 9,113 km great-circle path, yielding a 47.5% fiber efficiency and a “Fair” latency tier. The 35.22 ms spread between minimum and maximum RTT points to a path with more variability than the clean distance-based floor would suggest. This route is ranked 10th among the 19 outbound São Paulo routes, and the median variability across those 19 paths is 3.28% of average RTT. At 8.46 ms, this route’s standard deviation is about 4.5% of its average, so Marseille-bound traffic in this round was noticeably more uneven than the median outbound route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **187.7 ms** | | Jitter | **7.15 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.24 ms** | | Fiber Efficiency | **47.5%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **9,113 km** | | Vacuum RTT floor | **60.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.24 ms** | | Low-latency fiber material floor | **88.88 ms** | | Engineering floor (5% path allowance) | **93.72 ms** | | Research 1.33× mapped-fiber reference | **118.69 ms** | | Estimated unamplified path loss | **1913.7 dB** | | Transparent optical spans / inline amplifiers | **120 / 119** | | Published RTT inflation over fiber floor | **2.1×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **176.81 ms** | | Average RTT | **187.7 ms** | | Maximum RTT | **212.03 ms** | | Standard deviation | **8.46 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to São Paulo latency and RTT](/docs/network/latency/pairs/mrs-gru-rtt) — 186.7 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (South America → Europe)** * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms * [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms * [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-mrs-rtt). - **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. # São Paulo, Brazil → New York, USA RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo RTT from São Paulo, Brazil to New York, USA averaged 122ms across 50 samples, ranging from 116.85ms to 132.54ms. The 3.8ms standard deviation and 3.62ms jitter are modest, and all probes were returned without loss. The average sits 63% above the theoretical fiber floor of 74.99ms for the 7,657.6km great-circle distance, translating to a 61.5% fiber efficiency. This is a larger overhead than a near-optimal path would show, though the round-trip times remain consistent. This path is ranked second among the 19 outbound routes in the round, and its variability ratio of about 3.1% falls below the network median of 3.28%. The zero-loss result and contained jitter make it a dependable reference for São Paulo-to-New York latency, with the extra distance overhead being the main separating factor from a tighter fiber-floor result. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **122 ms** | | Jitter | **3.62 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **74.99 ms** | | Fiber Efficiency | **61.5%** | | Latency Tier | Good | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,657.6 km** | | Vacuum RTT floor | **51.09 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **74.99 ms** | | Low-latency fiber material floor | **74.69 ms** | | Engineering floor (5% path allowance) | **78.75 ms** | | Research 1.33× mapped-fiber reference | **99.74 ms** | | Estimated unamplified path loss | **1608.1 dB** | | Transparent optical spans / inline amplifiers | **101 / 100** | | Published RTT inflation over fiber floor | **1.63×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **116.85 ms** | | Average RTT | **122 ms** | | Maximum RTT | **132.54 ms** | | Standard deviation | **3.8 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [South America](/docs/network/latency/regions/south-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-nyc-rtt). - **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. # São Paulo, Brazil → Paris, France RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round between São Paulo, Brazil and Paris, France returned an average ICMP echo RTT of 180.2 ms, with a minimum of 169.53 ms and a maximum of 210.06 ms over 50 samples. No packets were lost, and jitter stayed at 7.23 ms. That average is about 1.96 times the theoretical fiber-floor estimate of roughly 91.8 ms for the 9,377.8 km geodesic separation, putting the route at 51% fiber efficiency. The spread of test samples was wider than the median spread across the network's 19 outbound routes: a standard deviation of 8.35 ms represents about 4.6% of the average, versus a median of roughly 3.3%. In the same round, this path ranked eighth of the 19 outbound routes measured from São Paulo, leaving faster options available but still ahead of more than half the set. The low packet loss and sub-8 ms jitter indicate a stable path; the larger-than-median sample spread suggests occasional slower packets, capped by the 210 ms maximum. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **180.2 ms** | | Jitter | **7.23 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.83 ms** | | Fiber Efficiency | **51%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,377.8 km** | | Vacuum RTT floor | **62.56 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.83 ms** | | Low-latency fiber material floor | **91.47 ms** | | Engineering floor (5% path allowance) | **96.44 ms** | | Research 1.33× mapped-fiber reference | **122.14 ms** | | Estimated unamplified path loss | **1969.3 dB** | | Transparent optical spans / inline amplifiers | **124 / 123** | | Published RTT inflation over fiber floor | **1.96×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **169.53 ms** | | Average RTT | **180.2 ms** | | Maximum RTT | **210.06 ms** | | Standard deviation | **8.35 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (South America → Europe)** * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms * [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms * [São Paulo to Frankfurt latency and RTT](/docs/network/latency/pairs/gru-fra-rtt) — 186.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-par-rtt). - **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. # São Paulo, Brazil → Seattle, USA RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from São Paulo, Brazil to Seattle, USA averaged 155.9ms over 50 samples, with a minimum of 151.12ms and a maximum of 166.61ms. Jitter was 3.4ms, standard deviation 3.7ms, and packet loss was zero. The 155.9ms average is 46% above the theoretical fiber floor of 106.76ms for the 10,902.3km great-circle distance, giving a fiber efficiency of 68.5%. Despite the Fair latency tier, the path shows a stable distribution and no loss. This path ranks fifth among the 19 outbound routes in the round, and its variability ratio of about 2.4% is well below the network median of 3.28%. The low relative variation is noteworthy for such a long hop, making the route a consistent performer despite its higher absolute latency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **155.9 ms** | | Jitter | **3.4 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.76 ms** | | Fiber Efficiency | **68.5%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,902.3 km** | | Vacuum RTT floor | **72.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.76 ms** | | Low-latency fiber material floor | **106.33 ms** | | Engineering floor (5% path allowance) | **112.12 ms** | | Research 1.33× mapped-fiber reference | **142 ms** | | Estimated unamplified path loss | **2289.5 dB** | | Transparent optical spans / inline amplifiers | **144 / 143** | | Published RTT inflation over fiber floor | **1.46×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **151.12 ms** | | Average RTT | **155.9 ms** | | Maximum RTT | **166.61 ms** | | Standard deviation | **3.7 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [South America](/docs/network/latency/regions/south-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-sea-rtt). - **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. # São Paulo, Brazil → Singapore RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from São Paulo to Singapore averaged 297.1 ms, with a minimum of 280.43 ms and a maximum of 326.59 ms. Standard deviation was 11.31 ms, jitter was 10.86 ms, and packet loss was 0% across the 50 samples. The great-circle distance is 15,998.2 km, yielding a vacuum one-way floor of 106.73 ms and an approximate fiber floor of 156.67 ms. The observed RTT is 1.9 times that fiber floor, or 52.7% fiber efficiency, placing this in the high-latency tier. This route ranked 18th of 19 outbound paths measured from São Paulo in this round. Its standard deviation is about 3.8% of the average, above the 3.28% median stdev-to-average ratio for those 19 paths, and the max-min spread of 46.16 ms makes the round-trip time less predictable than the average alone suggests. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **297.1 ms** | | Jitter | **10.86 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **156.67 ms** | | Fiber Efficiency | **52.7%** | | Latency Tier | High | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,998.2 km** | | Vacuum RTT floor | **106.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **156.67 ms** | | Low-latency fiber material floor | **156.04 ms** | | Engineering floor (5% path allowance) | **164.52 ms** | | Research 1.33× mapped-fiber reference | **208.37 ms** | | Estimated unamplified path loss | **3359.6 dB** | | Transparent optical spans / inline amplifiers | **210 / 209** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **280.43 ms** | | Average RTT | **297.1 ms** | | Maximum RTT | **326.59 ms** | | Standard deviation | **11.31 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to São Paulo latency and RTT](/docs/network/latency/pairs/sin-gru-rtt) — 311.4 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (South America → Asia Pacific)** * [São Paulo to Tokyo latency and RTT](/docs/network/latency/pairs/gru-tyo-rtt) — 230.3 ms * [São Paulo to Taipei latency and RTT](/docs/network/latency/pairs/gru-tpe-rtt) — 259.1 ms * [São Paulo to Sydney latency and RTT](/docs/network/latency/pairs/gru-syd-rtt) — 265.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-sin-rtt). - **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. # São Paulo, Brazil → Sydney, Australia RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo, Brazil to Sydney, Australia returned an average round-trip time of 265.5 ms, with a minimum of 255.6 ms and a maximum of 295.52 ms. The standard deviation of 9.22 ms and jitter of 8.27 ms indicate a fairly steady path, and no packets were lost. At 13,377 km apart, even a realistic fiber path has a floor near 131 ms, so the observed 265.5 ms average sits at 2.03 times that floor. This works out to 49.3 percent efficiency relative to the physical reference, meaning the route uses roughly half of its best-case optical headroom. Against the 19 outbound routes from São Paulo measured in the same round, Sydney ranked 15th, placing it in the slower half of the set. Across those 19 routes, the median spread of latency variability was 3.28 percent of average RTT; the 9.22 ms standard deviation here represents about 3.5 percent of the 265.5 ms average, tracking close to that typical dispersion. The route's standout feature is its inflation factor rather than instability: zero packet loss and moderate jitter accompany an average latency more than double the fiber floor, a useful distinction for anyone evaluating long-haul network paths from Brazil to Australia. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **265.5 ms** | | Jitter | **8.27 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **131 ms** | | Fiber Efficiency | **49.3%** | | Latency Tier | High | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **13,377 km** | | Vacuum RTT floor | **89.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **131 ms** | | Low-latency fiber material floor | **130.47 ms** | | Engineering floor (5% path allowance) | **137.57 ms** | | Research 1.33× mapped-fiber reference | **174.23 ms** | | Estimated unamplified path loss | **2809.2 dB** | | Transparent optical spans / inline amplifiers | **176 / 175** | | Published RTT inflation over fiber floor | **2.03×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **255.6 ms** | | Average RTT | **265.5 ms** | | Maximum RTT | **295.52 ms** | | Standard deviation | **9.22 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to São Paulo latency and RTT](/docs/network/latency/pairs/syd-gru-rtt) — 296.7 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (South America → Asia Pacific)** * [São Paulo to Tokyo latency and RTT](/docs/network/latency/pairs/gru-tyo-rtt) — 230.3 ms * [São Paulo to Taipei latency and RTT](/docs/network/latency/pairs/gru-tpe-rtt) — 259.1 ms * [São Paulo to Hong Kong latency and RTT](/docs/network/latency/pairs/gru-hkg-rtt) — 273.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-syd-rtt). - **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. # São Paulo, Brazil → Taipei, Taiwan RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo requests from São Paulo, Brazil to Taipei, Taiwan produced an average round-trip time of 259.1 ms, with a minimum of 248.08 ms and a maximum of 296.38 ms. The standard deviation was 8.63 ms, jitter was 7.16 ms, and packet loss was zero. The geodesic distance is 18,818.5 km, and the fiber floor is 184.29 ms, so the observed average sits at 1.41 times that floor. This gives a route efficiency of 71.1 percent, a relatively strong result for such a long intercontinental path. Within the 19 outbound routes measured from São Paulo, Taipei ranked 14th, placing it in the slower half of the group. The broader set's median variability was 3.28 percent of average latency; this route's 8.63 ms standard deviation is about 3.3 percent of its 259.1 ms average, aligning closely with the typical range. The minimum RTT of 248.08 ms is much closer to the average than the maximum, so occasional slower probes widen the range more than steady variation. Still, with zero loss and jitter under 8 ms, the high-latency tier here reflects distance and route efficiency rather than packet instability. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **259.1 ms** | | Jitter | **7.16 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **184.29 ms** | | Fiber Efficiency | **71.1%** | | Latency Tier | High | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **18,818.5 km** | | Vacuum RTT floor | **125.54 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **184.29 ms** | | Low-latency fiber material floor | **183.54 ms** | | Engineering floor (5% path allowance) | **193.52 ms** | | Research 1.33× mapped-fiber reference | **245.1 ms** | | Estimated unamplified path loss | **3951.9 dB** | | Transparent optical spans / inline amplifiers | **247 / 246** | | Published RTT inflation over fiber floor | **1.41×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **248.08 ms** | | Average RTT | **259.1 ms** | | Maximum RTT | **296.38 ms** | | Standard deviation | **8.63 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (South America → Asia Pacific)** * [São Paulo to Tokyo latency and RTT](/docs/network/latency/pairs/gru-tyo-rtt) — 230.3 ms * [São Paulo to Sydney latency and RTT](/docs/network/latency/pairs/gru-syd-rtt) — 265.5 ms * [São Paulo to Hong Kong latency and RTT](/docs/network/latency/pairs/gru-hkg-rtt) — 273.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-tpe-rtt). - **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. # São Paulo, Brazil → Tokyo, Japan RTT 🇧🇷 **São Paulo, Brazil (GRU)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo, Brazil to Tokyo, Japan produced an average round-trip time of 230.3 ms, with a minimum of 223.73 ms and a maximum of 259.55 ms. Standard deviation was 6.53 ms, jitter was 4.44 ms, and packet loss was zero. At 18,530.2 km, the fiber floor is 181.46 ms, and the observed average is only 1.27 times that floor, for a route efficiency of 78.8 percent. The low jitter and zero loss make this a comparatively well-behaved long-distance path. Tokyo ranked 13th among the 19 outbound routes from São Paulo, placing it slightly in the slower half of the set. The median variability across those routes was 3.28 percent of average latency; this route's 6.53 ms standard deviation equals about 2.8 percent of its 230.3 ms average, a bit tighter than the typical spread. The most useful signal here is the combination of efficiency and stability: the route stays close to its physical reference while maintaining a narrow jitter range, suggesting the fair latency tier reflects the long distance more than inconsistent network behavior. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **230.3 ms** | | Jitter | **4.44 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **181.46 ms** | | Fiber Efficiency | **78.8%** | | Latency Tier | Fair | | Source Region | [South America](/docs/network/latency/regions/south-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **18,530.2 km** | | Vacuum RTT floor | **123.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **181.46 ms** | | Low-latency fiber material floor | **180.73 ms** | | Engineering floor (5% path allowance) | **190.56 ms** | | Research 1.33× mapped-fiber reference | **241.34 ms** | | Estimated unamplified path loss | **3891.3 dB** | | Transparent optical spans / inline amplifiers | **244 / 243** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **223.73 ms** | | Average RTT | **230.3 ms** | | Maximum RTT | **259.55 ms** | | Standard deviation | **6.53 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [South America](/docs/network/latency/regions/south-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.5 ms **Fastest routes departing São Paulo (GRU)** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (South America → Asia Pacific)** * [São Paulo to Taipei latency and RTT](/docs/network/latency/pairs/gru-tpe-rtt) — 259.1 ms * [São Paulo to Sydney latency and RTT](/docs/network/latency/pairs/gru-syd-rtt) — 265.5 ms * [São Paulo to Hong Kong latency and RTT](/docs/network/latency/pairs/gru-hkg-rtt) — 273.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/gru-tyo-rtt). - **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. # Hong Kong → Amsterdam, Netherlands RTT 🇭🇰 **Hong Kong (HKG)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round measured ICMP echo RTT from Hong Kong to Amsterdam, Netherlands at an average of 154.4 ms, with a minimum of 148.52 ms and a maximum of 170.08 ms; zero packets were lost across 50 probes, and jitter was 4.6 ms. At 9,297.6 km great-circle distance, the fiber floor is 91.05 ms, making the observed average only 1.7 times the floor and translating to 59% fiber efficiency. This route ranked 11th among the 19 outbound routes in the round, placing it just past the middle of the latency order. Its standard deviation of 4.49 ms is about 2.91% of the average, lower than the network's median spread-to-average ratio of 3.28%, so the RTT stayed tight across the sample. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **154.4 ms** | | Jitter | **4.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.05 ms** | | Fiber Efficiency | **59%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,297.6 km** | | Vacuum RTT floor | **62.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.05 ms** | | Low-latency fiber material floor | **90.68 ms** | | Engineering floor (5% path allowance) | **95.61 ms** | | Research 1.33× mapped-fiber reference | **121.1 ms** | | Estimated unamplified path loss | **1952.5 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **1.7×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **148.52 ms** | | Average RTT | **154.4 ms** | | Maximum RTT | **170.08 ms** | | Standard deviation | **4.49 ms** | | Stdev / average | **2.9%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Hong Kong latency and RTT](/docs/network/latency/pairs/ams-hkg-rtt) — 155.9 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Asia Pacific → Europe)** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-ams-rtt). - **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. # Hong Kong → Berlin, Germany RTT 🇭🇰 **Hong Kong (HKG)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Hong Kong to Berlin, Germany averaged 145.1 ms, with a minimum of 138.49 ms and a maximum of 164.88 ms; all 50 probes succeeded, packet loss was 0%, and jitter was 5.8 ms. The 8,767.1 km great-circle distance puts the fiber floor at 85.85 ms, so the measured average is 1.69 times the floor and fiber efficiency reaches 59.2%. Ranked 9th among the 19 outbound routes in this round, this route sits on the faster side of the field. Its standard deviation of 6.67 ms is 4.60% of the average, higher than the network's median spread-to-average ratio of 3.28%, so the tail toward 164.88 ms adds noticeable spread despite the good mean RTT. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **145.1 ms** | | Jitter | **5.8 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.85 ms** | | Fiber Efficiency | **59.2%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,767.1 km** | | Vacuum RTT floor | **58.49 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.85 ms** | | Low-latency fiber material floor | **85.51 ms** | | Engineering floor (5% path allowance) | **90.16 ms** | | Research 1.33× mapped-fiber reference | **114.19 ms** | | Estimated unamplified path loss | **1841.1 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **138.49 ms** | | Average RTT | **145.1 ms** | | Maximum RTT | **164.88 ms** | | Standard deviation | **6.67 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Asia Pacific → Europe)** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Singapore to Moscow latency and RTT](/docs/network/latency/pairs/sin-mow-rtt) — 147.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-ber-rtt). - **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. # Hong Kong → Frankfurt, Germany RTT 🇭🇰 **Hong Kong (HKG)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes sent 100 ms apart from Hong Kong to Frankfurt returned with zero packet loss, giving an average round-trip time of 150.7 ms, a minimum of 147.02 ms, and a maximum of 163.83 ms. The standard deviation was 3.53 ms and jitter was 2.66 ms, so the path stayed fairly steady across the sample. The 9,177.1 km great-circle distance sets a round-trip vacuum floor of 61.22 ms and a fiber floor of 89.87 ms. The 150.7 ms average is 1.68 times that fiber floor, which corresponds to 59.6 percent fiber efficiency and a 60.83 ms difference from the straight-line fiber minimum. Within the same round, this route ranked 10th among 19 outbound paths measured from Hong Kong. The median standard-deviation-to-average ratio for those paths was 3.28 percent; this route's ratio was about 2.34 percent, indicating latency variation below the typical level for the set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **150.7 ms** | | Jitter | **2.66 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.87 ms** | | Fiber Efficiency | **59.6%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,177.1 km** | | Vacuum RTT floor | **61.22 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.87 ms** | | Low-latency fiber material floor | **89.51 ms** | | Engineering floor (5% path allowance) | **94.37 ms** | | Research 1.33× mapped-fiber reference | **119.53 ms** | | Estimated unamplified path loss | **1927.2 dB** | | Transparent optical spans / inline amplifiers | **121 / 120** | | Published RTT inflation over fiber floor | **1.68×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **147.02 ms** | | Average RTT | **150.7 ms** | | Maximum RTT | **163.83 ms** | | Standard deviation | **3.53 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Hong Kong latency and RTT](/docs/network/latency/pairs/fra-hkg-rtt) — 152 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Asia Pacific → Europe)** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-fra-rtt). - **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. # Hong Kong → São Paulo, Brazil RTT 🇭🇰 **Hong Kong (HKG)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo probes in the 2026-08-16T04:07:28Z round measured an average Hong Kong-to-São Paulo round-trip time of 287.6 ms, with a minimum of 276.79 ms and a maximum of 338.46 ms. The route landed in the high latency tier, while all 50 probes were answered and packet loss stayed at zero. Across the 19 outbound paths measured on this network, the route placed 18th by round-trip time, putting it near the slower end of the set. Its standard deviation of 13.48 ms and jitter of 8.34 ms are correspondingly larger in absolute terms, though relative to the 287.6 ms average the variability is about 4.7%, slightly above the 3.28% median for the route set. At roughly 18,060 km, this is a very long intercontinental haul, and the fiber floor is 176.86 ms. The measured average is 1.63 times that floor, or about 61.5% fiber efficiency, which points to a mostly efficient long-haul path despite the high absolute latency. With zero packet loss, the high RTT is best understood as a distance-driven feature of this round, and the 61.6 ms gap between minimum and maximum is a more noticeable source of variation. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **287.6 ms** | | Jitter | **8.34 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **176.86 ms** | | Fiber Efficiency | **61.5%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **18,060 km** | | Vacuum RTT floor | **120.48 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **176.86 ms** | | Low-latency fiber material floor | **176.15 ms** | | Engineering floor (5% path allowance) | **185.72 ms** | | Research 1.33× mapped-fiber reference | **235.22 ms** | | Estimated unamplified path loss | **3792.6 dB** | | Transparent optical spans / inline amplifiers | **238 / 237** | | Published RTT inflation over fiber floor | **1.63×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **276.79 ms** | | Average RTT | **287.6 ms** | | Maximum RTT | **338.46 ms** | | Standard deviation | **13.48 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Asia Pacific to South America](/docs/network/latency/regions/asia-pacific-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Hong Kong latency and RTT](/docs/network/latency/pairs/gru-hkg-rtt) — 273.5 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Asia Pacific → South America)** * [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.5 ms * [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 ms * [Sydney to São Paulo latency and RTT](/docs/network/latency/pairs/syd-gru-rtt) — 296.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-gru-rtt). - **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. # Hong Kong → Ashburn, USA RTT 🇭🇰 **Hong Kong (HKG)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Hong Kong to Ashburn were sent at 100 ms intervals, and all probes were answered. Average RTT was 186.2 ms, with a minimum of 178.2 ms and a maximum of 209.61 ms. With an 8.04 ms standard deviation and 5.28 ms jitter, this route falls in the Fair latency tier. It ranks sixteenth among the 19 outbound routes from Hong Kong measured in this round, and its variation coefficient is above the 3.28 percent median for that set, so the RTT spread is wider than typical. The route spans 13,108.8 km along the great circle, and its theoretical fiber-floor RTT is 128.37 ms. The observed average is 1.45 times that floor, giving a fiber efficiency of 68.9 percent. The 31.41 ms difference between minimum and maximum is a useful reminder that ICMP RTT is a network-layer signal, not a fixed value or an end-user performance predictor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **186.2 ms** | | Jitter | **5.28 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.37 ms** | | Fiber Efficiency | **68.9%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,108.8 km** | | Vacuum RTT floor | **87.45 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.37 ms** | | Low-latency fiber material floor | **127.86 ms** | | Engineering floor (5% path allowance) | **134.81 ms** | | Research 1.33× mapped-fiber reference | **170.73 ms** | | Estimated unamplified path loss | **2752.9 dB** | | Transparent optical spans / inline amplifiers | **173 / 172** | | Published RTT inflation over fiber floor | **1.45×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **178.2 ms** | | Average RTT | **186.2 ms** | | Maximum RTT | **209.61 ms** | | Standard deviation | **8.04 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Hong Kong latency and RTT](/docs/network/latency/pairs/iad-hkg-rtt) — 187.2 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-iad-rtt). - **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. # Hong Kong → Johannesburg, South Africa RTT 🇭🇰 **Hong Kong (HKG)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. Round 2026-08-16T04:07:28Z measured ICMP echo RTT between Hong Kong and Johannesburg at an average of 316.7 ms, with a 301.28 ms minimum, a 350.25 ms maximum, and zero packet loss across 50 samples. The 11.99 ms standard deviation and 10.88 ms jitter are noticeable but not extreme for an intercontinental route, and the high latency tier reflects the distance. This path ranks 19th out of the 19 outbound routes in this round, placing it at the high-latency end of the measured set. Its variability ratio of about 3.8% is close to the 3.28% network-wide median, so the long delay is consistent rather than erratic. The great-circle distance is 10,715.5 km, giving a vacuum floor of 71.49 ms and a fiber floor of 104.93 ms. The observed RTT is 3.02 times the fiber floor, a fiber efficiency of 33.1%, reflecting the practical geography of long-haul intercontinental cabling; even with 0% loss, a high RTT floor should be expected on this path. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **316.7 ms** | | Jitter | **10.88 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **104.93 ms** | | Fiber Efficiency | **33.1%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,715.5 km** | | Vacuum RTT floor | **71.49 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **104.93 ms** | | Low-latency fiber material floor | **104.51 ms** | | Engineering floor (5% path allowance) | **110.2 ms** | | Research 1.33× mapped-fiber reference | **139.56 ms** | | Estimated unamplified path loss | **2250.3 dB** | | Transparent optical spans / inline amplifiers | **141 / 140** | | Published RTT inflation over fiber floor | **3.02×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **301.28 ms** | | Average RTT | **316.7 ms** | | Maximum RTT | **350.25 ms** | | Standard deviation | **11.99 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Hong Kong latency and RTT](/docs/network/latency/pairs/jnb-hkg-rtt) — 318 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Asia Pacific → Africa)** * [Singapore to Johannesburg latency and RTT](/docs/network/latency/pairs/sin-jnb-rtt) — 312.6 ms * [Taipei to Johannesburg latency and RTT](/docs/network/latency/pairs/tpe-jnb-rtt) — 331 ms * [Tokyo to Johannesburg latency and RTT](/docs/network/latency/pairs/tyo-jnb-rtt) — 359.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-jnb-rtt). - **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. # Hong Kong → Los Angeles, USA RTT 🇭🇰 **Hong Kong (HKG)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. For measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Hong Kong to Los Angeles returned an average RTT of 145 ms, with a minimum of 139.67 ms and a maximum of 160.38 ms. No packets were lost, and the reported jitter was 3.79 ms. The measured average sits 1.27 times above the fiber floor for the 11,671.5 km geodesic span, giving a fiber-path efficiency of 78.8%. Standard deviation was 4.08 ms, or about 2.8% of the average, a little below the 3.28% median relative variability for the 19 outbound routes in this round. This route ranks 8th among those 19 outbound paths, placing it in the faster half of the Hong Kong outbound set while still showing a sub-150 ms average. Its Good latency tier, zero loss, and low jitter make it a consistent trans-Pacific reference for the round. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **145 ms** | | Jitter | **3.79 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **114.3 ms** | | Fiber Efficiency | **78.8%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,671.5 km** | | Vacuum RTT floor | **77.86 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **114.3 ms** | | Low-latency fiber material floor | **113.84 ms** | | Engineering floor (5% path allowance) | **120.03 ms** | | Research 1.33× mapped-fiber reference | **152.01 ms** | | Estimated unamplified path loss | **2451 dB** | | Transparent optical spans / inline amplifiers | **154 / 153** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **139.67 ms** | | Average RTT | **145 ms** | | Maximum RTT | **160.38 ms** | | Standard deviation | **4.08 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Hong Kong latency and RTT](/docs/network/latency/pairs/lax-hkg-rtt) — 146.5 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-lax-rtt). - **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. # Hong Kong → London, UK RTT 🇭🇰 **Hong Kong (HKG)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes sent 100 ms apart from Hong Kong to London all came back, producing zero packet loss and an average RTT of 158.7 ms, with a minimum of 154.18 ms and a maximum of 172.16 ms. The standard deviation was 4.34 ms and jitter was 3.3 ms, so the path was relatively stable during the sample. Against the 9,643.6 km great-circle distance, the round-trip vacuum floor is 64.34 ms and the fiber floor is 94.44 ms. The 158.7 ms average is 1.68 times the fiber floor, which corresponds to 59.5 percent fiber efficiency and leaves a 64.26 ms gap over the straight-line fiber minimum. This route ranked 12th among the 19 outbound paths measured from Hong Kong in the same round. Its variability ratio of roughly 2.73 percent was below the 3.28 percent median for those paths, meaning the round-trip times clustered more tightly around the average than was typical. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **158.7 ms** | | Jitter | **3.3 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **94.44 ms** | | Fiber Efficiency | **59.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,643.6 km** | | Vacuum RTT floor | **64.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **94.44 ms** | | Low-latency fiber material floor | **94.06 ms** | | Engineering floor (5% path allowance) | **99.17 ms** | | Research 1.33× mapped-fiber reference | **125.6 ms** | | Estimated unamplified path loss | **2025.2 dB** | | Transparent optical spans / inline amplifiers | **127 / 126** | | Published RTT inflation over fiber floor | **1.68×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **154.18 ms** | | Average RTT | **158.7 ms** | | Maximum RTT | **172.16 ms** | | Standard deviation | **4.34 ms** | | Stdev / average | **2.7%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Hong Kong latency and RTT](/docs/network/latency/pairs/lon-hkg-rtt) — 160.6 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Asia Pacific → Europe)** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-lon-rtt). - **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. # Hong Kong → Melbourne, Australia RTT 🇭🇰 **Hong Kong (HKG)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Hong Kong to Melbourne posted an average round-trip time of 138.4 ms, with a minimum of 132.66 ms and a maximum of 153.75 ms. All 50 probes returned, packet loss was zero, and the latency tier was good. On this network's 19-outbound-route measurement set, the path ranked 7th by round-trip time. Its standard deviation of 4.9 ms and jitter of 4.62 ms are modest, and relative to the average the variability is about 3.5%, close to the 3.28% median for the route set. The geodesic distance is about 7,391 km, with a fiber floor of 72.38 ms; the measured average is 1.91 times that floor, corresponding to a fiber efficiency of 52.3%. That relatively low efficiency suggests the route is not taking a minimal geographic line even though the absolute RTT remains comfortable, and the 21.1 ms spread between fastest and slowest probes keeps this path predictable within the round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **138.4 ms** | | Jitter | **4.62 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.38 ms** | | Fiber Efficiency | **52.3%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,391.1 km** | | Vacuum RTT floor | **49.31 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.38 ms** | | Low-latency fiber material floor | **72.09 ms** | | Engineering floor (5% path allowance) | **76.01 ms** | | Research 1.33× mapped-fiber reference | **96.26 ms** | | Estimated unamplified path loss | **1552.1 dB** | | Transparent optical spans / inline amplifiers | **98 / 97** | | Published RTT inflation over fiber floor | **1.91×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **132.66 ms** | | Average RTT | **138.4 ms** | | Maximum RTT | **153.75 ms** | | Standard deviation | **4.9 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms * [Los Angeles to Melbourne latency and RTT](/docs/network/latency/pairs/lax-mel-rtt) — 148.2 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-mel-rtt). - **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. # Hong Kong → Miami, USA RTT 🇭🇰 **Hong Kong (HKG)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. For measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Hong Kong to Miami returned an average RTT of 201.1 ms, with a minimum of 194.49 ms and a maximum of 226.67 ms. Packet loss was 0%, and jitter was 4.97 ms. The geodesic distance is 14,468.4 km, and the measured average is 1.42 times the fiber floor, which corresponds to 70.5% fiber-path efficiency. The 6.05 ms standard deviation equals about 3.0% of the average, slightly below the 3.28% median relative variability across the 19 outbound routes in this round. This route ranks 17th among those 19 outbound paths, so it sits near the slower end of the Hong Kong outbound set. Its Fair latency tier and 201 ms average reflect a long-haul route where absolute delay is substantial, yet the zero-loss result and contained jitter keep the path predictable. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **201.1 ms** | | Jitter | **4.97 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **141.69 ms** | | Fiber Efficiency | **70.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,468.4 km** | | Vacuum RTT floor | **96.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **141.69 ms** | | Low-latency fiber material floor | **141.12 ms** | | Engineering floor (5% path allowance) | **148.79 ms** | | Research 1.33× mapped-fiber reference | **188.44 ms** | | Estimated unamplified path loss | **3038.4 dB** | | Transparent optical spans / inline amplifiers | **190 / 189** | | Published RTT inflation over fiber floor | **1.42×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **194.49 ms** | | Average RTT | **201.1 ms** | | Maximum RTT | **226.67 ms** | | Standard deviation | **6.05 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Hong Kong latency and RTT](/docs/network/latency/pairs/mia-hkg-rtt) — 199.5 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-mia-rtt). - **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. # Hong Kong → Moscow, Russia RTT 🇭🇰 **Hong Kong (HKG)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round sent 50 ICMP echo probes from Hong Kong to Moscow at 100 ms intervals, and all probes came back, so packet loss was 0 percent. The average RTT was 118.2 ms, with a minimum of 115.72 ms and a maximum of 128.25 ms. A 2.23 ms standard deviation and 1.78 ms jitter keep this route inside a tight band, matching its Good latency tier. It ranks fourth among the 19 outbound routes measured from Hong Kong in this round, and its variation coefficient is well below the 3.28 percent median for that outbound set. The great-circle distance is 7,153.6 km, which puts the theoretical fiber-floor RTT at 70.05 ms; the measured 118.2 ms average is 1.69 times that floor, for a fiber efficiency of 59.3 percent. Zero loss and low variance make this a steady network-layer path, though ICMP RTT alone is not a predictor of end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **118.2 ms** | | Jitter | **1.78 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **70.05 ms** | | Fiber Efficiency | **59.3%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,153.6 km** | | Vacuum RTT floor | **47.72 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **70.05 ms** | | Low-latency fiber material floor | **69.77 ms** | | Engineering floor (5% path allowance) | **73.57 ms** | | Research 1.33× mapped-fiber reference | **93.17 ms** | | Estimated unamplified path loss | **1502.3 dB** | | Transparent optical spans / inline amplifiers | **94 / 93** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **115.72 ms** | | Average RTT | **118.2 ms** | | Maximum RTT | **128.25 ms** | | Standard deviation | **2.23 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Asia Pacific → Europe)** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-mow-rtt). - **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. # Hong Kong → Marseille, France RTT 🇭🇰 **Hong Kong (HKG)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes sent 100 ms apart from Hong Kong to Marseille recorded zero packet loss, with an average round-trip time of 165.4 ms, a minimum of 159.87 ms, and a maximum of 180.73 ms. The standard deviation was 4.35 ms and jitter was 3.54 ms, so the sample was relatively contained. The 9,750.5 km great-circle distance gives a round-trip vacuum floor of 65.05 ms and a fiber floor of 95.48 ms. At 165.4 ms, the average is 1.73 times the fiber floor, or 57.7 percent fiber efficiency, with an excess of 69.92 ms over the straight-line fiber minimum. This route ranked 14th of the 19 outbound paths measured from Hong Kong in the same round. Its standard-deviation-to-average ratio was about 2.63 percent, below the 3.28 percent median for the group, so the round-trip times were more consistent than the typical path in the same measurement set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **165.4 ms** | | Jitter | **3.54 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.48 ms** | | Fiber Efficiency | **57.7%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,750.5 km** | | Vacuum RTT floor | **65.05 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.48 ms** | | Low-latency fiber material floor | **95.1 ms** | | Engineering floor (5% path allowance) | **100.27 ms** | | Research 1.33× mapped-fiber reference | **126.99 ms** | | Estimated unamplified path loss | **2047.6 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **1.73×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **159.87 ms** | | Average RTT | **165.4 ms** | | Maximum RTT | **180.73 ms** | | Standard deviation | **4.35 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Hong Kong latency and RTT](/docs/network/latency/pairs/mrs-hkg-rtt) — 166.4 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Asia Pacific → Europe)** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-mrs-rtt). - **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. # Hong Kong → New York, USA RTT 🇭🇰 **Hong Kong (HKG)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. For measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Hong Kong to New York returned an average RTT of 184.7 ms, with a minimum of 181.35 ms and a maximum of 196.05 ms. The route reported zero packet loss and 2.83 ms jitter. Against the 12,979.6 km geodesic distance, the measured average is 1.45 times the fiber floor, for a fiber-path efficiency of 68.8%. Its 3.49 ms standard deviation is about 1.9% of the average, well below the 3.28% median relative variability seen across the 19 outbound routes in this round. Ranked 15th among those 19 outbound paths, this New York route is in the lower half of the round's results, but the narrow 181-196 ms RTT range and zero loss make it notably stable. The consistency is the standout feature; the efficiency gap relative to the fiber floor matters more than the route's variability. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **184.7 ms** | | Jitter | **2.83 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **127.11 ms** | | Fiber Efficiency | **68.8%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,979.6 km** | | Vacuum RTT floor | **86.59 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **127.11 ms** | | Low-latency fiber material floor | **126.6 ms** | | Engineering floor (5% path allowance) | **133.48 ms** | | Research 1.33× mapped-fiber reference | **169.05 ms** | | Estimated unamplified path loss | **2725.7 dB** | | Transparent optical spans / inline amplifiers | **171 / 170** | | Published RTT inflation over fiber floor | **1.45×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **181.35 ms** | | Average RTT | **184.7 ms** | | Maximum RTT | **196.05 ms** | | Standard deviation | **3.49 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Hong Kong latency and RTT](/docs/network/latency/pairs/nyc-hkg-rtt) — 187.1 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-nyc-rtt). - **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. # Hong Kong → Paris, France RTT 🇭🇰 **Hong Kong (HKG)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Hong Kong to Paris were sent at 100 ms intervals, and none were lost. The average round-trip time was 159.4 ms, with observed values between a minimum of 154.31 ms and a maximum of 174.31 ms. The route's 4.8 ms standard deviation and 4.33 ms jitter place it in the Fair latency tier. It ranks thirteenth among the 19 outbound routes from Hong Kong measured in this round, and its variation coefficient of roughly 3.0 percent sits close to the 3.28 percent median for that group. Geometrically, the 9,647.6 km great-circle route has a fiber-floor RTT of 94.48 ms, so the observed average is 1.69 times the floor and fiber efficiency is 59.3 percent. Zero packet loss is a positive signal for reachability, while the spread around the average suggests a typical long-haul profile in this Hong Kong outbound set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **159.4 ms** | | Jitter | **4.33 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **94.48 ms** | | Fiber Efficiency | **59.3%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,647.6 km** | | Vacuum RTT floor | **64.36 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **94.48 ms** | | Low-latency fiber material floor | **94.1 ms** | | Engineering floor (5% path allowance) | **99.21 ms** | | Research 1.33× mapped-fiber reference | **125.65 ms** | | Estimated unamplified path loss | **2026 dB** | | Transparent optical spans / inline amplifiers | **127 / 126** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **154.31 ms** | | Average RTT | **159.4 ms** | | Maximum RTT | **174.31 ms** | | Standard deviation | **4.8 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Hong Kong latency and RTT](/docs/network/latency/pairs/par-hkg-rtt) — 160.1 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Asia Pacific → Europe)** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-par-rtt). - **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. # Hong Kong → Seattle, USA RTT 🇭🇰 **Hong Kong (HKG)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of ICMP echo probes from Hong Kong to Seattle returned an average round-trip time of 131.6 ms, with a minimum of 125.78 ms and a maximum of 162.34 ms. All 50 probes were answered, so packet loss was zero; jitter came to 5.03 ms and the standard deviation was 6.2 ms, placing the route in the good latency tier. On this network's 19-outbound-route measurement set, the path ranked 5th by round-trip time, and the median variability across the set was 3.28% of the average RTT. The route's own variability is about 4.7% of its average, so it is a little less stable than the set's typical path, though the difference is modest. The geodesic reference for this crossing is roughly 10,436 km, with a vacuum floor of 69.62 ms and a fiber floor of 102.2 ms. The measured average is only 1.29 times the fiber floor, equivalent to a fiber efficiency of 77.7%, suggesting a fairly direct trans-Pacific alignment. Zero loss and a good latency tier make this a useful reference for the round, while the 36.6 ms spread between the fastest and slowest probes still shows noticeable RTT variation. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **131.6 ms** | | Jitter | **5.03 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **102.2 ms** | | Fiber Efficiency | **77.7%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,435.9 km** | | Vacuum RTT floor | **69.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **102.2 ms** | | Low-latency fiber material floor | **101.79 ms** | | Engineering floor (5% path allowance) | **107.32 ms** | | Research 1.33× mapped-fiber reference | **135.92 ms** | | Estimated unamplified path loss | **2191.5 dB** | | Transparent optical spans / inline amplifiers | **137 / 136** | | Published RTT inflation over fiber floor | **1.29×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **125.78 ms** | | Average RTT | **131.6 ms** | | Maximum RTT | **162.34 ms** | | Standard deviation | **6.2 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-sea-rtt). - **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. # Hong Kong → Singapore RTT 🇭🇰 **Hong Kong (HKG)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT from Hong Kong to Singapore averaged 31.5 ms across 50 samples, with a minimum of 29.73 ms and a maximum of 35.06 ms. There was no packet loss, and jitter measured 1.16 ms, keeping the route within the excellent latency tier. Over the 2,577.2 km great-circle distance, the observed average is 1.25 times the 25.24 ms fiber floor, which places fiber efficiency at 80.1 percent. The tight standard deviation of 1.22 ms reinforces that the route is both quick and stable. This path ranks second among the 19 outbound routes from Hong Kong in measurement round 2026-08-16T04:07:28Z. The median standard deviation as a share of average RTT for those routes is 3.28 percent, while this route's standard deviation works out to about 3.9 percent of its average, so it tracks closely to the group's typical variability. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **31.5 ms** | | Jitter | **1.16 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **25.24 ms** | | Fiber Efficiency | **80.1%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,577.2 km** | | Vacuum RTT floor | **17.19 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **25.24 ms** | | Low-latency fiber material floor | **25.14 ms** | | Engineering floor (5% path allowance) | **26.5 ms** | | Research 1.33× mapped-fiber reference | **33.57 ms** | | Estimated unamplified path loss | **541.2 dB** | | Transparent optical spans / inline amplifiers | **34 / 33** | | Published RTT inflation over fiber floor | **1.25×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **29.73 ms** | | Average RTT | **31.5 ms** | | Maximum RTT | **35.06 ms** | | Standard deviation | **1.22 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Fastest routes arriving at Singapore (SIN)** * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-sin-rtt). - **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. # Hong Kong → Sydney, Australia RTT 🇭🇰 **Hong Kong (HKG)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT from Hong Kong to Sydney averaged 137.2 ms across 50 samples, with a minimum of 129.36 ms and a maximum of 162.96 ms. There was no packet loss, but jitter of 5.69 ms and a 6.53 ms standard deviation show a moderate spread in the sample. The great-circle distance of 7,349.1 km implies a vacuum floor of 49.03 ms and a fiber floor of 71.97 ms. Observed latency is 1.91 times the fiber floor, or 52.5 percent fiber efficiency, leaving a sizeable overhead beyond the direct-fiber reference. Among the 19 outbound routes from Hong Kong in round 2026-08-16T04:07:28Z, this path ranks sixth in RTT performance. The group's median standard deviation as a share of average RTT is 3.28 percent; at roughly 4.8 percent of its average, this route's standard deviation is above that median, so the latency is both high and a bit less steady. Zero packet loss across all 50 samples remains a positive signal for reachability, even though round-trip time is the dominant factor on this long-haul route. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **137.2 ms** | | Jitter | **5.69 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **71.97 ms** | | Fiber Efficiency | **52.5%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,349.1 km** | | Vacuum RTT floor | **49.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **71.97 ms** | | Low-latency fiber material floor | **71.68 ms** | | Engineering floor (5% path allowance) | **75.58 ms** | | Research 1.33× mapped-fiber reference | **95.72 ms** | | Estimated unamplified path loss | **1543.3 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.91×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **129.36 ms** | | Average RTT | **137.2 ms** | | Maximum RTT | **162.96 ms** | | Standard deviation | **6.53 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-syd-rtt). - **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. # Hong Kong → Taipei, Taiwan RTT 🇭🇰 **Hong Kong (HKG)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT from Hong Kong to Taipei averaged 14.7 ms across 50 samples, with a minimum of 13.95 ms and a maximum of 17.24 ms. There was no packet loss and jitter was 0.56 ms, placing the route in the ultra-low latency tier. The great-circle distance is 810.3 km, giving a vacuum floor of 5.41 ms and a fiber floor of 7.94 ms. Observed latency is 1.85 times the fiber floor, or 54 percent fiber efficiency, with an absolute overhead of roughly 6.8 ms over the direct-fiber reference. This route ranks first among the 19 outbound paths from Hong Kong in measurement round 2026-08-16T04:07:28Z. Its standard deviation of 0.72 ms is only about 4.9 percent of the average, above the group's median standard deviation share of 3.28 percent, though the absolute jitter remains very small. In practical terms, the route delivers the lowest RTT in the measured set while maintaining zero packet loss, making it a clear reference for low-latency connectivity from Hong Kong. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **14.7 ms** | | Jitter | **0.56 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **7.94 ms** | | Fiber Efficiency | **54%** | | Latency Tier | Ultra-Low | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **810.3 km** | | Vacuum RTT floor | **5.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **7.94 ms** | | Low-latency fiber material floor | **7.9 ms** | | Engineering floor (5% path allowance) | **8.33 ms** | | Research 1.33× mapped-fiber reference | **10.55 ms** | | Estimated unamplified path loss | **170.2 dB** | | Transparent optical spans / inline amplifiers | **11 / 10** | | Published RTT inflation over fiber floor | **1.85×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **13.95 ms** | | Average RTT | **14.7 ms** | | Maximum RTT | **17.24 ms** | | Standard deviation | **0.72 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Fastest routes arriving at Taipei (TPE)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-tpe-rtt). - **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. # Hong Kong → Tokyo, Japan RTT 🇭🇰 **Hong Kong (HKG)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, ICMP echo requests from Hong Kong to Tokyo returned a 44.9 ms average RTT, with a 42.32 ms minimum, a 50.91 ms maximum, and no lost packets. The 1.82 ms standard deviation and 1.6 ms jitter confirm a stable intercity path, matching the excellent latency tier. This path is the third fastest among the 19 outbound routes measured in this round. Its variability ratio of about 4.1% sits slightly above the network-wide median of 3.28%, so the route is fast but not the most uniform in the set. Against the 2,883.5 km great-circle distance, the vacuum floor is 19.24 ms and the fiber floor is 28.24 ms. The observed RTT is 1.59 times the fiber floor, a fiber efficiency of 62.9%, indicating the route tracks a realistic regional fiber path with little excess delay. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **44.9 ms** | | Jitter | **1.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **28.24 ms** | | Fiber Efficiency | **62.9%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,883.5 km** | | Vacuum RTT floor | **19.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **28.24 ms** | | Low-latency fiber material floor | **28.12 ms** | | Engineering floor (5% path allowance) | **29.65 ms** | | Research 1.33× mapped-fiber reference | **37.56 ms** | | Estimated unamplified path loss | **605.5 dB** | | Transparent optical spans / inline amplifiers | **38 / 37** | | Published RTT inflation over fiber floor | **1.59×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **42.32 ms** | | Average RTT | **44.9 ms** | | Maximum RTT | **50.91 ms** | | Standard deviation | **1.82 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms **Fastest routes departing Hong Kong (HKG)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/hkg-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-tyo-rtt). - **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. # Ashburn, USA → Amsterdam, Netherlands RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z ICMP echo round, Ashburn, USA to Amsterdam, Netherlands averaged 75.2 ms over 50 probes, with a minimum of 72.76 ms and a maximum of 84.12 ms. All probes were returned without loss, and jitter measured 1.77 ms, putting the route in the Excellent latency tier. The physical reference for this 6,223.2 km path is a vacuum floor of 41.52 ms and a fiber floor of 60.94 ms. At 75.2 ms average, the route runs 1.23 times the fiber floor, yielding 81% fiber efficiency; that is a strong result for the distance and means the route is already close to its physical ideal. This route ranks 6th among the 19 outbound routes in the same measurement set, placing it on the faster side of the network profile. Its standard deviation of 2.32 ms works out to about 3.1% of the average, essentially matching the network's median 3.28% variability, so the excellent speed is accompanied by steady probe-to-probe behavior. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **75.2 ms** | | Jitter | **1.77 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **60.94 ms** | | Fiber Efficiency | **81%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,223.2 km** | | Vacuum RTT floor | **41.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **60.94 ms** | | Low-latency fiber material floor | **60.7 ms** | | Engineering floor (5% path allowance) | **64 ms** | | Research 1.33× mapped-fiber reference | **81.05 ms** | | Estimated unamplified path loss | **1306.9 dB** | | Transparent optical spans / inline amplifiers | **82 / 81** | | Published RTT inflation over fiber floor | **1.23×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **72.76 ms** | | Average RTT | **75.2 ms** | | Maximum RTT | **84.12 ms** | | Standard deviation | **2.32 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Ashburn latency and RTT](/docs/network/latency/pairs/ams-iad-rtt) — 75.7 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-ams-rtt). - **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. # Ashburn, USA → Berlin, Germany RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. On 2026-08-16T04:07:28Z, ICMP echo probes from Ashburn, USA to Berlin, Germany returned an average RTT of 86.1 ms, with a minimum of 84.07 ms and a maximum of 94.45 ms over 50 samples. Packet loss was 0% and jitter was 1.6 ms, placing the route in the Good latency tier. The physical reference for this 6,744.5 km path is a vacuum floor of 44.99 ms and a fiber floor of 66.05 ms. The observed average sits 1.30 times above the fiber floor, translating to 76.7% fiber efficiency — a solid outcome for the US-to-Germany distance and a clear step above the theoretical minimum. Within the same set of 19 outbound routes, this path ranks 9th, putting it near the middle of the network's latency distribution. Its standard deviation of 2.05 ms is about 2.4% of the average, which is tighter than the network's median 3.28% variability, so the route's Good-tier timing is also consistent across the run. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **86.1 ms** | | Jitter | **1.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **66.05 ms** | | Fiber Efficiency | **76.7%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,744.5 km** | | Vacuum RTT floor | **44.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **66.05 ms** | | Low-latency fiber material floor | **65.78 ms** | | Engineering floor (5% path allowance) | **69.36 ms** | | Research 1.33× mapped-fiber reference | **87.84 ms** | | Estimated unamplified path loss | **1416.4 dB** | | Transparent optical spans / inline amplifiers | **89 / 88** | | Published RTT inflation over fiber floor | **1.3×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **84.07 ms** | | Average RTT | **86.1 ms** | | Maximum RTT | **94.45 ms** | | Standard deviation | **2.05 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Ashburn latency and RTT](/docs/network/latency/pairs/ber-iad-rtt) — 85.7 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-ber-rtt). - **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. # Ashburn, USA → Frankfurt, Germany RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. During measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Ashburn, USA to Frankfurt, Germany returned an average round-trip time of 81.2 ms, with a minimum of 79.1 ms, a maximum of 86.57 ms, and no packet loss. The route's 6,566 km geodesic span has a theoretical vacuum floor of 43.8 ms and a fiber floor of 64.3 ms; the observed 81.2 ms average is 1.26 times the fiber floor, corresponding to 79.2% fiber efficiency. This suggests a path that stays reasonably close to a great-circle fiber trajectory despite connecting two major hubs. This route ranked eighth of the 19 outbound routes measured from Ashburn in the same round. Its standard deviation of 1.81 ms is 2.2% of the average, below the 3.28% median fluctuation ratio across the peer set, so the route paired a mid-pack ranking with notably stable timing. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **81.2 ms** | | Jitter | **1.11 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **64.3 ms** | | Fiber Efficiency | **79.2%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **6,566 km** | | Vacuum RTT floor | **43.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **64.3 ms** | | Low-latency fiber material floor | **64.04 ms** | | Engineering floor (5% path allowance) | **67.52 ms** | | Research 1.33× mapped-fiber reference | **85.52 ms** | | Estimated unamplified path loss | **1378.9 dB** | | Transparent optical spans / inline amplifiers | **87 / 86** | | Published RTT inflation over fiber floor | **1.26×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **79.1 ms** | | Average RTT | **81.2 ms** | | Maximum RTT | **86.57 ms** | | Standard deviation | **1.81 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Ashburn latency and RTT](/docs/network/latency/pairs/fra-iad-rtt) — 80.7 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-fra-rtt). - **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. # Ashburn, USA → São Paulo, Brazil RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Ashburn to São Paulo averaged 101.4 ms across 50 samples, with a minimum of 98.16 ms and a maximum of 107.74 ms. Zero packet loss and 2.06 ms jitter made the window unusually stable. The observed average is 1.36 times the theoretical fiber floor for the 7,637.7 km great-circle distance, translating to 73.8% fiber efficiency. The 2.31 ms standard deviation, or about 2.3% of the average, points to low sample-to-sample variation. Ranked 11th among the 19 outbound paths sampled from this network, the route showed less variability than the network-wide median ratio of 3.28%. The tight 9.6 ms spread between minimum and maximum is a useful bound for short-term RTT variation on this corridor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **101.4 ms** | | Jitter | **2.06 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **74.79 ms** | | Fiber Efficiency | **73.8%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,637.7 km** | | Vacuum RTT floor | **50.95 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **74.79 ms** | | Low-latency fiber material floor | **74.49 ms** | | Engineering floor (5% path allowance) | **78.54 ms** | | Research 1.33× mapped-fiber reference | **99.48 ms** | | Estimated unamplified path loss | **1603.9 dB** | | Transparent optical spans / inline amplifiers | **101 / 100** | | Published RTT inflation over fiber floor | **1.36×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **98.16 ms** | | Average RTT | **101.4 ms** | | Maximum RTT | **107.74 ms** | | Standard deviation | **2.31 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [North America to South America](/docs/network/latency/regions/north-america-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Ashburn latency and RTT](/docs/network/latency/pairs/gru-iad-rtt) — 128 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at São Paulo (GRU)** * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-gru-rtt). - **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. # Ashburn, USA → Hong Kong RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Ashburn to Hong Kong averaged 187.2 ms over 50 samples, with a minimum of 178.13 ms and a maximum of 213.4 ms. Zero packets were lost, while 6.84 ms jitter pointed to modest arrival-time variation. The path ran 1.46 times above the theoretical fiber floor for a 13,108.8 km great-circle distance, an efficiency of 68.6%. Its 8.01 ms standard deviation is about 4.3% of the average, a higher variability share than the network-wide median of 3.28%. Ranked 15th among the 19 outbound paths measured in this round, this route's variability ratio sits above the network median. The 35.3 ms split between minimum and maximum makes this a path worth watching for occasional latency outliers. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **187.2 ms** | | Jitter | **6.84 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.37 ms** | | Fiber Efficiency | **68.6%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,108.8 km** | | Vacuum RTT floor | **87.45 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.37 ms** | | Low-latency fiber material floor | **127.86 ms** | | Engineering floor (5% path allowance) | **134.81 ms** | | Research 1.33× mapped-fiber reference | **170.73 ms** | | Estimated unamplified path loss | **2752.9 dB** | | Transparent optical spans / inline amplifiers | **173 / 172** | | Published RTT inflation over fiber floor | **1.46×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **178.13 ms** | | Average RTT | **187.2 ms** | | Maximum RTT | **213.4 ms** | | Standard deviation | **8.01 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Ashburn latency and RTT](/docs/network/latency/pairs/hkg-iad-rtt) — 186.2 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-hkg-rtt). - **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. # Ashburn, USA → Johannesburg, South Africa RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo test from Ashburn, USA to Johannesburg, South Africa returned an average RTT of 228.3 ms, with values ranging from 216.38 ms to 264.39 ms and no packet loss across 50 samples. This route ranked 19th of the 19 routes measured in the same cycle, placing it at the high-latency end of the set. Its variability ratio of about 4.7 percent is above the network-wide median of 3.28 percent, and the 10.74 ms standard deviation and 7.98 ms jitter underline a path that is more dispersed than the average route in the set and consistent with the Fair latency tier. The 13,082 km great-circle distance gives a vacuum floor of 87.27 ms and a practical fiber floor of 128.11 ms. At 1.78 times that fiber floor, the route's 56.1 percent fiber efficiency shows a wide gap to the physical optimum, so operators should expect peak RTTs near the observed 264 ms upper bound during comparable measurement windows. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **228.3 ms** | | Jitter | **7.98 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.11 ms** | | Fiber Efficiency | **56.1%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **13,082 km** | | Vacuum RTT floor | **87.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.11 ms** | | Low-latency fiber material floor | **127.59 ms** | | Engineering floor (5% path allowance) | **134.53 ms** | | Research 1.33× mapped-fiber reference | **170.38 ms** | | Estimated unamplified path loss | **2747.2 dB** | | Transparent optical spans / inline amplifiers | **172 / 171** | | Published RTT inflation over fiber floor | **1.78×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **216.38 ms** | | Average RTT | **228.3 ms** | | Maximum RTT | **264.39 ms** | | Standard deviation | **10.74 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Ashburn latency and RTT](/docs/network/latency/pairs/jnb-iad-rtt) — 229 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (North America → Africa)** * [New York to Johannesburg latency and RTT](/docs/network/latency/pairs/nyc-jnb-rtt) — 221.5 ms * [Miami to Johannesburg latency and RTT](/docs/network/latency/pairs/mia-jnb-rtt) — 259.8 ms * [Seattle to Johannesburg latency and RTT](/docs/network/latency/pairs/sea-jnb-rtt) — 282.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-jnb-rtt). - **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. # Ashburn, USA → Los Angeles, USA RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z run, ICMP probes from Ashburn to Los Angeles averaged 60.7 ms across 50 samples, with a minimum of 58.56 ms and a maximum of 67.73 ms. All 50 probes returned without loss, and the 1.84 ms standard deviation kept jitter at 1.64 ms, making the route steady across the measurement window. The 3,660.1 km great-circle distance defines a 24.42 ms vacuum-latency floor and a 35.84 ms realistic fiber floor. At 60.7 ms, the route is about 1.69 times the fiber floor, or 59% fiber efficiency, so there is meaningful excess delay beyond the ideal straight-line fiber path. This route is ranked 3rd by RTT among the 19 outbound paths measured from the same starting point, putting it near the fast end of the set. The median standard-deviation-to-average ratio for outbound paths from this starting point is 3.28%, and the observed standard deviation of 1.84 ms is a small fraction of the 60.7 ms average, so the route is both fast and consistent; however, ICMP RTT should not be used as a proxy for end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **60.7 ms** | | Jitter | **1.64 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **35.84 ms** | | Fiber Efficiency | **59%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,660.1 km** | | Vacuum RTT floor | **24.42 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **35.84 ms** | | Low-latency fiber material floor | **35.7 ms** | | Engineering floor (5% path allowance) | **37.64 ms** | | Research 1.33× mapped-fiber reference | **47.67 ms** | | Estimated unamplified path loss | **768.6 dB** | | Transparent optical spans / inline amplifiers | **49 / 48** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **58.56 ms** | | Average RTT | **60.7 ms** | | Maximum RTT | **67.73 ms** | | Standard deviation | **1.84 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms * [Ashburn to Amsterdam latency and RTT](/docs/network/latency/pairs/iad-ams-rtt) — 75.2 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [London to Los Angeles latency and RTT](/docs/network/latency/pairs/lon-lax-rtt) — 127.5 ms **Same corridor (North America → North America)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-lax-rtt). - **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. # Ashburn, USA → London, UK RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. For measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Ashburn, USA to London, UK averaged 70.3 ms, with a minimum of 68.79 ms, a maximum of 73.78 ms, and zero packet loss. The 5,932.8 km geodesic distance implies a vacuum floor of 39.58 ms and a fiber floor of 58.1 ms; the measured average is only 1.21 times the fiber floor, for an 82.6% fiber efficiency rating. This crossing is operating close to the realistic floor for a transatlantic fiber link. This route ranked fifth of the 19 outbound routes measured from Ashburn, and its standard deviation of 1.22 ms is just 1.7% of the average, well below the 3.28% median fluctuation ratio across comparable routes. The result is a stable, high-efficiency transatlantic path from Ashburn to London. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **70.3 ms** | | Jitter | **1.06 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **58.1 ms** | | Fiber Efficiency | **82.6%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,932.8 km** | | Vacuum RTT floor | **39.58 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **58.1 ms** | | Low-latency fiber material floor | **57.87 ms** | | Engineering floor (5% path allowance) | **61.01 ms** | | Research 1.33× mapped-fiber reference | **77.27 ms** | | Estimated unamplified path loss | **1245.9 dB** | | Transparent optical spans / inline amplifiers | **78 / 77** | | Published RTT inflation over fiber floor | **1.21×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **68.79 ms** | | Average RTT | **70.3 ms** | | Maximum RTT | **73.78 ms** | | Standard deviation | **1.22 ms** | | Stdev / average | **1.7%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to Amsterdam latency and RTT](/docs/network/latency/pairs/iad-ams-rtt) — 75.2 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-lon-rtt). - **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. # Ashburn, USA → Melbourne, Australia RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Ashburn to Melbourne averaged 203.9 ms over 50 samples, with a minimum of 200.88 ms and a maximum of 217.16 ms. No packets were lost and jitter was only 2.28 ms, a notably tight result for the distance covered. The path sat 1.27 times above the theoretical fiber floor for its 16,348.2 km great-circle distance, translating to 78.5% fiber efficiency. The standard deviation of 3.32 ms, about 1.6% of the average, indicates remarkably low dispersion across the sample window. Ranked 17th among the 19 outbound paths measured in this round, the route's variability ratio is well below the network-wide median of 3.28%. The 16.3 ms difference between minimum and maximum suggests stable intercontinental transport despite the long haul. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **203.9 ms** | | Jitter | **2.28 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **160.09 ms** | | Fiber Efficiency | **78.5%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,348.2 km** | | Vacuum RTT floor | **109.06 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **160.09 ms** | | Low-latency fiber material floor | **159.45 ms** | | Engineering floor (5% path allowance) | **168.12 ms** | | Research 1.33× mapped-fiber reference | **212.92 ms** | | Estimated unamplified path loss | **3433.1 dB** | | Transparent optical spans / inline amplifiers | **215 / 214** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **200.88 ms** | | Average RTT | **203.9 ms** | | Maximum RTT | **217.16 ms** | | Standard deviation | **3.32 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Ashburn latency and RTT](/docs/network/latency/pairs/mel-iad-rtt) — 203.9 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-mel-rtt). - **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. # Ashburn, USA → Miami, USA RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the Ashburn-to-Miami route averaged 27.4 ms ICMP RTT across 50 samples, with a minimum of 26.09 ms and a maximum of 30.01 ms; no packets were lost and jitter stayed at 0.98 ms. Against the geodesic reference for 1,493.2 km, the vacuum floor is 9.96 ms and the direct fiber floor is 14.62 ms. The observed average is 1.87 times the fiber floor, giving a fiber efficiency of 53.4 percent—a useful baseline for judging how close this route's round-trip time is to the direct-fiber reference for that distance. This pair is the second-ranked outbound route among the 19 Ashburn routes captured in the same round. Its standard deviation of 1.06 ms represents roughly 3.9 percent of the average, slightly above the 3.28 percent median relative variation seen across the route set, so the route is stable but not the most consistent in comparative terms. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **27.4 ms** | | Jitter | **0.98 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **14.62 ms** | | Fiber Efficiency | **53.4%** | | Latency Tier | Ultra-Low | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,493.2 km** | | Vacuum RTT floor | **9.96 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **14.62 ms** | | Low-latency fiber material floor | **14.56 ms** | | Engineering floor (5% path allowance) | **15.36 ms** | | Research 1.33× mapped-fiber reference | **19.45 ms** | | Estimated unamplified path loss | **313.6 dB** | | Transparent optical spans / inline amplifiers | **20 / 19** | | Published RTT inflation over fiber floor | **1.87×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **26.09 ms** | | Average RTT | **27.4 ms** | | Maximum RTT | **30.01 ms** | | Standard deviation | **1.06 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms * [Ashburn to Amsterdam latency and RTT](/docs/network/latency/pairs/iad-ams-rtt) — 75.2 ms **Fastest routes arriving at Miami (MIA)** * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 ms **Same corridor (North America → North America)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-mia-rtt). - **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. # Ashburn, USA → Moscow, Russia RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z run, ICMP probes from Ashburn to Moscow averaged 112.8 ms across 50 samples, with a minimum of 109.18 ms and a maximum of 122.64 ms. Zero packets were lost, and the 3.63 ms standard deviation held jitter to about 3.16 ms, so the path stayed stable for the full measurement window. The 7,850.6 km great-circle distance defines a 52.37 ms vacuum-latency floor and a 76.88 ms realistic fiber floor. At 112.8 ms, the observed route runs about 1.47 times the fiber floor, or 68.2% fiber efficiency, meaning the extra delay above an ideal fiber path is moderate rather than extreme for a route spanning this geography. In this round, the route is ranked 12th by RTT among the 19 outbound paths measured from the same starting point. The median standard-deviation-to-average ratio for outbound paths from this starting point is 3.28%, and with zero loss and 3.16 ms jitter, this Moscow path is consistent enough that the 112.8 ms average can serve as a practical RTT baseline for planning; as with any ICMP measurement, it should not be mistaken for a predictor of end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **112.8 ms** | | Jitter | **3.16 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.88 ms** | | Fiber Efficiency | **68.2%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,850.6 km** | | Vacuum RTT floor | **52.37 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.88 ms** | | Low-latency fiber material floor | **76.57 ms** | | Engineering floor (5% path allowance) | **80.73 ms** | | Research 1.33× mapped-fiber reference | **102.25 ms** | | Estimated unamplified path loss | **1648.6 dB** | | Transparent optical spans / inline amplifiers | **104 / 103** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **109.18 ms** | | Average RTT | **112.8 ms** | | Maximum RTT | **122.64 ms** | | Standard deviation | **3.63 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Ashburn latency and RTT](/docs/network/latency/pairs/mow-iad-rtt) — 113.9 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-mow-rtt). - **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. # Ashburn, USA → Marseille, France RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z collected 50 ICMP echo probes from Ashburn, USA to Marseille, France, producing an average RTT of 86.5 ms, a minimum of 81.69 ms, a maximum of 97.62 ms, and no packet loss. The 6,672.7 km geodesic distance gives a vacuum floor of 44.52 ms and a fiber floor of 65.34 ms; at 86.5 ms the route runs 1.32 times the fiber floor, with 75.5% fiber efficiency. The wider spread between minimum and maximum, roughly 16 ms, and the 3.63 ms standard deviation show that Marseille-bound traffic can carry noticeable timing variability even with zero loss. This route ranked tenth of the 19 outbound routes measured from Ashburn. Its standard deviation of 3.63 ms represents 4.2% of the average, above the 3.28% median fluctuation ratio for comparable routes; the jitter of 3.41 ms is the main feature to watch on this path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **86.5 ms** | | Jitter | **3.41 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **65.34 ms** | | Fiber Efficiency | **75.5%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,672.7 km** | | Vacuum RTT floor | **44.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **65.34 ms** | | Low-latency fiber material floor | **65.08 ms** | | Engineering floor (5% path allowance) | **68.62 ms** | | Research 1.33× mapped-fiber reference | **86.91 ms** | | Estimated unamplified path loss | **1401.3 dB** | | Transparent optical spans / inline amplifiers | **88 / 87** | | Published RTT inflation over fiber floor | **1.32×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **81.69 ms** | | Average RTT | **86.5 ms** | | Maximum RTT | **97.62 ms** | | Standard deviation | **3.63 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Ashburn latency and RTT](/docs/network/latency/pairs/mrs-iad-rtt) — 85.7 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-mrs-rtt). - **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. # Ashburn, USA → New York, USA RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, Ashburn-to-New York produced an average ICMP RTT of 6 ms from 50 samples, with a minimum of 5.77 ms and a maximum of 6.79 ms, plus zero packet loss and jitter of 0.19 ms. At 350.8 km, the reference vacuum floor is 2.34 ms and the direct fiber floor is 3.44 ms. The observed 6 ms average runs 1.75 times the fiber floor, a fiber efficiency of 57.3 percent, placing the route well within ultra-low-latency territory for this distance. This route ranks first among the 19 Ashburn outbound routes measured in the same round. Its standard deviation of 0.20 ms is only about 3.3 percent of the average, close to the 3.28 percent median relative variation across the route set, and the near-zero jitter reinforces how consistent the short trip is. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **6 ms** | | Jitter | **0.19 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.44 ms** | | Fiber Efficiency | **57.3%** | | Latency Tier | Ultra-Low | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **350.8 km** | | Vacuum RTT floor | **2.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.44 ms** | | Low-latency fiber material floor | **3.42 ms** | | Engineering floor (5% path allowance) | **3.61 ms** | | Research 1.33× mapped-fiber reference | **4.57 ms** | | Estimated unamplified path loss | **73.7 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.75×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **5.77 ms** | | Average RTT | **6 ms** | | Maximum RTT | **6.79 ms** | | Standard deviation | **0.2 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms * [Ashburn to Amsterdam latency and RTT](/docs/network/latency/pairs/iad-ams-rtt) — 75.2 ms **Fastest routes arriving at New York (NYC)** * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms **Same corridor (North America → North America)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-nyc-rtt). - **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. # Ashburn, USA → Paris, France RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z run, ICMP probes from Ashburn to Paris averaged 76.1 ms across 50 samples, with a minimum of 74.36 ms and a maximum of 85 ms. No packets were lost, and the 1.76 ms standard deviation produced 1.12 ms of jitter, so the path was very stable throughout the measurement window. The 6,202 km great-circle distance yields a 41.38 ms vacuum-latency floor and a 60.73 ms fiber floor. The measured 76.1 ms is 1.25 times the fiber floor, a 79.8% fiber efficiency that leaves relatively little excess delay over the ideal fiber path. In this round, the route is ranked 7th by RTT among the 19 outbound paths measured from the same starting point, placing it in the upper half of that set. The median standard-deviation-to-average ratio for outbound paths from this starting point is 3.28%, and this route's spread of 1.76 ms around 76.1 ms is even tighter, so the route should deliver dependable network-layer RTT for Paris-bound traffic; ICMP RTT alone does not measure application experience. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **76.1 ms** | | Jitter | **1.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **60.73 ms** | | Fiber Efficiency | **79.8%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **6,202 km** | | Vacuum RTT floor | **41.38 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **60.73 ms** | | Low-latency fiber material floor | **60.49 ms** | | Engineering floor (5% path allowance) | **63.78 ms** | | Research 1.33× mapped-fiber reference | **80.78 ms** | | Estimated unamplified path loss | **1302.4 dB** | | Transparent optical spans / inline amplifiers | **82 / 81** | | Published RTT inflation over fiber floor | **1.25×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **74.36 ms** | | Average RTT | **76.1 ms** | | Maximum RTT | **85 ms** | | Standard deviation | **1.76 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Ashburn latency and RTT](/docs/network/latency/pairs/par-iad-rtt) — 75.5 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-par-rtt). - **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. # Ashburn, USA → Seattle, USA RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the Ashburn-to-Seattle route averaged 62.3 ms ICMP RTT across 50 samples, with a minimum of 59.37 ms and a maximum of 75.24 ms; no packets were lost and jitter was 1.89 ms. The geodesic span is 3,704 km, setting a vacuum floor of 24.71 ms and a direct fiber floor of 36.27 ms. At 62.3 ms, the measured path is 1.72 times the fiber floor—a 58.2 percent fiber efficiency—so the extra delay over the direct-fiber reference is modest for a transcontinental span. This route ranks fourth among the 19 Ashburn outbound routes in the same round. Its standard deviation of 2.67 ms is about 4.3 percent of the average, above the 3.28 percent median relative variation across the route set, but the zero-loss result and sub-2 ms jitter still leave the ICMP round-trip time essentially stable. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **62.3 ms** | | Jitter | **1.89 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **36.27 ms** | | Fiber Efficiency | **58.2%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **3,704 km** | | Vacuum RTT floor | **24.71 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **36.27 ms** | | Low-latency fiber material floor | **36.13 ms** | | Engineering floor (5% path allowance) | **38.09 ms** | | Research 1.33× mapped-fiber reference | **48.24 ms** | | Estimated unamplified path loss | **777.8 dB** | | Transparent optical spans / inline amplifiers | **49 / 48** | | Published RTT inflation over fiber floor | **1.72×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **59.37 ms** | | Average RTT | **62.3 ms** | | Maximum RTT | **75.24 ms** | | Standard deviation | **2.67 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms * [Ashburn to Amsterdam latency and RTT](/docs/network/latency/pairs/iad-ams-rtt) — 75.2 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms **Same corridor (North America → North America)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-sea-rtt). - **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. # Ashburn, USA → Singapore RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT measurement from Ashburn, USA, to Singapore, Singapore, produced an average of 211.5 ms across 50 samples, with a minimum of 203.83 ms and a maximum of 243.56 ms. All packets were returned, so reported packet loss is 0%; the standard deviation of 6.36 ms and jitter of 5.45 ms place the route in the Fair latency tier. At a geodesic distance of 15,535.9 km, the theoretical fiber-floor RTT is 152.14 ms. The measured average therefore sits at 1.39 times that floor, corresponding to roughly 71.9% fiber efficiency. That gap leaves room for possible path improvements, though this single series does not by itself explain where the extra delay occurs. Compared with the 19 outbound routes measured from this network, this path ranked 18th by average RTT. Its standard deviation is about 3.0% of the average, slightly below the 3.28% median variability observed across the outbound route set. The loss-free result is a useful stability signal, but ICMP RTT should not be treated as a predictor of end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **211.5 ms** | | Jitter | **5.45 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **152.14 ms** | | Fiber Efficiency | **71.9%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,535.9 km** | | Vacuum RTT floor | **103.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **152.14 ms** | | Low-latency fiber material floor | **151.53 ms** | | Engineering floor (5% path allowance) | **159.77 ms** | | Research 1.33× mapped-fiber reference | **202.35 ms** | | Estimated unamplified path loss | **3262.5 dB** | | Transparent optical spans / inline amplifiers | **204 / 203** | | Published RTT inflation over fiber floor | **1.39×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **203.83 ms** | | Average RTT | **211.5 ms** | | Maximum RTT | **243.56 ms** | | Standard deviation | **6.36 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Ashburn latency and RTT](/docs/network/latency/pairs/sin-iad-rtt) — 210 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-sin-rtt). - **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. # Ashburn, USA → Sydney, Australia RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT measurement from Ashburn, USA, to Sydney, Australia, showed an average round trip of 193.6 ms over 50 samples, with a minimum of 185.3 ms and a maximum of 213.55 ms. Zero packet loss was observed, while the 6.56 ms standard deviation and 5.83 ms jitter place the route in the Fair latency tier. Given the geodesic distance of 15,673.1 km, the theoretical fiber-floor RTT is 153.48 ms. The measured average is 1.26 times that floor, an efficiency of about 79.3%, which means the observed delay is relatively close to the physical lower bound for this distance. The route ranked 16th of 19 outbound paths from this origin by average RTT. Its variability is slightly above the route set's median: the standard deviation is about 3.4% of the average, versus a median of 3.28%. With zero loss and a moderate spread between minimum and maximum, the path appears stable, though ICMP RTT alone is not a measure of application-level performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **193.6 ms** | | Jitter | **5.83 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **153.48 ms** | | Fiber Efficiency | **79.3%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,673.1 km** | | Vacuum RTT floor | **104.56 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **153.48 ms** | | Low-latency fiber material floor | **152.87 ms** | | Engineering floor (5% path allowance) | **161.18 ms** | | Research 1.33× mapped-fiber reference | **204.13 ms** | | Estimated unamplified path loss | **3291.4 dB** | | Transparent optical spans / inline amplifiers | **206 / 205** | | Published RTT inflation over fiber floor | **1.26×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **185.3 ms** | | Average RTT | **193.6 ms** | | Maximum RTT | **213.55 ms** | | Standard deviation | **6.56 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Ashburn latency and RTT](/docs/network/latency/pairs/syd-iad-rtt) — 195.3 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-syd-rtt). - **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. # Ashburn, USA → Taipei, Taiwan RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT measurement from Ashburn, USA, to Taipei, Taiwan, recorded an average of 172.3 ms across 50 samples, with a minimum of 164.68 ms and a maximum of 192.64 ms. No packets were lost, and the 7.13 ms standard deviation and 6.51 ms jitter keep the route in the Fair latency tier. At a geodesic distance of 12,639.6 km, the theoretical fiber-floor RTT is 123.78 ms. The measured average is 1.39 times that floor, for a fiber efficiency of about 71.8%; in other words, the round trip carries a bit more than 48 ms of delay beyond the distance-based lower bound. Among the 19 outbound routes measured from this network, this path ranked 14th by average RTT. Its standard deviation is about 4.1% of the average, above the 3.28% median variability across the outbound route set, so the route is stable in terms of loss but a little more variable than the typical outbound path. ICMP RTT should not be used to infer end-user application speed. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **172.3 ms** | | Jitter | **6.51 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **123.78 ms** | | Fiber Efficiency | **71.8%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,639.6 km** | | Vacuum RTT floor | **84.32 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **123.78 ms** | | Low-latency fiber material floor | **123.28 ms** | | Engineering floor (5% path allowance) | **129.98 ms** | | Research 1.33× mapped-fiber reference | **164.62 ms** | | Estimated unamplified path loss | **2654.3 dB** | | Transparent optical spans / inline amplifiers | **166 / 165** | | Published RTT inflation over fiber floor | **1.39×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **164.68 ms** | | Average RTT | **172.3 ms** | | Maximum RTT | **192.64 ms** | | Standard deviation | **7.13 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Ashburn latency and RTT](/docs/network/latency/pairs/tpe-iad-rtt) — 171.6 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-tpe-rtt). - **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. # Ashburn, USA → Tokyo, Japan RTT 🇺🇸 **Ashburn, USA (IAD)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of ICMP echo measurements from Ashburn, USA to Tokyo, Japan collected 50 samples at 100 ms intervals, yielding an average RTT of 141.9 ms, a minimum of 136.1 ms and a maximum of 154.55 ms, with zero packet loss. On the 19-route set, this path ranked 13th, and its variability ratio of roughly 3.0 percent sits below the network-wide median of 3.28 percent. A standard deviation of 4.32 ms and jitter of 3.99 ms confirm a stable trans-Pacific latency profile despite the route's mid-pack ranking. The 10,894.6 km great-circle distance places the theoretical vacuum floor at 72.68 ms and the practical fiber floor at 106.69 ms. The measured 141.9 ms average is 1.33 times the fiber floor, or about 75.2 percent fiber efficiency, leaving a moderate but consistent gap between observed RTT and the physical lower bound. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **141.9 ms** | | Jitter | **3.99 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.69 ms** | | Fiber Efficiency | **75.2%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,894.6 km** | | Vacuum RTT floor | **72.68 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.69 ms** | | Low-latency fiber material floor | **106.26 ms** | | Engineering floor (5% path allowance) | **112.04 ms** | | Research 1.33× mapped-fiber reference | **141.9 ms** | | Estimated unamplified path loss | **2287.9 dB** | | Transparent optical spans / inline amplifiers | **143 / 142** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **136.1 ms** | | Average RTT | **141.9 ms** | | Maximum RTT | **154.55 ms** | | Standard deviation | **4.32 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Ashburn latency and RTT](/docs/network/latency/pairs/tyo-iad-rtt) — 142.9 ms **Fastest routes departing Ashburn (IAD)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/iad-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/iad-tyo-rtt). - **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. # City-to-City Ping & RTT Latency | AS203314 This section organizes published ping and round-trip time (RTT) pages across the Hats Network (AS203314) backbone. Each of the 380 directed route pages includes measured round statistics, physical fiber limits, efficiency, and open-data downloads. Measurement round: `2026-08-16T04:07:28Z`. ## Browse by Source City Use each PoP page as a focused hub for all outbound and inbound city-pair routes. | Source PoP | Region | Routes | | ----------------------------------------------------------------- | ------------- | ----------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) | Europe | 19 outbound | | [🇩🇪 Berlin (BER)](/docs/network/latency/ber-berlin) | Europe | 19 outbound | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) | Europe | 19 outbound | | [🇬🇧 London (LON)](/docs/network/latency/lon-london) | Europe | 19 outbound | | [🇫🇷 Marseille (MRS)](/docs/network/latency/mrs-marseille) | Europe | 19 outbound | | [🇷🇺 Moscow (MOW)](/docs/network/latency/mow-moscow) | Europe | 19 outbound | | [🇫🇷 Paris (PAR)](/docs/network/latency/par-paris) | Europe | 19 outbound | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/iad-ashburn) | North America | 19 outbound | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) | North America | 19 outbound | | [🇺🇸 Miami (MIA)](/docs/network/latency/mia-miami) | North America | 19 outbound | | [🇺🇸 New York (NYC)](/docs/network/latency/nyc-new-york) | North America | 19 outbound | | [🇺🇸 Seattle (SEA)](/docs/network/latency/sea-seattle) | North America | 19 outbound | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) | South America | 19 outbound | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) | Asia Pacific | 19 outbound | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/mel-melbourne) | Asia Pacific | 19 outbound | | [🇸🇬 Singapore (SIN)](/docs/network/latency/sin-singapore) | Asia Pacific | 19 outbound | | [🇦🇺 Sydney (SYD)](/docs/network/latency/syd-sydney) | Asia Pacific | 19 outbound | | [🇹🇼 Taipei (TPE)](/docs/network/latency/tpe-taipei) | Asia Pacific | 19 outbound | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/tyo-tokyo) | Asia Pacific | 19 outbound | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) | Africa | 19 outbound | ## Fastest City-Pair Routes | Route | RTT (ms) | Tier | | ------------------------------------------- | -------------------------------------------------- | --------- | | 🇳🇱 Amsterdam (AMS) → 🇬🇧 London (LON) | **[5.2](/docs/network/latency/pairs/ams-lon-rtt)** | Ultra-Low | | 🇬🇧 London (LON) → 🇳🇱 Amsterdam (AMS) | **[5.2](/docs/network/latency/pairs/lon-ams-rtt)** | Ultra-Low | | 🇳🇱 Amsterdam (AMS) → 🇩🇪 Frankfurt (FRA) | **[5.9](/docs/network/latency/pairs/ams-fra-rtt)** | Ultra-Low | | 🇩🇪 Frankfurt (FRA) → 🇳🇱 Amsterdam (AMS) | **[5.9](/docs/network/latency/pairs/fra-ams-rtt)** | Ultra-Low | | 🇺🇸 Ashburn (IAD) → 🇺🇸 New York (NYC) | **[6](/docs/network/latency/pairs/iad-nyc-rtt)** | Ultra-Low | | 🇺🇸 New York (NYC) → 🇺🇸 Ashburn (IAD) | **[6](/docs/network/latency/pairs/nyc-iad-rtt)** | Ultra-Low | | 🇩🇪 Berlin (BER) → 🇩🇪 Frankfurt (FRA) | **[6.1](/docs/network/latency/pairs/ber-fra-rtt)** | Ultra-Low | | 🇩🇪 Frankfurt (FRA) → 🇩🇪 Berlin (BER) | **[6.1](/docs/network/latency/pairs/fra-ber-rtt)** | Ultra-Low | | 🇬🇧 London (LON) → 🇫🇷 Paris (PAR) | **[6.4](/docs/network/latency/pairs/lon-par-rtt)** | Ultra-Low | | 🇫🇷 Paris (PAR) → 🇬🇧 London (LON) | **[6.4](/docs/network/latency/pairs/par-lon-rtt)** | Ultra-Low | ## All 380 City-Pair Routes Every measured directed route, grouped by source region and departure PoP. Each destination links to its dedicated latency page. ### Routes from Europe (133) **🇳🇱 Amsterdam (AMS) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/ams-ber-rtt) | **7.2 ms** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/ams-fra-rtt) | **5.9 ms** | Ultra-Low | | [🇬🇧 London (LON)](/docs/network/latency/pairs/ams-lon-rtt) | **5.2 ms** | Ultra-Low | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/ams-mrs-rtt) | **19.6 ms** | Ultra-Low | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/ams-mow-rtt) | **38.1 ms** | Excellent | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/ams-par-rtt) | **7 ms** | Ultra-Low | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/ams-iad-rtt) | **75.7 ms** | Excellent | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/ams-lax-rtt) | **133.7 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/ams-mia-rtt) | **106 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/ams-nyc-rtt) | **68.6 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/ams-sea-rtt) | **130.2 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/ams-gru-rtt) | **175.5 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/ams-hkg-rtt) | **155.9 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/ams-mel-rtt) | **252.5 ms** | High | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/ams-sin-rtt) | **157.6 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/ams-syd-rtt) | **258 ms** | High | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/ams-tpe-rtt) | **168.7 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/ams-tyo-rtt) | **198.2 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/ams-jnb-rtt) | **171.9 ms** | Fair | **🇩🇪 Berlin (BER) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/ber-ams-rtt) | **7.2 ms** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/ber-fra-rtt) | **6.1 ms** | Ultra-Low | | [🇬🇧 London (LON)](/docs/network/latency/pairs/ber-lon-rtt) | **15.2 ms** | Ultra-Low | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/ber-mrs-rtt) | **20.2 ms** | Ultra-Low | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/ber-mow-rtt) | **28.6 ms** | Ultra-Low | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/ber-par-rtt) | **15.6 ms** | Ultra-Low | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/ber-iad-rtt) | **85.7 ms** | Good | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/ber-lax-rtt) | **140.9 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/ber-mia-rtt) | **118.3 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/ber-nyc-rtt) | **79.6 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/ber-sea-rtt) | **139.7 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/ber-gru-rtt) | **186.5 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/ber-hkg-rtt) | **144.9 ms** | Good | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/ber-mel-rtt) | **256.2 ms** | High | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/ber-sin-rtt) | **158.3 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/ber-syd-rtt) | **262.1 ms** | High | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/ber-tpe-rtt) | **156.8 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/ber-tyo-rtt) | **187.5 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/ber-jnb-rtt) | **172.1 ms** | Fair | **🇩🇪 Frankfurt (FRA) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/fra-ams-rtt) | **5.9 ms** | Ultra-Low | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/fra-ber-rtt) | **6.1 ms** | Ultra-Low | | [🇬🇧 London (LON)](/docs/network/latency/pairs/fra-lon-rtt) | **12.9 ms** | Ultra-Low | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/fra-mrs-rtt) | **16.4 ms** | Ultra-Low | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/fra-mow-rtt) | **34.7 ms** | Excellent | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/fra-par-rtt) | **7.6 ms** | Ultra-Low | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/fra-iad-rtt) | **80.7 ms** | Good | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/fra-lax-rtt) | **141.8 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/fra-mia-rtt) | **112 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/fra-nyc-rtt) | **74.4 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/fra-sea-rtt) | **135.2 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/fra-gru-rtt) | **181.3 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/fra-hkg-rtt) | **152 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/fra-mel-rtt) | **250.1 ms** | High | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/fra-sin-rtt) | **151.4 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/fra-syd-rtt) | **256 ms** | High | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/fra-tpe-rtt) | **163.8 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/fra-tyo-rtt) | **194.5 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/fra-jnb-rtt) | **188.4 ms** | Fair | **🇬🇧 London (LON) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-rtt) | **5.2 ms** | Ultra-Low | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/lon-ber-rtt) | **16.2 ms** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/lon-fra-rtt) | **13.6 ms** | Ultra-Low | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/lon-mrs-rtt) | **17.9 ms** | Ultra-Low | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/lon-mow-rtt) | **43.5 ms** | Excellent | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/lon-par-rtt) | **6.4 ms** | Ultra-Low | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/lon-iad-rtt) | **71 ms** | Excellent | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/lon-lax-rtt) | **127.5 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/lon-mia-rtt) | **101.9 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/lon-nyc-rtt) | **63.8 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/lon-sea-rtt) | **123.2 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/lon-gru-rtt) | **170.7 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/lon-hkg-rtt) | **160.6 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/lon-mel-rtt) | **249.6 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/lon-sin-rtt) | **156.5 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/lon-syd-rtt) | **258.1 ms** | High | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/lon-tpe-rtt) | **173.8 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/lon-tyo-rtt) | **202.9 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/lon-jnb-rtt) | **179.6 ms** | Fair | **🇫🇷 Marseille (MRS) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/mrs-ams-rtt) | **20.3 ms** | Ultra-Low | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/mrs-ber-rtt) | **20.6 ms** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/mrs-fra-rtt) | **16 ms** | Ultra-Low | | [🇬🇧 London (LON)](/docs/network/latency/pairs/mrs-lon-rtt) | **18.9 ms** | Ultra-Low | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/mrs-mow-rtt) | **49.6 ms** | Excellent | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/mrs-par-rtt) | **8.9 ms** | Ultra-Low | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/mrs-iad-rtt) | **85.7 ms** | Good | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/mrs-lax-rtt) | **144.5 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/mrs-mia-rtt) | **112.4 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/mrs-nyc-rtt) | **79.8 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/mrs-sea-rtt) | **141.7 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/mrs-gru-rtt) | **186.7 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/mrs-hkg-rtt) | **166.4 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/mrs-mel-rtt) | **234.2 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/mrs-sin-rtt) | **139.6 ms** | Good | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mrs-syd-rtt) | **240.6 ms** | Fair | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/mrs-tpe-rtt) | **180.9 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/mrs-tyo-rtt) | **203.8 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/mrs-jnb-rtt) | **198.5 ms** | Fair | **🇷🇺 Moscow (MOW) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/mow-ams-rtt) | **37.6 ms** | Excellent | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/mow-ber-rtt) | **27.5 ms** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/mow-fra-rtt) | **35.9 ms** | Excellent | | [🇬🇧 London (LON)](/docs/network/latency/pairs/mow-lon-rtt) | **42.4 ms** | Excellent | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/mow-mrs-rtt) | **49.9 ms** | Excellent | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/mow-par-rtt) | **44 ms** | Excellent | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/mow-iad-rtt) | **113.9 ms** | Good | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/mow-lax-rtt) | **177.7 ms** | Fair | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/mow-mia-rtt) | **144.5 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/mow-nyc-rtt) | **107.5 ms** | Good | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/mow-sea-rtt) | **164.8 ms** | Fair | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/mow-gru-rtt) | **214.4 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/mow-hkg-rtt) | **118.6 ms** | Good | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/mow-mel-rtt) | **235.9 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/mow-sin-rtt) | **147.3 ms** | Good | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mow-syd-rtt) | **241.8 ms** | Fair | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/mow-tpe-rtt) | **132.1 ms** | Good | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/mow-tyo-rtt) | **162.2 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/mow-jnb-rtt) | **201.9 ms** | Fair | **🇫🇷 Paris (PAR) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/par-ams-rtt) | **7 ms** | Ultra-Low | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/par-ber-rtt) | **15.5 ms** | Ultra-Low | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/par-fra-rtt) | **7.6 ms** | Ultra-Low | | [🇬🇧 London (LON)](/docs/network/latency/pairs/par-lon-rtt) | **6.4 ms** | Ultra-Low | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/par-mrs-rtt) | **8.9 ms** | Ultra-Low | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/par-mow-rtt) | **44.7 ms** | Excellent | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/par-iad-rtt) | **75.5 ms** | Excellent | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/par-lax-rtt) | **136.5 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/par-mia-rtt) | **106.8 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/par-nyc-rtt) | **68.9 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/par-sea-rtt) | **128 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/par-gru-rtt) | **175.8 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/par-hkg-rtt) | **160.1 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/par-mel-rtt) | **246.4 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/par-sin-rtt) | **150.3 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/par-syd-rtt) | **249.7 ms** | Fair | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/par-tpe-rtt) | **171.9 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/par-tyo-rtt) | **204.7 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/par-jnb-rtt) | **180.9 ms** | Fair | ### Routes from North America (95) **🇺🇸 Ashburn (IAD) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/iad-ams-rtt) | **75.2 ms** | Excellent | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/iad-ber-rtt) | **86.1 ms** | Good | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/iad-fra-rtt) | **81.2 ms** | Good | | [🇬🇧 London (LON)](/docs/network/latency/pairs/iad-lon-rtt) | **70.3 ms** | Excellent | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/iad-mrs-rtt) | **86.5 ms** | Good | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/iad-mow-rtt) | **112.8 ms** | Good | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/iad-par-rtt) | **76.1 ms** | Excellent | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/iad-lax-rtt) | **60.7 ms** | Excellent | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/iad-mia-rtt) | **27.4 ms** | Ultra-Low | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/iad-nyc-rtt) | **6 ms** | Ultra-Low | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/iad-sea-rtt) | **62.3 ms** | Excellent | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/iad-gru-rtt) | **101.4 ms** | Good | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/iad-hkg-rtt) | **187.2 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/iad-mel-rtt) | **203.9 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/iad-sin-rtt) | **211.5 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/iad-syd-rtt) | **193.6 ms** | Fair | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/iad-tpe-rtt) | **172.3 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/iad-tyo-rtt) | **141.9 ms** | Good | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/iad-jnb-rtt) | **228.3 ms** | Fair | **🇺🇸 Los Angeles (LAX) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/lax-ams-rtt) | **132.1 ms** | Good | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/lax-ber-rtt) | **139.3 ms** | Good | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/lax-fra-rtt) | **142.3 ms** | Good | | [🇬🇧 London (LON)](/docs/network/latency/pairs/lax-lon-rtt) | **129.2 ms** | Good | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/lax-mrs-rtt) | **143.9 ms** | Good | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/lax-mow-rtt) | **177 ms** | Fair | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/lax-par-rtt) | **135.9 ms** | Good | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/lax-iad-rtt) | **60.4 ms** | Excellent | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/lax-mia-rtt) | **57.3 ms** | Excellent | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/lax-nyc-rtt) | **57.9 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/lax-sea-rtt) | **26.9 ms** | Ultra-Low | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/lax-gru-rtt) | **131.3 ms** | Good | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/lax-hkg-rtt) | **146.5 ms** | Good | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/lax-mel-rtt) | **148.2 ms** | Good | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/lax-sin-rtt) | **167.7 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/lax-syd-rtt) | **137.6 ms** | Good | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/lax-tpe-rtt) | **132.9 ms** | Good | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/lax-tyo-rtt) | **101.2 ms** | Good | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/lax-jnb-rtt) | **287.2 ms** | High | **🇺🇸 Miami (MIA) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/mia-ams-rtt) | **106 ms** | Good | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/mia-ber-rtt) | **117.3 ms** | Good | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/mia-fra-rtt) | **112.2 ms** | Good | | [🇬🇧 London (LON)](/docs/network/latency/pairs/mia-lon-rtt) | **101.8 ms** | Good | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/mia-mrs-rtt) | **113.7 ms** | Good | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/mia-mow-rtt) | **145.5 ms** | Good | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/mia-par-rtt) | **106.2 ms** | Good | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/mia-iad-rtt) | **27.3 ms** | Ultra-Low | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/mia-lax-rtt) | **56.8 ms** | Excellent | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/mia-nyc-rtt) | **33.3 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/mia-sea-rtt) | **81.9 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/mia-gru-rtt) | **128.7 ms** | Good | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/mia-hkg-rtt) | **199.5 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/mia-mel-rtt) | **200.7 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/mia-sin-rtt) | **223.1 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mia-syd-rtt) | **191.5 ms** | Fair | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/mia-tpe-rtt) | **185.1 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/mia-tyo-rtt) | **156.3 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/mia-jnb-rtt) | **259.8 ms** | High | **🇺🇸 New York (NYC) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/nyc-ams-rtt) | **68.7 ms** | Excellent | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/nyc-ber-rtt) | **78.8 ms** | Excellent | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/nyc-fra-rtt) | **73.9 ms** | Excellent | | [🇬🇧 London (LON)](/docs/network/latency/pairs/nyc-lon-rtt) | **63.5 ms** | Excellent | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/nyc-mrs-rtt) | **80.2 ms** | Good | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/nyc-mow-rtt) | **107 ms** | Good | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/nyc-par-rtt) | **68.9 ms** | Excellent | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/nyc-iad-rtt) | **6 ms** | Ultra-Low | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/nyc-lax-rtt) | **58.9 ms** | Excellent | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/nyc-mia-rtt) | **32.9 ms** | Excellent | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/nyc-sea-rtt) | **58.7 ms** | Excellent | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/nyc-gru-rtt) | **106.9 ms** | Good | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/nyc-hkg-rtt) | **187.1 ms** | Fair | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/nyc-mel-rtt) | **205.1 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/nyc-sin-rtt) | **208.7 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/nyc-syd-rtt) | **192.6 ms** | Fair | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/nyc-tpe-rtt) | **173.4 ms** | Fair | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/nyc-tyo-rtt) | **143.1 ms** | Good | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/nyc-jnb-rtt) | **221.5 ms** | Fair | **🇺🇸 Seattle (SEA) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/sea-ams-rtt) | **128.6 ms** | Good | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/sea-ber-rtt) | **140.9 ms** | Good | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/sea-fra-rtt) | **133.2 ms** | Good | | [🇬🇧 London (LON)](/docs/network/latency/pairs/sea-lon-rtt) | **124.1 ms** | Good | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/sea-mrs-rtt) | **141.2 ms** | Good | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/sea-mow-rtt) | **164.6 ms** | Fair | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/sea-par-rtt) | **129.2 ms** | Good | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/sea-iad-rtt) | **61.5 ms** | Excellent | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-rtt) | **25.9 ms** | Ultra-Low | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/sea-mia-rtt) | **81.7 ms** | Good | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/sea-nyc-rtt) | **59.5 ms** | Excellent | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/sea-gru-rtt) | **155.7 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/sea-hkg-rtt) | **130.4 ms** | Good | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/sea-mel-rtt) | **170.1 ms** | Fair | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/sea-sin-rtt) | **151.1 ms** | Fair | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/sea-syd-rtt) | **161.3 ms** | Fair | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/sea-tpe-rtt) | **114.7 ms** | Good | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/sea-tyo-rtt) | **85 ms** | Good | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/sea-jnb-rtt) | **282.1 ms** | High | ### Routes from South America (19) **🇧🇷 São Paulo (GRU) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/gru-ams-rtt) | **180 ms** | Fair | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/gru-ber-rtt) | **191.3 ms** | Fair | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/gru-fra-rtt) | **186.2 ms** | Fair | | [🇬🇧 London (LON)](/docs/network/latency/pairs/gru-lon-rtt) | **175.8 ms** | Fair | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/gru-mrs-rtt) | **187.7 ms** | Fair | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/gru-mow-rtt) | **219.5 ms** | Fair | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/gru-par-rtt) | **180.2 ms** | Fair | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/gru-iad-rtt) | **128 ms** | Good | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/gru-lax-rtt) | **130.8 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/gru-mia-rtt) | **74 ms** | Excellent | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/gru-nyc-rtt) | **122 ms** | Good | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/gru-sea-rtt) | **155.9 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/gru-hkg-rtt) | **273.5 ms** | High | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/gru-mel-rtt) | **274.7 ms** | High | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/gru-sin-rtt) | **297.1 ms** | High | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/gru-syd-rtt) | **265.5 ms** | High | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/gru-tpe-rtt) | **259.1 ms** | High | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/gru-tyo-rtt) | **230.3 ms** | Fair | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/gru-jnb-rtt) | **333.8 ms** | High | ### Routes from Asia Pacific (114) **🇭🇰 Hong Kong (HKG) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/hkg-ams-rtt) | **154.4 ms** | Fair | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/hkg-ber-rtt) | **145.1 ms** | Good | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/hkg-fra-rtt) | **150.7 ms** | Fair | | [🇬🇧 London (LON)](/docs/network/latency/pairs/hkg-lon-rtt) | **158.7 ms** | Fair | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/hkg-mrs-rtt) | **165.4 ms** | Fair | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/hkg-mow-rtt) | **118.2 ms** | Good | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/hkg-par-rtt) | **159.4 ms** | Fair | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/hkg-iad-rtt) | **186.2 ms** | Fair | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/hkg-lax-rtt) | **145 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/hkg-mia-rtt) | **201.1 ms** | Fair | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/hkg-nyc-rtt) | **184.7 ms** | Fair | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/hkg-sea-rtt) | **131.6 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/hkg-gru-rtt) | **287.6 ms** | High | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/hkg-mel-rtt) | **138.4 ms** | Good | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/hkg-sin-rtt) | **31.5 ms** | Excellent | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/hkg-syd-rtt) | **137.2 ms** | Good | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt) | **14.7 ms** | Ultra-Low | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/hkg-tyo-rtt) | **44.9 ms** | Excellent | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/hkg-jnb-rtt) | **316.7 ms** | High | **🇦🇺 Melbourne (MEL) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/mel-ams-rtt) | **252.8 ms** | High | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/mel-ber-rtt) | **254.7 ms** | High | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/mel-fra-rtt) | **248.6 ms** | Fair | | [🇬🇧 London (LON)](/docs/network/latency/pairs/mel-lon-rtt) | **252 ms** | High | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/mel-mrs-rtt) | **233.5 ms** | Fair | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/mel-mow-rtt) | **236.1 ms** | Fair | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/mel-par-rtt) | **246.5 ms** | Fair | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/mel-iad-rtt) | **203.9 ms** | Fair | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/mel-lax-rtt) | **148.4 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/mel-mia-rtt) | **201 ms** | Fair | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/mel-nyc-rtt) | **204.2 ms** | Fair | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/mel-sea-rtt) | **172.1 ms** | Fair | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/mel-gru-rtt) | **305.3 ms** | High | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/mel-hkg-rtt) | **138.5 ms** | Good | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/mel-sin-rtt) | **88.4 ms** | Good | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mel-syd-rtt) | **9.8 ms** | Ultra-Low | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/mel-tpe-rtt) | **143.2 ms** | Good | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/mel-tyo-rtt) | **112 ms** | Good | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/mel-jnb-rtt) | **405.5 ms** | High | **🇸🇬 Singapore (SIN) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/sin-ams-rtt) | **155.8 ms** | Fair | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/sin-ber-rtt) | **160.3 ms** | Fair | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/sin-fra-rtt) | **151.6 ms** | Fair | | [🇬🇧 London (LON)](/docs/network/latency/pairs/sin-lon-rtt) | **155.4 ms** | Fair | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/sin-mrs-rtt) | **140.6 ms** | Good | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/sin-mow-rtt) | **147.7 ms** | Good | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/sin-par-rtt) | **151.4 ms** | Fair | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/sin-iad-rtt) | **210 ms** | Fair | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/sin-lax-rtt) | **168.2 ms** | Fair | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/sin-mia-rtt) | **221.7 ms** | Fair | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/sin-nyc-rtt) | **209.3 ms** | Fair | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/sin-sea-rtt) | **151.5 ms** | Fair | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/sin-gru-rtt) | **311.4 ms** | High | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/sin-hkg-rtt) | **30.8 ms** | Excellent | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/sin-mel-rtt) | **88.6 ms** | Good | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/sin-syd-rtt) | **94.5 ms** | Good | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/sin-tpe-rtt) | **45.8 ms** | Excellent | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/sin-tyo-rtt) | **68.9 ms** | Excellent | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/sin-jnb-rtt) | **312.6 ms** | High | **🇦🇺 Sydney (SYD) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/syd-ams-rtt) | **258.9 ms** | High | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/syd-ber-rtt) | **260.5 ms** | High | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/syd-fra-rtt) | **254.4 ms** | High | | [🇬🇧 London (LON)](/docs/network/latency/pairs/syd-lon-rtt) | **256.5 ms** | High | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/syd-mrs-rtt) | **240.5 ms** | Fair | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/syd-mow-rtt) | **242.2 ms** | Fair | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/syd-par-rtt) | **250.3 ms** | High | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/syd-iad-rtt) | **195.3 ms** | Fair | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/syd-lax-rtt) | **136.5 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/syd-mia-rtt) | **191.5 ms** | Fair | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/syd-nyc-rtt) | **191.9 ms** | Fair | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/syd-sea-rtt) | **161.9 ms** | Fair | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/syd-gru-rtt) | **296.7 ms** | High | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/syd-hkg-rtt) | **135.7 ms** | Good | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/syd-mel-rtt) | **9.8 ms** | Ultra-Low | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/syd-sin-rtt) | **94.5 ms** | Good | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/syd-tpe-rtt) | **131.7 ms** | Good | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/syd-tyo-rtt) | **101.3 ms** | Good | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/syd-jnb-rtt) | **412.5 ms** | High | **🇹🇼 Taipei (TPE) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/tpe-ams-rtt) | **166.5 ms** | Fair | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/tpe-ber-rtt) | **158.6 ms** | Fair | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/tpe-fra-rtt) | **166 ms** | Fair | | [🇬🇧 London (LON)](/docs/network/latency/pairs/tpe-lon-rtt) | **173 ms** | Fair | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/tpe-mrs-rtt) | **179.5 ms** | Fair | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/tpe-mow-rtt) | **132.7 ms** | Good | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/tpe-par-rtt) | **173.8 ms** | Fair | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/tpe-iad-rtt) | **171.6 ms** | Fair | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/tpe-lax-rtt) | **132 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/tpe-mia-rtt) | **185.7 ms** | Fair | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/tpe-nyc-rtt) | **174.2 ms** | Fair | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/tpe-sea-rtt) | **115.8 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/tpe-gru-rtt) | **273 ms** | High | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt) | **15.5 ms** | Ultra-Low | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/tpe-mel-rtt) | **142 ms** | Good | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/tpe-sin-rtt) | **44.3 ms** | Excellent | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/tpe-syd-rtt) | **133.2 ms** | Good | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/tpe-tyo-rtt) | **31.9 ms** | Excellent | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/tpe-jnb-rtt) | **331 ms** | High | **🇯🇵 Tokyo (TYO) — 19 outbound routes** | Destination | RTT | Tier | | ------------------------------------------------------------------ | -----------: | --------- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/tyo-ams-rtt) | **197.4 ms** | Fair | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/tyo-ber-rtt) | **186.1 ms** | Fair | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/tyo-fra-rtt) | **193.2 ms** | Fair | | [🇬🇧 London (LON)](/docs/network/latency/pairs/tyo-lon-rtt) | **202.7 ms** | Fair | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/tyo-mrs-rtt) | **205.6 ms** | Fair | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/tyo-mow-rtt) | **161.7 ms** | Fair | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/tyo-par-rtt) | **204.8 ms** | Fair | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/tyo-iad-rtt) | **142.9 ms** | Good | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/tyo-lax-rtt) | **101.2 ms** | Good | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/tyo-mia-rtt) | **156.5 ms** | Fair | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/tyo-nyc-rtt) | **144.6 ms** | Good | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/tyo-sea-rtt) | **84.8 ms** | Good | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/tyo-gru-rtt) | **230.5 ms** | Fair | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/tyo-hkg-rtt) | **44.8 ms** | Excellent | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/tyo-mel-rtt) | **113.9 ms** | Good | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/tyo-sin-rtt) | **69.4 ms** | Excellent | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/tyo-syd-rtt) | **101.9 ms** | Good | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/tyo-tpe-rtt) | **32.3 ms** | Excellent | | [🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/tyo-jnb-rtt) | **359.2 ms** | High | ### Routes from Africa (19) **🇿🇦 Johannesburg (JNB) — 19 outbound routes** | Destination | RTT | Tier | | ----------------------------------------------------------------- | -----------: | ---- | | [🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/jnb-ams-rtt) | **163.2 ms** | Fair | | [🇩🇪 Berlin (BER)](/docs/network/latency/pairs/jnb-ber-rtt) | **172.1 ms** | Fair | | [🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/jnb-fra-rtt) | **166 ms** | Fair | | [🇬🇧 London (LON)](/docs/network/latency/pairs/jnb-lon-rtt) | **158 ms** | Fair | | [🇫🇷 Marseille (MRS)](/docs/network/latency/pairs/jnb-mrs-rtt) | **172 ms** | Fair | | [🇷🇺 Moscow (MOW)](/docs/network/latency/pairs/jnb-mow-rtt) | **200.7 ms** | Fair | | [🇫🇷 Paris (PAR)](/docs/network/latency/pairs/jnb-par-rtt) | **164.4 ms** | Fair | | [🇺🇸 Ashburn (IAD)](/docs/network/latency/pairs/jnb-iad-rtt) | **229 ms** | Fair | | [🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/jnb-lax-rtt) | **285.5 ms** | High | | [🇺🇸 Miami (MIA)](/docs/network/latency/pairs/jnb-mia-rtt) | **259.9 ms** | High | | [🇺🇸 New York (NYC)](/docs/network/latency/pairs/jnb-nyc-rtt) | **221.8 ms** | Fair | | [🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/jnb-sea-rtt) | **281.2 ms** | High | | [🇧🇷 São Paulo (GRU)](/docs/network/latency/pairs/jnb-gru-rtt) | **328.7 ms** | High | | [🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/jnb-hkg-rtt) | **318 ms** | High | | [🇦🇺 Melbourne (MEL)](/docs/network/latency/pairs/jnb-mel-rtt) | **406.2 ms** | High | | [🇸🇬 Singapore (SIN)](/docs/network/latency/pairs/jnb-sin-rtt) | **311.6 ms** | High | | [🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/jnb-syd-rtt) | **412.6 ms** | High | | [🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/jnb-tpe-rtt) | **329.8 ms** | High | | [🇯🇵 Tokyo (TYO)](/docs/network/latency/pairs/jnb-tyo-rtt) | **360.5 ms** | High | *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse by [region & corridor](/docs/network/latency/regions).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs). - **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. # Johannesburg, South Africa → Amsterdam, Netherlands RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. The Johannesburg–Amsterdam path produced a 163.2 ms average ICMP echo RTT across 50 samples at 100 ms intervals, with samples ranging from 158.68 ms to 177.43 ms and no packet loss. The 4.23 ms standard deviation and 3.46 ms jitter indicate a comparatively stable fair-latency route. For the 2026-08-16T04:07:28Z round, this route ranks second in a 19-route outbound set, and its standard deviation works out to about 2.59% of the average, below the 3.28% median ratio for the set. The 8,991.8 km great-circle distance has a line-of-sight speed-of-light floor of 59.99 ms and a fiber-floor reference of 88.05 ms. With an RTT only 1.85 times the fiber-floor reference, the route reaches 54% fiber efficiency, indicating that the measured latency leaves relatively little headroom over the physical reference. Low loss, low jitter, and a top-two outbound position make this one of the steadier long-haul measurements in the round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **163.2 ms** | | Jitter | **3.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **88.05 ms** | | Fiber Efficiency | **54%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,991.8 km** | | Vacuum RTT floor | **59.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **88.05 ms** | | Low-latency fiber material floor | **87.7 ms** | | Engineering floor (5% path allowance) | **92.47 ms** | | Research 1.33× mapped-fiber reference | **117.11 ms** | | Estimated unamplified path loss | **1888.3 dB** | | Transparent optical spans / inline amplifiers | **119 / 118** | | Published RTT inflation over fiber floor | **1.85×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **158.68 ms** | | Average RTT | **163.2 ms** | | Maximum RTT | **177.43 ms** | | Standard deviation | **4.23 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms * [Johannesburg to Berlin latency and RTT](/docs/network/latency/pairs/jnb-ber-rtt) — 172.1 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Africa → Europe)** * [Johannesburg to Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt) — 200.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-ams-rtt). - **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. # Johannesburg, South Africa → Berlin, Germany RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. The Johannesburg–Berlin ICMP echo path averaged 172.1 ms over 50 samples, with a 168.33 ms minimum, a 187.75 ms maximum, and zero packet loss. The 3.76 ms standard deviation and 2.87 ms jitter place this in the fair-latency tier with very tight sample-to-sample behavior. In the 2026-08-16T04:07:28Z round, the route ranks sixth among 19 outbound routes, and its standard deviation is about 2.18% of the average RTT, comfortably below the 3.28% median ratio for the outbound set. The physical reference is 8,836.6 km of great-circle distance, a 58.95 ms vacuum floor, and an 86.53 ms fiber floor. The observed average is 1.99 times the fiber floor, which puts the route at 50.3% fiber efficiency. That combination of moderate latency, minimal variability, and no loss gives Berlin-bound traffic a more predictable round-trip profile than many routes in the same outbound set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **172.1 ms** | | Jitter | **2.87 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **86.53 ms** | | Fiber Efficiency | **50.3%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,836.6 km** | | Vacuum RTT floor | **58.95 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **86.53 ms** | | Low-latency fiber material floor | **86.19 ms** | | Engineering floor (5% path allowance) | **90.87 ms** | | Research 1.33× mapped-fiber reference | **115.09 ms** | | Estimated unamplified path loss | **1855.7 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.99×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **168.33 ms** | | Average RTT | **172.1 ms** | | Maximum RTT | **187.75 ms** | | Standard deviation | **3.76 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Africa → Europe)** * [Johannesburg to Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt) — 200.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-ber-rtt). - **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. # Johannesburg, South Africa → Frankfurt, Germany RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Johannesburg to Frankfurt averaged 166 ms, with a minimum of 156.26 ms, a maximum of 186.26 ms and zero packet loss across all 50 samples. The standard deviation was 7.97 ms and jitter was 7.73 ms, so the route showed a fairly consistent profile despite a roughly 30 ms range between its fastest and slowest replies. That standard deviation is about 4.8% of the average, above the 3.28% median stdev-to-average ratio seen across the 19 outbound routes in the same measurement set. This route ranked 4th among those 19 routes. Its 166 ms average is 1.96 times the theoretical fiber-floor minimum for the 8,666.9 km great-circle distance, placing fiber efficiency at 51.1%; in practical terms, the path remains well above the optical floor, but the zero-loss sample and modest jitter make the route a stable reference for Johannesburg-to-Frankfurt connectivity. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **166 ms** | | Jitter | **7.73 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **84.87 ms** | | Fiber Efficiency | **51.1%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,666.9 km** | | Vacuum RTT floor | **57.82 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **84.87 ms** | | Low-latency fiber material floor | **84.53 ms** | | Engineering floor (5% path allowance) | **89.13 ms** | | Research 1.33× mapped-fiber reference | **112.88 ms** | | Estimated unamplified path loss | **1820.1 dB** | | Transparent optical spans / inline amplifiers | **114 / 113** | | Published RTT inflation over fiber floor | **1.96×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **156.26 ms** | | Average RTT | **166 ms** | | Maximum RTT | **186.26 ms** | | Standard deviation | **7.97 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms * [Johannesburg to Berlin latency and RTT](/docs/network/latency/pairs/jnb-ber-rtt) — 172.1 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Africa → Europe)** * [Johannesburg to Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt) — 200.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-fra-rtt). - **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. # Johannesburg, South Africa → São Paulo, Brazil RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Johannesburg, South Africa to São Paulo, Brazil produced an average RTT of 328.7 ms, with a minimum of 319.02 ms and a maximum of 366.86 ms. Packet loss was zero percent across the entire sample. The straight-line distance between Johannesburg and São Paulo is only 7,441.9 km, giving a vacuum round-trip floor of 49.65 ms and a direct fiber floor of 72.88 ms. At 328.7 ms, the measured route is 4.51 times higher than that fiber floor and achieves just 22.2 percent fiber efficiency, indicating that the actual network path is substantially longer than the map distance suggests. Among the 19 outbound routes in this measurement set, the Johannesburg–São Paulo leg ranks 15th by average RTT, placing it in the slower tail. Its standard deviation of 9.87 ms is only about 3.00 percent of the average, however, and jitter was 7.53 ms, so the path, while slow, is very consistent. The observed variability is below the 3.28 percent median seen across the network. The practical takeaway is that 328.7 ms is not an anomaly from a few bad probes: the entire 50-sample range stays between 319.02 ms and 366.86 ms. This stable, high-latency band can be treated as the route's normal ICMP behavior for this measurement round. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **328.7 ms** | | Jitter | **7.53 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.88 ms** | | Fiber Efficiency | **22.2%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,441.9 km** | | Vacuum RTT floor | **49.65 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.88 ms** | | Low-latency fiber material floor | **72.58 ms** | | Engineering floor (5% path allowance) | **76.53 ms** | | Research 1.33× mapped-fiber reference | **96.93 ms** | | Estimated unamplified path loss | **1562.8 dB** | | Transparent optical spans / inline amplifiers | **98 / 97** | | Published RTT inflation over fiber floor | **4.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **319.02 ms** | | Average RTT | **328.7 ms** | | Maximum RTT | **366.86 ms** | | Standard deviation | **9.87 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Africa](/docs/network/latency/regions/africa) → [South America](/docs/network/latency/regions/south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Johannesburg latency and RTT](/docs/network/latency/pairs/gru-jnb-rtt) — 333.8 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-gru-rtt). - **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. # Johannesburg, South Africa → Hong Kong RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z recorded 50 ICMP echo responses from Johannesburg, South Africa to Hong Kong, Hong Kong with an average round-trip time of 318.0 ms. The minimum was 302.56 ms, the maximum was 363.62 ms, and packet loss remained at zero percent. The two cities are separated by 10,715.5 km along the great circle, which sets a vacuum floor of 71.49 ms and a direct fiber floor of 104.93 ms for a round trip. The observed 318 ms average is 3.03 times that fiber floor and corresponds to 33 percent fiber efficiency, so the route carries considerable overhead relative to the ideal straight-line path. Within the same round's set of 19 outbound routes, this leg ranks 14th by average RTT, putting it in the slower half. Its standard deviation of 12.41 ms equals about 3.90 percent of the mean, above the 3.28 percent median variability across the network; jitter of 9.12 ms confirms that probe-to-probe timing varied more than the typical route in the set. With no loss and a steady but elevated RTT envelope, the observed minimum of 302.56 ms provides a useful reference point for this corridor, while 318.0 ms remains the central baseline for Johannesburg-to-Hong Kong ICMP latency in this round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **318 ms** | | Jitter | **9.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **104.93 ms** | | Fiber Efficiency | **33%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,715.5 km** | | Vacuum RTT floor | **71.49 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **104.93 ms** | | Low-latency fiber material floor | **104.51 ms** | | Engineering floor (5% path allowance) | **110.2 ms** | | Research 1.33× mapped-fiber reference | **139.56 ms** | | Estimated unamplified path loss | **2250.3 dB** | | Transparent optical spans / inline amplifiers | **141 / 140** | | Published RTT inflation over fiber floor | **3.03×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **302.56 ms** | | Average RTT | **318 ms** | | Maximum RTT | **363.62 ms** | | Standard deviation | **12.41 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt) — 316.7 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Africa → Asia Pacific)** * [Johannesburg to Singapore latency and RTT](/docs/network/latency/pairs/jnb-sin-rtt) — 311.6 ms * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt) — 329.8 ms * [Johannesburg to Tokyo latency and RTT](/docs/network/latency/pairs/jnb-tyo-rtt) — 360.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-hkg-rtt). - **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. # Johannesburg, South Africa → Ashburn, USA RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z ICMP echo measurement round, Johannesburg to Ashburn recorded an average round-trip time of 229 ms across 50 samples at 100 ms intervals, with a minimum of 223.41 ms and a maximum of 246.68 ms. No packets were lost, and jitter measured 4.4 ms against a 5.3 ms standard deviation. The great-circle distance is 13,082 km, giving a theoretical fiber floor of 128.11 ms; the measured average was 1.79 times that floor, or about 55.9% fiber efficiency. This route was 9th in the set of 19 outbound paths, and its relative spread of roughly 2.3% of the average was below the network's median 3.28% standard-deviation-to-average ratio. Because the entire 50-sample round fell within a 23.27 ms range and the minimum-to-average gap was only 5.59 ms, the 229 ms average serves as a consistent diagnostic benchmark for Johannesburg–Ashburn in the 2026-08-16T04:07:28Z round. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **229 ms** | | Jitter | **4.4 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.11 ms** | | Fiber Efficiency | **55.9%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **13,082 km** | | Vacuum RTT floor | **87.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.11 ms** | | Low-latency fiber material floor | **127.59 ms** | | Engineering floor (5% path allowance) | **134.53 ms** | | Research 1.33× mapped-fiber reference | **170.38 ms** | | Estimated unamplified path loss | **2747.2 dB** | | Transparent optical spans / inline amplifiers | **172 / 171** | | Published RTT inflation over fiber floor | **1.79×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **223.41 ms** | | Average RTT | **229 ms** | | Maximum RTT | **246.68 ms** | | Standard deviation | **5.3 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Africa](/docs/network/latency/regions/africa) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Johannesburg latency and RTT](/docs/network/latency/pairs/iad-jnb-rtt) — 228.3 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Africa → North America)** * [Johannesburg to New York latency and RTT](/docs/network/latency/pairs/jnb-nyc-rtt) — 221.8 ms * [Johannesburg to Miami latency and RTT](/docs/network/latency/pairs/jnb-mia-rtt) — 259.9 ms * [Johannesburg to Seattle latency and RTT](/docs/network/latency/pairs/jnb-sea-rtt) — 281.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-iad-rtt). - **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. # Johannesburg, South Africa → Los Angeles, USA RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. Round 2026-08-16T04:07:28Z measured ICMP echo RTT from Johannesburg, South Africa, to Los Angeles, USA, using 50 samples at 100 ms intervals. The average RTT was 285.5 ms, with a minimum of 274.6 ms, a maximum of 308.95 ms, and zero packet loss, placing the route in the high latency tier. For a geodesic distance of 16,680.3 km, the theoretical fiber floor is 163.35 ms; the observed average sits about 1.75 times that floor, giving a fiber efficiency of 57.2%. The 8.74 ms standard deviation and 7.72 ms jitter indicate a relatively narrow spread around the average. This Johannesburg outbound route was one of 19 measured paths in the round and ranked 12th by average RTT. Its variability, at about 3.1% of the average, is slightly tighter than the network-wide median of 3.28%, and the zero-loss, 34.35 ms max-min spread makes the average a dependable baseline for this long-distance route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **285.5 ms** | | Jitter | **7.72 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **163.35 ms** | | Fiber Efficiency | **57.2%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,680.3 km** | | Vacuum RTT floor | **111.28 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **163.35 ms** | | Low-latency fiber material floor | **162.69 ms** | | Engineering floor (5% path allowance) | **171.54 ms** | | Research 1.33× mapped-fiber reference | **217.25 ms** | | Estimated unamplified path loss | **3502.9 dB** | | Transparent optical spans / inline amplifiers | **219 / 218** | | Published RTT inflation over fiber floor | **1.75×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **274.6 ms** | | Average RTT | **285.5 ms** | | Maximum RTT | **308.95 ms** | | Standard deviation | **8.74 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Africa](/docs/network/latency/regions/africa) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Johannesburg latency and RTT](/docs/network/latency/pairs/lax-jnb-rtt) — 287.2 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Africa → North America)** * [Johannesburg to New York latency and RTT](/docs/network/latency/pairs/jnb-nyc-rtt) — 221.8 ms * [Johannesburg to Ashburn latency and RTT](/docs/network/latency/pairs/jnb-iad-rtt) — 229 ms * [Johannesburg to Miami latency and RTT](/docs/network/latency/pairs/jnb-mia-rtt) — 259.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-lax-rtt). - **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. # Johannesburg, South Africa → London, UK RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Johannesburg to London averaged 158 ms, with a minimum of 151.59 ms, a maximum of 170.89 ms and zero packet loss across all 50 samples. This route ranked 1st among the 19 outbound routes in the same measurement set. Its standard deviation of 4.48 ms is only 2.8% of the average, below the 3.28% median stdev-to-average ratio across that group, and jitter was 3.47 ms. The 158 ms average is 1.78 times the theoretical fiber-floor minimum for the 9,039.3 km great-circle distance, corresponding to 56.0% fiber efficiency. With a narrow 19.3 ms min-to-max range and no loss, the route is notably stable in this round and offers a strong baseline for Johannesburg-to-London RTT. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **158 ms** | | Jitter | **3.47 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **88.52 ms** | | Fiber Efficiency | **56%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,039.3 km** | | Vacuum RTT floor | **60.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **88.52 ms** | | Low-latency fiber material floor | **88.16 ms** | | Engineering floor (5% path allowance) | **92.96 ms** | | Research 1.33× mapped-fiber reference | **117.73 ms** | | Estimated unamplified path loss | **1898.3 dB** | | Transparent optical spans / inline amplifiers | **119 / 118** | | Published RTT inflation over fiber floor | **1.78×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **151.59 ms** | | Average RTT | **158 ms** | | Maximum RTT | **170.89 ms** | | Standard deviation | **4.48 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms * [Johannesburg to Berlin latency and RTT](/docs/network/latency/pairs/jnb-ber-rtt) — 172.1 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Africa → Europe)** * [Johannesburg to Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt) — 200.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-lon-rtt). - **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. # Johannesburg, South Africa → Melbourne, Australia RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, Johannesburg-to-Melbourne ICMP echo requests averaged 406.2 ms over 50 samples, with a minimum of 391.17 ms, a maximum of 483.64 ms and zero packet loss. The 16.4 ms standard deviation and 10.85 ms jitter put variation at about 4.0 percent of the average, a modest spread for a route whose minimum and maximum differ by roughly 92 ms. This path was 18th of the 19 routes measured in the same round, meaning only one route in the set had a higher average latency. The network median standard-deviation-to-average ratio was 3.28 percent, so this route's variability sits slightly above the typical route while remaining within the same general range. The 10,347 km great-circle distance corresponds to a fiber-floor RTT of approximately 101 ms, making the measured 406.2 ms average a 4.01x inflation over that ideal floor. With fiber efficiency at 24.9 percent, the route is best understood as a long-haul intercontinental path where substantial overhead beyond pure propagation is expected. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **406.2 ms** | | Jitter | **10.85 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **101.33 ms** | | Fiber Efficiency | **24.9%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **10,347 km** | | Vacuum RTT floor | **69.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **101.33 ms** | | Low-latency fiber material floor | **100.92 ms** | | Engineering floor (5% path allowance) | **106.41 ms** | | Research 1.33× mapped-fiber reference | **134.76 ms** | | Estimated unamplified path loss | **2172.9 dB** | | Transparent optical spans / inline amplifiers | **136 / 135** | | Published RTT inflation over fiber floor | **4.01×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **391.17 ms** | | Average RTT | **406.2 ms** | | Maximum RTT | **483.64 ms** | | Standard deviation | **16.4 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Johannesburg latency and RTT](/docs/network/latency/pairs/mel-jnb-rtt) — 405.5 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Africa → Asia Pacific)** * [Johannesburg to Singapore latency and RTT](/docs/network/latency/pairs/jnb-sin-rtt) — 311.6 ms * [Johannesburg to Hong Kong latency and RTT](/docs/network/latency/pairs/jnb-hkg-rtt) — 318 ms * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt) — 329.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-mel-rtt). - **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. # Johannesburg, South Africa → Miami, USA RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. Round 2026-08-16T04:07:28Z recorded ICMP echo RTT from Johannesburg, South Africa, to Miami, USA, across 50 samples. The average RTT was 259.9 ms, with a tight range from 252.44 ms to 275.29 ms and no packet loss, placing it in the high latency tier. At a geodesic distance of 12,945.8 km, the vacuum floor is 86.36 ms and the fiber floor is 126.78 ms. The measured average is about 2.05 times the fiber floor, corresponding to a fiber efficiency of 48.8%, with a standard deviation of 5.02 ms and jitter of 4.08 ms. This was one of 19 outbound routes from Johannesburg in the round, ranked 10th by average RTT. Variability around 1.9% of the average is well below the network-wide median of 3.28%, and a 22.85 ms maximum-minimum spread shows a stable RTT distribution on this path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **259.9 ms** | | Jitter | **4.08 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **126.78 ms** | | Fiber Efficiency | **48.8%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,945.8 km** | | Vacuum RTT floor | **86.36 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **126.78 ms** | | Low-latency fiber material floor | **126.27 ms** | | Engineering floor (5% path allowance) | **133.13 ms** | | Research 1.33× mapped-fiber reference | **168.61 ms** | | Estimated unamplified path loss | **2718.6 dB** | | Transparent optical spans / inline amplifiers | **170 / 169** | | Published RTT inflation over fiber floor | **2.05×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **252.44 ms** | | Average RTT | **259.9 ms** | | Maximum RTT | **275.29 ms** | | Standard deviation | **5.02 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Africa](/docs/network/latency/regions/africa) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Johannesburg latency and RTT](/docs/network/latency/pairs/mia-jnb-rtt) — 259.8 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Africa → North America)** * [Johannesburg to New York latency and RTT](/docs/network/latency/pairs/jnb-nyc-rtt) — 221.8 ms * [Johannesburg to Ashburn latency and RTT](/docs/network/latency/pairs/jnb-iad-rtt) — 229 ms * [Johannesburg to Seattle latency and RTT](/docs/network/latency/pairs/jnb-sea-rtt) — 281.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-mia-rtt). - **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. # Johannesburg, South Africa → Moscow, Russia RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z ICMP echo measurement round, Johannesburg to Moscow produced an average round-trip time of 200.7 ms over 50 samples at 100 ms intervals, with a minimum of 196.07 ms, a maximum of 218.52 ms, and zero packet loss. Across the 9,125.7 km geodesic separation, the measured average was 2.25 times the 89.37 ms fiber floor, putting the route at about 44.5% fiber efficiency. It was 7th in the set of 19 outbound paths, and its 4.34 ms standard deviation was only about 2.2% of the average, below the network's median 3.28% standard-deviation-to-average ratio. The 50-sample window stayed within a 22.45 ms range, so the 200.7 ms average is a stable reference point for this Johannesburg–Moscow route in the 2026-08-16T04:07:28Z round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **200.7 ms** | | Jitter | **4.03 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.37 ms** | | Fiber Efficiency | **44.5%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,125.7 km** | | Vacuum RTT floor | **60.88 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.37 ms** | | Low-latency fiber material floor | **89.01 ms** | | Engineering floor (5% path allowance) | **93.85 ms** | | Research 1.33× mapped-fiber reference | **118.86 ms** | | Estimated unamplified path loss | **1916.4 dB** | | Transparent optical spans / inline amplifiers | **120 / 119** | | Published RTT inflation over fiber floor | **2.25×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **196.07 ms** | | Average RTT | **200.7 ms** | | Maximum RTT | **218.52 ms** | | Standard deviation | **4.34 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Johannesburg latency and RTT](/docs/network/latency/pairs/mow-jnb-rtt) — 201.9 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Africa → Europe)** * [Johannesburg to Berlin latency and RTT](/docs/network/latency/pairs/jnb-ber-rtt) — 172.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-mow-rtt). - **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. # Johannesburg, South Africa → Marseille, France RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Johannesburg to Marseille averaged 172 ms, with a minimum of 168.24 ms, a maximum of 182.06 ms and zero packet loss across all 50 samples. This route ranked 5th among the 19 outbound routes in the same measurement set. Its standard deviation of 3.29 ms is only 1.9% of the average, well below the 3.28% median stdev-to-average ratio across that group, and jitter was 2.46 ms. The low variation is the standout feature: the min-to-max range is just 13.82 ms, and the 172 ms average sits 2.19 times above the theoretical fiber-floor minimum for the 8,037.1 km great-circle distance, or 45.8% fiber efficiency. That combination of a moderate average with a very tight spread is a useful route-specific signal for Johannesburg-to-Marseille measurements. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **172 ms** | | Jitter | **2.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **78.71 ms** | | Fiber Efficiency | **45.8%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,037.1 km** | | Vacuum RTT floor | **53.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **78.71 ms** | | Low-latency fiber material floor | **78.39 ms** | | Engineering floor (5% path allowance) | **82.65 ms** | | Research 1.33× mapped-fiber reference | **104.68 ms** | | Estimated unamplified path loss | **1687.8 dB** | | Transparent optical spans / inline amplifiers | **106 / 105** | | Published RTT inflation over fiber floor | **2.19×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **168.24 ms** | | Average RTT | **172 ms** | | Maximum RTT | **182.06 ms** | | Standard deviation | **3.29 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt) — 198.5 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Berlin latency and RTT](/docs/network/latency/pairs/jnb-ber-rtt) — 172.1 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Africa → Europe)** * [Johannesburg to Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt) — 200.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-mrs-rtt). - **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. # Johannesburg, South Africa → New York, USA RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. Round 2026-08-16T04:07:28Z captured ICMP echo RTT from Johannesburg, South Africa, to New York, USA, with 50 samples. Average RTT was 221.8 ms; the minimum was 213.14 ms and the maximum 261.72 ms, with zero packet loss, and the route was classified in the fair latency tier. The geodesic distance is 12,832.9 km, giving a fiber floor of 125.67 ms. The measured average is about 1.76 times that floor, corresponding to a fiber efficiency of 56.7%, and the standard deviation and jitter are 8.43 ms and 6.44 ms, respectively. This was one of 19 outbound routes from Johannesburg in the round, ranked 8th by average RTT. Variability at about 3.8% of the average is above the network-wide median of 3.28%, and the 48.58 ms gap between minimum and maximum suggests peak RTT values deserve attention on this route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **221.8 ms** | | Jitter | **6.44 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **125.67 ms** | | Fiber Efficiency | **56.7%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,832.9 km** | | Vacuum RTT floor | **85.61 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **125.67 ms** | | Low-latency fiber material floor | **125.16 ms** | | Engineering floor (5% path allowance) | **131.97 ms** | | Research 1.33× mapped-fiber reference | **167.14 ms** | | Estimated unamplified path loss | **2694.9 dB** | | Transparent optical spans / inline amplifiers | **169 / 168** | | Published RTT inflation over fiber floor | **1.76×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **213.14 ms** | | Average RTT | **221.8 ms** | | Maximum RTT | **261.72 ms** | | Standard deviation | **8.43 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Africa](/docs/network/latency/regions/africa) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Johannesburg latency and RTT](/docs/network/latency/pairs/nyc-jnb-rtt) — 221.5 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Africa → North America)** * [Johannesburg to Ashburn latency and RTT](/docs/network/latency/pairs/jnb-iad-rtt) — 229 ms * [Johannesburg to Miami latency and RTT](/docs/network/latency/pairs/jnb-mia-rtt) — 259.9 ms * [Johannesburg to Seattle latency and RTT](/docs/network/latency/pairs/jnb-sea-rtt) — 281.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-nyc-rtt). - **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. # Johannesburg, South Africa → Paris, France RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z ICMP echo measurement round, Johannesburg to Paris averaged 164.4 ms over 50 samples sent at 100 ms intervals, with a minimum of 158.64 ms and a maximum of 177.46 ms. All samples returned, so packet loss was 0%, and the 4.15 ms standard deviation produced 4.24 ms jitter. The geodesic distance between the two cities is 8,697.3 km, and the theoretical fiber floor is 85.17 ms; the measured average was 1.93 times that floor, an efficiency of 51.8%. This route was 3rd in the set of 19 outbound paths, and its relative variability of about 2.5% of the average remained tighter than the network's median 3.28% standard-deviation-to-average ratio. Notably, the 18.82 ms spread between minimum and maximum is small for an 8,697 km route, making the 164.4 ms average a reliable diagnostic reference for this pair in the 2026-08-16T04:07:28Z round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **164.4 ms** | | Jitter | **4.24 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.17 ms** | | Fiber Efficiency | **51.8%** | | Latency Tier | Fair | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,697.3 km** | | Vacuum RTT floor | **58.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.17 ms** | | Low-latency fiber material floor | **84.83 ms** | | Engineering floor (5% path allowance) | **89.44 ms** | | Research 1.33× mapped-fiber reference | **113.28 ms** | | Estimated unamplified path loss | **1826.4 dB** | | Transparent optical spans / inline amplifiers | **115 / 114** | | Published RTT inflation over fiber floor | **1.93×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **158.64 ms** | | Average RTT | **164.4 ms** | | Maximum RTT | **177.46 ms** | | Standard deviation | **4.15 ms** | | Stdev / average | **2.5%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms * [Johannesburg to Berlin latency and RTT](/docs/network/latency/pairs/jnb-ber-rtt) — 172.1 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Africa → Europe)** * [Johannesburg to Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt) — 200.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-par-rtt). - **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. # Johannesburg, South Africa → Seattle, USA RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In measurement round 2026-08-16T04:07:28Z, 50 ICMP echo requests were sent from Johannesburg, South Africa to Seattle, USA at 100 ms intervals. The average round-trip time was 281.2 ms, with a minimum of 267.91 ms and a maximum of 315.6 ms, and all 50 probes were returned, so packet loss was zero percent. The great-circle distance between the two cities is 16,502.7 km. A round trip at the vacuum speed of light would need 110.09 ms, while a theoretical direct fiber route would need at least 161.61 ms. The measured average is 1.74 times that fiber floor, a fiber efficiency of 57.5 percent, which shows meaningful routing overhead for an intercontinental route. Across the 19 outbound routes measured in this round, this leg ranks 11th by average RTT, placing it near the midpoint of the set. Its 9.73 ms standard deviation is about 3.46 percent of the mean, close to the 3.28 percent median variability seen across the network, and jitter was 9.21 ms. The route is therefore stable and loss-free even though its absolute latency is high. For planning purposes, the realistic ICMP RTT envelope for Johannesburg to Seattle in this round is 267.91 ms to 315.6 ms, with 281.2 ms as a reliable baseline near the center of that range. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **281.2 ms** | | Jitter | **9.21 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **161.61 ms** | | Fiber Efficiency | **57.5%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,502.7 km** | | Vacuum RTT floor | **110.09 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **161.61 ms** | | Low-latency fiber material floor | **160.96 ms** | | Engineering floor (5% path allowance) | **169.71 ms** | | Research 1.33× mapped-fiber reference | **214.94 ms** | | Estimated unamplified path loss | **3465.6 dB** | | Transparent optical spans / inline amplifiers | **217 / 216** | | Published RTT inflation over fiber floor | **1.74×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **267.91 ms** | | Average RTT | **281.2 ms** | | Maximum RTT | **315.6 ms** | | Standard deviation | **9.73 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Africa](/docs/network/latency/regions/africa) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Johannesburg latency and RTT](/docs/network/latency/pairs/sea-jnb-rtt) — 282.1 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Africa → North America)** * [Johannesburg to New York latency and RTT](/docs/network/latency/pairs/jnb-nyc-rtt) — 221.8 ms * [Johannesburg to Ashburn latency and RTT](/docs/network/latency/pairs/jnb-iad-rtt) — 229 ms * [Johannesburg to Miami latency and RTT](/docs/network/latency/pairs/jnb-mia-rtt) — 259.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-sea-rtt). - **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. # Johannesburg, South Africa → Singapore RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo requests between Johannesburg and Singapore in the 2026-08-16T04:07:28Z round returned an average RTT of 311.6 ms, with a minimum of 301.09 ms and a maximum of 347.05 ms over 50 samples. Zero packets were lost, and the 9.83 ms standard deviation with 7.03 ms jitter indicates a stable but inherently long-haul path. This route was 13th in latency among the 19 routes tracked in the same round, putting it just past the midpoint of the set. Its standard-deviation-to-average ratio is about 3.2 percent, slightly below the 3.28 percent median across the network's measured routes, so the delay is mostly steady-state rather than bursty variation. The great-circle distance of 8,664.2 km implies a vacuum RTT of 57.8 ms and a fiber-floor RTT near 84.85 ms. At 311.6 ms, the route represents a 3.67x overhead over the fiber floor and 27.2 percent fiber efficiency, a useful indicator of how much of the round-trip time sits beyond the minimum possible propagation window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **311.6 ms** | | Jitter | **7.03 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **84.85 ms** | | Fiber Efficiency | **27.2%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,664.2 km** | | Vacuum RTT floor | **57.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **84.85 ms** | | Low-latency fiber material floor | **84.51 ms** | | Engineering floor (5% path allowance) | **89.1 ms** | | Research 1.33× mapped-fiber reference | **112.85 ms** | | Estimated unamplified path loss | **1819.5 dB** | | Transparent optical spans / inline amplifiers | **114 / 113** | | Published RTT inflation over fiber floor | **3.67×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **301.09 ms** | | Average RTT | **311.6 ms** | | Maximum RTT | **347.05 ms** | | Standard deviation | **9.83 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Johannesburg latency and RTT](/docs/network/latency/pairs/sin-jnb-rtt) — 312.6 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Africa → Asia Pacific)** * [Johannesburg to Hong Kong latency and RTT](/docs/network/latency/pairs/jnb-hkg-rtt) — 318 ms * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt) — 329.8 ms * [Johannesburg to Tokyo latency and RTT](/docs/network/latency/pairs/jnb-tyo-rtt) — 360.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-sin-rtt). - **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. # Johannesburg, South Africa → Sydney, Australia RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, Johannesburg-to-Sydney ICMP echo RTT averaged 412.6 ms, with a 391.98 ms minimum and a 456.66 ms maximum across 50 samples. No packets were lost, so the 16.76 ms standard deviation and 13.13 ms jitter describe a path that is consistently slow rather than intermittently unstable. Across the 19 routes captured in the same round, this path ranked 19th, meaning it carried the highest average latency of the set. Its variation is about 4.1 percent of its average, above the network's 3.28 percent median standard-deviation-to-average ratio, so it combines the slowest mean with somewhat more spread around that mean. The geodesic distance of 11,060.7 km sets a vacuum RTT of 73.79 ms and an ideal fiber RTT of 108.32 ms. The measured 412.6 ms average is therefore 3.81 times the fiber floor, or a fiber efficiency of 26.3 percent, a concise way to express how far the observed round-trip time is from the theoretical minimum for that distance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **412.6 ms** | | Jitter | **13.13 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **108.32 ms** | | Fiber Efficiency | **26.3%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,060.7 km** | | Vacuum RTT floor | **73.79 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **108.32 ms** | | Low-latency fiber material floor | **107.88 ms** | | Engineering floor (5% path allowance) | **113.75 ms** | | Research 1.33× mapped-fiber reference | **144.06 ms** | | Estimated unamplified path loss | **2322.8 dB** | | Transparent optical spans / inline amplifiers | **146 / 145** | | Published RTT inflation over fiber floor | **3.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **391.98 ms** | | Average RTT | **412.6 ms** | | Maximum RTT | **456.66 ms** | | Standard deviation | **16.76 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Johannesburg latency and RTT](/docs/network/latency/pairs/syd-jnb-rtt) — 412.5 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Africa → Asia Pacific)** * [Johannesburg to Singapore latency and RTT](/docs/network/latency/pairs/jnb-sin-rtt) — 311.6 ms * [Johannesburg to Hong Kong latency and RTT](/docs/network/latency/pairs/jnb-hkg-rtt) — 318 ms * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt) — 329.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-syd-rtt). - **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. # Johannesburg, South Africa → Taipei, Taiwan RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT measurement from Johannesburg, South Africa to Taipei, Taiwan returned a 329.8 ms average over 50 samples, with the minimum at 316.93 ms and the maximum at 358.31 ms. Packet loss was 0%, and the 9.77 ms standard deviation produced 9.42 ms jitter, putting this high-latency path on the stable side. The great-circle distance between the two cities is 11,525.4 km, for which the vacuum floor is 76.89 ms and the ideal fiber path is 112.87 ms. The measured 329.8 ms average is 2.92 times that fiber floor, so the route's fiber efficiency is 34.2% - a reminder that intercontinental RTT carries far more than the straight-line distance. In the current outbound group of 19 routes, this route is ranked 16th. Its standard deviation equals roughly 2.96% of the average, below the group's 3.28% median variability, and the narrow 41.38 ms min-to-max spread reinforces that the latency is consistent even though it is high. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **329.8 ms** | | Jitter | **9.42 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **112.87 ms** | | Fiber Efficiency | **34.2%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,525.4 km** | | Vacuum RTT floor | **76.89 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **112.87 ms** | | Low-latency fiber material floor | **112.41 ms** | | Engineering floor (5% path allowance) | **118.52 ms** | | Research 1.33× mapped-fiber reference | **150.11 ms** | | Estimated unamplified path loss | **2420.3 dB** | | Transparent optical spans / inline amplifiers | **152 / 151** | | Published RTT inflation over fiber floor | **2.92×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **316.93 ms** | | Average RTT | **329.8 ms** | | Maximum RTT | **358.31 ms** | | Standard deviation | **9.77 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Johannesburg latency and RTT](/docs/network/latency/pairs/tpe-jnb-rtt) — 331 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Africa → Asia Pacific)** * [Johannesburg to Singapore latency and RTT](/docs/network/latency/pairs/jnb-sin-rtt) — 311.6 ms * [Johannesburg to Hong Kong latency and RTT](/docs/network/latency/pairs/jnb-hkg-rtt) — 318 ms * [Johannesburg to Tokyo latency and RTT](/docs/network/latency/pairs/jnb-tyo-rtt) — 360.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-tpe-rtt). - **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. # Johannesburg, South Africa → Tokyo, Japan RTT 🇿🇦 **Johannesburg, South Africa (JNB)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT measurement from Johannesburg, South Africa to Tokyo, Japan averaged 360.5 ms across 50 samples, with the minimum at 339.64 ms and the maximum at 427.1 ms. The standard deviation was 16.2 ms, jitter was 13.91 ms, and packet loss was 0%, so the path stayed reachable throughout the sample window. The two cities are 13,537.7 km apart along a great circle, corresponding to a 90.31 ms vacuum floor and a 132.57 ms fiber floor. At 360.5 ms, the measured average is 2.72 times the fiber floor, yielding a fiber efficiency of 36.8% - a long-haul route where absolute latency is heavily influenced by distance. Within the current outbound route set of 19, this path is ranked 17th. Its standard deviation is about 4.49% of the average, above the group's 3.28% median variability, and the 87.46 ms range between the minimum and maximum shows a wider spread than the average alone suggests. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **360.5 ms** | | Jitter | **13.91 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **132.57 ms** | | Fiber Efficiency | **36.8%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,537.7 km** | | Vacuum RTT floor | **90.31 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **132.57 ms** | | Low-latency fiber material floor | **132.04 ms** | | Engineering floor (5% path allowance) | **139.22 ms** | | Research 1.33× mapped-fiber reference | **176.32 ms** | | Estimated unamplified path loss | **2842.9 dB** | | Transparent optical spans / inline amplifiers | **178 / 177** | | Published RTT inflation over fiber floor | **2.72×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **339.64 ms** | | Average RTT | **360.5 ms** | | Maximum RTT | **427.1 ms** | | Standard deviation | **16.2 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Africa](/docs/network/latency/regions/africa) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Johannesburg latency and RTT](/docs/network/latency/pairs/tyo-jnb-rtt) — 359.2 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Africa → Asia Pacific)** * [Johannesburg to Singapore latency and RTT](/docs/network/latency/pairs/jnb-sin-rtt) — 311.6 ms * [Johannesburg to Hong Kong latency and RTT](/docs/network/latency/pairs/jnb-hkg-rtt) — 318 ms * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt) — 329.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-tyo-rtt). - **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. # Los Angeles, USA → Amsterdam, Netherlands RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z echo round between Los Angeles, USA and Amsterdam, Netherlands used 50 ICMP requests and produced an average RTT of 132.1 ms, a minimum of 127 ms and a maximum of 143.89 ms, with zero packet loss. This path ranked 8th of the 19 routes in the cycle, placing it near the middle of the distribution. Its variability ratio of about 3.4 percent is only slightly above the network-wide median of 3.28 percent, and the 4.46 ms standard deviation and 3.59 ms jitter support a Good latency tier classification. The 8,960 km great-circle route has a vacuum floor of 59.77 ms and a practical fiber floor of 87.74 ms. Measured RTT is 1.51 times that floor, or 66.4 percent fiber efficiency, and with a maximum of 143.89 ms the route's latency envelope stays under 145 ms for the round. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **132.1 ms** | | Jitter | **3.59 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **87.74 ms** | | Fiber Efficiency | **66.4%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **8,960 km** | | Vacuum RTT floor | **59.77 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **87.74 ms** | | Low-latency fiber material floor | **87.39 ms** | | Engineering floor (5% path allowance) | **92.14 ms** | | Research 1.33× mapped-fiber reference | **116.7 ms** | | Estimated unamplified path loss | **1881.6 dB** | | Transparent optical spans / inline amplifiers | **118 / 117** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **127 ms** | | Average RTT | **132.1 ms** | | Maximum RTT | **143.89 ms** | | Standard deviation | **4.46 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Los Angeles latency and RTT](/docs/network/latency/pairs/ams-lax-rtt) — 133.7 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-ams-rtt). - **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. # Los Angeles, USA → Berlin, Germany RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the Los Angeles-to-Berlin path returned an average ICMP round-trip time of 139.3 ms, with a minimum of 136.33 ms and a maximum of 148.84 ms across 50 echo samples. All samples arrived with zero packet loss, and the 1.96 ms jitter kept the path close to its typical response. The 2.96 ms standard deviation is only about 2.1% of the average, a tighter spread than the 3.28% median relative spread for the 19 paths measured in the same round. Berlin's average is about 48 ms above the 91.39 ms fiber-floor estimate for the 9,331.9 km great-circle distance, an inflation of 1.52x and a fiber efficiency of 65.6%. Ranked 12th among the 19 paths by average latency, the route sits in the middle of the pack while remaining highly consistent. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **139.3 ms** | | Jitter | **1.96 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.39 ms** | | Fiber Efficiency | **65.6%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,331.9 km** | | Vacuum RTT floor | **62.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.39 ms** | | Low-latency fiber material floor | **91.02 ms** | | Engineering floor (5% path allowance) | **95.97 ms** | | Research 1.33× mapped-fiber reference | **121.54 ms** | | Estimated unamplified path loss | **1959.7 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **1.52×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **136.33 ms** | | Average RTT | **139.3 ms** | | Maximum RTT | **148.84 ms** | | Standard deviation | **2.96 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Los Angeles latency and RTT](/docs/network/latency/pairs/ber-lax-rtt) — 140.9 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-ber-rtt). - **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. # Los Angeles, USA → Frankfurt, Germany RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, the Los Angeles-to-Frankfurt path produced an average ICMP round-trip time of 142.3 ms, with a minimum of 137.29 ms and a maximum of 154.07 ms over 50 echo samples. There was no packet loss, and jitter of 3.06 ms held the path to a fairly steady response. The 3.29 ms standard deviation equals about 2.3% of the average, slightly tighter than the 3.28% median relative spread across the 19 routes in the same round. Frankfurt's average is 1.56 times the 91.31 ms fiber-floor estimate for the 9,324.5 km great-circle distance, giving a fiber efficiency of 64.2%. Among the 19 paths in this round, the route ranked 13th by average latency, with a small upward tail reflected by a maximum about 12 ms above the mean. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **142.3 ms** | | Jitter | **3.06 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.31 ms** | | Fiber Efficiency | **64.2%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,324.5 km** | | Vacuum RTT floor | **62.21 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.31 ms** | | Low-latency fiber material floor | **90.95 ms** | | Engineering floor (5% path allowance) | **95.89 ms** | | Research 1.33× mapped-fiber reference | **121.45 ms** | | Estimated unamplified path loss | **1958.1 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **1.56×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **137.29 ms** | | Average RTT | **142.3 ms** | | Maximum RTT | **154.07 ms** | | Standard deviation | **3.29 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Los Angeles latency and RTT](/docs/network/latency/pairs/fra-lax-rtt) — 141.8 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-fra-rtt). - **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. # Los Angeles, USA → São Paulo, Brazil RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round for the Los Angeles, USA to São Paulo, Brazil route returned an average ICMP echo RTT of 131.3 ms across 50 samples, with a minimum of 125.74 ms and a maximum of 147.12 ms. No packets were lost, and the 5.03 ms jitter is moderate for such a long intercontinental path. This route ranked seventh among the 19 routes measured from this origin in the same cycle. Its relative variability is about 3.8%, close to the 3.28% median across the route set; the 4.94 ms standard deviation shows the latency is reasonably consistent despite the distance. São Paulo is South America's internet capital, and Los Angeles is a primary US West Coast landing point for trans-Pacific cables. The 9,894.5 km geodesic distance has a fiber floor of 96.89 ms; the observed 131.3 ms average is only 1.36x the floor, a fiber efficiency of 73.8%, which points to a route operating close to its physical limit. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **131.3 ms** | | Jitter | **5.03 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **96.89 ms** | | Fiber Efficiency | **73.8%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,894.5 km** | | Vacuum RTT floor | **66.01 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **96.89 ms** | | Low-latency fiber material floor | **96.51 ms** | | Engineering floor (5% path allowance) | **101.75 ms** | | Research 1.33× mapped-fiber reference | **128.87 ms** | | Estimated unamplified path loss | **2077.8 dB** | | Transparent optical spans / inline amplifiers | **130 / 129** | | Published RTT inflation over fiber floor | **1.36×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **125.74 ms** | | Average RTT | **131.3 ms** | | Maximum RTT | **147.12 ms** | | Standard deviation | **4.94 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [North America to South America](/docs/network/latency/regions/north-america-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Los Angeles latency and RTT](/docs/network/latency/pairs/gru-lax-rtt) — 130.8 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-gru-rtt). - **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. # Los Angeles, USA → Hong Kong RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Los Angeles, USA to Hong Kong averaged 146.5 ms over 50 samples, with a minimum of 143.01 ms and a maximum of 158.89 ms. Zero packet loss and 2.27 ms jitter make the route steady for a trans-Pacific connection. The route ranked 15th among 19 routes measured from the same origin in this cycle. Its relative variability is around 2.2%, below the 3.28% median across the route set, so the 3.29 ms standard deviation indicates notably consistent latency even at this distance. Los Angeles is a primary US West Coast landing point for trans-Pacific cables, and Hong Kong is a dense Asia-Pacific interconnection hub. The 11,671.5 km geodesic path has a fiber floor of 114.3 ms; at 146.5 ms the route is 1.28x the floor, a fiber efficiency of 78%, showing the measured path tracks the physical geography well. Despite the lower rank, the high fiber efficiency indicates a physically efficient route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **146.5 ms** | | Jitter | **2.27 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **114.3 ms** | | Fiber Efficiency | **78%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,671.5 km** | | Vacuum RTT floor | **77.86 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **114.3 ms** | | Low-latency fiber material floor | **113.84 ms** | | Engineering floor (5% path allowance) | **120.03 ms** | | Research 1.33× mapped-fiber reference | **152.01 ms** | | Estimated unamplified path loss | **2451 dB** | | Transparent optical spans / inline amplifiers | **154 / 153** | | Published RTT inflation over fiber floor | **1.28×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **143.01 ms** | | Average RTT | **146.5 ms** | | Maximum RTT | **158.89 ms** | | Standard deviation | **3.29 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Los Angeles latency and RTT](/docs/network/latency/pairs/hkg-lax-rtt) — 145 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-hkg-rtt). - **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. # Los Angeles, USA → Ashburn, USA RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. In the measurement round 2026-08-16T04:07:28Z, ICMP echo requests sent from Los Angeles, USA toward Ashburn, USA returned an average round-trip time of 60.4 ms over 50 samples, with a minimum of 57.19 ms, a maximum of 70.55 ms, and zero packet loss. The 2.61 ms standard deviation and 2.06 ms jitter indicate a stable path, though the spread as a share of the average is higher than the 3.28% median variability for the 19-route set. This route ranked fourth in that set, and its average RTT is 1.69 times the theoretical fiber floor, corresponding to 59.3% fiber efficiency. Zero packet loss and tight jitter make this a consistent ICMP RTT profile; the gap to the fiber floor suggests the route still has theoretical headroom for lower latency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **60.4 ms** | | Jitter | **2.06 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **35.84 ms** | | Fiber Efficiency | **59.3%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,660.1 km** | | Vacuum RTT floor | **24.42 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **35.84 ms** | | Low-latency fiber material floor | **35.7 ms** | | Engineering floor (5% path allowance) | **37.64 ms** | | Research 1.33× mapped-fiber reference | **47.67 ms** | | Estimated unamplified path loss | **768.6 dB** | | Transparent optical spans / inline amplifiers | **49 / 48** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **57.19 ms** | | Average RTT | **60.4 ms** | | Maximum RTT | **70.55 ms** | | Standard deviation | **2.61 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Los Angeles to London latency and RTT](/docs/network/latency/pairs/lax-lon-rtt) — 129.2 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms * [Paris to Ashburn latency and RTT](/docs/network/latency/pairs/par-iad-rtt) — 75.5 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-iad-rtt). - **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. # Los Angeles, USA → Johannesburg, South Africa RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Los Angeles to Johannesburg averaged 287.2 ms, with a minimum of 281.06 ms and a maximum of 306.43 ms. The 5.36 ms standard deviation and 4.1 ms jitter show the path is steady even at high latency, and all 50 samples were returned without loss. For a great-circle distance of 16,680.3 km, the average is 1.76 times the 163.35 ms fiber floor, an efficiency of 56.9%. That larger inflation over the floor reflects a route where physical distance alone imposes a very high round-trip propagation baseline. This route was ranked 19th among the 19 outbound routes in the same round, with the highest average latency in that set. Its relative variability is lower than the 3.28% median standard-deviation-to-average ratio, and the zero packet loss indicates that the high RTT is not accompanied by instability. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **287.2 ms** | | Jitter | **4.1 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **163.35 ms** | | Fiber Efficiency | **56.9%** | | Latency Tier | High | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,680.3 km** | | Vacuum RTT floor | **111.28 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **163.35 ms** | | Low-latency fiber material floor | **162.69 ms** | | Engineering floor (5% path allowance) | **171.54 ms** | | Research 1.33× mapped-fiber reference | **217.25 ms** | | Estimated unamplified path loss | **3502.9 dB** | | Transparent optical spans / inline amplifiers | **219 / 218** | | Published RTT inflation over fiber floor | **1.76×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **281.06 ms** | | Average RTT | **287.2 ms** | | Maximum RTT | **306.43 ms** | | Standard deviation | **5.36 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Los Angeles latency and RTT](/docs/network/latency/pairs/jnb-lax-rtt) — 285.5 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (North America → Africa)** * [New York to Johannesburg latency and RTT](/docs/network/latency/pairs/nyc-jnb-rtt) — 221.5 ms * [Ashburn to Johannesburg latency and RTT](/docs/network/latency/pairs/iad-jnb-rtt) — 228.3 ms * [Miami to Johannesburg latency and RTT](/docs/network/latency/pairs/mia-jnb-rtt) — 259.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-jnb-rtt). - **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. # Los Angeles, USA → London, UK RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the Los Angeles-to-London path delivered an average ICMP round-trip time of 129.2 ms, with a minimum of 123.19 ms and a maximum of 146.01 ms across 50 echo samples. Packet loss was zero, though the 3.99 ms jitter and 4.9 ms standard deviation indicate a wider response spread than the 3.28% median relative spread for the 19 routes in this round; the standard deviation is about 3.8% of the average. London's average is 1.50 times the 85.95 ms fiber-floor estimate for the 8,776.7 km great-circle distance, a fiber efficiency of 66.5%. The route ranked 6th among the 19 paths by average latency, so the lower round-trip time comes with a slightly broader distribution around the central value. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **129.2 ms** | | Jitter | **3.99 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.95 ms** | | Fiber Efficiency | **66.5%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,776.7 km** | | Vacuum RTT floor | **58.55 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.95 ms** | | Low-latency fiber material floor | **85.6 ms** | | Engineering floor (5% path allowance) | **90.26 ms** | | Research 1.33× mapped-fiber reference | **114.31 ms** | | Estimated unamplified path loss | **1843.1 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **123.19 ms** | | Average RTT | **129.2 ms** | | Maximum RTT | **146.01 ms** | | Standard deviation | **4.9 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Los Angeles latency and RTT](/docs/network/latency/pairs/lon-lax-rtt) — 127.5 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-lon-rtt). - **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. # Los Angeles, USA → Melbourne, Australia RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Los Angeles to Melbourne measured an average RTT of 148.2 ms, with a minimum of 142.14 ms and a maximum of 162.19 ms. None of the 50 probes were lost, and the 5.38 ms standard deviation with 4.01 ms jitter indicates a stable path. The average is roughly 19% above the 125 ms fiber-floor estimate for the 12,764 km great-circle distance, so the reported latency is mostly distance-driven. Within the 19-route outbound set, this Los Angeles-Melbourne path holds 16th position. Its standard deviation is about 3.6% of the average, slightly above the 3.28% median across the set, meaning the path is consistent even though it sits toward the slower end. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **148.2 ms** | | Jitter | **4.01 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **125 ms** | | Fiber Efficiency | **84.3%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **12,764 km** | | Vacuum RTT floor | **85.15 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **125 ms** | | Low-latency fiber material floor | **124.49 ms** | | Engineering floor (5% path allowance) | **131.26 ms** | | Research 1.33× mapped-fiber reference | **166.24 ms** | | Estimated unamplified path loss | **2680.4 dB** | | Transparent optical spans / inline amplifiers | **168 / 167** | | Published RTT inflation over fiber floor | **1.19×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **142.14 ms** | | Average RTT | **148.2 ms** | | Maximum RTT | **162.19 ms** | | Standard deviation | **5.38 ms** | | Stdev / average | **3.6%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-mel-rtt). - **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. # Los Angeles, USA → Miami, USA RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo RTT between Los Angeles, USA and Miami, USA averaged 57.3 ms across 50 samples, with a minimum of 55.45 ms, a maximum of 63.93 ms, and no packet loss. The route's 1.73 ms standard deviation and 1.26 ms jitter keep variability below the 3.28% median for the 19-route set, and the average latency places it second in that set. Its average sits 1.55 times above the theoretical fiber floor, yielding 64.3% fiber efficiency. With zero loss and low jitter, the route presents a stable RTT profile; most of the measured delay is accounted for by the 3,764 km separation rather than by additional latency beyond the fiber floor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **57.3 ms** | | Jitter | **1.26 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **36.86 ms** | | Fiber Efficiency | **64.3%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,764.3 km** | | Vacuum RTT floor | **25.11 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **36.86 ms** | | Low-latency fiber material floor | **36.71 ms** | | Engineering floor (5% path allowance) | **38.71 ms** | | Research 1.33× mapped-fiber reference | **49.03 ms** | | Estimated unamplified path loss | **790.5 dB** | | Transparent optical spans / inline amplifiers | **50 / 49** | | Published RTT inflation over fiber floor | **1.55×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **55.45 ms** | | Average RTT | **57.3 ms** | | Maximum RTT | **63.93 ms** | | Standard deviation | **1.73 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Los Angeles to London latency and RTT](/docs/network/latency/pairs/lax-lon-rtt) — 129.2 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-mia-rtt). - **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. # Los Angeles, USA → Moscow, Russia RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo requests from Los Angeles, USA to Moscow, Russia averaged 177.0 ms over 50 samples at 100 ms intervals. The minimum RTT was 169.62 ms, the maximum was 197.78 ms, and no packets were lost. A standard deviation of 6.43 ms and jitter of 4.63 ms make this route more variable than the network median, with RTT variation equal to 3.63% of the average. It ranked 18th among 19 outbound routes in the same measurement network. On the 9,793.2 km great-circle baseline, the average RTT is 1.85 times the theoretical fiber floor, corresponding to 54.2% fiber efficiency. The lower efficiency and the Fair latency tier give network teams a clear reference for Moscow-bound traffic from the US West Coast. These ICMP values describe network-layer behavior only and are not an SLA or a predictor of end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **177 ms** | | Jitter | **4.63 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.9 ms** | | Fiber Efficiency | **54.2%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,793.2 km** | | Vacuum RTT floor | **65.33 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.9 ms** | | Low-latency fiber material floor | **95.52 ms** | | Engineering floor (5% path allowance) | **100.71 ms** | | Research 1.33× mapped-fiber reference | **127.55 ms** | | Estimated unamplified path loss | **2056.6 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.85×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **169.62 ms** | | Average RTT | **177 ms** | | Maximum RTT | **197.78 ms** | | Standard deviation | **6.43 ms** | | Stdev / average | **3.6%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Los Angeles latency and RTT](/docs/network/latency/pairs/mow-lax-rtt) — 177.7 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-mow-rtt). - **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. # Los Angeles, USA → Marseille, France RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo requests from Los Angeles, USA to Marseille, France averaged 143.9 ms across 50 samples taken at 100 ms intervals. The minimum RTT was 139.48 ms, the maximum was 166.33 ms, and packet loss was 0%. The 4.83 ms standard deviation and 3.12 ms jitter point to a largely stable path, though the 26.85 ms gap between the fastest and slowest replies is worth noting. This route ranked 14th among 19 outbound routes in the same measurement network, and its variation of 3.36% of the average is just above the network median of 3.28%. Relative to the 9,710.4 km great-circle distance, the measured RTT is 1.51 times the theoretical fiber floor, or 66.1% fiber efficiency. As a Mediterranean cable landing hub, Marseille makes this round a useful latency baseline for France-terminated intercontinental traffic; the zero-loss result and Good latency tier support using it as a network-layer reference rather than as an SLA or an end-user performance predictor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **143.9 ms** | | Jitter | **3.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.09 ms** | | Fiber Efficiency | **66.1%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,710.4 km** | | Vacuum RTT floor | **64.78 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.09 ms** | | Low-latency fiber material floor | **94.71 ms** | | Engineering floor (5% path allowance) | **99.86 ms** | | Research 1.33× mapped-fiber reference | **126.47 ms** | | Estimated unamplified path loss | **2039.2 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **139.48 ms** | | Average RTT | **143.9 ms** | | Maximum RTT | **166.33 ms** | | Standard deviation | **4.83 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Los Angeles latency and RTT](/docs/network/latency/pairs/mrs-lax-rtt) — 144.5 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-mrs-rtt). - **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. # Los Angeles, USA → New York, USA RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, the ICMP echo RTT from Los Angeles, USA to New York, USA averaged 57.9 ms over 50 samples, with a minimum of 55.78 ms, a maximum of 62.74 ms, and zero packet loss. The measured standard deviation of 1.33 ms and jitter of 1.19 ms are tight, placing this route's variability well below the 3.28% median for the 19-route set; its average latency ranks third in that set. The average RTT is 1.50 times the theoretical fiber floor, or 66.7% fiber efficiency. The narrow min-max range and zero loss across all 50 samples reinforce a stable route; at 1.50x the fiber floor, the average RTT tracks closely to the theoretical limit for the 3,944 km distance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **57.9 ms** | | Jitter | **1.19 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **38.63 ms** | | Fiber Efficiency | **66.7%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,944.4 km** | | Vacuum RTT floor | **26.31 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **38.63 ms** | | Low-latency fiber material floor | **38.47 ms** | | Engineering floor (5% path allowance) | **40.56 ms** | | Research 1.33× mapped-fiber reference | **51.37 ms** | | Estimated unamplified path loss | **828.3 dB** | | Transparent optical spans / inline amplifiers | **52 / 51** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **55.78 ms** | | Average RTT | **57.9 ms** | | Maximum RTT | **62.74 ms** | | Standard deviation | **1.33 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Los Angeles to London latency and RTT](/docs/network/latency/pairs/lax-lon-rtt) — 129.2 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms **Same corridor (North America → North America)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-nyc-rtt). - **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. # Los Angeles, USA → Paris, France RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo requests from Los Angeles, USA to Paris, France averaged 135.9 ms over 50 samples taken at 100 ms intervals. The minimum RTT was 128.01 ms, the maximum was 155.68 ms, and packet loss was 0%. The route's standard deviation of 6.27 ms and jitter of 6.02 ms put variability at 4.61% of the average, above the network median of 3.28%. It ranked 10th among 19 outbound routes in the same measurement network, placing it near the middle of the set. Against the 9,107.2 km great-circle distance, the observed RTT is 1.52 times the theoretical fiber floor, or 65.6% fiber efficiency. The average still lands in the Good latency tier, making this round a practical reference for Paris-bound traffic from the West Coast and for separating distance-related delay from network overhead. It is a network-layer ICMP measurement, not an SLA and not a proxy for end-user application experience. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **135.9 ms** | | Jitter | **6.02 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.18 ms** | | Fiber Efficiency | **65.6%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,107.2 km** | | Vacuum RTT floor | **60.76 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.18 ms** | | Low-latency fiber material floor | **88.83 ms** | | Engineering floor (5% path allowance) | **93.66 ms** | | Research 1.33× mapped-fiber reference | **118.62 ms** | | Estimated unamplified path loss | **1912.5 dB** | | Transparent optical spans / inline amplifiers | **120 / 119** | | Published RTT inflation over fiber floor | **1.52×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **128.01 ms** | | Average RTT | **135.9 ms** | | Maximum RTT | **155.68 ms** | | Standard deviation | **6.27 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Los Angeles latency and RTT](/docs/network/latency/pairs/par-lax-rtt) — 136.5 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-par-rtt). - **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. # Los Angeles, USA → Seattle, USA RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the ICMP echo RTT from Los Angeles, USA to Seattle, USA averaged 26.9 ms over 50 samples, with a minimum of 25.5 ms and a maximum of 29.88 ms. Zero packet loss and 0.89 ms jitter place this path in the ultra-low-latency tier. The route ranked first among the 19 routes measured from this origin in the same cycle. Its 1.13 ms standard deviation is low in absolute terms, though the corresponding relative variation of about 4.2% is slightly above the 3.28% median across the route set; the connection remains very stable at the ICMP layer. Los Angeles is a primary US West Coast landing point for trans-Pacific cables, and Seattle is the Pacific Northwest's primary interconnection hub, so this path is more regional than intercontinental. The 1,543.6 km geodesic distance implies a fiber floor of 15.12 ms; at 26.9 ms the measured RTT is 1.78x that floor, or 56.2% fiber efficiency, leaving noticeable headroom relative to the fiber floor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **26.9 ms** | | Jitter | **0.89 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **15.12 ms** | | Fiber Efficiency | **56.2%** | | Latency Tier | Ultra-Low | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,543.6 km** | | Vacuum RTT floor | **10.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **15.12 ms** | | Low-latency fiber material floor | **15.06 ms** | | Engineering floor (5% path allowance) | **15.87 ms** | | Research 1.33× mapped-fiber reference | **20.1 ms** | | Estimated unamplified path loss | **324.2 dB** | | Transparent optical spans / inline amplifiers | **21 / 20** | | Published RTT inflation over fiber floor | **1.78×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **25.5 ms** | | Average RTT | **26.9 ms** | | Maximum RTT | **29.88 ms** | | Standard deviation | **1.13 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Los Angeles to London latency and RTT](/docs/network/latency/pairs/lax-lon-rtt) — 129.2 ms **Fastest routes arriving at Seattle (SEA)** * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-sea-rtt). - **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. # Los Angeles, USA → Singapore RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round sent 50 ICMP echo probes from Los Angeles to Singapore and recorded an average RTT of 167.7 ms, with a minimum of 163.93 ms and a maximum of 178.4 ms. All 50 probes were returned, and the 3.29 ms standard deviation with 2.59 ms jitter points to a steady path. The average is about 21% above the 138.43 ms fiber-floor estimate for the 14,135.8 km great-circle distance, so geographical separation explains most of the latency. Singapore ranks 17th among the 19 outbound routes in this set, near the slower end. The observed spread is 2.0% of the average, well below the 3.28% median across those routes, so this route pairs a higher average with notably low variability. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **167.7 ms** | | Jitter | **2.59 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **138.43 ms** | | Fiber Efficiency | **82.5%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,135.8 km** | | Vacuum RTT floor | **94.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **138.43 ms** | | Low-latency fiber material floor | **137.87 ms** | | Engineering floor (5% path allowance) | **145.37 ms** | | Research 1.33× mapped-fiber reference | **184.11 ms** | | Estimated unamplified path loss | **2968.5 dB** | | Transparent optical spans / inline amplifiers | **186 / 185** | | Published RTT inflation over fiber floor | **1.21×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **163.93 ms** | | Average RTT | **167.7 ms** | | Maximum RTT | **178.4 ms** | | Standard deviation | **3.29 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Los Angeles latency and RTT](/docs/network/latency/pairs/sin-lax-rtt) — 168.2 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-sin-rtt). - **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. # Los Angeles, USA → Sydney, Australia RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. Using the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Los Angeles to Sydney produced an average RTT of 137.6 ms, with a minimum of 134.53 ms and a maximum of 146.99 ms. All 50 probes were answered, and the 2.45 ms standard deviation with 1.96 ms jitter shows a very stable result. The average is only 16% above the 118.13 ms fiber-floor estimate for the 12,063.2 km great-circle distance, and the 85.9% fiber efficiency indicates the path is close to its physical reference. This route is 11th of 19 in the outbound route set, putting it near the middle. Its spread is 1.8% of the average, much tighter than the 3.28% median across the set, so mid-pack latency here is accompanied by strong consistency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **137.6 ms** | | Jitter | **1.96 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **118.13 ms** | | Fiber Efficiency | **85.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,063.2 km** | | Vacuum RTT floor | **80.48 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **118.13 ms** | | Low-latency fiber material floor | **117.66 ms** | | Engineering floor (5% path allowance) | **124.05 ms** | | Research 1.33× mapped-fiber reference | **157.12 ms** | | Estimated unamplified path loss | **2533.3 dB** | | Transparent optical spans / inline amplifiers | **159 / 158** | | Published RTT inflation over fiber floor | **1.16×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **134.53 ms** | | Average RTT | **137.6 ms** | | Maximum RTT | **146.99 ms** | | Standard deviation | **2.45 ms** | | Stdev / average | **1.8%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-syd-rtt). - **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. # Los Angeles, USA → Taipei, Taiwan RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Los Angeles to Taipei averaged 132.9 ms, with a minimum of 128.75 ms and a maximum of 148.78 ms. The 4.24 ms standard deviation and 3.59 ms jitter show a relatively steady trans-Pacific path, and none of the 50 samples were lost. The measured average is 1.24 times the 107 ms fiber floor implied by the 10,926.8 km great-circle distance, putting the route at 80.5% fiber efficiency. That leaves a moderate amount of headroom above the minimum possible round-trip propagation time for this long-haul path. This route ranked 9th among the 19 outbound routes in the same round, and its observed variability is slightly below the 3.28% median standard-deviation-to-average ratio for that route set. The combination of zero loss, low jitter, and stable latency makes LAX-to-Taipei a dependable baseline for trans-Pacific traffic. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **132.9 ms** | | Jitter | **3.59 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **107 ms** | | Fiber Efficiency | **80.5%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,926.8 km** | | Vacuum RTT floor | **72.9 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **107 ms** | | Low-latency fiber material floor | **106.57 ms** | | Engineering floor (5% path allowance) | **112.37 ms** | | Research 1.33× mapped-fiber reference | **142.32 ms** | | Estimated unamplified path loss | **2294.6 dB** | | Transparent optical spans / inline amplifiers | **144 / 143** | | Published RTT inflation over fiber floor | **1.24×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **128.75 ms** | | Average RTT | **132.9 ms** | | Maximum RTT | **148.78 ms** | | Standard deviation | **4.24 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-tpe-rtt). - **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. # Los Angeles, USA → Tokyo, Japan RTT 🇺🇸 **Los Angeles, USA (LAX)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT from Los Angeles to Tokyo in the 2026-08-16T04:07:28Z round averaged 101.2 ms, with samples between 97.1 ms and 112.57 ms. The standard deviation of 3.72 ms and jitter of 3.3 ms point to a consistently paced trans-Pacific path, and the 50-sample run recorded zero packet loss. Against the 8,834.5 km great-circle distance, the average sits 1.17 times the 86.51 ms fiber floor, yielding 85.5% fiber efficiency. That efficiency is notably high for an intercontinental route and shows the path is operating close to its physical round-trip propagation limit. This route was the 5th-ranked outbound route among 19 in the round. Its standard-deviation-to-average ratio is modestly above the 3.28% median for that route set, but the low absolute jitter and zero loss still leave a stable operational picture for USA-to-Japan traffic. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **101.2 ms** | | Jitter | **3.3 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **86.51 ms** | | Fiber Efficiency | **85.5%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,834.5 km** | | Vacuum RTT floor | **58.94 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **86.51 ms** | | Low-latency fiber material floor | **86.17 ms** | | Engineering floor (5% path allowance) | **90.85 ms** | | Research 1.33× mapped-fiber reference | **115.06 ms** | | Estimated unamplified path loss | **1855.3 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.17×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **97.1 ms** | | Average RTT | **101.2 ms** | | Maximum RTT | **112.57 ms** | | Standard deviation | **3.72 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes departing Los Angeles (LAX)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Los Angeles to London latency and RTT](/docs/network/latency/pairs/lax-lon-rtt) — 129.2 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lax-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Los Angeles → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lax-tyo-rtt). - **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. # London, UK → Amsterdam, Netherlands RTT 🇬🇧 **London, UK (LON)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In measurement round 2026-08-16T04:07:28Z, ICMP echo round-trip time from London, UK to Amsterdam, Netherlands averaged 5.2 ms across 50 samples, with a minimum of 5.03 ms and a maximum of 5.75 ms. Packet loss was 0% and jitter was 0.13 ms. London and Amsterdam are 358 km apart by geodesic distance. The measured average is 1.48 times the 3.51 ms fiber-floor estimate, equivalent to 67.4% fiber efficiency, while the minimum observed RTT sits only 1.52 ms above that floor. The route ranked first among the 19 routes measured from London in this round. Its standard deviation of 0.16 ms is about 3.1% of the mean, slightly better than the 3.28% median spread across the 19-route set. This ultra-low-latency, lossless combination makes the route a useful short-haul European RTT reference. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **5.2 ms** | | Jitter | **0.13 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.51 ms** | | Fiber Efficiency | **67.4%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ----------- | | WGS-84 geodesic distance | **358 km** | | Vacuum RTT floor | **2.39 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.51 ms** | | Low-latency fiber material floor | **3.49 ms** | | Engineering floor (5% path allowance) | **3.68 ms** | | Research 1.33× mapped-fiber reference | **4.66 ms** | | Estimated unamplified path loss | **75.2 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.48×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **5.03 ms** | | Average RTT | **5.2 ms** | | Maximum RTT | **5.75 ms** | | Standard deviation | **0.16 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms **Fastest routes departing London (LON)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms **Fastest routes arriving at Amsterdam (AMS)** * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-ams-rtt). - **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. # London, UK → Berlin, Germany RTT 🇬🇧 **London, UK (LON)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, ICMP echo round-trip time from London, UK to Berlin, Germany averaged 16.2 ms over 50 samples, with minimum 15.5 ms and maximum 19.35 ms. The route reported 0% packet loss and jitter of 0.64 ms. The 934.7 km geodesic distance corresponds to a fiber-floor RTT estimate of 9.15 ms. The 16.2 ms average is 1.77 times that floor, or 56.5% fiber efficiency; even the 15.5 ms minimum is 6.35 ms above the fiber-floor estimate. This route ranked fourth among the 19 routes measured from London in this round. Its standard deviation of 0.73 ms equals about 4.5% of the mean, above the 3.28% median spread across those 19 routes. With a 3.85 ms difference between minimum and maximum, the route stays lossless but shows more timing variation than its ultra-low average might imply. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **16.2 ms** | | Jitter | **0.64 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **9.15 ms** | | Fiber Efficiency | **56.5%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **934.7 km** | | Vacuum RTT floor | **6.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **9.15 ms** | | Low-latency fiber material floor | **9.12 ms** | | Engineering floor (5% path allowance) | **9.61 ms** | | Research 1.33× mapped-fiber reference | **12.17 ms** | | Estimated unamplified path loss | **196.3 dB** | | Transparent optical spans / inline amplifiers | **13 / 12** | | Published RTT inflation over fiber floor | **1.77×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **15.5 ms** | | Average RTT | **16.2 ms** | | Maximum RTT | **19.35 ms** | | Standard deviation | **0.73 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-ber-rtt). - **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. # London, UK → Frankfurt, Germany RTT 🇬🇧 **London, UK (LON)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, ICMP echo round-trip time from London, UK to Frankfurt, Germany averaged 13.6 ms across 50 samples, with a minimum of 13.18 ms and a maximum of 15.43 ms. No packets were lost, and jitter was 0.29 ms. The geodesic distance of 639.5 km yields a fiber-floor round-trip estimate of 6.26 ms. The observed 13.6 ms average is 2.17 times that floor, corresponding to 46.1% fiber efficiency; the 13.18 ms minimum remains 6.92 ms above the floor, so the route does not approach its physical limit in this round. This route ranked third among the 19 routes measured from London in this round. Its standard deviation of 0.42 ms is about 3.1% of the mean, close to the 3.28% median spread across the set, and jitter stayed at 0.29 ms. Despite the modest fiber-efficiency figure, the route shows tight dispersion within the ultra-low latency tier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **13.6 ms** | | Jitter | **0.29 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **6.26 ms** | | Fiber Efficiency | **46.1%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **639.5 km** | | Vacuum RTT floor | **4.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **6.26 ms** | | Low-latency fiber material floor | **6.24 ms** | | Engineering floor (5% path allowance) | **6.58 ms** | | Research 1.33× mapped-fiber reference | **8.33 ms** | | Estimated unamplified path loss | **134.3 dB** | | Transparent optical spans / inline amplifiers | **9 / 8** | | Published RTT inflation over fiber floor | **2.17×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **13.18 ms** | | Average RTT | **13.6 ms** | | Maximum RTT | **15.43 ms** | | Standard deviation | **0.42 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-fra-rtt). - **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. # London, UK → São Paulo, Brazil RTT 🇬🇧 **London, UK (LON)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, London-to-São Paulo produced an average ICMP echo RTT of 170.7 ms from 50 samples, with a minimum of 165.28 ms and a maximum of 185.16 ms. The 4.35 ms standard deviation and 4.17 ms jitter place the route in the fair latency tier, and no packet loss was observed. Across the 9,472.8 km great-circle distance, the fiber floor is 92.76 ms, so the average is 1.84 times that floor and fiber efficiency is 54.3%. Ranked 14th among the 19 routes measured in this round, this route is one of the slower ones in the set. Its standard deviation is 2.55% of the average, below the median of 3.28% across the measured route set, so timing remains relatively consistent even at the higher latency level. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **170.7 ms** | | Jitter | **4.17 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **92.76 ms** | | Fiber Efficiency | **54.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,472.8 km** | | Vacuum RTT floor | **63.2 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **92.76 ms** | | Low-latency fiber material floor | **92.39 ms** | | Engineering floor (5% path allowance) | **97.42 ms** | | Research 1.33× mapped-fiber reference | **123.38 ms** | | Estimated unamplified path loss | **1989.3 dB** | | Transparent optical spans / inline amplifiers | **125 / 124** | | Published RTT inflation over fiber floor | **1.84×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **165.28 ms** | | Average RTT | **170.7 ms** | | Maximum RTT | **185.16 ms** | | Standard deviation | **4.35 ms** | | Stdev / average | **2.5%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Europe → South America)** * [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms * [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 ms * [Frankfurt to São Paulo latency and RTT](/docs/network/latency/pairs/fra-gru-rtt) — 181.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-gru-rtt). - **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. # London, UK → Hong Kong RTT 🇬🇧 **London, UK (LON)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from London to Hong Kong averaged 160.6 ms, with the fastest sample at 151.57 ms and the slowest at 189.08 ms. Packet loss was 0% and jitter was 6.03 ms. The great-circle distance of 9,643.6 km implies a fiber-floor estimate near 94.4 ms, so the observed mean is about 1.7 times that lower bound. The route ranks 13th among the 19 London-origin departures tracked in this round. Sample spread was moderate: the 7.9 ms standard deviation translates to about 4.9% of the average, slightly above the 3.3% typical for the round's London departure set. With zero loss and a min-to-max range of 37.5 ms, London-to-Hong Kong is stable enough to be a useful reference for long-haul Asia-Pacific latency. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **160.6 ms** | | Jitter | **6.03 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **94.44 ms** | | Fiber Efficiency | **58.8%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,643.6 km** | | Vacuum RTT floor | **64.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **94.44 ms** | | Low-latency fiber material floor | **94.06 ms** | | Engineering floor (5% path allowance) | **99.17 ms** | | Research 1.33× mapped-fiber reference | **125.6 ms** | | Estimated unamplified path loss | **2025.2 dB** | | Transparent optical spans / inline amplifiers | **127 / 126** | | Published RTT inflation over fiber floor | **1.7×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **151.57 ms** | | Average RTT | **160.6 ms** | | Maximum RTT | **189.08 ms** | | Standard deviation | **7.9 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to London latency and RTT](/docs/network/latency/pairs/hkg-lon-rtt) — 158.7 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-hkg-rtt). - **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. # London, UK → Ashburn, USA RTT 🇬🇧 **London, UK (LON)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. At the 2026-08-16T04:07:28Z measurement round, London-to-Ashburn ICMP echo RTT averaged 71ms, with a minimum of 68.31ms, a maximum of 80.67ms, and no packet loss across 50 samples. The 71ms average is 1.22 times the theoretical fiber-floor time for the 5,932.8km geodesic distance, corresponding to 81.8% fiber efficiency. The 2.3ms standard deviation and 1.76ms jitter indicate a steady window, and the route's standard deviation is about 3.2% of its average — slightly below the 3.28% median for the 19-route set. It ranked 8th among those routes in this cycle. The Excellent latency tier, zero packet loss, and small gap between minimum and maximum RTT all point to a clean transatlantic measurement profile; the useful takeaway is that London-to-Ashburn RTT is already close to the fiber-floor estimate for this geography. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **71 ms** | | Jitter | **1.76 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **58.1 ms** | | Fiber Efficiency | **81.8%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,932.8 km** | | Vacuum RTT floor | **39.58 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **58.1 ms** | | Low-latency fiber material floor | **57.87 ms** | | Engineering floor (5% path allowance) | **61.01 ms** | | Research 1.33× mapped-fiber reference | **77.27 ms** | | Estimated unamplified path loss | **1245.9 dB** | | Transparent optical spans / inline amplifiers | **78 / 77** | | Published RTT inflation over fiber floor | **1.22×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **68.31 ms** | | Average RTT | **71 ms** | | Maximum RTT | **80.67 ms** | | Standard deviation | **2.3 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Paris to Ashburn latency and RTT](/docs/network/latency/pairs/par-iad-rtt) — 75.5 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-iad-rtt). - **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. # London, UK → Johannesburg, South Africa RTT 🇬🇧 **London, UK (LON)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z London-to-Johannesburg ICMP echo round returned an average RTT of 179.6 ms, with a minimum of 171.6 ms and a maximum of 203.66 ms across 50 samples. Zero packet loss and 4.3 ms of jitter point to a stable long-haul path, even though the average sits in the 'Fair' latency tier. At roughly 9,039 km apart, the pair's straight-line vacuum floor is 60.3 ms and its fiber floor is 88.52 ms. The measured RTT is 2.03 times that fiber floor, equal to about 49.3% fiber efficiency; the extra time is consistent with a real cable route longer than the geodesic, not with loss or erratic delay. Among the 19 outbound routes in this round, this path ranks 16th by average RTT, placing it in the slower half of the source's outbound set. Its standard deviation of 5.96 ms is about 3.32% of the average, close to the round's median variability of 3.28% across the outbound group. For operators watching London–South Africa latency, the stable, loss-free profile is the more notable result: average delay is less informative than the narrow spread around it. The 2026-08-16T04:07:28Z round shows a route that may be relatively slow among outbound destinations, but it is not a volatile one. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **179.6 ms** | | Jitter | **4.3 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **88.52 ms** | | Fiber Efficiency | **49.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,039.3 km** | | Vacuum RTT floor | **60.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **88.52 ms** | | Low-latency fiber material floor | **88.16 ms** | | Engineering floor (5% path allowance) | **92.96 ms** | | Research 1.33× mapped-fiber reference | **117.73 ms** | | Estimated unamplified path loss | **1898.3 dB** | | Transparent optical spans / inline amplifiers | **119 / 118** | | Published RTT inflation over fiber floor | **2.03×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **171.6 ms** | | Average RTT | **179.6 ms** | | Maximum RTT | **203.66 ms** | | Standard deviation | **5.96 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms * [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt) — 198.5 ms **Same corridor (Europe → Africa)** * [Moscow to Johannesburg latency and RTT](/docs/network/latency/pairs/mow-jnb-rtt) — 201.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-jnb-rtt). - **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. # London, UK → Los Angeles, USA RTT 🇬🇧 **London, UK (LON)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, London-to-Los Angeles ICMP echo RTT averaged 127.5ms, with a minimum of 123.84ms, a maximum of 138.75ms, and no packet loss across 50 samples. The 127.5ms average is 1.48 times the theoretical fiber-floor time for the 8,776.7km geodesic distance, corresponding to 67.4% fiber efficiency. Its standard deviation is about 2.4% of its average, well below the 3.28% median for the 19-route set, and the route ranked 11th among those routes in this cycle; the 3.03ms standard deviation and 2.52ms jitter are both low in absolute terms. The Good latency tier reflects the long 8,776.7km span, whose vacuum floor is 58.55ms and fiber floor is 85.95ms; the observed 127.5ms is therefore mostly explained by distance, with little sign of excess variability or loss. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **127.5 ms** | | Jitter | **2.52 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.95 ms** | | Fiber Efficiency | **67.4%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,776.7 km** | | Vacuum RTT floor | **58.55 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.95 ms** | | Low-latency fiber material floor | **85.6 ms** | | Engineering floor (5% path allowance) | **90.26 ms** | | Research 1.33× mapped-fiber reference | **114.31 ms** | | Estimated unamplified path loss | **1843.1 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.48×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **123.84 ms** | | Average RTT | **127.5 ms** | | Maximum RTT | **138.75 ms** | | Standard deviation | **3.03 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to London latency and RTT](/docs/network/latency/pairs/lax-lon-rtt) — 129.2 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-lax-rtt). - **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. # London, UK → Melbourne, Australia RTT 🇬🇧 **London, UK (LON)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from London to Melbourne produced an average RTT of 249.6 ms, with a minimum of 242.04 ms and a maximum of 269.23 ms. Packet loss was zero. With a great-circle separation of 16,898.4 km, a theoretical fiber floor near 165.5 ms means the observed average is 1.51 times that bound. The route ranks 18th among the 19 London-origin departures in this round. The latency profile is consistent: the 5.89 ms standard deviation is about 2.4% of the average, and jitter is 4.83 ms, both below the 3.3% typical for the round's London departures. London-to-Melbourne therefore shows a high but predictable round-trip time rather than one that fluctuates widely. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **249.6 ms** | | Jitter | **4.83 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **165.48 ms** | | Fiber Efficiency | **66.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,898.4 km** | | Vacuum RTT floor | **112.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **165.48 ms** | | Low-latency fiber material floor | **164.82 ms** | | Engineering floor (5% path allowance) | **173.78 ms** | | Research 1.33× mapped-fiber reference | **220.09 ms** | | Estimated unamplified path loss | **3548.7 dB** | | Transparent optical spans / inline amplifiers | **222 / 221** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **242.04 ms** | | Average RTT | **249.6 ms** | | Maximum RTT | **269.23 ms** | | Standard deviation | **5.89 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to London latency and RTT](/docs/network/latency/pairs/mel-lon-rtt) — 252 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-mel-rtt). - **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. # London, UK → Miami, USA RTT 🇬🇧 **London, UK (LON)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, London-to-Miami ICMP echo RTT averaged 101.9ms, with a minimum of 97.83ms, a maximum of 115.14ms, and no packet loss across 50 samples. The 101.9ms average is 1.46 times the theoretical fiber-floor time for the 7,138.4km geodesic distance, corresponding to 68.6% fiber efficiency. The route's standard deviation is about 3.8% of its average, above the 3.28% median for the 19-route set, and it ranked 9th among those routes in this cycle. Given that the fiber floor for 7,138.4km is 69.9ms and the observed average is 101.9ms, the route behaves as the distance would suggest. The wider relative standard deviation is the main thing to watch, but zero packet loss keeps the measurement clean. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **101.9 ms** | | Jitter | **3.08 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **69.9 ms** | | Fiber Efficiency | **68.6%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,138.4 km** | | Vacuum RTT floor | **47.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **69.9 ms** | | Low-latency fiber material floor | **69.62 ms** | | Engineering floor (5% path allowance) | **73.41 ms** | | Research 1.33× mapped-fiber reference | **92.97 ms** | | Estimated unamplified path loss | **1499.1 dB** | | Transparent optical spans / inline amplifiers | **94 / 93** | | Published RTT inflation over fiber floor | **1.46×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **97.83 ms** | | Average RTT | **101.9 ms** | | Maximum RTT | **115.14 ms** | | Standard deviation | **3.85 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-mia-rtt). - **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. # London, UK → Moscow, Russia RTT 🇬🇧 **London, UK (LON)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from London, UK to Moscow, Russia averaged 43.5 ms over 50 samples, with a minimum of 41.81 ms, a maximum of 48.52 ms, jitter of 1.21 ms, and no packet loss. With a geodesic distance of 2,508.5 km, the vacuum-floor time is 16.73 ms and the fiber-floor time is 24.56 ms; the observed RTT is 1.77 times the fiber floor, equivalent to 56.5% fiber-floor efficiency. For a route spanning roughly 2,500 km, this is a high-efficiency long-haul path and sits in the Excellent latency tier. Relative to the 19 outbound routes from the same origin, this path ranks 6th in the round. Its 1.38 ms standard deviation is 3.2% of the average RTT, slightly tighter than the route set's 3.28% median standard deviation as a share of average RTT, so London-Moscow is both well-positioned for its distance and unusually consistent in this measurement round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **43.5 ms** | | Jitter | **1.21 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **24.56 ms** | | Fiber Efficiency | **56.5%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,508.5 km** | | Vacuum RTT floor | **16.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **24.56 ms** | | Low-latency fiber material floor | **24.47 ms** | | Engineering floor (5% path allowance) | **25.8 ms** | | Research 1.33× mapped-fiber reference | **32.67 ms** | | Estimated unamplified path loss | **526.8 dB** | | Transparent optical spans / inline amplifiers | **33 / 32** | | Published RTT inflation over fiber floor | **1.77×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **41.81 ms** | | Average RTT | **43.5 ms** | | Maximum RTT | **48.52 ms** | | Standard deviation | **1.38 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-mow-rtt). - **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. # London, UK → Marseille, France RTT 🇬🇧 **London, UK (LON)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo requests from London, UK to Marseille, France produced an average RTT of 17.9 ms from 50 samples, with a minimum of 17.02 ms, a maximum of 21.69 ms, jitter of 0.62 ms, and zero packet loss. The geodesic distance is 1,002.4 km; light in a vacuum would take 6.69 ms and the realistic fiber-floor time is 9.82 ms. At 17.9 ms average, the measured route runs 1.82 times the fiber floor, or 54.8% fiber-floor efficiency, placing it in the Ultra-Low latency tier. Among the 19 outbound routes measured from London in the same round, this path ranks 5th. Its 0.84 ms standard deviation equals 4.7% of the average RTT, while the median standard deviation as a share of average RTT across the route set is 3.28%, so London-Marseille is a touch more variable than the typical route in this set despite the low absolute spread. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **17.9 ms** | | Jitter | **0.62 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **9.82 ms** | | Fiber Efficiency | **54.8%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,002.4 km** | | Vacuum RTT floor | **6.69 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **9.82 ms** | | Low-latency fiber material floor | **9.78 ms** | | Engineering floor (5% path allowance) | **10.31 ms** | | Research 1.33× mapped-fiber reference | **13.06 ms** | | Estimated unamplified path loss | **210.5 dB** | | Transparent optical spans / inline amplifiers | **14 / 13** | | Published RTT inflation over fiber floor | **1.82×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **17.02 ms** | | Average RTT | **17.9 ms** | | Maximum RTT | **21.69 ms** | | Standard deviation | **0.84 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-mrs-rtt). - **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. # London, UK → New York, USA RTT 🇬🇧 **London, UK (LON)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, London-to-New York returned an average ICMP echo RTT of 63.8 ms from 50 samples, with a minimum of 60.82 ms, a maximum of 74.75 ms, and zero packet loss. The 2.78 ms standard deviation and 2.55 ms jitter place the route in the excellent latency tier. Over the 5,585.2 km great-circle distance, the measured average is 1.17 times the fiber floor, which corresponds to 85.7% fiber efficiency. This route ranks 7th among the 19 routes measured in the same round. Its standard deviation equals about 4.36% of the average, slightly above the median of 3.28% across the measured route set, so latency is close to the fiber floor but sample-to-sample variation is a bit looser than the typical route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **63.8 ms** | | Jitter | **2.55 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **54.69 ms** | | Fiber Efficiency | **85.7%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,585.2 km** | | Vacuum RTT floor | **37.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **54.69 ms** | | Low-latency fiber material floor | **54.48 ms** | | Engineering floor (5% path allowance) | **57.44 ms** | | Research 1.33× mapped-fiber reference | **72.74 ms** | | Estimated unamplified path loss | **1172.9 dB** | | Transparent optical spans / inline amplifiers | **74 / 73** | | Published RTT inflation over fiber floor | **1.17×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **60.82 ms** | | Average RTT | **63.8 ms** | | Maximum RTT | **74.75 ms** | | Standard deviation | **2.78 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms **Same corridor (Europe → North America)** * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms * [Frankfurt to New York latency and RTT](/docs/network/latency/pairs/fra-nyc-rtt) — 74.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-nyc-rtt). - **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. # London, UK → Paris, France RTT 🇬🇧 **London, UK (LON)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo tests between London, UK and Paris, France returned an average RTT of 6.4 ms across 50 samples, with a minimum of 6.23 ms, a maximum of 6.9 ms, jitter of 0.11 ms, and zero packet loss. The 344.1 km geodesic path corresponds to a 2.3 ms vacuum-floor time and a 3.37 ms fiber-floor time. The measured average is 1.9 times the fiber floor, or 52.7% fiber-floor efficiency, consistent with a short cross-border route that remains firmly in the Ultra-Low latency tier. This path ranks 2nd among the 19 outbound routes measured from London in the same round. Its 0.15 ms standard deviation is just 2.3% of the average RTT, below the route set's 3.28% median standard deviation as a share of average RTT, making London-Paris one of the most stable ultrafast paths in the group. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **6.4 ms** | | Jitter | **0.11 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.37 ms** | | Fiber Efficiency | **52.7%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **344.1 km** | | Vacuum RTT floor | **2.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.37 ms** | | Low-latency fiber material floor | **3.36 ms** | | Engineering floor (5% path allowance) | **3.54 ms** | | Research 1.33× mapped-fiber reference | **4.48 ms** | | Estimated unamplified path loss | **72.3 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **6.23 ms** | | Average RTT | **6.4 ms** | | Maximum RTT | **6.9 ms** | | Standard deviation | **0.15 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms **Fastest routes arriving at Paris (PAR)** * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-par-rtt). - **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. # London, UK → Seattle, USA RTT 🇬🇧 **London, UK (LON)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, London-to-Seattle produced an average ICMP echo RTT of 123.2 ms from 50 samples, with a minimum of 121.09 ms and a maximum of 129.68 ms. The 1.95 ms standard deviation and 1.63 ms jitter point to a stable route, and zero packet loss accompanies the good latency tier. Over the 7,722.7 km great-circle distance, the fiber floor is 75.63 ms, so the measured average is 1.63 times that floor and fiber efficiency is 61.4%. This route ranks 10th among the 19 routes measured in this round. Its standard deviation is only 1.58% of the average, well below the median of 3.28% across the measured route set, making it one of the more consistent routes in the set despite the longer geographic span. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **123.2 ms** | | Jitter | **1.63 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **75.63 ms** | | Fiber Efficiency | **61.4%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,722.7 km** | | Vacuum RTT floor | **51.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **75.63 ms** | | Low-latency fiber material floor | **75.32 ms** | | Engineering floor (5% path allowance) | **79.42 ms** | | Research 1.33× mapped-fiber reference | **100.58 ms** | | Estimated unamplified path loss | **1621.8 dB** | | Transparent optical spans / inline amplifiers | **102 / 101** | | Published RTT inflation over fiber floor | **1.63×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **121.09 ms** | | Average RTT | **123.2 ms** | | Maximum RTT | **129.68 ms** | | Standard deviation | **1.95 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to London latency and RTT](/docs/network/latency/pairs/sea-lon-rtt) — 124.1 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-sea-rtt). - **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. # London, UK → Singapore RTT 🇬🇧 **London, UK (LON)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from London to Singapore averaged 156.5 ms, with a minimum of 151.92 ms and a maximum of 167.3 ms. All 50 samples returned, so packet loss was 0%. The route spans 10,859.7 km on a great-circle path, where the fiber-floor estimate is 106.35 ms, making the observed average 1.47 times that bound. It ranks 12th among the 19 London-origin departures tracked in the same round. The RTT distribution is tight: the 3.54 ms standard deviation equals about 2.3% of the average, and jitter is 3.13 ms, both below the 3.3% typical for the round's London departures. London-to-Singapore pairs a relatively low average RTT with low sample-to-sample variability. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **156.5 ms** | | Jitter | **3.13 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.35 ms** | | Fiber Efficiency | **68%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,859.7 km** | | Vacuum RTT floor | **72.45 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.35 ms** | | Low-latency fiber material floor | **105.92 ms** | | Engineering floor (5% path allowance) | **111.68 ms** | | Research 1.33× mapped-fiber reference | **141.44 ms** | | Estimated unamplified path loss | **2280.5 dB** | | Transparent optical spans / inline amplifiers | **143 / 142** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **151.92 ms** | | Average RTT | **156.5 ms** | | Maximum RTT | **167.3 ms** | | Standard deviation | **3.54 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to London latency and RTT](/docs/network/latency/pairs/sin-lon-rtt) — 155.4 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-sin-rtt). - **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. # London, UK → Sydney, Australia RTT 🇬🇧 **London, UK (LON)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT from London, UK, to Sydney, Australia, averaged 258.1 ms in the 2026-08-16T04:07:28Z test round. Across 50 samples sent at 100 ms intervals, RTTs ranged from a minimum of 249.91 ms to a maximum of 280.95 ms, with 0% packet loss. At a geodesic distance of 16,988.9 km, the theoretical vacuum round-trip floor is 113.34 ms and the fiber round-trip floor is 166.37 ms. The measured average is 1.55 times that fiber floor, a result consistent with a high-latency intercontinental route where absolute delay is dominated by the distance between the two endpoints. This path ranked 19th among the 19 outbound routes measured in the same round. Its standard deviation was 6.66 ms and jitter was 5.27 ms; the 31.04 ms difference between maximum and minimum RTT is small relative to the 258.1 ms average, and the route set's median standard-deviation-to-average ratio of 3.28% points to broadly stable timing on this London-Sydney path. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **258.1 ms** | | Jitter | **5.27 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **166.37 ms** | | Fiber Efficiency | **64.5%** | | Latency Tier | High | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,988.9 km** | | Vacuum RTT floor | **113.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **166.37 ms** | | Low-latency fiber material floor | **165.7 ms** | | Engineering floor (5% path allowance) | **174.71 ms** | | Research 1.33× mapped-fiber reference | **221.27 ms** | | Estimated unamplified path loss | **3567.7 dB** | | Transparent optical spans / inline amplifiers | **223 / 222** | | Published RTT inflation over fiber floor | **1.55×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **249.91 ms** | | Average RTT | **258.1 ms** | | Maximum RTT | **280.95 ms** | | Standard deviation | **6.66 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to London latency and RTT](/docs/network/latency/pairs/syd-lon-rtt) — 256.5 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-syd-rtt). - **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. # London, UK → Taipei, Taiwan RTT 🇬🇧 **London, UK (LON)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT from London, UK, to Taipei, Taiwan, averaged 173.8 ms in the 2026-08-16T04:07:28Z test round. The 50 samples, collected at 100 ms intervals, produced a minimum of 166.08 ms and a maximum of 201.98 ms, with no packet loss. The geodesic distance between London and Taipei is 9,799.7 km, placing the theoretical vacuum round-trip floor at 65.38 ms and the fiber round-trip floor at 95.97 ms. The measured average is 1.81 times the fiber floor, placing the route in the fair latency tier for a long-haul connection between Europe and East Asia. This route ranked 15th among the 19 outbound routes measured in the same round. Its standard deviation of 7.40 ms and jitter of 5.49 ms produce a standard-deviation-to-average ratio of about 4.3%, slightly above the 3.28% median across the measured route set, and the RTT spread between minimum and maximum is 35.90 ms. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **173.8 ms** | | Jitter | **5.49 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.97 ms** | | Fiber Efficiency | **55.2%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,799.7 km** | | Vacuum RTT floor | **65.38 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.97 ms** | | Low-latency fiber material floor | **95.58 ms** | | Engineering floor (5% path allowance) | **100.78 ms** | | Research 1.33× mapped-fiber reference | **127.63 ms** | | Estimated unamplified path loss | **2057.9 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **166.08 ms** | | Average RTT | **173.8 ms** | | Maximum RTT | **201.98 ms** | | Standard deviation | **7.4 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to London latency and RTT](/docs/network/latency/pairs/tpe-lon-rtt) — 173 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-tpe-rtt). - **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. # London, UK → Tokyo, Japan RTT 🇬🇧 **London, UK (LON)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT from London, UK, to Tokyo, Japan, averaged 202.9 ms in the 2026-08-16T04:07:28Z test round. Across 50 samples at 100 ms intervals, RTTs stayed between 197.73 ms and 219 ms, and packet loss was 0%. London and Tokyo are separated by 9,582.1 km on the geodesic line, giving a theoretical vacuum round-trip floor of 63.93 ms and a fiber round-trip floor of 93.84 ms. The observed average is 2.16 times the fiber floor, with a fiber efficiency of 46.2%, and the route falls in the fair latency tier. Ranked 17th among the 19 outbound routes measured in the same round, this path still produced tight timing: standard deviation of 4.43 ms and jitter of 3.56 ms. Its standard-deviation-to-average ratio of about 2.2% is below the 3.28% median across the measured route set, so London-Tokyo RTTs were especially consistent for this round, despite the elevated absolute latency. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **202.9 ms** | | Jitter | **3.56 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **93.84 ms** | | Fiber Efficiency | **46.2%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [London](https://www.geonames.org/2643743) (51.50853, -0.12574) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,582.1 km** | | Vacuum RTT floor | **63.93 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **93.84 ms** | | Low-latency fiber material floor | **93.46 ms** | | Engineering floor (5% path allowance) | **98.54 ms** | | Research 1.33× mapped-fiber reference | **124.8 ms** | | Estimated unamplified path loss | **2012.2 dB** | | Transparent optical spans / inline amplifiers | **126 / 125** | | Published RTT inflation over fiber floor | **2.16×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **197.73 ms** | | Average RTT | **202.9 ms** | | Maximum RTT | **219 ms** | | Standard deviation | **4.43 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [London (LON)](/docs/network/latency/lon-london) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to London latency and RTT](/docs/network/latency/pairs/tyo-lon-rtt) — 202.7 ms **Fastest routes departing London (LON)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/lon-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/lon-tyo-rtt). - **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. # Melbourne, Australia → Amsterdam, Netherlands RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. Round 2026-08-16T04:07:28Z measured ICMP echo RTT between Melbourne and Amsterdam at an average of 252.8 ms, with a 241.73 ms minimum, a 276.97 ms maximum, and zero packet loss across 50 samples. The 7.18 ms standard deviation and 6.4 ms jitter are modest for a 16,540.5 km intercontinental route, and the high latency tier is consistent with the distance. This path ranks 16th out of the 19 outbound routes in this round, placing it toward the high-latency end of the measured set. Its variability ratio of about 2.8% is below the 3.28% network-wide median, so relative to its delay the route is actually quite consistent. The observed RTT is 1.56 times the 161.98 ms fiber floor for the great-circle distance, a fiber efficiency of 64.1%. Most of the delay is the unavoidable distance, while the 0% loss and low jitter suggest a clean transcontinental path during the measurement window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **252.8 ms** | | Jitter | **6.4 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **161.98 ms** | | Fiber Efficiency | **64.1%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,540.5 km** | | Vacuum RTT floor | **110.35 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **161.98 ms** | | Low-latency fiber material floor | **161.33 ms** | | Engineering floor (5% path allowance) | **170.1 ms** | | Research 1.33× mapped-fiber reference | **215.43 ms** | | Estimated unamplified path loss | **3473.5 dB** | | Transparent optical spans / inline amplifiers | **218 / 217** | | Published RTT inflation over fiber floor | **1.56×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **241.73 ms** | | Average RTT | **252.8 ms** | | Maximum RTT | **276.97 ms** | | Standard deviation | **7.18 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Melbourne latency and RTT](/docs/network/latency/pairs/ams-mel-rtt) — 252.5 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-ams-rtt). - **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. # Melbourne, Australia → Berlin, Germany RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. In the measurement round 2026-08-16T04:07:28Z, the Melbourne-to-Berlin path returned an average ICMP echo RTT of 254.7 ms, with a minimum of 239.97 ms and a maximum of 301.16 ms. None of the 50 probes were lost, and the standard deviation was 11.1 ms (jitter 10.6 ms), so the intercontinental path was stable despite its high latency tier. The average is 1.63 times the theoretical fiber floor for the 15,965.1 km great-circle distance, which translates to 61.4% fiber-floor efficiency. Within the 19 outbound route options in this measurement set, this path ranks 17th by outbound latency; the peer group's median standard-deviation-to-average ratio is 3.28%, helping to contextualize the observed spread. The zero packet loss and narrow 61.19 ms gap between minimum and maximum indicate that this direction had healthy capacity at test time. Because the minimum sits only about 14.7 ms below the average, the route's steady-state latency is close to its best observed case, so the numbers from this round can serve as a baseline for future Melbourne–Berlin troubleshooting. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **254.7 ms** | | Jitter | **10.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **156.34 ms** | | Fiber Efficiency | **61.4%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,965.1 km** | | Vacuum RTT floor | **106.51 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **156.34 ms** | | Low-latency fiber material floor | **155.71 ms** | | Engineering floor (5% path allowance) | **164.18 ms** | | Research 1.33× mapped-fiber reference | **207.94 ms** | | Estimated unamplified path loss | **3352.7 dB** | | Transparent optical spans / inline amplifiers | **210 / 209** | | Published RTT inflation over fiber floor | **1.63×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **239.97 ms** | | Average RTT | **254.7 ms** | | Maximum RTT | **301.16 ms** | | Standard deviation | **11.1 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Melbourne latency and RTT](/docs/network/latency/pairs/ber-mel-rtt) — 256.2 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-ber-rtt). - **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. # Melbourne, Australia → Frankfurt, Germany RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo RTT from Melbourne to Frankfurt averaged 248.6 ms over 50 samples, with a minimum of 238.22 ms, a maximum of 288.5 ms, and zero packet loss. That average is 1.56 times the theoretical fiber floor for the 16,315.5 km geodesic separation, giving a fiber efficiency of 64.3 percent. With 10.01 ms standard deviation and 8.5 ms jitter, the connection held a fairly steady latency profile despite being a long intercontinental route. In the context of the 19 outbound routes in this network's monitoring set, the Melbourne-Frankfurt average ranks 14th by RTT. The network's median stdev-to-average ratio sits at 3.28 percent, while this route's standard deviation is about 4.03 percent of its average, so it is slightly more variable than the midpoint rather than dramatically inconsistent. The minimum sample of 238.22 ms is just 49 percent above the direct-fiber minimum, showing the path can get close to the physical bottom under good conditions. ICMP RTT reflects reachability and delay, not the full experience an end user would see, and it should not be treated as an SLA or a proxy for application performance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **248.6 ms** | | Jitter | **8.5 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **159.77 ms** | | Fiber Efficiency | **64.3%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,315.5 km** | | Vacuum RTT floor | **108.85 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **159.77 ms** | | Low-latency fiber material floor | **159.13 ms** | | Engineering floor (5% path allowance) | **167.78 ms** | | Research 1.33× mapped-fiber reference | **212.5 ms** | | Estimated unamplified path loss | **3426.2 dB** | | Transparent optical spans / inline amplifiers | **215 / 214** | | Published RTT inflation over fiber floor | **1.56×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **238.22 ms** | | Average RTT | **248.6 ms** | | Maximum RTT | **288.5 ms** | | Standard deviation | **10.01 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Melbourne latency and RTT](/docs/network/latency/pairs/fra-mel-rtt) — 250.1 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-fra-rtt). - **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. # Melbourne, Australia → São Paulo, Brazil RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round measured ICMP echo RTT between Melbourne, Australia and São Paulo, Brazil across 50 samples. The average was 305.3 ms, with a minimum of 295.61 ms and a maximum of 333.89 ms; standard deviation was 8.1 ms, jitter was 6 ms, and packet loss was 0 percent. At a geodesic distance of 13,105.1 km, the vacuum floor is 87.43 ms and the fiber floor is 128.34 ms. The observed average is 2.38 times the fiber floor, putting fiber efficiency at 42 percent; the large inflation above the physical reference indicates substantial path overhead. This route ranks 18th among 19 outbound routes in the same round, placing it near the lower end of the set. Its standard deviation is about 2.7 percent of the average RTT, below the median variability of 3.28 percent across the route set, while jitter stayed at 6 ms. The path is therefore consistently slow: zero packets were lost, but the RTT floor remains far above the theoretical minimum. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **305.3 ms** | | Jitter | **6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.34 ms** | | Fiber Efficiency | **42%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,105.1 km** | | Vacuum RTT floor | **87.43 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.34 ms** | | Low-latency fiber material floor | **127.82 ms** | | Engineering floor (5% path allowance) | **134.77 ms** | | Research 1.33× mapped-fiber reference | **170.69 ms** | | Estimated unamplified path loss | **2752.1 dB** | | Transparent optical spans / inline amplifiers | **173 / 172** | | Published RTT inflation over fiber floor | **2.38×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **295.61 ms** | | Average RTT | **305.3 ms** | | Maximum RTT | **333.89 ms** | | Standard deviation | **8.1 ms** | | Stdev / average | **2.7%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Asia Pacific to South America](/docs/network/latency/regions/asia-pacific-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Melbourne latency and RTT](/docs/network/latency/pairs/gru-mel-rtt) — 274.7 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Asia Pacific → South America)** * [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.5 ms * [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 ms * [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-gru-rtt). - **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. # Melbourne, Australia → Hong Kong RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z ICMP echo round, 50 probes at 100 ms intervals from Melbourne, Australia to Hong Kong returned an average RTT of 138.5 ms, with a minimum of 133.73 ms and a maximum of 150.99 ms. No packets were lost, and jitter was 3.66 ms, indicating a stable long-haul path. Relative to the 72.38 ms fibre-floor estimate for the 7,391 km geodesic separation, the measured average is 1.91 times that ideal, or roughly 91% above the physical minimum. The 4.36 ms standard deviation is consistent with the 133.73–150.99 ms range, and the route's 52.3% fibre efficiency leaves a clear gap to the theoretical optimum. In the 19-route outbound set from this Melbourne source, the Hong Kong path is ranked fourth. Its standard deviation as a share of the average is about 3.15%, slightly tighter than the 3.28% median relative spread for the set, and the zero-loss sample reinforces that the RTT distribution is compact for a route covering more than 7,000 km. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **138.5 ms** | | Jitter | **3.66 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.38 ms** | | Fiber Efficiency | **52.3%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,391.1 km** | | Vacuum RTT floor | **49.31 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.38 ms** | | Low-latency fiber material floor | **72.09 ms** | | Engineering floor (5% path allowance) | **76.01 ms** | | Research 1.33× mapped-fiber reference | **96.26 ms** | | Estimated unamplified path loss | **1552.1 dB** | | Transparent optical spans / inline amplifiers | **98 / 97** | | Published RTT inflation over fiber floor | **1.91×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **133.73 ms** | | Average RTT | **138.5 ms** | | Maximum RTT | **150.99 ms** | | Standard deviation | **4.36 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms * [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-hkg-rtt). - **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. # Melbourne, Australia → Ashburn, USA RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. For the round from 2026-08-16T04:07:28Z, the 50 ICMP echo probes from Melbourne to Ashburn settled at an average of 203.9 ms, with a minimum of 194.63 ms and a maximum of 221.82 ms. No packets were lost, while jitter reached 6.81 ms and the standard deviation was 7.18 ms. This path ranks ninth among the 19 outbound routes measured from Melbourne and carries a Fair latency tier. The measured variability of about 3.5% of the average is slightly above the network-wide median of 3.28%, meaning the route is steady but not the tightest in the set. At 16,348.2 km apart, the absolute vacuum floor for this pair is 109.06 ms, while the realistic fiber floor sits at 160.09 ms. The observed average is 1.27 times the fiber floor and achieves 78.5% fiber efficiency, so the extra delay beyond physics is modest for a route of this length. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **203.9 ms** | | Jitter | **6.81 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **160.09 ms** | | Fiber Efficiency | **78.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,348.2 km** | | Vacuum RTT floor | **109.06 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **160.09 ms** | | Low-latency fiber material floor | **159.45 ms** | | Engineering floor (5% path allowance) | **168.12 ms** | | Research 1.33× mapped-fiber reference | **212.92 ms** | | Estimated unamplified path loss | **3433.1 dB** | | Transparent optical spans / inline amplifiers | **215 / 214** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **194.63 ms** | | Average RTT | **203.9 ms** | | Maximum RTT | **221.82 ms** | | Standard deviation | **7.18 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Melbourne latency and RTT](/docs/network/latency/pairs/iad-mel-rtt) — 203.9 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-iad-rtt). - **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. # Melbourne, Australia → Johannesburg, South Africa RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, Melbourne to Johannesburg ICMP RTT averaged 405.5 ms, with a minimum of 387.75 ms and a maximum of 464.78 ms across 50 samples. The latency tier is high, but packet loss was 0 percent, so the long delay is not accompanied by probes being dropped. This pairing ranks 19th by average RTT among the 19 outbound routes in the set, making it the slowest of the group by that measure. Its relative variation of about 4.1 percent is only moderately above the 3.28 percent median for the set, so the high latency is relatively consistent rather than erratic. The geodesic distance of 10,347 km sets a straight-line fiber floor of 101.33 ms. At 405.5 ms, the route runs at 4.00 times that floor and achieves 25 percent fiber efficiency, a useful route-specific signal that the actual distance penalty is the dominant factor in this connection's latency profile. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **405.5 ms** | | Jitter | **12.98 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **101.33 ms** | | Fiber Efficiency | **25%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **10,347 km** | | Vacuum RTT floor | **69.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **101.33 ms** | | Low-latency fiber material floor | **100.92 ms** | | Engineering floor (5% path allowance) | **106.41 ms** | | Research 1.33× mapped-fiber reference | **134.76 ms** | | Estimated unamplified path loss | **2172.9 dB** | | Transparent optical spans / inline amplifiers | **136 / 135** | | Published RTT inflation over fiber floor | **4×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **387.75 ms** | | Average RTT | **405.5 ms** | | Maximum RTT | **464.78 ms** | | Standard deviation | **16.64 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Melbourne latency and RTT](/docs/network/latency/pairs/jnb-mel-rtt) — 406.2 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Asia Pacific → Africa)** * [Singapore to Johannesburg latency and RTT](/docs/network/latency/pairs/sin-jnb-rtt) — 312.6 ms * [Hong Kong to Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt) — 316.7 ms * [Taipei to Johannesburg latency and RTT](/docs/network/latency/pairs/tpe-jnb-rtt) — 331 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-jnb-rtt). - **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. # Melbourne, Australia → Los Angeles, USA RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round from Melbourne to Los Angeles produced a Good latency result: an average of 148.4 ms, a minimum of 145.47 ms, a maximum of 157.53 ms, and zero packet loss. Jitter was 2.8 ms and the standard deviation was 2.96 ms, making this a tightly grouped set of probes. Ranked sixth among the 19 outbound routes measured from Melbourne, the route's variability of about 2.0% of the average is well below the network-wide median of 3.28%. This is a stable profile for a trans-Pacific path. The geodesic distance of 12,764 km gives a vacuum floor of 85.15 ms and a fiber floor of 125 ms. The observed average is 1.19 times the fiber floor, with 84.2% fiber efficiency, indicating the overhead over the theoretical minimum is relatively small. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **148.4 ms** | | Jitter | **2.8 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **125 ms** | | Fiber Efficiency | **84.2%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **12,764 km** | | Vacuum RTT floor | **85.15 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **125 ms** | | Low-latency fiber material floor | **124.49 ms** | | Engineering floor (5% path allowance) | **131.26 ms** | | Research 1.33× mapped-fiber reference | **166.24 ms** | | Estimated unamplified path loss | **2680.4 dB** | | Transparent optical spans / inline amplifiers | **168 / 167** | | Published RTT inflation over fiber floor | **1.19×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **145.47 ms** | | Average RTT | **148.4 ms** | | Maximum RTT | **157.53 ms** | | Standard deviation | **2.96 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Melbourne latency and RTT](/docs/network/latency/pairs/lax-mel-rtt) — 148.2 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-lax-rtt). - **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. # Melbourne, Australia → London, UK RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo round-trip time from Melbourne, Australia to London, UK averaged 252 ms over 50 probes, with a minimum of 239.89 ms and a maximum of 289.22 ms. The route's 16,898 km separation yields a theoretical vacuum floor of 112.73 ms and a straight-fiber floor of 165.48 ms, so the measured average is about 1.52 times the straight-fiber minimum. This path is one of 19 outbound routes measured for the network and is ranked 15th in that set. The standard deviation of 10.82 ms is about 4.3% of the 252 ms average, and jitter is 8.6 ms, putting the route slightly above the network's median variability of 3.28% of average RTT. The absolute spread is still small, and the sample recorded zero packet loss. The minimum RTT of 239.89 ms already sits 74.41 ms above the straight-fiber floor, indicating that most of the latency is a fixed consequence of the intercontinental distance and path geometry rather than a short-term problem. With a maximum-minimum range of 49.33 ms and no lost packets, these ICMP echo results describe a high-latency but relatively consistent path at the time of the round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **252 ms** | | Jitter | **8.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **165.48 ms** | | Fiber Efficiency | **65.7%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,898.4 km** | | Vacuum RTT floor | **112.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **165.48 ms** | | Low-latency fiber material floor | **164.82 ms** | | Engineering floor (5% path allowance) | **173.78 ms** | | Research 1.33× mapped-fiber reference | **220.09 ms** | | Estimated unamplified path loss | **3548.7 dB** | | Transparent optical spans / inline amplifiers | **222 / 221** | | Published RTT inflation over fiber floor | **1.52×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **239.89 ms** | | Average RTT | **252 ms** | | Maximum RTT | **289.22 ms** | | Standard deviation | **10.82 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Melbourne latency and RTT](/docs/network/latency/pairs/lon-mel-rtt) — 249.6 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-lon-rtt). - **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. # Melbourne, Australia → Miami, USA RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. For the round from 2026-08-16T04:07:28Z, the 50 ICMP echo probes from Melbourne to Miami recorded an average RTT of 201 ms, with a minimum of 191.59 ms and a maximum of 222.86 ms. Zero packets were lost, while jitter reached 7.48 ms and the standard deviation was 7.91 ms. This route ranks eighth among the 19 outbound paths measured from Melbourne and lands in the Fair latency tier. The measured spread is about 3.9% of the average, slightly above the network-wide median of 3.28%, so the delay profile is consistent but not exceptionally tight. Miami's role as the digital gateway between North and South America makes it a distinct destination, but the physical distance of 15,591.9 km still dominates: the vacuum floor is 104.02 ms and the fiber floor is 152.69 ms. The observed average is 1.32 times the fiber floor, with 76% fiber efficiency, indicating the route carries more overhead relative to the theoretical minimum. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **201 ms** | | Jitter | **7.48 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **152.69 ms** | | Fiber Efficiency | **76%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,591.9 km** | | Vacuum RTT floor | **104.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **152.69 ms** | | Low-latency fiber material floor | **152.07 ms** | | Engineering floor (5% path allowance) | **160.34 ms** | | Research 1.33× mapped-fiber reference | **203.07 ms** | | Estimated unamplified path loss | **3274.3 dB** | | Transparent optical spans / inline amplifiers | **205 / 204** | | Published RTT inflation over fiber floor | **1.32×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **191.59 ms** | | Average RTT | **201 ms** | | Maximum RTT | **222.86 ms** | | Standard deviation | **7.91 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Melbourne latency and RTT](/docs/network/latency/pairs/mia-mel-rtt) — 200.7 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-mia-rtt). - **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. # Melbourne, Australia → Moscow, Russia RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Melbourne, Australia to Moscow, Russia produced an average round-trip time of 236.1 ms across 50 probes, with a minimum of 226.33 ms and a maximum of 266.71 ms. Packet loss was zero and the latency tier was Fair. The measured average is 1.67 times the theoretical fiber floor of about 141.13 ms, yielding 59.8 percent fiber efficiency over a geodesic distance of 14,412.1 km. The larger inflation suggests that this route carries more distance-adjusted overhead than its raw geographic length alone would imply. Ranked 12th among the 19 route pairs in this measurement set, the route showed a standard deviation of 8.22 ms—about 3.5 percent of the average RTT—close to the route-set median of 3.28 percent. Jitter averaged 7.04 ms, and the spread between minimum and maximum RTT stayed under 41 ms. Moscow's position as a transit corridor between European and Asia-Pacific networks makes this a useful reference for east-west intercontinental round-trip behavior from Melbourne. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **236.1 ms** | | Jitter | **7.04 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **141.13 ms** | | Fiber Efficiency | **59.8%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,412.1 km** | | Vacuum RTT floor | **96.15 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **141.13 ms** | | Low-latency fiber material floor | **140.57 ms** | | Engineering floor (5% path allowance) | **148.21 ms** | | Research 1.33× mapped-fiber reference | **187.71 ms** | | Estimated unamplified path loss | **3026.5 dB** | | Transparent optical spans / inline amplifiers | **190 / 189** | | Published RTT inflation over fiber floor | **1.67×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **226.33 ms** | | Average RTT | **236.1 ms** | | Maximum RTT | **266.71 ms** | | Standard deviation | **8.22 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Melbourne latency and RTT](/docs/network/latency/pairs/mow-mel-rtt) — 235.9 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-mow-rtt). - **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. # Melbourne, Australia → Marseille, France RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Melbourne, Australia to Marseille, France returned an average round-trip time of 233.5 ms over 50 probes, with a low of 221.74 ms and a high of 271.93 ms. The route lost no packets and earned a Fair latency classification. Against a straight-line fiber path, this average is 1.44 times the theoretical fiber floor of roughly 162 ms, placing the route at 69.5 percent fiber efficiency over a geodesic distance of 16,579.2 km. That gap is a useful distance-adjusted sign of how intercontinental transport overhead accumulates. This route ranked 11th among the 19 route pairs measured in the same round. Its standard deviation of 10.3 ms is about 4.4 percent of the average RTT, somewhat above the route-set median of 3.28 percent, while jitter averaged 8.57 ms. Given Marseille's role as a Mediterranean cable landing hub, this measurement offers a useful Melbourne-to-southern-Europe reference point for steady, loss-free ICMP reachability. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **233.5 ms** | | Jitter | **8.57 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **162.36 ms** | | Fiber Efficiency | **69.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,579.2 km** | | Vacuum RTT floor | **110.6 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **162.36 ms** | | Low-latency fiber material floor | **161.7 ms** | | Engineering floor (5% path allowance) | **170.5 ms** | | Research 1.33× mapped-fiber reference | **215.93 ms** | | Estimated unamplified path loss | **3481.6 dB** | | Transparent optical spans / inline amplifiers | **218 / 217** | | Published RTT inflation over fiber floor | **1.44×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **221.74 ms** | | Average RTT | **233.5 ms** | | Maximum RTT | **271.93 ms** | | Standard deviation | **10.3 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Melbourne latency and RTT](/docs/network/latency/pairs/mrs-mel-rtt) — 234.2 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-mrs-rtt). - **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. # Melbourne, Australia → New York, USA RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round measured ICMP echo RTT between Melbourne, Australia and New York, USA across 50 samples. The average was 204.2 ms, with a minimum of 191.39 ms and a maximum of 227.39 ms; standard deviation was 8.13 ms, jitter was 7.67 ms, and packet loss was 0 percent. At a geodesic distance of 16,672 km, the vacuum floor is 111.22 ms and the fiber floor is 163.27 ms. The observed average sits 1.25 times the fiber floor, equal to an 80 percent fiber efficiency; the extra delay over the physical reference is modest in absolute terms. This route ranks 10th among 19 outbound routes in the same round, placing it in the middle of the set. Its standard deviation is about 4.0 percent of the average RTT, close to the median variability of 3.28 percent across the route set. With no packet loss and jitter under 8 ms, the main constraint is the absolute RTT rather than consistency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **204.2 ms** | | Jitter | **7.67 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **163.27 ms** | | Fiber Efficiency | **80%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **16,672 km** | | Vacuum RTT floor | **111.22 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **163.27 ms** | | Low-latency fiber material floor | **162.61 ms** | | Engineering floor (5% path allowance) | **171.45 ms** | | Research 1.33× mapped-fiber reference | **217.14 ms** | | Estimated unamplified path loss | **3501.1 dB** | | Transparent optical spans / inline amplifiers | **219 / 218** | | Published RTT inflation over fiber floor | **1.25×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **191.39 ms** | | Average RTT | **204.2 ms** | | Maximum RTT | **227.39 ms** | | Standard deviation | **8.13 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Melbourne latency and RTT](/docs/network/latency/pairs/nyc-mel-rtt) — 205.1 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-nyc-rtt). - **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. # Melbourne, Australia → Paris, France RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Melbourne, Australia to Paris, France averaged 246.5 ms over 50 probes, with a minimum of 234.28 ms and a maximum of 275.63 ms. No packets were lost, and the route was classified as Fair latency. The average RTT is 1.5 times the theoretical fiber floor of 164.4 ms, corresponding to 66.7 percent fiber efficiency over a geodesic distance of 16,787.7 km. The inflation above the fiber floor is modest for a route of this length. This route ranked 13th among the 19 route pairs measured in the same round. Its standard deviation of 8.75 ms is about 3.6 percent of the average RTT, slightly above the route-set median of 3.28 percent, while jitter averaged 6.84 ms. Because Paris sits on the dense Northwest European corridor, this measurement provides a practical Melbourne-to-France baseline for loss-free ICMP round trips into that regional market. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **246.5 ms** | | Jitter | **6.84 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **164.4 ms** | | Fiber Efficiency | **66.7%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,787.7 km** | | Vacuum RTT floor | **112 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **164.4 ms** | | Low-latency fiber material floor | **163.74 ms** | | Engineering floor (5% path allowance) | **172.64 ms** | | Research 1.33× mapped-fiber reference | **218.65 ms** | | Estimated unamplified path loss | **3525.4 dB** | | Transparent optical spans / inline amplifiers | **221 / 220** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **234.28 ms** | | Average RTT | **246.5 ms** | | Maximum RTT | **275.63 ms** | | Standard deviation | **8.75 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Melbourne latency and RTT](/docs/network/latency/pairs/par-mel-rtt) — 246.4 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-par-rtt). - **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. # Melbourne, Australia → Seattle, USA RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round recorded ICMP echo RTT from Melbourne, Australia to Seattle, USA with 50 samples. The average was 172.1 ms, the minimum 169 ms, and the maximum 187.7 ms; standard deviation was 3.51 ms, jitter was 2.55 ms, and packet loss was 0 percent. Given the geodesic distance of 13,166 km, the vacuum floor is 87.83 ms and the fiber floor is 128.93 ms. The observed average is 1.33 times the fiber floor, which puts fiber efficiency at 74.9 percent, a reasonable outcome for a route landing at Seattle's major trans-Pacific interconnection hub. This route ranks 7th among 19 outbound routes in the same round, placing it in the stronger half of the set. Its standard deviation is about 2.0 percent of the average RTT, clearly below the median variability of 3.28 percent across the route set. The combination of low jitter, zero packet loss, and a tight RTT distribution makes this a stable and efficient crossing. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **172.1 ms** | | Jitter | **2.55 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.93 ms** | | Fiber Efficiency | **74.9%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **13,166 km** | | Vacuum RTT floor | **87.83 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.93 ms** | | Low-latency fiber material floor | **128.41 ms** | | Engineering floor (5% path allowance) | **135.4 ms** | | Research 1.33× mapped-fiber reference | **171.48 ms** | | Estimated unamplified path loss | **2764.9 dB** | | Transparent optical spans / inline amplifiers | **173 / 172** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **169 ms** | | Average RTT | **172.1 ms** | | Maximum RTT | **187.7 ms** | | Standard deviation | **3.51 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Melbourne latency and RTT](/docs/network/latency/pairs/sea-mel-rtt) — 170.1 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-sea-rtt). - **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. # Melbourne, Australia → Singapore RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z ICMP echo round, 50 probes at 100 ms intervals from Melbourne, Australia to Singapore produced an average RTT of 88.4 ms, with a minimum of 83.08 ms and a maximum of 108.06 ms. Packet loss was zero and jitter measured 3.46 ms, so the path stayed within a Good latency tier. At roughly 6,047 km of geodesic separation, the theoretical fibre floor is 59.22 ms; the measured average is 1.49 times that floor, a 67% fibre efficiency score. The route is therefore closer to the idealised minimum than the distance alone might imply, while the 4.37 ms standard deviation shows a moderately stable distribution. The Singapore path is ranked second among this source's 19 outbound routes. Its relative RTT variability is about 4.94% of the average, above the 3.28% median for the set, so the low 88.4 ms average should be read alongside the wider 83.08–108.06 ms envelope; occasional probes near 108 ms are part of the normal pattern. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **88.4 ms** | | Jitter | **3.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **59.22 ms** | | Fiber Efficiency | **67%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,046.9 km** | | Vacuum RTT floor | **40.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **59.22 ms** | | Low-latency fiber material floor | **58.98 ms** | | Engineering floor (5% path allowance) | **62.18 ms** | | Research 1.33× mapped-fiber reference | **78.76 ms** | | Estimated unamplified path loss | **1269.9 dB** | | Transparent optical spans / inline amplifiers | **80 / 79** | | Published RTT inflation over fiber floor | **1.49×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **83.08 ms** | | Average RTT | **88.4 ms** | | Maximum RTT | **108.06 ms** | | Standard deviation | **4.37 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms * [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-sin-rtt). - **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. # Melbourne, Australia → Sydney, Australia RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z ICMP echo round, 50 probes at 100 ms intervals between Melbourne and Sydney, Australia returned an average RTT of 9.8 ms, with a minimum of 9.36 ms and a maximum of 11.08 ms. Packet loss was zero and jitter was just 0.31 ms, placing the route in the Ultra-Low latency tier. With a geodesic distance of 713.8 km, the fibre floor is 6.99 ms, so the measured average is 1.4 times that ideal and represents 71.3% fibre efficiency. The absolute spread is tiny: the standard deviation is only 0.40 ms, and the entire sample range spans less than 2 ms. Within the 19 outbound routes measured from Melbourne, this domestic path is ranked first. Its relative RTT variability of about 4.08% is higher than the 3.28% median for the set, but the absolute numbers are so small that the route remains effectively consistent; a 0.40 ms standard deviation and zero packet loss make it a reliable domestic latency reference. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **9.8 ms** | | Jitter | **0.31 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **6.99 ms** | | Fiber Efficiency | **71.3%** | | Latency Tier | Ultra-Low | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **713.8 km** | | Vacuum RTT floor | **4.76 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **6.99 ms** | | Low-latency fiber material floor | **6.96 ms** | | Engineering floor (5% path allowance) | **7.34 ms** | | Research 1.33× mapped-fiber reference | **9.3 ms** | | Estimated unamplified path loss | **149.9 dB** | | Transparent optical spans / inline amplifiers | **10 / 9** | | Published RTT inflation over fiber floor | **1.4×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **9.36 ms** | | Average RTT | **9.8 ms** | | Maximum RTT | **11.08 ms** | | Standard deviation | **0.4 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms * [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms **Fastest routes arriving at Sydney (SYD)** * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-syd-rtt). - **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. # Melbourne, Australia → Taipei, Taiwan RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, Melbourne to Taipei ICMP RTT averaged 143.2 ms, with a minimum of 135 ms and a maximum of 166.26 ms across 50 samples; packet loss was 0 percent. The 6.42 ms jitter and 7.11 ms standard deviation show a path that remains usable and stable despite a roughly 31 ms spread between best and worst samples. Within the 19 outbound routes in this measurement set, this pairing ranks fifth by average RTT. Its relative variation of about 5.0 percent is above the 3.28 percent median for the same set, so the route is quicker than most of the set while being a little less uniform than the typical route. The geodesic distance of 7,377.8 km sets a straight-line fiber floor of 72.25 ms. The measured average is 1.98 times that floor, for 50.5 percent fiber efficiency, and with zero packet loss the extra delay is best attributed to the longer path the packets actually travel rather than to loss or retransmission. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **143.2 ms** | | Jitter | **6.42 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.25 ms** | | Fiber Efficiency | **50.5%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,377.8 km** | | Vacuum RTT floor | **49.22 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.25 ms** | | Low-latency fiber material floor | **71.96 ms** | | Engineering floor (5% path allowance) | **75.87 ms** | | Research 1.33× mapped-fiber reference | **96.09 ms** | | Estimated unamplified path loss | **1549.3 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.98×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **135 ms** | | Average RTT | **143.2 ms** | | Maximum RTT | **166.26 ms** | | Standard deviation | **7.11 ms** | | Stdev / average | **5.0%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-tpe-rtt). - **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. # Melbourne, Australia → Tokyo, Japan RTT 🇦🇺 **Melbourne, Australia (MEL)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, Melbourne to Tokyo ICMP RTT averaged 112 ms, with a minimum of 105.34 ms and a maximum of 140.34 ms across 50 samples. Packet loss was 0 percent, and a jitter of 4.68 ms with a standard deviation of 5.58 ms points to a steady long-haul path that rarely drifts outside a narrow band. This route ranks third by average RTT among the 19 outbound routes in the set. Its variability is roughly 5.0 percent of the mean, which is above the 3.28 percent median for the set, so the route is among the fastest while still showing a bit more spread than the set's typical connection. For a geodesic distance of 8,156.1 km, the straight-line fiber floor is 79.87 ms. The observed average of 112 ms is only 1.40 times that floor, giving 71.3 percent fiber efficiency and showing that this pairing realizes a large share of the direct-distance speed potential despite its long geography. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **112 ms** | | Jitter | **4.68 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **79.87 ms** | | Fiber Efficiency | **71.3%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,156.1 km** | | Vacuum RTT floor | **54.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **79.87 ms** | | Low-latency fiber material floor | **79.55 ms** | | Engineering floor (5% path allowance) | **83.88 ms** | | Research 1.33× mapped-fiber reference | **106.23 ms** | | Estimated unamplified path loss | **1712.8 dB** | | Transparent optical spans / inline amplifiers | **108 / 107** | | Published RTT inflation over fiber floor | **1.4×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **105.34 ms** | | Average RTT | **112 ms** | | Maximum RTT | **140.34 ms** | | Standard deviation | **5.58 ms** | | Stdev / average | **5.0%** | ## Route Context * Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms **Fastest routes departing Melbourne (MEL)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Melbourne to Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms * [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mel-tyo-rtt). - **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. # Miami, USA → Amsterdam, Netherlands RTT 🇺🇸 **Miami, USA (MIA)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, Miami to Amsterdam returned an average ICMP RTT of 106 ms from 50 samples, with a minimum of 103.48 ms and a maximum of 113.5 ms. No packets were lost, and jitter held at 1.97 ms, so the route operated in the good latency tier throughout the test. The 7,457.8 km geodesic path has a vacuum-floor latency of 49.75 ms and a realistic fiber floor of 73.03 ms. At 106 ms average, the observed RTT is about 1.45 times that fiber floor, an efficiency of 68.9%, meaning the path covers the distance reasonably but with expected transatlantic network overhead. The route ranked 6th among the 19 outbound routes measured from Miami, placing it in the faster half. Its standard deviation of 2.2 ms equals about 2.1% of the average, below the network-wide median standard-deviation-to-average ratio of 3.28%, so the path displayed better-than-typical consistency as well. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **106 ms** | | Jitter | **1.97 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **73.03 ms** | | Fiber Efficiency | **68.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,457.8 km** | | Vacuum RTT floor | **49.75 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **73.03 ms** | | Low-latency fiber material floor | **72.74 ms** | | Engineering floor (5% path allowance) | **76.69 ms** | | Research 1.33× mapped-fiber reference | **97.13 ms** | | Estimated unamplified path loss | **1566.1 dB** | | Transparent optical spans / inline amplifiers | **98 / 97** | | Published RTT inflation over fiber floor | **1.45×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **103.48 ms** | | Average RTT | **106 ms** | | Maximum RTT | **113.5 ms** | | Standard deviation | **2.2 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Miami latency and RTT](/docs/network/latency/pairs/ams-mia-rtt) — 106 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-ams-rtt). - **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. # Miami, USA → Berlin, Germany RTT 🇺🇸 **Miami, USA (MIA)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, Miami to Berlin averaged 117.3 ms across 50 ICMP echo samples, with a low point of 113.83 ms and a peak of 127.02 ms. The route lost no packets, and jitter of 2.12 ms kept it within the good latency tier. Given the 8,009.8 km geodesic distance, the vacuum floor is 53.44 ms and the theoretical fiber floor is 78.44 ms. The observed average sits about 1.50 times above that fiber floor, an efficiency of 66.9%, which is a measurable overhead over the theoretical minimum for reaching this far into Central Europe. The route came in 10th out of 19 outbound routes measured from Miami, placing it near the middle of the group. Its standard deviation of 2.73 ms is roughly 2.3% of the average, below the network-wide median standard-deviation-to-average ratio of 3.28%, so the variation here was comparatively modest. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **117.3 ms** | | Jitter | **2.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **78.44 ms** | | Fiber Efficiency | **66.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,009.8 km** | | Vacuum RTT floor | **53.44 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **78.44 ms** | | Low-latency fiber material floor | **78.12 ms** | | Engineering floor (5% path allowance) | **82.37 ms** | | Research 1.33× mapped-fiber reference | **104.32 ms** | | Estimated unamplified path loss | **1682.1 dB** | | Transparent optical spans / inline amplifiers | **106 / 105** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **113.83 ms** | | Average RTT | **117.3 ms** | | Maximum RTT | **127.02 ms** | | Standard deviation | **2.73 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Miami latency and RTT](/docs/network/latency/pairs/ber-mia-rtt) — 118.3 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-ber-rtt). - **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. # Miami, USA → Frankfurt, Germany RTT 🇺🇸 **Miami, USA (MIA)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round for Miami to Frankfurt produced an average ICMP RTT of 112.2 ms over 50 samples, with a minimum of 108.19 ms and a maximum of 121.5 ms. There was zero packet loss, and jitter of 2.73 ms placed the path in the good latency tier. With a geodesic distance of 7,777.9 km, the vacuum floor is 51.89 ms and the theoretical fiber floor is 76.17 ms. The 112.2 ms average is about 1.47 times the fiber floor, or 67.9% fiber efficiency, showing a moderate amount of overhead beyond the shortest feasible optical path. The route placed 8th out of 19 outbound routes measured from Miami, just ahead of the midpoint. Its standard deviation of 3.61 ms represents about 3.2% of the average, slightly below the network-wide median standard-deviation-to-average ratio of 3.28%, so stability was broadly in line with typical performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **112.2 ms** | | Jitter | **2.73 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.17 ms** | | Fiber Efficiency | **67.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,777.9 km** | | Vacuum RTT floor | **51.89 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.17 ms** | | Low-latency fiber material floor | **75.86 ms** | | Engineering floor (5% path allowance) | **79.99 ms** | | Research 1.33× mapped-fiber reference | **101.3 ms** | | Estimated unamplified path loss | **1633.4 dB** | | Transparent optical spans / inline amplifiers | **103 / 102** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **108.19 ms** | | Average RTT | **112.2 ms** | | Maximum RTT | **121.5 ms** | | Standard deviation | **3.61 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Miami latency and RTT](/docs/network/latency/pairs/fra-mia-rtt) — 112 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-fra-rtt). - **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. # Miami, USA → São Paulo, Brazil RTT 🇺🇸 **Miami, USA (MIA)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo requests from Miami to São Paulo averaged 128.7 ms, with a minimum of 126.78 ms, a maximum of 136.62 ms, and zero packet loss across 50 samples. Over the 6,546.4 km geodesic distance, that average is 2.01 times the 64.11 ms fiber floor, or 49.8% straight-line fiber efficiency, and the sample stays tight with a 1.96 ms standard deviation and 1.47 ms jitter. The route ranked eleventh among the 19 routes measured in the same round; the median standard-deviation-to-average ratio across that route set was 3.28%, while this route's relative spread comes out around 1.5%, making the high latency notably steady. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **128.7 ms** | | Jitter | **1.47 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **64.11 ms** | | Fiber Efficiency | **49.8%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,546.4 km** | | Vacuum RTT floor | **43.67 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **64.11 ms** | | Low-latency fiber material floor | **63.85 ms** | | Engineering floor (5% path allowance) | **67.32 ms** | | Research 1.33× mapped-fiber reference | **85.26 ms** | | Estimated unamplified path loss | **1374.7 dB** | | Transparent optical spans / inline amplifiers | **86 / 85** | | Published RTT inflation over fiber floor | **2.01×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **126.78 ms** | | Average RTT | **128.7 ms** | | Maximum RTT | **136.62 ms** | | Standard deviation | **1.96 ms** | | Stdev / average | **1.5%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [North America to South America](/docs/network/latency/regions/north-america-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-gru-rtt). - **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. # Miami, USA → Hong Kong RTT 🇺🇸 **Miami, USA (MIA)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. During the measurement round 2026-08-16T04:07:28Z, ICMP echo requests from Miami to Hong Kong returned an average round-trip time of 199.5 ms across 50 samples, with a minimum of 188.29 ms and a maximum of 231.23 ms. Packet loss was 0 percent because every probe completed. The geodesic distance is 14,468.4 km, which sets a vacuum round-trip floor of 96.52 ms and a fiber floor of 141.69 ms. The observed 199.5 ms average is 1.41 times the fiber floor, an effective fiber efficiency near 71 percent, and the path falls into the 'Fair' latency tier. This path sat at position 16 among 19 measured outbound routes from this origin. Its 8.84 ms standard deviation is about 4.4 percent of the average, above the 3.28 percent median standard-deviation-to-average ratio across the measured set, and the 8.19 ms jitter reflects a broader timing spread across the 188.29 to 231.23 ms window. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **199.5 ms** | | Jitter | **8.19 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **141.69 ms** | | Fiber Efficiency | **71%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,468.4 km** | | Vacuum RTT floor | **96.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **141.69 ms** | | Low-latency fiber material floor | **141.12 ms** | | Engineering floor (5% path allowance) | **148.79 ms** | | Research 1.33× mapped-fiber reference | **188.44 ms** | | Estimated unamplified path loss | **3038.4 dB** | | Transparent optical spans / inline amplifiers | **190 / 189** | | Published RTT inflation over fiber floor | **1.41×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **188.29 ms** | | Average RTT | **199.5 ms** | | Maximum RTT | **231.23 ms** | | Standard deviation | **8.84 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Miami latency and RTT](/docs/network/latency/pairs/hkg-mia-rtt) — 201.1 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-hkg-rtt). - **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. # Miami, USA → Ashburn, USA RTT 🇺🇸 **Miami, USA (MIA)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Miami, USA, to Ashburn, USA, averaged 27.3 ms over 50 samples, with a 1.02 ms standard deviation, 0.94 ms jitter, and no packet loss. The minimum was 26.26 ms and the maximum 30.45 ms. The 1,493.2 km geodesic separation puts the round-trip vacuum floor near 10.0 ms and the fiber floor near 14.6 ms. The observed 27.3 ms average is 1.87 times the fiber floor, a 53.6% fiber efficiency result that still falls in the Ultra-Low latency tier. This route ranks first among the 19 outbound routes measured from Miami, though its standard-deviation-to-average ratio of about 3.7% is slightly above the network's median variability of 3.28%. The key takeaway is that Miami-to-Ashburn is the lowest-latency route in this outbound set for the round, with jitter below 1 ms and zero loss. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **27.3 ms** | | Jitter | **0.94 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **14.62 ms** | | Fiber Efficiency | **53.6%** | | Latency Tier | Ultra-Low | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,493.2 km** | | Vacuum RTT floor | **9.96 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **14.62 ms** | | Low-latency fiber material floor | **14.56 ms** | | Engineering floor (5% path allowance) | **15.36 ms** | | Research 1.33× mapped-fiber reference | **19.45 ms** | | Estimated unamplified path loss | **313.6 dB** | | Transparent optical spans / inline amplifiers | **20 / 19** | | Published RTT inflation over fiber floor | **1.87×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **26.26 ms** | | Average RTT | **27.3 ms** | | Maximum RTT | **30.45 ms** | | Standard deviation | **1.02 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms **Fastest routes departing Miami (MIA)** * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms * [Miami to Amsterdam latency and RTT](/docs/network/latency/pairs/mia-ams-rtt) — 106 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms * [Paris to Ashburn latency and RTT](/docs/network/latency/pairs/par-iad-rtt) — 75.5 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-iad-rtt). - **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. # Miami, USA → Johannesburg, South Africa RTT 🇺🇸 **Miami, USA (MIA)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT run from Miami, USA to Johannesburg, South Africa averaged 259.8 ms over 50 samples, with a minimum of 252.44 ms and a maximum of 277.9 ms. Zero packet loss, a 6.11 ms standard deviation, and 5.21 ms jitter show that the high-latency classification is driven by distance rather than instability. At a geodesic distance of 12,945.8 km, the theoretical fiber-floor RTT is 126.78 ms. The observed average is 2.05x that floor, which corresponds to a fiber efficiency of 48.8% — in other words, the measured path uses about 49% of the theoretical optical speed limit. This route ranked 19th of 19 outbound routes in the network's measurement set. Its standard deviation relative to average RTT was 2.35%, below the 3.28% median across that set, so even at 259.8 ms the connection is more predictable than its rank might suggest. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **259.8 ms** | | Jitter | **5.21 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **126.78 ms** | | Fiber Efficiency | **48.8%** | | Latency Tier | High | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,945.8 km** | | Vacuum RTT floor | **86.36 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **126.78 ms** | | Low-latency fiber material floor | **126.27 ms** | | Engineering floor (5% path allowance) | **133.13 ms** | | Research 1.33× mapped-fiber reference | **168.61 ms** | | Estimated unamplified path loss | **2718.6 dB** | | Transparent optical spans / inline amplifiers | **170 / 169** | | Published RTT inflation over fiber floor | **2.05×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **252.44 ms** | | Average RTT | **259.8 ms** | | Maximum RTT | **277.9 ms** | | Standard deviation | **6.11 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Miami latency and RTT](/docs/network/latency/pairs/jnb-mia-rtt) — 259.9 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (North America → Africa)** * [New York to Johannesburg latency and RTT](/docs/network/latency/pairs/nyc-jnb-rtt) — 221.5 ms * [Ashburn to Johannesburg latency and RTT](/docs/network/latency/pairs/iad-jnb-rtt) — 228.3 ms * [Seattle to Johannesburg latency and RTT](/docs/network/latency/pairs/sea-jnb-rtt) — 282.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-jnb-rtt). - **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. # Miami, USA → Los Angeles, USA RTT 🇺🇸 **Miami, USA (MIA)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Miami, USA, to Los Angeles, USA, averaged 56.8 ms across 50 samples, with a 2.11 ms standard deviation, 1.82 ms jitter, and no packet loss. The minimum was 54.44 ms and the maximum 64.31 ms, a spread of about 9.9 ms. The geodesic distance of 3,764.3 km implies a round-trip vacuum floor of 25.1 ms and a fiber floor of 36.9 ms, placing the 56.8 ms average at 1.54 times the fiber floor and a 64.9% fiber efficiency figure. This route ranks 3rd among the 19 outbound routes measured from Miami, and its standard-deviation-to-average ratio of about 3.7% is slightly above the network's median variability of 3.28%. While the typical latency is solid, the maximum observation of 64.31 ms shows the path can add roughly 8 ms beyond the average in this round, so latency budgets should include a modest cushion. Key takeaway: Miami-to-Los Angeles delivered loss-free, sub-65 ms RTT in this measurement round, with efficiency that fits a coast-to-coast hop. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **56.8 ms** | | Jitter | **1.82 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **36.86 ms** | | Fiber Efficiency | **64.9%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,764.3 km** | | Vacuum RTT floor | **25.11 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **36.86 ms** | | Low-latency fiber material floor | **36.71 ms** | | Engineering floor (5% path allowance) | **38.71 ms** | | Research 1.33× mapped-fiber reference | **49.03 ms** | | Estimated unamplified path loss | **790.5 dB** | | Transparent optical spans / inline amplifiers | **50 / 49** | | Published RTT inflation over fiber floor | **1.54×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **54.44 ms** | | Average RTT | **56.8 ms** | | Maximum RTT | **64.31 ms** | | Standard deviation | **2.11 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms * [Miami to Amsterdam latency and RTT](/docs/network/latency/pairs/mia-ams-rtt) — 106 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [London to Los Angeles latency and RTT](/docs/network/latency/pairs/lon-lax-rtt) — 127.5 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-lax-rtt). - **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. # Miami, USA → London, UK RTT 🇺🇸 **Miami, USA (MIA)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z run, Miami, USA to London, UK returned a 101.8 ms average ICMP echo RTT, with zero packet loss across 50 samples and a Good latency tier. The minimum observed was 96.22 ms and the maximum 114.36 ms, giving 2.93 ms of jitter. At a geodesic distance of 7,138.4 km, the theoretical fiber-floor latency is 69.9 ms, so the measured average sits 1.46 times above that floor and corresponds to about 68.7% fiber efficiency. The 96.22 ms minimum shows the best sample came within 26.3 ms of the fiber floor, a useful benchmark for a transatlantic gateway route. This route ranked 5th among the 19 outbound routes measured by the same network in the same window. Its standard deviation of 3.81 ms is about 3.7% of the average, slightly above the network median variability of 3.28%, while the 0% loss and modest jitter keep the route within a reliable range for ICMP-based latency checks. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **101.8 ms** | | Jitter | **2.93 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **69.9 ms** | | Fiber Efficiency | **68.7%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,138.4 km** | | Vacuum RTT floor | **47.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **69.9 ms** | | Low-latency fiber material floor | **69.62 ms** | | Engineering floor (5% path allowance) | **73.41 ms** | | Research 1.33× mapped-fiber reference | **92.97 ms** | | Estimated unamplified path loss | **1499.1 dB** | | Transparent optical spans / inline amplifiers | **94 / 93** | | Published RTT inflation over fiber floor | **1.46×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **96.22 ms** | | Average RTT | **101.8 ms** | | Maximum RTT | **114.36 ms** | | Standard deviation | **3.81 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to Amsterdam latency and RTT](/docs/network/latency/pairs/mia-ams-rtt) — 106 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-lon-rtt). - **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. # Miami, USA → Melbourne, Australia RTT 🇺🇸 **Miami, USA (MIA)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. During the measurement round 2026-08-16T04:07:28Z, ICMP echo requests from Miami to Melbourne produced an average round-trip time of 200.7 ms over 50 samples, with a minimum of 190.44 ms and a maximum of 231.45 ms. No probes were dropped, so the packet loss rate was 0 percent. The path spans 15,591.9 km, corresponding to a vacuum round-trip floor of 104.02 ms and a fiber floor of 152.69 ms. The average is 1.31 times the fiber floor, about 76.1 percent fiber efficiency, and the route is placed in the 'Fair' latency tier. This path was ranked 17th among 19 measured outbound routes from this origin. The 9.1 ms standard deviation is about 4.5 percent of the average, above the 3.28 percent median standard-deviation-to-average ratio across the measured set, and jitter of 6.99 ms leaves the 190.44 to 231.45 ms range with a spread of just over 41 ms. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **200.7 ms** | | Jitter | **6.99 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **152.69 ms** | | Fiber Efficiency | **76.1%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,591.9 km** | | Vacuum RTT floor | **104.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **152.69 ms** | | Low-latency fiber material floor | **152.07 ms** | | Engineering floor (5% path allowance) | **160.34 ms** | | Research 1.33× mapped-fiber reference | **203.07 ms** | | Estimated unamplified path loss | **3274.3 dB** | | Transparent optical spans / inline amplifiers | **205 / 204** | | Published RTT inflation over fiber floor | **1.31×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **190.44 ms** | | Average RTT | **200.7 ms** | | Maximum RTT | **231.45 ms** | | Standard deviation | **9.1 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Miami latency and RTT](/docs/network/latency/pairs/mel-mia-rtt) — 201 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-mel-rtt). - **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. # Miami, USA → Moscow, Russia RTT 🇺🇸 **Miami, USA (MIA)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement for Miami, USA to Moscow, Russia returned an average ICMP echo RTT of 145.5 ms, with zero packet loss across 50 samples and a Good latency tier. The minimum was 142.62 ms, the maximum 152.94 ms, and jitter was just 1.94 ms. Given 9,239.8 km of geodesic distance, the fiber floor is around 90.48 ms, putting the measured average 1.61 times above that floor, or roughly 62.2% fiber efficiency. That inflation factor is the highest among the three route pairs in this set, and the 145.5 ms average still falls within a Good latency tier. This route ranked 12th among the 19 outbound routes measured by the same network. Its standard deviation of 2.55 ms is only about 1.75% of the average, well below the 3.28% network median variability; the low jitter and zero loss mean that, while absolute latency is high, the route is unusually stable and predictable. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **145.5 ms** | | Jitter | **1.94 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **90.48 ms** | | Fiber Efficiency | **62.2%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,239.8 km** | | Vacuum RTT floor | **61.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **90.48 ms** | | Low-latency fiber material floor | **90.12 ms** | | Engineering floor (5% path allowance) | **95.02 ms** | | Research 1.33× mapped-fiber reference | **120.34 ms** | | Estimated unamplified path loss | **1940.4 dB** | | Transparent optical spans / inline amplifiers | **122 / 121** | | Published RTT inflation over fiber floor | **1.61×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **142.62 ms** | | Average RTT | **145.5 ms** | | Maximum RTT | **152.94 ms** | | Standard deviation | **2.55 ms** | | Stdev / average | **1.8%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Miami latency and RTT](/docs/network/latency/pairs/mow-mia-rtt) — 144.5 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-mow-rtt). - **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. # Miami, USA → Marseille, France RTT 🇺🇸 **Miami, USA (MIA)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z window, Miami, USA to Marseille, France averaged 113.7 ms on ICMP echo RTT, with zero loss across 50 samples and a Good latency tier. The minimum was 110.36 ms, the maximum 126.2 ms, and jitter was 2.44 ms. With 7,752.4 km between the cities, the fiber floor is about 75.92 ms; the measured average is 1.50 times that floor, equivalent to roughly 66.8% fiber efficiency. The minimum of 110.36 ms leaves a 34.4 ms overhead above that floor, while the full range of samples stayed within a 15.84 ms band. Among the 19 outbound routes in the same measurement set, Miami-Marseille ranked 9th by RTT. Its standard deviation of 3.72 ms equals about 3.3% of the average, effectively matching the 3.28% network median variability; the combination of stable spread, 2.44 ms jitter, and no loss makes this a dependable route despite the 113.7 ms average. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **113.7 ms** | | Jitter | **2.44 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **75.92 ms** | | Fiber Efficiency | **66.8%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,752.4 km** | | Vacuum RTT floor | **51.72 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **75.92 ms** | | Low-latency fiber material floor | **75.61 ms** | | Engineering floor (5% path allowance) | **79.72 ms** | | Research 1.33× mapped-fiber reference | **100.97 ms** | | Estimated unamplified path loss | **1628 dB** | | Transparent optical spans / inline amplifiers | **102 / 101** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **110.36 ms** | | Average RTT | **113.7 ms** | | Maximum RTT | **126.2 ms** | | Standard deviation | **3.72 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Miami latency and RTT](/docs/network/latency/pairs/mrs-mia-rtt) — 112.4 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-mrs-rtt). - **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. # Miami, USA → New York, USA RTT 🇺🇸 **Miami, USA (MIA)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo requests from Miami to New York averaged 33.3 ms, with a minimum of 31.68 ms, a maximum of 39.04 ms, and zero packet loss across 50 samples. The observed average is 1.94 times the straight-line fiber floor of 17.17 ms over the 1,753.2 km geodesic distance, or 51.6% straight-line fiber efficiency, so the route stays reasonably close to the physical latency limit. Ranked second among the 19 routes measured in the same round, this path sits in an Excellent tier; the median standard-deviation-to-average ratio across that route set was 3.28%, while its own 1.51 ms standard deviation and 1.24 ms jitter keep the absolute spread compact. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **33.3 ms** | | Jitter | **1.24 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **17.17 ms** | | Fiber Efficiency | **51.6%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,753.2 km** | | Vacuum RTT floor | **11.7 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **17.17 ms** | | Low-latency fiber material floor | **17.1 ms** | | Engineering floor (5% path allowance) | **18.03 ms** | | Research 1.33× mapped-fiber reference | **22.83 ms** | | Estimated unamplified path loss | **368.2 dB** | | Transparent optical spans / inline amplifiers | **24 / 23** | | Published RTT inflation over fiber floor | **1.94×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **31.68 ms** | | Average RTT | **33.3 ms** | | Maximum RTT | **39.04 ms** | | Standard deviation | **1.51 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms * [Miami to Amsterdam latency and RTT](/docs/network/latency/pairs/mia-ams-rtt) — 106 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms **Same corridor (North America → North America)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-nyc-rtt). - **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. # Miami, USA → Paris, France RTT 🇺🇸 **Miami, USA (MIA)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Miami, USA, to Paris, France, averaged 106.2 ms across 50 samples, with a 1.69 ms standard deviation, 1.31 ms jitter, and zero packet loss. The minimum was 104.35 ms and the maximum 111.43 ms, so the full spread stayed near 7 ms. The geodesic distance of 7,368.8 km implies a round-trip vacuum floor of about 49.2 ms and a practical fiber floor of 72.2 ms; the observed 106.2 ms average is 1.47 times that fiber floor, a 67.9% fiber efficiency figure. This route ranks 7th among the 19 outbound routes measured from Miami, and its standard-deviation-to-average ratio of about 1.6% is below the network's median variability of 3.28%. Useful takeaway: in this round, Miami-to-Paris latency is consistently between roughly 104 ms and 112 ms with no loss, making it a stable choice for operators building transatlantic latency budgets. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **106.2 ms** | | Jitter | **1.31 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.16 ms** | | Fiber Efficiency | **67.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,368.8 km** | | Vacuum RTT floor | **49.16 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.16 ms** | | Low-latency fiber material floor | **71.87 ms** | | Engineering floor (5% path allowance) | **75.78 ms** | | Research 1.33× mapped-fiber reference | **95.97 ms** | | Estimated unamplified path loss | **1547.4 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **104.35 ms** | | Average RTT | **106.2 ms** | | Maximum RTT | **111.43 ms** | | Standard deviation | **1.69 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Miami latency and RTT](/docs/network/latency/pairs/par-mia-rtt) — 106.8 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-par-rtt). - **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. # Miami, USA → Seattle, USA RTT 🇺🇸 **Miami, USA (MIA)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo requests from Miami to Seattle in the 2026-08-16T04:07:28Z round averaged 81.9 ms, with a minimum of 78.54 ms, a maximum of 93.5 ms, and no packet loss over 50 samples. Against the 4,399.4 km geodesic distance, that average is 1.9 times the 43.08 ms fiber floor, or 52.6% straight-line fiber efficiency; the 3.48 ms standard deviation and 2.63 ms jitter show a wider but still loss-free spread. The route ranked fourth among the 19 routes measured in the same round; the median standard-deviation-to-average ratio across that route set was 3.28%, so this route's relative spread sits above that median for transcontinental North American paths. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **81.9 ms** | | Jitter | **2.63 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **43.08 ms** | | Fiber Efficiency | **52.6%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **4,399.4 km** | | Vacuum RTT floor | **29.35 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **43.08 ms** | | Low-latency fiber material floor | **42.91 ms** | | Engineering floor (5% path allowance) | **45.24 ms** | | Research 1.33× mapped-fiber reference | **57.3 ms** | | Estimated unamplified path loss | **923.9 dB** | | Transparent optical spans / inline amplifiers | **58 / 57** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **78.54 ms** | | Average RTT | **81.9 ms** | | Maximum RTT | **93.5 ms** | | Standard deviation | **3.48 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms * [Miami to Amsterdam latency and RTT](/docs/network/latency/pairs/mia-ams-rtt) — 106 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-sea-rtt). - **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. # Miami, USA → Singapore RTT 🇺🇸 **Miami, USA (MIA)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. During the measurement round 2026-08-16T04:07:28Z, ICMP echo requests from Miami to Singapore returned an average round-trip time of 223.1 ms over 50 samples, with a minimum of 218.84 ms and a maximum of 234.03 ms. Every probe completed, leaving the packet loss rate at 0 percent. The route spans about 16,978.7 km, giving a vacuum round-trip floor of 113.27 ms and a fiber floor of 166.27 ms. The measured 223.1 ms average is 1.34 times the fiber floor, about 74.5 percent fiber efficiency, which matches the 'Fair' latency tier. The path was ranked 18th among 19 measured outbound routes from this origin. Its 3.52 ms standard deviation is only about 1.6 percent of the average, well below the 3.28 percent median standard-deviation-to-average ratio across the measured set, and jitter was 2.98 ms. The resulting 218.84 to 234.03 ms window kept sample delays tightly grouped. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **223.1 ms** | | Jitter | **2.98 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **166.27 ms** | | Fiber Efficiency | **74.5%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,978.7 km** | | Vacuum RTT floor | **113.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **166.27 ms** | | Low-latency fiber material floor | **165.6 ms** | | Engineering floor (5% path allowance) | **174.6 ms** | | Research 1.33× mapped-fiber reference | **221.14 ms** | | Estimated unamplified path loss | **3565.5 dB** | | Transparent optical spans / inline amplifiers | **223 / 222** | | Published RTT inflation over fiber floor | **1.34×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **218.84 ms** | | Average RTT | **223.1 ms** | | Maximum RTT | **234.03 ms** | | Standard deviation | **3.52 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Miami latency and RTT](/docs/network/latency/pairs/sin-mia-rtt) — 221.7 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-sin-rtt). - **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. # Miami, USA → Sydney, Australia RTT 🇺🇸 **Miami, USA (MIA)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Miami, USA to Sydney, Australia averaged 191.5 ms across 50 samples, with a minimum of 181.65 ms and a maximum of 213.36 ms. The 7.74 ms standard deviation and 6.14 ms jitter show a noticeable spread, but every one of the 50 probes returned, so packet loss is not part of that spread. The geodesic distance of 15,029.6 km gives a vacuum speed-of-light floor of 100.27 ms and a fiber-based floor of 147.18 ms; the observed mean is about 1.30 times the fiber floor, or roughly 76.9% fiber efficiency. The gap from the 181.65 ms minimum to the 213.36 ms maximum means the route's extra latency is not uniform across probes. This destination ranked 15th among the 19 outbound routes measured from Miami, meaning 14 of those routes were faster and 4 were slower in this round. Its standard deviation equals about 4.0% of the average, above the network-wide median of 3.28% of average, so the variability near the upper end is the main feature to watch on this long path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **191.5 ms** | | Jitter | **6.14 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **147.18 ms** | | Fiber Efficiency | **76.9%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,029.6 km** | | Vacuum RTT floor | **100.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **147.18 ms** | | Low-latency fiber material floor | **146.59 ms** | | Engineering floor (5% path allowance) | **154.56 ms** | | Research 1.33× mapped-fiber reference | **195.75 ms** | | Estimated unamplified path loss | **3156.2 dB** | | Transparent optical spans / inline amplifiers | **198 / 197** | | Published RTT inflation over fiber floor | **1.3×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **181.65 ms** | | Average RTT | **191.5 ms** | | Maximum RTT | **213.36 ms** | | Standard deviation | **7.74 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Miami latency and RTT](/docs/network/latency/pairs/syd-mia-rtt) — 191.5 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-syd-rtt). - **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. # Miami, USA → Taipei, Taiwan RTT 🇺🇸 **Miami, USA (MIA)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Miami, USA to Taipei, Taiwan averaged 185.1 ms over 50 samples, with a minimum of 178.34 ms and a maximum of 197.2 ms. The 5.13 ms standard deviation and 4.64 ms jitter indicate a tightly grouped result, and all 50 echoes were answered. At a geodesic distance of 13,918.7 km, the vacuum floor is 92.86 ms and the fiber floor is 136.3 ms; the measured mean sits about 1.36 times the fiber floor, corresponding to 73.6% fiber efficiency. The narrow min-to-max range of 18.86 ms shows that the overhead is fairly consistent across every sample rather than driven by occasional outliers. Ranked 14th among Miami's 19 outbound routes, Taipei's average RTT was slower than 13 of those routes and faster than 5. Its standard deviation is roughly 2.77% of the average, below the network-wide median of 3.28% of average, so the route's stability is actually better than the typical outbound path despite the higher average latency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **185.1 ms** | | Jitter | **4.64 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **136.3 ms** | | Fiber Efficiency | **73.6%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,918.7 km** | | Vacuum RTT floor | **92.86 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **136.3 ms** | | Low-latency fiber material floor | **135.76 ms** | | Engineering floor (5% path allowance) | **143.14 ms** | | Research 1.33× mapped-fiber reference | **181.28 ms** | | Estimated unamplified path loss | **2922.9 dB** | | Transparent optical spans / inline amplifiers | **183 / 182** | | Published RTT inflation over fiber floor | **1.36×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **178.34 ms** | | Average RTT | **185.1 ms** | | Maximum RTT | **197.2 ms** | | Standard deviation | **5.13 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Miami latency and RTT](/docs/network/latency/pairs/tpe-mia-rtt) — 185.7 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-tpe-rtt). - **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. # Miami, USA → Tokyo, Japan RTT 🇺🇸 **Miami, USA (MIA)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, Miami-to-Tokyo ICMP echo RTT averaged 156.3 ms across 50 samples, with a minimum of 149.17 ms and a maximum of 178.72 ms. The 6.19 ms standard deviation and 4.99 ms jitter reflect a moderate spread, while 0% packet loss means all probes completed. The direct-line distance of 12,019.9 km sets a vacuum floor of 80.19 ms and a fiber floor of 117.71 ms; the observed average is about 1.33 times the fiber floor, or 75.3% fiber efficiency. The maximum sits 22.42 ms above the average, while the minimum is only 7.13 ms below it, so the spread is more visible at the high end of the sample. This path ranked 13th among Miami's 19 outbound routes, with 12 routes faster and 6 slower in the same round. Its standard deviation is about 3.96% of the average, above the network-wide median of 3.28% of average, which makes the upper tail worth examining even though most probes cluster near the lower end of the measured range. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **156.3 ms** | | Jitter | **4.99 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **117.71 ms** | | Fiber Efficiency | **75.3%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,019.9 km** | | Vacuum RTT floor | **80.19 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **117.71 ms** | | Low-latency fiber material floor | **117.24 ms** | | Engineering floor (5% path allowance) | **123.61 ms** | | Research 1.33× mapped-fiber reference | **156.55 ms** | | Estimated unamplified path loss | **2524.2 dB** | | Transparent optical spans / inline amplifiers | **158 / 157** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **149.17 ms** | | Average RTT | **156.3 ms** | | Maximum RTT | **178.72 ms** | | Standard deviation | **6.19 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Miami latency and RTT](/docs/network/latency/pairs/tyo-mia-rtt) — 156.5 ms **Fastest routes departing Miami (MIA)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mia-tyo-rtt). - **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. # Moscow, Russia → Amsterdam, Netherlands RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Moscow to Amsterdam averaged **37.6 ms** across 50 samples, with a minimum of 37.09 ms and a maximum of 39.9 ms. Packet loss was 0%, jitter was 0.36 ms, and the route reached an Excellent latency tier with a sample spread of just 2.81 ms. The geodesic distance of 2,154.6 km corresponds to a vacuum floor of 14.37 ms and a fiber floor of 21.1 ms. At 37.6 ms, the observed RTT is 1.78 times the fiber floor, or 56.1% fiber efficiency, pointing to a comparatively direct path between Moscow and Amsterdam. Ranked 3rd among 19 outbound routes in the same round, Moscow–Amsterdam is clearly positioned at the faster end. Its standard deviation of 0.57 ms is about 1.5% of the average RTT, below the network-wide median of 3.28%, so the route is both quick and highly predictable. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **37.6 ms** | | Jitter | **0.36 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **21.1 ms** | | Fiber Efficiency | **56.1%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,154.6 km** | | Vacuum RTT floor | **14.37 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **21.1 ms** | | Low-latency fiber material floor | **21.02 ms** | | Engineering floor (5% path allowance) | **22.16 ms** | | Research 1.33× mapped-fiber reference | **28.06 ms** | | Estimated unamplified path loss | **452.5 dB** | | Transparent optical spans / inline amplifiers | **29 / 28** | | Published RTT inflation over fiber floor | **1.78×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **37.09 ms** | | Average RTT | **37.6 ms** | | Maximum RTT | **39.9 ms** | | Standard deviation | **0.57 ms** | | Stdev / average | **1.5%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-ams-rtt). - **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. # Moscow, Russia → Berlin, Germany RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round sent 50 ICMP echo requests from Moscow to Berlin at 100ms intervals and recorded an average round-trip time of 27.5ms, with a 26.72ms minimum and a 29.96ms maximum. The standard deviation was 0.74ms, jitter was 0.54ms, and no packets were lost. Over the 1,613.5km geodesic path, the speed-of-light vacuum floor is 10.76ms and the fiber floor is 15.8ms. The observed average is 1.74 times the fiber floor, corresponding to a 57.5% fiber efficiency figure. This route ranked first among the 19 outbound routes in the round. Its standard deviation of 0.74ms is about 2.7% of the average, below the 3.28% median ratio for the outbound route set, so the path combined 0% loss with unusually stable sub-millisecond variation. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **27.5 ms** | | Jitter | **0.54 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **15.8 ms** | | Fiber Efficiency | **57.5%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,613.5 km** | | Vacuum RTT floor | **10.76 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **15.8 ms** | | Low-latency fiber material floor | **15.74 ms** | | Engineering floor (5% path allowance) | **16.59 ms** | | Research 1.33× mapped-fiber reference | **21.01 ms** | | Estimated unamplified path loss | **338.8 dB** | | Transparent optical spans / inline amplifiers | **22 / 21** | | Published RTT inflation over fiber floor | **1.74×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **26.72 ms** | | Average RTT | **27.5 ms** | | Maximum RTT | **29.96 ms** | | Standard deviation | **0.74 ms** | | Stdev / average | **2.7%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-ber-rtt). - **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. # Moscow, Russia → Frankfurt, Germany RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round sent 50 ICMP echo requests from Moscow to Frankfurt at 100ms intervals and recorded an average round-trip time of 35.9ms, with a 33.56ms minimum and a 42.93ms maximum. Standard deviation was 1.78ms, jitter was 1.52ms, and no packets were lost. Frankfurt is a central switching point of the European fiber ring. For the 2,026.8km geodesic path, the vacuum floor is 13.52ms and the fiber floor is 19.85ms; the observed average is 1.81 times that fiber floor, with a 55.3% fiber efficiency figure. This route ranked second among the 19 outbound routes, but its relative variability is about 5.0% of the average, above the 3.28% median ratio for the outbound route set. The 9.37ms gap between the minimum and maximum shows that individual probes varied more than the route's strong rank alone might suggest. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **35.9 ms** | | Jitter | **1.52 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **19.85 ms** | | Fiber Efficiency | **55.3%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,026.8 km** | | Vacuum RTT floor | **13.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **19.85 ms** | | Low-latency fiber material floor | **19.77 ms** | | Engineering floor (5% path allowance) | **20.84 ms** | | Research 1.33× mapped-fiber reference | **26.4 ms** | | Estimated unamplified path loss | **425.6 dB** | | Transparent optical spans / inline amplifiers | **27 / 26** | | Published RTT inflation over fiber floor | **1.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **33.56 ms** | | Average RTT | **35.9 ms** | | Maximum RTT | **42.93 ms** | | Standard deviation | **1.78 ms** | | Stdev / average | **5.0%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-fra-rtt). - **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. # Moscow, Russia → São Paulo, Brazil RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z ICMP echo round, Moscow to São Paulo averaged 214.4 ms across 50 samples, with a minimum of 203.61 ms and a maximum of 257.23 ms. The round recorded zero packet loss. With a great-circle distance near 11,791 km, the fiber floor is about 115.5 ms, so the average represents 1.86 times that floor and a fiber efficiency of 53.9 percent. The path’s 10.55 ms standard deviation and 8.94 ms jitter are modest for the distance, but the 53.6 ms gap between minimum and maximum shows occasional larger swings. In the Moscow outbound set, this route ranked 17th among 19 paths, while the median variability was 3.28 percent of average latency. São Paulo’s own variability of 10.55 ms is about 4.9 percent of the 214.4 ms average, placing it on the higher-variability side despite stable reachability. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **214.4 ms** | | Jitter | **8.94 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **115.47 ms** | | Fiber Efficiency | **53.9%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,791.1 km** | | Vacuum RTT floor | **78.66 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **115.47 ms** | | Low-latency fiber material floor | **115 ms** | | Engineering floor (5% path allowance) | **121.26 ms** | | Research 1.33× mapped-fiber reference | **153.57 ms** | | Estimated unamplified path loss | **2476.1 dB** | | Transparent optical spans / inline amplifiers | **155 / 154** | | Published RTT inflation over fiber floor | **1.86×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **203.61 ms** | | Average RTT | **214.4 ms** | | Maximum RTT | **257.23 ms** | | Standard deviation | **10.55 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Moscow latency and RTT](/docs/network/latency/pairs/gru-mow-rtt) — 219.5 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Europe → South America)** * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms * [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms * [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-gru-rtt). - **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. # Moscow, Russia → Hong Kong RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z ICMP echo round, Moscow to Hong Kong averaged 118.6 ms across 50 samples, with a narrow range from 116.41 ms to 127.8 ms and zero packet loss. A standard deviation of 2.24 ms and jitter of 1.64 ms make this a notably stable path. The great-circle distance of about 7,154 km implies a fiber floor near 70.1 ms, so the observed mean is 1.69 times that floor and fiber efficiency reaches 59.1 percent. The steady sample distribution confirms the route is behaving close to its physical potential. This route ranked 9th among 19 Moscow outbound paths, and the median variability across the Moscow outbound set was 3.28 percent of average latency. Its own standard deviation is only about 1.9 percent of the average, so latency is not just low—it is also unusually consistent for this outbound set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **118.6 ms** | | Jitter | **1.64 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **70.05 ms** | | Fiber Efficiency | **59.1%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,153.6 km** | | Vacuum RTT floor | **47.72 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **70.05 ms** | | Low-latency fiber material floor | **69.77 ms** | | Engineering floor (5% path allowance) | **73.57 ms** | | Research 1.33× mapped-fiber reference | **93.17 ms** | | Estimated unamplified path loss | **1502.3 dB** | | Transparent optical spans / inline amplifiers | **94 / 93** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **116.41 ms** | | Average RTT | **118.6 ms** | | Maximum RTT | **127.8 ms** | | Standard deviation | **2.24 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-hkg-rtt). - **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. # Moscow, Russia → Ashburn, USA RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Moscow to Ashburn averaged 113.9 ms over 50 samples, with a minimum of 107.82 ms and a maximum of 129.74 ms. The route had zero packet loss, though jitter of 4.1 ms and a 5.37 ms standard deviation place it in the good latency tier rather than excellent. For a geodesic separation of 7,850.6 km, the average is 1.48 times the 76.88 ms theoretical fiber floor, a 67.5% efficiency ratio. Among the 19 Moscow-origin routes in this round, this path ranks eighth by average RTT; its spread-to-average ratio of about 4.7% is above the 3.28% median for the route set. The main takeaway is that the long transatlantic path is efficiently routed in terms of distance versus RTT, but the sample tail is wider: the maximum ran 15.84 ms above the average, about 13.9% higher. Loss-free operation keeps the profile clean despite the wider spread separating this route from the excellent tier. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **113.9 ms** | | Jitter | **4.1 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.88 ms** | | Fiber Efficiency | **67.5%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,850.6 km** | | Vacuum RTT floor | **52.37 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.88 ms** | | Low-latency fiber material floor | **76.57 ms** | | Engineering floor (5% path allowance) | **80.73 ms** | | Research 1.33× mapped-fiber reference | **102.25 ms** | | Estimated unamplified path loss | **1648.6 dB** | | Transparent optical spans / inline amplifiers | **104 / 103** | | Published RTT inflation over fiber floor | **1.48×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **107.82 ms** | | Average RTT | **113.9 ms** | | Maximum RTT | **129.74 ms** | | Standard deviation | **5.37 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Moscow latency and RTT](/docs/network/latency/pairs/iad-mow-rtt) — 112.8 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-iad-rtt). - **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. # Moscow, Russia → Johannesburg, South Africa RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Moscow to Johannesburg produced an average RTT of 201.9 ms, with a minimum of 192.01 ms and a maximum of 232.17 ms. The route recorded 0% packet loss and a jitter of 7.49 ms. For a geodesic distance of 9,125.7 km, the vacuum floor is 60.88 ms and the fiber floor is 89.37 ms. At 201.9 ms, the average is 2.26 times the fiber floor, corresponding to a fiber-floor efficiency of 44.3%. This route ranked 16th among the 19 routes measured in the round, placing it near the higher-latency end of the set. Its standard deviation of 7.94 ms is about 3.9% of the mean, above the 3.28% median standard-deviation-to-average ratio for the round. Despite the higher average and wider spread, every probe was returned without loss, indicating the route remained fully available across the entire measurement window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **201.9 ms** | | Jitter | **7.49 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.37 ms** | | Fiber Efficiency | **44.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,125.7 km** | | Vacuum RTT floor | **60.88 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.37 ms** | | Low-latency fiber material floor | **89.01 ms** | | Engineering floor (5% path allowance) | **93.85 ms** | | Research 1.33× mapped-fiber reference | **118.86 ms** | | Estimated unamplified path loss | **1916.4 dB** | | Transparent optical spans / inline amplifiers | **120 / 119** | | Published RTT inflation over fiber floor | **2.26×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **192.01 ms** | | Average RTT | **201.9 ms** | | Maximum RTT | **232.17 ms** | | Standard deviation | **7.94 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt) — 200.7 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Europe → Africa)** * [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt) — 198.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-jnb-rtt). - **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. # Moscow, Russia → Los Angeles, USA RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. Across the 2026-08-16T04:07:28Z round, Moscow to Los Angeles returned an average ICMP RTT of 177.7 ms, with a minimum of 173.78 ms and a maximum of 191.21 ms. The 3.21 ms standard deviation and 2.25 ms jitter point to a consistent path, and all 50 probes completed without packet loss. For the 9,793.2 km great-circle distance, the vacuum floor is 65.33 ms and a practical fiber-optic floor is 95.9 ms. At 177.7 ms average, the route sits 1.85 times above the fiber floor—a fiber efficiency of 54%—so the measured latency carries a significant distance penalty relative to the shortest possible optical path. This path ranks 15th among the 19 outbound routes in the set by average latency. Its relative variability of 1.8% is well below the 3.28% median for the set, meaning the elevated Fair-tier latency is paired with strong stability. If lower RTT is the goal, the most useful avenue is bringing the actual path closer to the fiber floor rather than reducing variance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **177.7 ms** | | Jitter | **2.25 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.9 ms** | | Fiber Efficiency | **54%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,793.2 km** | | Vacuum RTT floor | **65.33 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.9 ms** | | Low-latency fiber material floor | **95.52 ms** | | Engineering floor (5% path allowance) | **100.71 ms** | | Research 1.33× mapped-fiber reference | **127.55 ms** | | Estimated unamplified path loss | **2056.6 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.85×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **173.78 ms** | | Average RTT | **177.7 ms** | | Maximum RTT | **191.21 ms** | | Standard deviation | **3.21 ms** | | Stdev / average | **1.8%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Moscow latency and RTT](/docs/network/latency/pairs/lax-mow-rtt) — 177 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-lax-rtt). - **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. # Moscow, Russia → London, UK RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round sent 50 ICMP echo requests from Moscow to London at 100ms intervals and recorded an average round-trip time of 42.4ms, with a 40.38ms minimum and a 48.72ms maximum. Standard deviation was 1.83ms, jitter was 1.31ms, and no packets were lost. London is the western anchor of the Northwest European corridor and Europe's traditional transatlantic gateway. Over the 2,508.5km geodesic path, the vacuum floor is 16.73ms and the fiber floor is 24.56ms; the observed average is 1.73 times the fiber floor, corresponding to a 57.9% fiber efficiency figure. This route ranked fourth among the 19 outbound routes in the round. Its relative variability is about 4.3% of the average, above the 3.28% median ratio for the outbound route set, and the maximum was 6.32ms above the average—useful context for network planning. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **42.4 ms** | | Jitter | **1.31 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **24.56 ms** | | Fiber Efficiency | **57.9%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,508.5 km** | | Vacuum RTT floor | **16.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **24.56 ms** | | Low-latency fiber material floor | **24.47 ms** | | Engineering floor (5% path allowance) | **25.8 ms** | | Research 1.33× mapped-fiber reference | **32.67 ms** | | Estimated unamplified path loss | **526.8 dB** | | Transparent optical spans / inline amplifiers | **33 / 32** | | Published RTT inflation over fiber floor | **1.73×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **40.38 ms** | | Average RTT | **42.4 ms** | | Maximum RTT | **48.72 ms** | | Standard deviation | **1.83 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-lon-rtt). - **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. # Moscow, Russia → Melbourne, Australia RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. The Moscow-to-Melbourne path in the 2026-08-16T04:07:28Z measurement round averaged 235.9 ms ICMP echo RTT, with a minimum of 223.93 ms, a maximum of 262.01 ms, and zero packet loss across 50 samples. That average is about 1.67 times the fiber-optic propagation floor for the 14,412 km great-circle distance, implying the route operates at roughly 59.8% fiber efficiency. The 8.78 ms standard deviation and 7.29 ms jitter point to a moderately steady path over a very long haul. It ranked 18th among the 19 Moscow outbound paths in this round, placing it near the slower end of the set. Its standard deviation is 3.7% of the average, slightly above the 3.28% median relative variability for those 19 paths, so the higher latency also comes with a bit more inconsistency. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **235.9 ms** | | Jitter | **7.29 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **141.13 ms** | | Fiber Efficiency | **59.8%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,412.1 km** | | Vacuum RTT floor | **96.15 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **141.13 ms** | | Low-latency fiber material floor | **140.57 ms** | | Engineering floor (5% path allowance) | **148.21 ms** | | Research 1.33× mapped-fiber reference | **187.71 ms** | | Estimated unamplified path loss | **3026.5 dB** | | Transparent optical spans / inline amplifiers | **190 / 189** | | Published RTT inflation over fiber floor | **1.67×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **223.93 ms** | | Average RTT | **235.9 ms** | | Maximum RTT | **262.01 ms** | | Standard deviation | **8.78 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Moscow latency and RTT](/docs/network/latency/pairs/mel-mow-rtt) — 236.1 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-mel-rtt). - **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. # Moscow, Russia → Miami, USA RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, Moscow to Miami produced an average ICMP RTT of 144.5 ms, with a 138.89 ms minimum and a 163.99 ms maximum. The 5.03 ms standard deviation and 4.68 ms jitter are moderate, and all 50 probes succeeded with zero packet loss. Given a 9,239.8 km great-circle distance, the vacuum floor is 61.64 ms and the fiber floor is 90.48 ms. The observed average is 1.60 times the fiber floor, translating to 62.6% fiber efficiency—a moderately efficient use of the geographic distance. By average latency, this route ranks 11th of the 19 outbound paths in this set. Its relative variability of 3.5% sits close to the 3.28% median for the set, so the Good-tier result is representative of the route's normal behavior rather than an outlier. The main route-specific observation is that the min-to-max spread of 25.1 ms is wider than the sub-5 ms standard deviation suggests; most samples cluster near the average, but occasional excursions occur. With no packet loss, latency stability is not the concern; the remaining headroom lies in reducing the distance-based overhead. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **144.5 ms** | | Jitter | **4.68 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **90.48 ms** | | Fiber Efficiency | **62.6%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,239.8 km** | | Vacuum RTT floor | **61.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **90.48 ms** | | Low-latency fiber material floor | **90.12 ms** | | Engineering floor (5% path allowance) | **95.02 ms** | | Research 1.33× mapped-fiber reference | **120.34 ms** | | Estimated unamplified path loss | **1940.4 dB** | | Transparent optical spans / inline amplifiers | **122 / 121** | | Published RTT inflation over fiber floor | **1.6×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **138.89 ms** | | Average RTT | **144.5 ms** | | Maximum RTT | **163.99 ms** | | Standard deviation | **5.03 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Moscow latency and RTT](/docs/network/latency/pairs/mia-mow-rtt) — 145.5 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-mia-rtt). - **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. # Moscow, Russia → Marseille, France RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo RTT from Moscow to Marseille averaged 49.9 ms over 50 samples, with a 47.94 ms minimum and 53.35 ms maximum; jitter was 1.46 ms and packet loss was zero, placing the pair in the excellent latency tier. The average is about 1.9 times the 26.23 ms theoretical fiber floor for the 2,678.2 km geodesic separation, a 52.6% efficiency ratio. Among the 19 Moscow-origin routes in this round, this path ranks sixth by average RTT, and its spread-to-average ratio of roughly 2.9% is below the 3.28% median for the route set. The sample was uniformly clean: the maximum ran only 3.45 ms above the average, and no packets were lost. For the Mediterranean landing direction, the route offers a tightly bounded latency profile rather than a low-floor-only result. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **49.9 ms** | | Jitter | **1.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **26.23 ms** | | Fiber Efficiency | **52.6%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,678.2 km** | | Vacuum RTT floor | **17.87 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **26.23 ms** | | Low-latency fiber material floor | **26.12 ms** | | Engineering floor (5% path allowance) | **27.54 ms** | | Research 1.33× mapped-fiber reference | **34.88 ms** | | Estimated unamplified path loss | **562.4 dB** | | Transparent optical spans / inline amplifiers | **36 / 35** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **47.94 ms** | | Average RTT | **49.9 ms** | | Maximum RTT | **53.35 ms** | | Standard deviation | **1.46 ms** | | Stdev / average | **2.9%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-mrs-rtt). - **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. # Moscow, Russia → New York, USA RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. From Moscow to New York, the 2026-08-16T04:07:28Z round measured an average ICMP RTT of 107.5 ms, a minimum of 103.9 ms, and a maximum of 121.54 ms. The 3.46 ms standard deviation and 2.69 ms jitter indicate a steady transatlantic path, and all 50 probes returned without loss. For the 7,531.3 km great-circle distance, the vacuum floor is 50.24 ms and the fiber floor is 73.75 ms. The route runs 1.46 times the fiber floor, or 68.6% fiber efficiency, which leaves less room for distance-based improvement than most long intercontinental paths. This path ranks 7th of the 19 outbound routes in the set by average latency. Its relative variability of 3.2% is just below the 3.28% median, so the Good-tier latency is paired with consistency typical of the better-performing half of the route group. The route-specific takeaway is tight but not perfectly flat: the min-to-max range is 17.64 ms, while the average and standard deviation suggest most probes land within a few milliseconds of 107.5 ms. Zero packet loss and a fiber efficiency near 69% make this a well-behaved long-haul result. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **107.5 ms** | | Jitter | **2.69 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **73.75 ms** | | Fiber Efficiency | **68.6%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,531.3 km** | | Vacuum RTT floor | **50.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **73.75 ms** | | Low-latency fiber material floor | **73.46 ms** | | Engineering floor (5% path allowance) | **77.45 ms** | | Research 1.33× mapped-fiber reference | **98.09 ms** | | Estimated unamplified path loss | **1581.6 dB** | | Transparent optical spans / inline amplifiers | **99 / 98** | | Published RTT inflation over fiber floor | **1.46×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **103.9 ms** | | Average RTT | **107.5 ms** | | Maximum RTT | **121.54 ms** | | Standard deviation | **3.46 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Moscow latency and RTT](/docs/network/latency/pairs/nyc-mow-rtt) — 107 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Europe → North America)** * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-nyc-rtt). - **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. # Moscow, Russia → Paris, France RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Moscow to Paris averaged 44 ms over 50 samples, with values between 42.02 ms and 49.11 ms. Packet loss was zero, and jitter measured 1.37 ms, keeping the route in the excellent latency tier. The average is 1.8 times the 24.42 ms theoretical fiber floor for a 2,494.1 km straight-line path, a 55.5% efficiency ratio. Among the 19 Moscow-origin routes in this round, this pair ranks fifth by average RTT; its 1.64 ms standard deviation is about 3.7% of the mean, slightly above the 3.28% median variability ratio for the route set. The maximum sample was 5.11 ms above the average, so the measured spread is modest even though the variability ratio edges past the route-set median. The route therefore combines a sub-50 ms average with a consistent, loss-free RTT profile across the sample window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **44 ms** | | Jitter | **1.37 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **24.42 ms** | | Fiber Efficiency | **55.5%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,494.1 km** | | Vacuum RTT floor | **16.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **24.42 ms** | | Low-latency fiber material floor | **24.33 ms** | | Engineering floor (5% path allowance) | **25.65 ms** | | Research 1.33× mapped-fiber reference | **32.48 ms** | | Estimated unamplified path loss | **523.8 dB** | | Transparent optical spans / inline amplifiers | **33 / 32** | | Published RTT inflation over fiber floor | **1.8×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **42.02 ms** | | Average RTT | **44 ms** | | Maximum RTT | **49.11 ms** | | Standard deviation | **1.64 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-par-rtt). - **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. # Moscow, Russia → Seattle, USA RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z ICMP echo round, Moscow to Seattle averaged 164.8 ms across 50 samples, with a minimum of 155.86 ms and a maximum of 193.38 ms. No packets were lost, so the route’s stability is defined by timing rather than reachability. The great-circle distance of about 8,397 km gives a fiber-floor estimate near 82 ms, meaning the observed average is roughly two times the floor and fiber efficiency is 49.9 percent. A standard deviation of 7.9 ms and jitter of 6.37 ms keep the path fairly steady despite the headroom above the floor. This route ranked 14th among 19 Moscow outbound paths in this round; the median variability across the Moscow outbound set was 3.28 percent of average latency. At 4.8 percent of average latency, this route’s own variability sits above that median, and the max sample sits 28.6 ms above the average, a tail worth watching. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **164.8 ms** | | Jitter | **6.37 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **82.23 ms** | | Fiber Efficiency | **49.9%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,396.9 km** | | Vacuum RTT floor | **56.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **82.23 ms** | | Low-latency fiber material floor | **81.9 ms** | | Engineering floor (5% path allowance) | **86.35 ms** | | Research 1.33× mapped-fiber reference | **109.36 ms** | | Estimated unamplified path loss | **1763.3 dB** | | Transparent optical spans / inline amplifiers | **111 / 110** | | Published RTT inflation over fiber floor | **2×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **155.86 ms** | | Average RTT | **164.8 ms** | | Maximum RTT | **193.38 ms** | | Standard deviation | **7.9 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Moscow latency and RTT](/docs/network/latency/pairs/sea-mow-rtt) — 164.6 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-sea-rtt). - **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. # Moscow, Russia → Singapore RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, Moscow to Singapore returned an average ICMP echo RTT of 147.3 ms, a minimum of 144.41 ms, a maximum of 156.92 ms, and no packet loss across 50 samples. At 1.79 times the fiber-optic propagation floor for the 8,423 km great-circle distance, the average corresponds to 56% fiber efficiency. The 2.32 ms standard deviation and 1.99 ms jitter are both small, indicating a highly consistent route. This path was ranked 12th among the 19 Moscow outbound paths in this round, close to the middle of the group. Its relative variability is about 1.6% of the average, well below the 3.28% median for those 19 paths, so mid-pack latency arrives with unusually steady timing. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **147.3 ms** | | Jitter | **1.99 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **82.49 ms** | | Fiber Efficiency | **56%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,423.2 km** | | Vacuum RTT floor | **56.19 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **82.49 ms** | | Low-latency fiber material floor | **82.15 ms** | | Engineering floor (5% path allowance) | **86.62 ms** | | Research 1.33× mapped-fiber reference | **109.71 ms** | | Estimated unamplified path loss | **1768.9 dB** | | Transparent optical spans / inline amplifiers | **111 / 110** | | Published RTT inflation over fiber floor | **1.79×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **144.41 ms** | | Average RTT | **147.3 ms** | | Maximum RTT | **156.92 ms** | | Standard deviation | **2.32 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Moscow latency and RTT](/docs/network/latency/pairs/sin-mow-rtt) — 147.7 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-sin-rtt). - **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. # Moscow, Russia → Sydney, Australia RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, Moscow to Sydney averaged 241.8 ms ICMP echo RTT, with a minimum of 231.04 ms, a maximum of 265.67 ms, and zero packet loss across 50 samples. The average is 1.70 times the fiber-optic propagation floor for the 14,484 km great-circle distance, translating to 58.7% fiber efficiency. The 7.65 ms standard deviation and 5.98 ms jitter indicate reasonably stable behavior even near the upper end of this route set. It was ranked 19th among the 19 Moscow outbound paths in this round, placing it at the bottom of the ranking. Its relative variability of 3.2% of the average, however, sits just below the 3.28% median for those paths, so the lowest-ranked route in this set is not the most erratic. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **241.8 ms** | | Jitter | **5.98 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **141.84 ms** | | Fiber Efficiency | **58.7%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,483.9 km** | | Vacuum RTT floor | **96.63 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **141.84 ms** | | Low-latency fiber material floor | **141.27 ms** | | Engineering floor (5% path allowance) | **148.95 ms** | | Research 1.33× mapped-fiber reference | **188.64 ms** | | Estimated unamplified path loss | **3041.6 dB** | | Transparent optical spans / inline amplifiers | **191 / 190** | | Published RTT inflation over fiber floor | **1.7×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **231.04 ms** | | Average RTT | **241.8 ms** | | Maximum RTT | **265.67 ms** | | Standard deviation | **7.65 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Moscow latency and RTT](/docs/network/latency/pairs/syd-mow-rtt) — 242.2 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-syd-rtt). - **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. # Moscow, Russia → Taipei, Taiwan RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Moscow to Taipei produced an average RTT of 132.1 ms, with a minimum of 126.75 ms and a maximum of 145.67 ms. No packets were lost, and jitter was 4.42 ms. Over a geodesic distance of 7,369 km, the theoretical vacuum one-way floor is 49.16 ms and the fiber floor is 72.16 ms. The observed average is 1.83 times the fiber floor, placing the route at 54.6% fiber-floor efficiency. Ranked 10th among the 19 routes measured in the same round, Moscow-to-Taipei sits around the middle of the set. Its standard deviation of 4.52 ms is about 3.4% of the average, just above the 3.28% median standard-deviation-to-average ratio for the round. With zero packet loss and moderate jitter, this round offers a stable baseline for Moscow-to-Taipei latency. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **132.1 ms** | | Jitter | **4.42 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.16 ms** | | Fiber Efficiency | **54.6%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **7,369 km** | | Vacuum RTT floor | **49.16 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.16 ms** | | Low-latency fiber material floor | **71.87 ms** | | Engineering floor (5% path allowance) | **75.78 ms** | | Research 1.33× mapped-fiber reference | **95.98 ms** | | Estimated unamplified path loss | **1547.5 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.83×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **126.75 ms** | | Average RTT | **132.1 ms** | | Maximum RTT | **145.67 ms** | | Standard deviation | **4.52 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-tpe-rtt). - **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. # Moscow, Russia → Tokyo, Japan RTT 🇷🇺 **Moscow, Russia (MOW)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Moscow to Tokyo produced an average RTT of 162.2 ms, with a minimum of 152.69 ms and a maximum of 185.56 ms. Packet loss was 0%, and jitter was 5.65 ms. Given a geodesic distance of 7,497 km, the vacuum floor is 50.01 ms and the fiber floor is 73.42 ms. The measured average sits 2.21 times above that fiber floor, for a fiber-floor efficiency of 45.3%. Ranked 13th of the 19 routes measured in this round, Moscow-to-Tokyo falls in the upper-middle range for latency. The standard deviation of 6.91 ms is about 4.3% of the average, above the 3.28% median standard-deviation-to-average ratio for the round, so sample-to-sample RTT varied more than was typical. All 50 probes still completed without loss, keeping the route fully responsive throughout the round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **162.2 ms** | | Jitter | **5.65 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **73.42 ms** | | Fiber Efficiency | **45.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **7,497 km** | | Vacuum RTT floor | **50.01 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **73.42 ms** | | Low-latency fiber material floor | **73.12 ms** | | Engineering floor (5% path allowance) | **77.1 ms** | | Research 1.33× mapped-fiber reference | **97.64 ms** | | Estimated unamplified path loss | **1574.4 dB** | | Transparent optical spans / inline amplifiers | **99 / 98** | | Published RTT inflation over fiber floor | **2.21×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **152.69 ms** | | Average RTT | **162.2 ms** | | Maximum RTT | **185.56 ms** | | Standard deviation | **6.91 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Moscow latency and RTT](/docs/network/latency/pairs/tyo-mow-rtt) — 161.7 ms **Fastest routes departing Moscow (MOW)** * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-tyo-rtt). - **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. # Marseille, France → Amsterdam, Netherlands RTT 🇫🇷 **Marseille, France (MRS)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo measurements in the 2026-08-16T04:07:28Z round put Marseille-to-Amsterdam at an average RTT of 20.3 ms, with a minimum of 19.62 ms and a maximum of 22.75 ms over 50 samples. The route posted zero packet loss and 0.48 ms of jitter, which is why it lands in the 'Ultra-Low' latency tier. The geodesic distance is about 1,009.9 km, placing the vacuum floor at 6.74 ms and the fiber floor at 9.89 ms. At 20.3 ms, the measured RTT is 2.05 times the fiber floor, or roughly 48.7% fiber efficiency, leaving room for the extra cable length that real networks require between a Mediterranean landing hub and a Northwest European interconnection point. This route ranked 4th among the 19 outbound routes measured from Marseille in this round, placing it close to the top of the source's latency order. Its standard deviation of 0.64 ms is about 3.15% of the average, slightly below the round-wide median variability of 3.28% across the outbound group. The practical takeaway is that the Marseille–Amsterdam path is both fast and consistent for a roughly 1,000 km link. With no sample loss and very low jitter, the 20.3 ms average is a representative value rather than a lucky outlier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **20.3 ms** | | Jitter | **0.48 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **9.89 ms** | | Fiber Efficiency | **48.7%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,009.9 km** | | Vacuum RTT floor | **6.74 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **9.89 ms** | | Low-latency fiber material floor | **9.85 ms** | | Engineering floor (5% path allowance) | **10.39 ms** | | Research 1.33× mapped-fiber reference | **13.15 ms** | | Estimated unamplified path loss | **212.1 dB** | | Transparent optical spans / inline amplifiers | **14 / 13** | | Published RTT inflation over fiber floor | **2.05×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **19.62 ms** | | Average RTT | **20.3 ms** | | Maximum RTT | **22.75 ms** | | Standard deviation | **0.64 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-ams-rtt). - **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. # Marseille, France → Berlin, Germany RTT 🇫🇷 **Marseille, France (MRS)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z ICMP echo round, Marseille-to-Berlin recorded an average RTT of 20.6 ms, a minimum of 19.99 ms, and a maximum of 21.74 ms across 50 samples. Packet loss was 0% and jitter was 0.3 ms, placing the route in the 'Ultra-Low' latency tier. The route spans about 1,187 km in a straight line, corresponding to a 7.92 ms vacuum floor and an 11.62 ms fiber floor. Measured RTT comes in at 1.77 times the fiber floor, yielding roughly 56.4% fiber efficiency; that is a tighter fit to the theoretical floor than the distance alone would suggest. Within the 19 outbound routes measured from Marseille in this round, this path ranked 5th by average RTT, putting it near the faster end of the group. Its standard deviation of 0.35 ms is about 1.70% of the average, well below the outbound group's median variability of 3.28%. The standout feature of this round is consistency: the spread between minimum and maximum RTT is only 1.75 ms, and jitter is extremely low. For a link of nearly 1,200 km, the 20.6 ms average is remarkably steady, making this route one of the more predictable outbound paths from Marseille in the 2026-08-16T04:07:28Z measurement set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **20.6 ms** | | Jitter | **0.3 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **11.62 ms** | | Fiber Efficiency | **56.4%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **1,187 km** | | Vacuum RTT floor | **7.92 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **11.62 ms** | | Low-latency fiber material floor | **11.58 ms** | | Engineering floor (5% path allowance) | **12.21 ms** | | Research 1.33× mapped-fiber reference | **15.46 ms** | | Estimated unamplified path loss | **249.3 dB** | | Transparent optical spans / inline amplifiers | **16 / 15** | | Published RTT inflation over fiber floor | **1.77×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **19.99 ms** | | Average RTT | **20.6 ms** | | Maximum RTT | **21.74 ms** | | Standard deviation | **0.35 ms** | | Stdev / average | **1.7%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-ber-rtt). - **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. # Marseille, France → Frankfurt, Germany RTT 🇫🇷 **Marseille, France (MRS)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. During round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Marseille to Frankfurt produced an average round-trip time of 16 ms, with a minimum of 15.12 ms and a maximum of 18.91 ms. The 0.79 ms standard deviation and 0.59 ms jitter indicate a stable path, and no packets were lost. Across the 19 outbound routes measured from Marseille, this route ranks second by average latency, and the median variability-to-average ratio for that route set is 3.28%. The low delay is not just a single favorable reading; the spread around the average is tight enough to place the route in the ultra-low latency tier. Marseille's Mediterranean cable landing role and Frankfurt's position as a central European switching point are visible in the numbers: the physical reference puts the measured average at 2.05 times the theoretical fiber-floor latency, with a fiber-efficiency value of 48.9%. That makes the Marseille-Frankfurt pair an efficient backbone link, though ICMP RTT remains a path-level signal rather than a predictor of end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **16 ms** | | Jitter | **0.59 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **7.82 ms** | | Fiber Efficiency | **48.9%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **798.8 km** | | Vacuum RTT floor | **5.33 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **7.82 ms** | | Low-latency fiber material floor | **7.79 ms** | | Engineering floor (5% path allowance) | **8.21 ms** | | Research 1.33× mapped-fiber reference | **10.4 ms** | | Estimated unamplified path loss | **167.7 dB** | | Transparent optical spans / inline amplifiers | **11 / 10** | | Published RTT inflation over fiber floor | **2.05×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **15.12 ms** | | Average RTT | **16 ms** | | Maximum RTT | **18.91 ms** | | Standard deviation | **0.79 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-fra-rtt). - **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. # Marseille, France → São Paulo, Brazil RTT 🇫🇷 **Marseille, France (MRS)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Marseille, France to São Paulo, Brazil averaged 186.7 ms, with a minimum of 176.61 ms and a maximum of 215.07 ms. All 50 probes returned, yielding 0% packet loss; jitter was 6.61 ms and the standard deviation was 7.56 ms. The average places the route in the Fair latency tier and is 2.09 times the theoretical fiber floor of 89.24 ms, so the measured path is well above the shortest possible fiber route. This path ranks 15th among the 19 outbound routes measured in the round, and its variability relative to the average is about 4%, slightly above the 3.28% median across the 19 outbound paths. The route-specific takeaway is that the Marseille–São Paulo connection is stable and loss-free, but its distance-adjusted efficiency of 47.8% leaves substantial headroom. Network planners should expect consistent Fair-tier performance rather than a best-case near-optimal path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **186.7 ms** | | Jitter | **6.61 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.24 ms** | | Fiber Efficiency | **47.8%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **9,113 km** | | Vacuum RTT floor | **60.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.24 ms** | | Low-latency fiber material floor | **88.88 ms** | | Engineering floor (5% path allowance) | **93.72 ms** | | Research 1.33× mapped-fiber reference | **118.69 ms** | | Estimated unamplified path loss | **1913.7 dB** | | Transparent optical spans / inline amplifiers | **120 / 119** | | Published RTT inflation over fiber floor | **2.09×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **176.61 ms** | | Average RTT | **186.7 ms** | | Maximum RTT | **215.07 ms** | | Standard deviation | **7.56 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Marseille latency and RTT](/docs/network/latency/pairs/gru-mrs-rtt) — 187.7 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Europe → South America)** * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms * [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms * [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-gru-rtt). - **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. # Marseille, France → Hong Kong RTT 🇫🇷 **Marseille, France (MRS)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, Marseille, France to Hong Kong produced an average ICMP round-trip time of 166.4 ms, with a minimum of 161.4 ms and maximum of 176.84 ms. All 50 probes returned, with no packet loss; jitter was 2.92 ms and standard deviation was 3.5 ms. This Fair-tier result is 1.74 times the theoretical fiber floor of 95.48 ms, corresponding to a route efficiency of 57.4%. The path ranks 13th among the 19 outbound routes in this round, and its variability relative to the average is about 2.1%, comfortably below the 3.28% median across the 19 outbound paths. The useful signal from this round is consistency: across more than 9,700 km, the low jitter and zero loss make the RTT highly predictable. The average is still far from the shortest possible fiber time, but the route behaves steadily for an intercontinental path. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **166.4 ms** | | Jitter | **2.92 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.48 ms** | | Fiber Efficiency | **57.4%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,750.5 km** | | Vacuum RTT floor | **65.05 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.48 ms** | | Low-latency fiber material floor | **95.1 ms** | | Engineering floor (5% path allowance) | **100.27 ms** | | Research 1.33× mapped-fiber reference | **126.99 ms** | | Estimated unamplified path loss | **2047.6 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **1.74×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **161.4 ms** | | Average RTT | **166.4 ms** | | Maximum RTT | **176.84 ms** | | Standard deviation | **3.5 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Marseille latency and RTT](/docs/network/latency/pairs/hkg-mrs-rtt) — 165.4 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-hkg-rtt). - **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. # Marseille, France → Ashburn, USA RTT 🇫🇷 **Marseille, France (MRS)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z sent 50 ICMP echo probes from Marseille to Ashburn and recorded an average RTT of 85.7 ms, with a minimum of 82.1 ms and a maximum of 94.47 ms. The 2.63 ms standard deviation and 1.95 ms jitter sit in a narrow band for a route of this span, and all probes returned without packet loss. At a geodesic distance of 6,672.7 km, the measured average is 1.31 times the fiber-floor estimate of 65.34 ms, corresponding to a fiber efficiency of 76.2 percent. That places the route in the Good latency tier and indicates the transatlantic path is operating close to its distance-limited floor. Among the 19 outbound routes measured in this round, Marseille-Ashburn ranks 8th. Its standard-deviation-to-average ratio is about 3.1 percent, slightly below the network-median 3.28 percent, so the route is comparable to or a bit more stable than the typical route in the outbound set. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **85.7 ms** | | Jitter | **1.95 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **65.34 ms** | | Fiber Efficiency | **76.2%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,672.7 km** | | Vacuum RTT floor | **44.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **65.34 ms** | | Low-latency fiber material floor | **65.08 ms** | | Engineering floor (5% path allowance) | **68.62 ms** | | Research 1.33× mapped-fiber reference | **86.91 ms** | | Estimated unamplified path loss | **1401.3 dB** | | Transparent optical spans / inline amplifiers | **88 / 87** | | Published RTT inflation over fiber floor | **1.31×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **82.1 ms** | | Average RTT | **85.7 ms** | | Maximum RTT | **94.47 ms** | | Standard deviation | **2.63 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Marseille latency and RTT](/docs/network/latency/pairs/iad-mrs-rtt) — 86.5 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-iad-rtt). - **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. # Marseille, France → Johannesburg, South Africa RTT 🇫🇷 **Marseille, France (MRS)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Marseille to Johannesburg averaged **198.5 ms** over 50 samples, with a minimum of 194.33 ms and a maximum of 207.86 ms. Packet loss was 0%, jitter was 2.5 ms, and the entire sample spread was only 13.53 ms, earning a Fair latency tier with unusually tight behavior. At a geodesic distance of 8,037.1 km, the vacuum floor is 53.62 ms and the fiber floor is 78.71 ms. The 198.5 ms average is 2.52 times the fiber floor, or 39.7% fiber efficiency, indicating that the path's practical length is far greater than the direct Marseille–Johannesburg line. This route was ranked 16th among the 19 outbound routes in the round, so it sits near the slower end of the set. Its standard deviation of 3.18 ms is only about 1.6% of the average RTT, well below the network-wide median of 3.28%, which makes it one of the more consistent long-distance routes in this measurement set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **198.5 ms** | | Jitter | **2.5 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **78.71 ms** | | Fiber Efficiency | **39.7%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,037.1 km** | | Vacuum RTT floor | **53.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **78.71 ms** | | Low-latency fiber material floor | **78.39 ms** | | Engineering floor (5% path allowance) | **82.65 ms** | | Research 1.33× mapped-fiber reference | **104.68 ms** | | Estimated unamplified path loss | **1687.8 dB** | | Transparent optical spans / inline amplifiers | **106 / 105** | | Published RTT inflation over fiber floor | **2.52×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **194.33 ms** | | Average RTT | **198.5 ms** | | Maximum RTT | **207.86 ms** | | Standard deviation | **3.18 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Europe → Africa)** * [Moscow to Johannesburg latency and RTT](/docs/network/latency/pairs/mow-jnb-rtt) — 201.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-jnb-rtt). - **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. # Marseille, France → Los Angeles, USA RTT 🇫🇷 **Marseille, France (MRS)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z covered 50 ICMP echo probes from Marseille to Los Angeles with an average RTT of 144.5 ms, a minimum of 140.24 ms, and a maximum of 154.02 ms. The 3.04 ms standard deviation and 2.51 ms jitter show moderate spread over a very long path, while zero packet loss indicates the route remained fully responsive during the sample window. With a geodesic distance of 9,710.4 km, the fiber-floor estimate for this route is 95.09 ms. The observed average is 1.52 times that floor, giving a fiber efficiency of 65.8 percent and placing the route in the Good latency tier. Among the 19 outbound routes in this measurement set, Marseille-Los Angeles ranks 12th, placing it toward the lower half of the current outbound order. Its standard-deviation-to-average ratio is about 2.1 percent, well below the network-median 3.28 percent, so absolute RTT is high but the round-trip times remained comparatively steady across the 50 probes. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **144.5 ms** | | Jitter | **2.51 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.09 ms** | | Fiber Efficiency | **65.8%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,710.4 km** | | Vacuum RTT floor | **64.78 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.09 ms** | | Low-latency fiber material floor | **94.71 ms** | | Engineering floor (5% path allowance) | **99.86 ms** | | Research 1.33× mapped-fiber reference | **126.47 ms** | | Estimated unamplified path loss | **2039.2 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **1.52×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **140.24 ms** | | Average RTT | **144.5 ms** | | Maximum RTT | **154.02 ms** | | Standard deviation | **3.04 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Marseille latency and RTT](/docs/network/latency/pairs/lax-mrs-rtt) — 143.9 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-lax-rtt). - **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. # Marseille, France → London, UK RTT 🇫🇷 **Marseille, France (MRS)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, the Marseille-to-London ICMP echo run averaged 18.9 ms over 50 probes, with a minimum of 18.41 ms and a maximum of 20.09 ms. No packets were lost, and the 0.42 ms standard deviation with 0.34 ms jitter points to very steady delivery. Within the 19 outbound routes measured from Marseille, this pair ranks third by average latency. The median variability-to-average ratio across that route set is 3.28%, and this route's own ratio is below that level, so the low average is accompanied by equally consistent sample-to-sample behavior. London is the western anchor of the Northwest European corridor, while Marseille is a Mediterranean cable landing hub, making this a useful westbound corridor for traffic coming ashore in southern France. The measured average is 1.93 times the theoretical fiber-floor latency, corresponding to a fiber-efficiency value of 51.9%. As an ICMP round-trip reading, it describes the network path's delay profile rather than end-user application quality. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **18.9 ms** | | Jitter | **0.34 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **9.82 ms** | | Fiber Efficiency | **51.9%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,002.4 km** | | Vacuum RTT floor | **6.69 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **9.82 ms** | | Low-latency fiber material floor | **9.78 ms** | | Engineering floor (5% path allowance) | **10.31 ms** | | Research 1.33× mapped-fiber reference | **13.06 ms** | | Estimated unamplified path loss | **210.5 dB** | | Transparent optical spans / inline amplifiers | **14 / 13** | | Published RTT inflation over fiber floor | **1.93×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **18.41 ms** | | Average RTT | **18.9 ms** | | Maximum RTT | **20.09 ms** | | Standard deviation | **0.42 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-lon-rtt). - **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. # Marseille, France → Melbourne, Australia RTT 🇫🇷 **Marseille, France (MRS)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo requests from Marseille, France to Melbourne, Australia averaged 234.2 ms, with a minimum of 225.73 ms and a maximum of 253.61 ms. The 50-probe sample had no packet loss, jitter of 5.82 ms, and a standard deviation of 7.53 ms. This Fair-tier route's geodesic distance is roughly 16,580 km and it measures 1.44 times the theoretical fiber floor of 162.36 ms, giving it a route efficiency of 69.3%. Although it ranks 18th among the 19 outbound routes in this round by absolute round-trip time, its variability relative to the average is about 3.2%, essentially matching the 3.28% median across the 19 outbound paths. The key insight is that high absolute latency is expected for a route of this distance, but the measured path is relatively efficient: an inflation factor of 1.44 means it stays closer to the shortest conceivable fiber route than its raw milliseconds suggest. The route is stable, loss-free, and predictable despite its long geographic span. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **234.2 ms** | | Jitter | **5.82 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **162.36 ms** | | Fiber Efficiency | **69.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,579.2 km** | | Vacuum RTT floor | **110.6 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **162.36 ms** | | Low-latency fiber material floor | **161.7 ms** | | Engineering floor (5% path allowance) | **170.5 ms** | | Research 1.33× mapped-fiber reference | **215.93 ms** | | Estimated unamplified path loss | **3481.6 dB** | | Transparent optical spans / inline amplifiers | **218 / 217** | | Published RTT inflation over fiber floor | **1.44×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **225.73 ms** | | Average RTT | **234.2 ms** | | Maximum RTT | **253.61 ms** | | Standard deviation | **7.53 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Marseille latency and RTT](/docs/network/latency/pairs/mel-mrs-rtt) — 233.5 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-mel-rtt). - **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. # Marseille, France → Miami, USA RTT 🇫🇷 **Marseille, France (MRS)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z test round, ICMP echo measurements from Marseille, France, to Miami, USA, averaged 112.4 ms over 50 samples, with a minimum of 105.38 ms and a maximum of 129.43 ms. No packet loss was observed and the route was rated Good for latency. The 7,752.4 km great-circle distance has a theoretical fiber-floor RTT of 75.92 ms, putting the measured average at 1.48 times that floor and at 67.5% fiber efficiency. The 5.13 ms standard deviation and 4.52 ms jitter point to a stable path over the test interval. This route ranked 9th among the 19 outbound routes from Marseille measured in the same round, while the network-wide median standard-deviation-to-average ratio was 3.28%. The practical upshot is a reliable Mediterranean-to-Florida baseline with average latency near 112 ms and no packet loss. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **112.4 ms** | | Jitter | **4.52 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **75.92 ms** | | Fiber Efficiency | **67.5%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,752.4 km** | | Vacuum RTT floor | **51.72 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **75.92 ms** | | Low-latency fiber material floor | **75.61 ms** | | Engineering floor (5% path allowance) | **79.72 ms** | | Research 1.33× mapped-fiber reference | **100.97 ms** | | Estimated unamplified path loss | **1628 dB** | | Transparent optical spans / inline amplifiers | **102 / 101** | | Published RTT inflation over fiber floor | **1.48×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **105.38 ms** | | Average RTT | **112.4 ms** | | Maximum RTT | **129.43 ms** | | Standard deviation | **5.13 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Marseille latency and RTT](/docs/network/latency/pairs/mia-mrs-rtt) — 113.7 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-mia-rtt). - **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. # Marseille, France → Moscow, Russia RTT 🇫🇷 **Marseille, France (MRS)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, 50 ICMP probes from Marseille to Moscow returned an average round-trip time of 49.6 ms, with a minimum of 47.26 ms and a maximum of 58 ms. The 2.18 ms standard deviation and 1.92 ms jitter reflect a no-loss path whose variability keeps it in the excellent latency tier. Among the 19 outbound routes measured from Marseille, this route ranks sixth by average latency. Its variability-to-average ratio sits above the 3.28% median across that route set, which is consistent with the much longer distance and the wider delay range captured in the sample. The physical reference puts the Marseille-Moscow average at 1.89 times the theoretical fiber-floor latency, with a fiber-efficiency value of 52.9%. Moscow extends the backbone eastward toward European and Asia-Pacific networks, so this latency profile is particularly relevant for traffic moving between southern Europe and those farther regions. ICMP RTT is best read as a path-level indicator, not a proxy for end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **49.6 ms** | | Jitter | **1.92 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **26.23 ms** | | Fiber Efficiency | **52.9%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,678.2 km** | | Vacuum RTT floor | **17.87 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **26.23 ms** | | Low-latency fiber material floor | **26.12 ms** | | Engineering floor (5% path allowance) | **27.54 ms** | | Research 1.33× mapped-fiber reference | **34.88 ms** | | Estimated unamplified path loss | **562.4 dB** | | Transparent optical spans / inline amplifiers | **36 / 35** | | Published RTT inflation over fiber floor | **1.89×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **47.26 ms** | | Average RTT | **49.6 ms** | | Maximum RTT | **58 ms** | | Standard deviation | **2.18 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-mow-rtt). - **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. # Marseille, France → New York, USA RTT 🇫🇷 **Marseille, France (MRS)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Marseille, France, to New York, USA, averaged 79.8 ms across 50 samples, ranging from 75.53 ms to 89.73 ms. The route logged zero packet loss and earned an Excellent latency rating. The 6,321.9 km great-circle distance yields a theoretical fiber-floor RTT of 61.91 ms, so the observed mean sits just 1.29 times above that floor at 77.6% fiber efficiency. With a standard deviation of 3.65 ms and jitter of 3.14 ms, the path was both fast and consistent. This route ranked 7th among 19 outbound routes from Marseille in the same round, against a network-wide median standard-deviation-to-average ratio of 3.28%. The result gives operators a strong low-latency benchmark for Southern Europe-to-US East Coast connectivity. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **79.8 ms** | | Jitter | **3.14 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **61.91 ms** | | Fiber Efficiency | **77.6%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,321.9 km** | | Vacuum RTT floor | **42.18 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **61.91 ms** | | Low-latency fiber material floor | **61.66 ms** | | Engineering floor (5% path allowance) | **65.01 ms** | | Research 1.33× mapped-fiber reference | **82.34 ms** | | Estimated unamplified path loss | **1327.6 dB** | | Transparent optical spans / inline amplifiers | **83 / 82** | | Published RTT inflation over fiber floor | **1.29×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **75.53 ms** | | Average RTT | **79.8 ms** | | Maximum RTT | **89.73 ms** | | Standard deviation | **3.65 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Marseille latency and RTT](/docs/network/latency/pairs/nyc-mrs-rtt) — 80.2 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Europe → North America)** * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-nyc-rtt). - **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. # Marseille, France → Paris, France RTT 🇫🇷 **Marseille, France (MRS)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z captured 50 ICMP echo probes from Marseille to Paris with an average RTT of 8.9 ms, a minimum of 8.72 ms, and a maximum of 9.67 ms. The 0.16 ms standard deviation and 0.13 ms jitter indicate a tightly grouped distribution, and zero packet loss over the sample window points to a stable domestic path. For a 660.5 km straight-line distance, the observed average is 1.38 times the fiber-floor estimate of 6.47 ms, which corresponds to a fiber efficiency of 72.7 percent. The result stays within the Ultra-Low latency tier and leaves little room between the measured value and the theoretical floor for this route. Among the 19 outbound routes in this measurement set, Marseille-Paris ranks first, and its standard-deviation-to-average ratio of about 1.8 percent is well below the network-median 3.28 percent. That combination gives this route the best outbound rank in the set while also keeping variability comparatively low. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **8.9 ms** | | Jitter | **0.13 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **6.47 ms** | | Fiber Efficiency | **72.7%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **660.5 km** | | Vacuum RTT floor | **4.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **6.47 ms** | | Low-latency fiber material floor | **6.44 ms** | | Engineering floor (5% path allowance) | **6.79 ms** | | Research 1.33× mapped-fiber reference | **8.6 ms** | | Estimated unamplified path loss | **138.7 dB** | | Transparent optical spans / inline amplifiers | **9 / 8** | | Published RTT inflation over fiber floor | **1.38×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **8.72 ms** | | Average RTT | **8.9 ms** | | Maximum RTT | **9.67 ms** | | Standard deviation | **0.16 ms** | | Stdev / average | **1.8%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-par-rtt). - **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. # Marseille, France → Seattle, USA RTT 🇫🇷 **Marseille, France (MRS)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo measurements from Marseille, France, to Seattle, USA, produced an average round-trip time of 141.7 ms over 50 samples, with a minimum of 135.29 ms and a maximum of 163.72 ms. Packet loss was zero and the route was rated Good for latency. The 8,707.5 km great-circle distance has a theoretical fiber-floor RTT of 85.27 ms, placing the measured average at 1.66 times that floor and at 60.2% fiber efficiency. The wider gap above the fiber floor indicates the full path operates with more RTT overhead than the geometric minimum, though the 5.67 ms standard deviation and 4.70 ms jitter show the route stayed steady across the 50-sample window. Ranked 11th among the 19 outbound routes from Marseille in the same round, this route's variability sat near the network-wide median standard-deviation-to-average ratio of 3.28%. The key metric for planners is the 141.7 ms average itself, a useful reference for Mediterranean-to-Pacific Northwest latency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **141.7 ms** | | Jitter | **4.7 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.27 ms** | | Fiber Efficiency | **60.2%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,707.5 km** | | Vacuum RTT floor | **58.09 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.27 ms** | | Low-latency fiber material floor | **84.93 ms** | | Engineering floor (5% path allowance) | **89.55 ms** | | Research 1.33× mapped-fiber reference | **113.41 ms** | | Estimated unamplified path loss | **1828.6 dB** | | Transparent optical spans / inline amplifiers | **115 / 114** | | Published RTT inflation over fiber floor | **1.66×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **135.29 ms** | | Average RTT | **141.7 ms** | | Maximum RTT | **163.72 ms** | | Standard deviation | **5.67 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Marseille latency and RTT](/docs/network/latency/pairs/sea-mrs-rtt) — 141.2 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-sea-rtt). - **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. # Marseille, France → Singapore RTT 🇫🇷 **Marseille, France (MRS)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. The Marseille-to-Singapore ICMP echo RTT path averaged 139.6 ms across 50 samples in round 2026-08-16T04:07:28Z, with a minimum of 132.36 ms and a maximum of 163.5 ms. No packets were lost, and the 4.16 ms jitter and 6.56 ms standard deviation point to a stable network path. Marseille, France is a Mediterranean submarine cable landing hub, while Singapore, Singapore is Southeast Asia's interconnection center; this round-trip measurement spans about 10,598.5 km along the great-circle reference. The 139.6 ms average is 1.35 times the 103.79 ms fiber-floor estimate, so the route retains 74.3% fiber efficiency. The route ranked 10th of 19 outbound paths measured in this round. Its standard deviation equals roughly 4.7% of the average RTT, slightly above the round's median standard-deviation-to-average ratio of 3.28%, but the absence of loss and the low jitter keep the overall latency tier at Good. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **139.6 ms** | | Jitter | **4.16 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **103.79 ms** | | Fiber Efficiency | **74.3%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,598.5 km** | | Vacuum RTT floor | **70.71 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **103.79 ms** | | Low-latency fiber material floor | **103.37 ms** | | Engineering floor (5% path allowance) | **108.99 ms** | | Research 1.33× mapped-fiber reference | **138.04 ms** | | Estimated unamplified path loss | **2225.7 dB** | | Transparent optical spans / inline amplifiers | **140 / 139** | | Published RTT inflation over fiber floor | **1.35×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **132.36 ms** | | Average RTT | **139.6 ms** | | Maximum RTT | **163.5 ms** | | Standard deviation | **6.56 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-sin-rtt). - **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. # Marseille, France → Sydney, Australia RTT 🇫🇷 **Marseille, France (MRS)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. The Marseille-to-Sydney ICMP echo RTT path averaged 240.6 ms over 50 samples in round 2026-08-16T04:07:28Z, with a minimum of 231.48 ms and a maximum of 266.22 ms. The route completed with zero packet loss, and the 6.59 ms jitter and 8.19 ms standard deviation show timing stayed relatively consistent. Marseille, France and Sydney, Australia are connected by a great-circle distance of 16,891 km, reflecting Sydney's role as Australia's primary internet gateway. The measured average sits 1.45 times above the 165.41 ms fiber-floor estimate, a 68.7% fiber-efficiency ratio for this European-to-Asia-Pacific path. Ranked 19th of the 19 outbound routes measured in this round, Marseille-Sydney is the long-distance tail of the set, and its latency tier is Fair. The route's standard deviation is about 3.4% of the average RTT, in line with the round's median standard-deviation-to-average ratio of 3.28%, so the elevated RTT is not accompanied by erratic variation. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **240.6 ms** | | Jitter | **6.59 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **165.41 ms** | | Fiber Efficiency | **68.7%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **16,891 km** | | Vacuum RTT floor | **112.68 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **165.41 ms** | | Low-latency fiber material floor | **164.74 ms** | | Engineering floor (5% path allowance) | **173.7 ms** | | Research 1.33× mapped-fiber reference | **219.99 ms** | | Estimated unamplified path loss | **3547.1 dB** | | Transparent optical spans / inline amplifiers | **222 / 221** | | Published RTT inflation over fiber floor | **1.45×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **231.48 ms** | | Average RTT | **240.6 ms** | | Maximum RTT | **266.22 ms** | | Standard deviation | **8.19 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Marseille latency and RTT](/docs/network/latency/pairs/syd-mrs-rtt) — 240.5 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-syd-rtt). - **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. # Marseille, France → Taipei, Taiwan RTT 🇫🇷 **Marseille, France (MRS)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. The Marseille-to-Taipei ICMP echo RTT path averaged 180.9 ms over 50 samples in round 2026-08-16T04:07:28Z, with a minimum of 172.41 ms and a maximum of 200.88 ms. No packets were lost, and the 5.8 ms jitter and 6.92 ms standard deviation suggest the path was steady during the sample window. Both endpoints are significant cable hubs—Marseille on France's Mediterranean coast and Taipei on the East Asia corridor—and the great-circle reference is 10,027.3 km. The measured RTT is 1.84 times the 98.2 ms fiber-floor estimate, so fiber efficiency is 54.3% and the route carries more overhead than its geographic distance alone implies. Ranked 14th of 19 outbound routes measured in this round, Marseille-Taipei falls in the mid-to-upper latency range and is labeled Fair. The round's median standard-deviation-to-average ratio was 3.28%, and this route's variability is comparable, with zero loss and a maximum spread of about 28.5 ms across the 50 samples. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **180.9 ms** | | Jitter | **5.8 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **98.2 ms** | | Fiber Efficiency | **54.3%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,027.3 km** | | Vacuum RTT floor | **66.9 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **98.2 ms** | | Low-latency fiber material floor | **97.8 ms** | | Engineering floor (5% path allowance) | **103.12 ms** | | Research 1.33× mapped-fiber reference | **130.6 ms** | | Estimated unamplified path loss | **2105.7 dB** | | Transparent optical spans / inline amplifiers | **132 / 131** | | Published RTT inflation over fiber floor | **1.84×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **172.41 ms** | | Average RTT | **180.9 ms** | | Maximum RTT | **200.88 ms** | | Standard deviation | **6.92 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Marseille latency and RTT](/docs/network/latency/pairs/tpe-mrs-rtt) — 179.5 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-tpe-rtt). - **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. # Marseille, France → Tokyo, Japan RTT 🇫🇷 **Marseille, France (MRS)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Marseille to Tokyo averaged **203.8 ms** across 50 samples, with a minimum of 194.59 ms and a maximum of 241.85 ms. No packets were lost, and jitter was 7.35 ms, so the path stayed reachable throughout but carried a 47.26 ms gap between its best and worst samples. The geodesic separation of 10,112.8 km sets a vacuum floor of 67.47 ms and a fiber floor of 99.03 ms. The measured average is 2.06 times the fiber floor, which translates to 48.6% fiber efficiency and suggests that the actual path does not follow the straight line between Marseille and Tokyo. This route ranked 17th among the 19 outbound routes measured in the same round, placing it at the slower end of the current outbound profile. Its standard deviation of 8.55 ms is roughly 4.2% of the average RTT, above the network-wide median of 3.28%, so the path combines high absolute latency with a wider-than-median spread. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **203.8 ms** | | Jitter | **7.35 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **99.03 ms** | | Fiber Efficiency | **48.6%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,112.8 km** | | Vacuum RTT floor | **67.47 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **99.03 ms** | | Low-latency fiber material floor | **98.63 ms** | | Engineering floor (5% path allowance) | **104 ms** | | Research 1.33× mapped-fiber reference | **131.71 ms** | | Estimated unamplified path loss | **2123.7 dB** | | Transparent optical spans / inline amplifiers | **133 / 132** | | Published RTT inflation over fiber floor | **2.06×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **194.59 ms** | | Average RTT | **203.8 ms** | | Maximum RTT | **241.85 ms** | | Standard deviation | **8.55 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Marseille latency and RTT](/docs/network/latency/pairs/tyo-mrs-rtt) — 205.6 ms **Fastest routes departing Marseille (MRS)** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mrs-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mrs-tyo-rtt). - **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. # New York, USA → Amsterdam, Netherlands RTT 🇺🇸 **New York, USA (NYC)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT run from New York, USA to Amsterdam, Netherlands averaged 68.7 ms over 50 samples, with a minimum of 66.97 ms and a maximum of 74.13 ms. Packet loss was zero, while the 1.38 ms standard deviation and 1.26 ms jitter place the route in the excellent latency tier. The geodesic distance of 5,877.8 km gives a theoretical fiber-floor RTT of 57.56 ms, so the measured average is just 1.19x that floor. Fiber efficiency reaches 83.8%, meaning the route extracts most of the speed-of-light budget available across the Atlantic. This route ranked 6th of 19 outbound routes in the network's measurement set. Its standard deviation relative to average RTT was 2.01%, below the 3.28% median for that set, so the low average is matched by unusually consistent behavior. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **68.7 ms** | | Jitter | **1.26 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **57.56 ms** | | Fiber Efficiency | **83.8%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,877.8 km** | | Vacuum RTT floor | **39.21 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **57.56 ms** | | Low-latency fiber material floor | **57.33 ms** | | Engineering floor (5% path allowance) | **60.45 ms** | | Research 1.33× mapped-fiber reference | **76.56 ms** | | Estimated unamplified path loss | **1234.3 dB** | | Transparent optical spans / inline amplifiers | **78 / 77** | | Published RTT inflation over fiber floor | **1.19×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **66.97 ms** | | Average RTT | **68.7 ms** | | Maximum RTT | **74.13 ms** | | Standard deviation | **1.38 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (North America → Europe)** * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms * [New York to Frankfurt latency and RTT](/docs/network/latency/pairs/nyc-fra-rtt) — 73.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-ams-rtt). - **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. # New York, USA → Berlin, Germany RTT 🇺🇸 **New York, USA (NYC)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo RTT run from New York, USA to Berlin, Germany averaged 78.8 ms over 50 samples, with a minimum of 77.15 ms and a maximum of 84.9 ms. Zero packet loss, a 1.59 ms standard deviation, and 1.13 ms jitter place this route in the excellent latency tier. Covering a geodesic distance of 6,402.4 km, the route has a theoretical fiber-floor RTT of 62.7 ms. The observed average is 1.26x that floor, for a fiber efficiency of 79.6% — a strong result for an intercontinental route. This route ranked 9th of 19 outbound routes in the network's measurement set. Its standard deviation relative to average RTT was 2.02%, below the 3.28% median for that set, so the extra milliseconds over the fastest routes are not accompanied by added variability. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **78.8 ms** | | Jitter | **1.13 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **62.7 ms** | | Fiber Efficiency | **79.6%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,402.4 km** | | Vacuum RTT floor | **42.71 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **62.7 ms** | | Low-latency fiber material floor | **62.45 ms** | | Engineering floor (5% path allowance) | **65.84 ms** | | Research 1.33× mapped-fiber reference | **83.39 ms** | | Estimated unamplified path loss | **1344.5 dB** | | Transparent optical spans / inline amplifiers | **85 / 84** | | Published RTT inflation over fiber floor | **1.26×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **77.15 ms** | | Average RTT | **78.8 ms** | | Maximum RTT | **84.9 ms** | | Standard deviation | **1.59 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to New York latency and RTT](/docs/network/latency/pairs/ber-nyc-rtt) — 79.6 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (North America → Europe)** * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-ber-rtt). - **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. # New York, USA → Frankfurt, Germany RTT 🇺🇸 **New York, USA (NYC)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round from New York to Frankfurt returned a 73.9 ms average ICMP echo RTT, with 0.0% packet loss across 50 samples. The minimum of 71.94 ms and maximum of 81.47 ms produce a 1.98 ms standard deviation and 1.42 ms jitter, so the delay spread was narrow. Relative to the 60.9 ms fiber-floor estimate for a 6,219 km crossing, the measured average is 21% higher, putting fiber efficiency at 82.4%. The route ranked 8th among 19 outbound routes from New York in this round, and its variability is comfortably below the 3.28% median relative variability for that outbound group. The absence of loss combined with a sub-2 ms standard deviation points to a stable path at the time of measurement. The 73.9 ms figure is a useful ICMP latency baseline for this route, not a predictor of end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **73.9 ms** | | Jitter | **1.42 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **60.9 ms** | | Fiber Efficiency | **82.4%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,219.3 km** | | Vacuum RTT floor | **41.49 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **60.9 ms** | | Low-latency fiber material floor | **60.66 ms** | | Engineering floor (5% path allowance) | **63.96 ms** | | Research 1.33× mapped-fiber reference | **81 ms** | | Estimated unamplified path loss | **1306 dB** | | Transparent optical spans / inline amplifiers | **82 / 81** | | Published RTT inflation over fiber floor | **1.21×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **71.94 ms** | | Average RTT | **73.9 ms** | | Maximum RTT | **81.47 ms** | | Standard deviation | **1.98 ms** | | Stdev / average | **2.7%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to New York latency and RTT](/docs/network/latency/pairs/fra-nyc-rtt) — 74.4 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (North America → Europe)** * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-fra-rtt). - **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. # New York, USA → São Paulo, Brazil RTT 🇺🇸 **New York, USA (NYC)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, 50 ICMP echo samples from New York to São Paulo averaged 106.9 ms, with a minimum of 104.25 ms and a maximum of 117.31 ms. Zero packet loss and 1.84 ms jitter accompany that average. At a great-circle distance of 7,657.6 km, the vacuum round-trip floor is 51.09 ms and the fiber floor is 74.99 ms. The measured average is 1.43 times the fiber floor, putting the route's fiber efficiency at 70.1 percent. Within the measured set of 19 routes from New York, this pairing ranked 11th. Its standard-deviation-to-average ratio is about 2.1 percent, well below the 3.28 percent network median, so individual samples tend to stay close to the 106.9 ms average. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **106.9 ms** | | Jitter | **1.84 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **74.99 ms** | | Fiber Efficiency | **70.1%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,657.6 km** | | Vacuum RTT floor | **51.09 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **74.99 ms** | | Low-latency fiber material floor | **74.69 ms** | | Engineering floor (5% path allowance) | **78.75 ms** | | Research 1.33× mapped-fiber reference | **99.74 ms** | | Estimated unamplified path loss | **1608.1 dB** | | Transparent optical spans / inline amplifiers | **101 / 100** | | Published RTT inflation over fiber floor | **1.43×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **104.25 ms** | | Average RTT | **106.9 ms** | | Maximum RTT | **117.31 ms** | | Standard deviation | **2.21 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [North America to South America](/docs/network/latency/regions/north-america-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to New York latency and RTT](/docs/network/latency/pairs/gru-nyc-rtt) — 122 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-gru-rtt). - **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. # New York, USA → Hong Kong RTT 🇺🇸 **New York, USA (NYC)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, 50 ICMP echo samples from New York to Hong Kong averaged 187.1 ms, with a 178.46 ms minimum and a 215.39 ms maximum. No packets were lost, and jitter was 6.29 ms. The great-circle distance of 12,979.6 km sets a vacuum round-trip floor of 86.59 ms and a fiber floor of 127.11 ms. At 1.47 times the fiber floor, the measured average corresponds to 67.9 percent fiber efficiency. Within the measured set of 19 routes from New York, this pairing ranked 15th. Its standard-deviation-to-average ratio is about 3.94 percent, above the 3.28 percent network median, so a short series of samples gives a more reliable latency picture than any single measurement. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **187.1 ms** | | Jitter | **6.29 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **127.11 ms** | | Fiber Efficiency | **67.9%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,979.6 km** | | Vacuum RTT floor | **86.59 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **127.11 ms** | | Low-latency fiber material floor | **126.6 ms** | | Engineering floor (5% path allowance) | **133.48 ms** | | Research 1.33× mapped-fiber reference | **169.05 ms** | | Estimated unamplified path loss | **2725.7 dB** | | Transparent optical spans / inline amplifiers | **171 / 170** | | Published RTT inflation over fiber floor | **1.47×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **178.46 ms** | | Average RTT | **187.1 ms** | | Maximum RTT | **215.39 ms** | | Standard deviation | **7.38 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to New York latency and RTT](/docs/network/latency/pairs/hkg-nyc-rtt) — 184.7 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-hkg-rtt). - **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. # New York, USA → Ashburn, USA RTT 🇺🇸 **New York, USA (NYC)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo RTT from New York, USA to Ashburn, USA averaged 6 ms, with a 5.58 ms minimum, 7.18 ms maximum, 0.30 ms standard deviation, and 0.26 ms jitter. None of the 50 packets were lost. For the 350.8 km between the two cities, the vacuum floor is 2.34 ms and the straight-line fiber floor is 3.44 ms, so the observed 6 ms average is 1.75 times the fiber floor, or 57.3% fiber efficiency. The absolute latency remains ultra-low, but the inflation illustrates the practical difference between great-circle distance and a real route linking two dense interconnection hubs. This route ranked first among the round's 19 outbound routes. Its 0.30 ms standard deviation is 5.0% of the 6 ms average, higher than the 3.28% median variability, but the variation is still less than one-third of a millisecond. The combination of 6 ms RTT, 0.26 ms jitter, and zero packet loss makes this a useful local performance reference for East Coast interconnection. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **6 ms** | | Jitter | **0.26 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.44 ms** | | Fiber Efficiency | **57.3%** | | Latency Tier | Ultra-Low | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **350.8 km** | | Vacuum RTT floor | **2.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.44 ms** | | Low-latency fiber material floor | **3.42 ms** | | Engineering floor (5% path allowance) | **3.61 ms** | | Research 1.33× mapped-fiber reference | **4.57 ms** | | Estimated unamplified path loss | **73.7 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.75×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **5.58 ms** | | Average RTT | **6 ms** | | Maximum RTT | **7.18 ms** | | Standard deviation | **0.3 ms** | | Stdev / average | **5.0%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms **Fastest routes departing New York (NYC)** * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms **Fastest routes arriving at Ashburn (IAD)** * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms * [Paris to Ashburn latency and RTT](/docs/network/latency/pairs/par-iad-rtt) — 75.5 ms **Same corridor (North America → North America)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-iad-rtt). - **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. # New York, USA → Johannesburg, South Africa RTT 🇺🇸 **New York, USA (NYC)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of ICMP echo RTT measurements from New York, USA to Johannesburg, South Africa used 50 samples at a 100 ms interval. The round-trip time averaged 221.5 ms, with a minimum of 209.09 ms, a maximum of 252.44 ms, and a standard deviation of 9.18 ms; jitter was 8.44 ms and packet loss was 0%. By distance, New York and Johannesburg are about 12,832.9 km apart along the great circle. A direct fiber path for that separation would have a theoretical round-trip floor of 125.67 ms, so the measured average is 1.76 times that floor and the route is operating at 56.7% fiber efficiency. The 85.61 ms vacuum floor provides the absolute lower bound if light could travel in a straight line with no medium. In the 19-city-pair set sharing this measurement direction, the route ranked 19th by average RTT, the highest-latency member of that set. Its standard deviation equals about 4.1% of the average, above the 3.28% median variability seen across the network's measured routes, though zero loss and a 0.0% packet loss figure show the path remained usable throughout the sample. The Fair latency tier fits this profile: high average RTT for an intercontinental link, but no dropped probes and a jitter value below 10 ms. Because the route is already last among the measured pairs for average latency, the most useful future signal is a reduction in the 1.76x inflation over the fiber floor; small changes in jitter alone would not materially change its position. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **221.5 ms** | | Jitter | **8.44 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **125.67 ms** | | Fiber Efficiency | **56.7%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,832.9 km** | | Vacuum RTT floor | **85.61 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **125.67 ms** | | Low-latency fiber material floor | **125.16 ms** | | Engineering floor (5% path allowance) | **131.97 ms** | | Research 1.33× mapped-fiber reference | **167.14 ms** | | Estimated unamplified path loss | **2694.9 dB** | | Transparent optical spans / inline amplifiers | **169 / 168** | | Published RTT inflation over fiber floor | **1.76×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **209.09 ms** | | Average RTT | **221.5 ms** | | Maximum RTT | **252.44 ms** | | Standard deviation | **9.18 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to New York latency and RTT](/docs/network/latency/pairs/jnb-nyc-rtt) — 221.8 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (North America → Africa)** * [Ashburn to Johannesburg latency and RTT](/docs/network/latency/pairs/iad-jnb-rtt) — 228.3 ms * [Miami to Johannesburg latency and RTT](/docs/network/latency/pairs/mia-jnb-rtt) — 259.8 ms * [Seattle to Johannesburg latency and RTT](/docs/network/latency/pairs/sea-jnb-rtt) — 282.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-jnb-rtt). - **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. # New York, USA → Los Angeles, USA RTT 🇺🇸 **New York, USA (NYC)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, the New York-to-Los Angeles ICMP echo path averaged 58.9 ms, with a minimum of 56.67 ms, a maximum of 64.24 ms, and zero packet loss across 50 samples. The 2.02 ms standard deviation and 1.55 ms jitter kept the route inside the excellent latency tier, with no lost probes. Relative to the 3,944.4 km great-circle distance, the vacuum floor would be 26.31 ms and a realistic fiber floor about 38.63 ms; the observed average sits 1.52 times above that fiber floor, implying a fiber efficiency of 65.6%. This suggests the path follows a fairly direct cross-country alignment despite the span. The route placed 4th among 19 outbound routes from New York for the round, and its per-sample variability was slightly above the network's median ratio of 3.28%. With jitter under 2 ms and no loss, the transatlantic corridor endpoint shows stable path characteristics for cross-country monitoring. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **58.9 ms** | | Jitter | **1.55 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **38.63 ms** | | Fiber Efficiency | **65.6%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,944.4 km** | | Vacuum RTT floor | **26.31 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **38.63 ms** | | Low-latency fiber material floor | **38.47 ms** | | Engineering floor (5% path allowance) | **40.56 ms** | | Research 1.33× mapped-fiber reference | **51.37 ms** | | Estimated unamplified path loss | **828.3 dB** | | Transparent optical spans / inline amplifiers | **52 / 51** | | Published RTT inflation over fiber floor | **1.52×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **56.67 ms** | | Average RTT | **58.9 ms** | | Maximum RTT | **64.24 ms** | | Standard deviation | **2.02 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [London to Los Angeles latency and RTT](/docs/network/latency/pairs/lon-lax-rtt) — 127.5 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-lax-rtt). - **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. # New York, USA → London, UK RTT 🇺🇸 **New York, USA (NYC)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo RTT from New York to London averaged 63.5 ms, with a minimum of 61.91 ms and a maximum of 68.19 ms over 50 samples. There was no packet loss, and the 1.32 ms standard deviation with 1.15 ms jitter points to a very consistent transatlantic path. The average sits 16% above the 54.69 ms fiber-floor estimate for the 5,585 km route, giving a fiber efficiency of 86.1%. In this round the route ranked 5th among 19 outbound routes from New York, and its measured variability was well below the 3.28% median relative variability for that outbound group. For a crossing of this length, the absence of loss and the low jitter figure make 63.5 ms a reliable ICMP latency baseline, though ICMP RTT alone should not be used to predict application performance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **63.5 ms** | | Jitter | **1.15 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **54.69 ms** | | Fiber Efficiency | **86.1%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,585.2 km** | | Vacuum RTT floor | **37.26 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **54.69 ms** | | Low-latency fiber material floor | **54.48 ms** | | Engineering floor (5% path allowance) | **57.44 ms** | | Research 1.33× mapped-fiber reference | **72.74 ms** | | Estimated unamplified path loss | **1172.9 dB** | | Transparent optical spans / inline amplifiers | **74 / 73** | | Published RTT inflation over fiber floor | **1.16×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **61.91 ms** | | Average RTT | **63.5 ms** | | Maximum RTT | **68.19 ms** | | Standard deviation | **1.32 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (North America → Europe)** * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms * [New York to Frankfurt latency and RTT](/docs/network/latency/pairs/nyc-fra-rtt) — 73.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-lon-rtt). - **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. # New York, USA → Melbourne, Australia RTT 🇺🇸 **New York, USA (NYC)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, 50 ICMP echo samples from New York to Melbourne averaged 205.1 ms, with a 196.41 ms minimum and a 229.31 ms maximum. Packet loss was zero and jitter was 6.21 ms. At 16,672 km, the great-circle distance sets a vacuum round-trip floor of 111.22 ms and a fiber floor of 163.27 ms. The measured average is 1.26 times the fiber floor, yielding 79.6 percent fiber efficiency. Within the measured set of 19 routes from New York, this pairing ranked 17th. Its standard-deviation-to-average ratio of about 3.29 percent closely matches the 3.28 percent network median, and the low inflation over the fiber floor suggests an efficient use of the long distance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **205.1 ms** | | Jitter | **6.21 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **163.27 ms** | | Fiber Efficiency | **79.6%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **16,672 km** | | Vacuum RTT floor | **111.22 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **163.27 ms** | | Low-latency fiber material floor | **162.61 ms** | | Engineering floor (5% path allowance) | **171.45 ms** | | Research 1.33× mapped-fiber reference | **217.14 ms** | | Estimated unamplified path loss | **3501.1 dB** | | Transparent optical spans / inline amplifiers | **219 / 218** | | Published RTT inflation over fiber floor | **1.26×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **196.41 ms** | | Average RTT | **205.1 ms** | | Maximum RTT | **229.31 ms** | | Standard deviation | **6.74 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to New York latency and RTT](/docs/network/latency/pairs/mel-nyc-rtt) — 204.2 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-mel-rtt). - **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. # New York, USA → Miami, USA RTT 🇺🇸 **New York, USA (NYC)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, New York to Miami averaged 32.9 ms, with a minimum of 31.54 ms, a maximum of 39.09 ms, and zero packet loss. The 1.24 ms standard deviation and 0.86 ms jitter confirm an excellent latency tier with a notably tight distribution. Over a 1,753.2 km great-circle path, the vacuum floor is 11.7 ms and the fiber floor 17.17 ms. The observed 32.9 ms average is 1.92 times the fiber floor, or 52.2% fiber efficiency, so the route is quick in absolute terms but still carries measurable geographic overhead relative to the straight-line path. It ranked 2nd among 19 outbound routes from New York, with a coefficient of variation around 3.8%, slightly above the network's median of 3.28%. The combination of low jitter, no loss, and a strong route ranking makes this path a consistent eastern-seaboard reference for latency triage. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **32.9 ms** | | Jitter | **0.86 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **17.17 ms** | | Fiber Efficiency | **52.2%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,753.2 km** | | Vacuum RTT floor | **11.7 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **17.17 ms** | | Low-latency fiber material floor | **17.1 ms** | | Engineering floor (5% path allowance) | **18.03 ms** | | Research 1.33× mapped-fiber reference | **22.83 ms** | | Estimated unamplified path loss | **368.2 dB** | | Transparent optical spans / inline amplifiers | **24 / 23** | | Published RTT inflation over fiber floor | **1.92×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **31.54 ms** | | Average RTT | **32.9 ms** | | Maximum RTT | **39.09 ms** | | Standard deviation | **1.24 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-mia-rtt). - **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. # New York, USA → Moscow, Russia RTT 🇺🇸 **New York, USA (NYC)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. On the 2026-08-16T04:07:28Z round, ICMP echo RTT from New York, USA to Moscow, Russia averaged 107 ms, with a 101.46 ms minimum, 119.28 ms maximum, 4.26 ms standard deviation, and 3.73 ms jitter. All 50 samples returned without packet loss. Against the 50.24 ms vacuum floor and 73.75 ms straight-line fiber floor for the 7,531.3 km separation, the observed average is 1.45 times the fiber floor, or 68.9% fiber efficiency. The extra time reflects the practical distance of a transatlantic-and-continental route, while the stable minimum and zero loss keep this path in the Good latency tier. This link ranked 12th among the round's 19 outbound routes. Its standard deviation is about 3.98% of the average, slightly above the 3.28% median variability for that route set. For teams treating Moscow as a gateway toward Asia-Pacific, this 107 ms RTT provides a useful eastward baseline from the US East Coast. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **107 ms** | | Jitter | **3.73 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **73.75 ms** | | Fiber Efficiency | **68.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,531.3 km** | | Vacuum RTT floor | **50.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **73.75 ms** | | Low-latency fiber material floor | **73.46 ms** | | Engineering floor (5% path allowance) | **77.45 ms** | | Research 1.33× mapped-fiber reference | **98.09 ms** | | Estimated unamplified path loss | **1581.6 dB** | | Transparent optical spans / inline amplifiers | **99 / 98** | | Published RTT inflation over fiber floor | **1.45×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **101.46 ms** | | Average RTT | **107 ms** | | Maximum RTT | **119.28 ms** | | Standard deviation | **4.26 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to New York latency and RTT](/docs/network/latency/pairs/mow-nyc-rtt) — 107.5 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (North America → Europe)** * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-mow-rtt). - **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. # New York, USA → Marseille, France RTT 🇺🇸 **New York, USA (NYC)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round from New York to Marseille recorded an 80.2 ms average ICMP echo RTT, with 0.0% packet loss across 50 samples. The minimum of 78.94 ms and maximum of 85.06 ms translate to a 1.32 ms standard deviation and 0.93 ms jitter, so the path remained stable at this latency level. Relative to the 61.91 ms fiber-floor estimate for a 6,321.9 km route, the measured average is 30% above the floor, putting fiber efficiency at 77.2%. This route ranked 10th among 19 outbound routes from New York in this round, and its relative variability was below the 3.28% median for that outbound group. The absence of loss and the tight delay spread are useful signs that the path was stable during the round. The 80.2 ms figure is a useful ICMP latency baseline for a Mediterranean landing route, but it should not be interpreted as a forecast of end-user application speed. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **80.2 ms** | | Jitter | **0.93 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **61.91 ms** | | Fiber Efficiency | **77.2%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,321.9 km** | | Vacuum RTT floor | **42.18 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **61.91 ms** | | Low-latency fiber material floor | **61.66 ms** | | Engineering floor (5% path allowance) | **65.01 ms** | | Research 1.33× mapped-fiber reference | **82.34 ms** | | Estimated unamplified path loss | **1327.6 dB** | | Transparent optical spans / inline amplifiers | **83 / 82** | | Published RTT inflation over fiber floor | **1.3×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **78.94 ms** | | Average RTT | **80.2 ms** | | Maximum RTT | **85.06 ms** | | Standard deviation | **1.32 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to New York latency and RTT](/docs/network/latency/pairs/mrs-nyc-rtt) — 79.8 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (North America → Europe)** * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-mrs-rtt). - **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. # New York, USA → Paris, France RTT 🇺🇸 **New York, USA (NYC)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. Round 2026-08-16T04:07:28Z measured ICMP echo RTT from New York, USA to Paris, France at 68.9 ms on average, with a 67.48 ms minimum, 73.26 ms maximum, 1.31 ms standard deviation, and 1.05 ms jitter. All 50 samples were returned with zero packet loss. The geodesic distance of 5,852.7 km implies a vacuum floor of 39.05 ms and a straight-line fiber floor of 57.31 ms. At 68.9 ms, the measured average is only 1.2 times that fiber floor, or 83.2% fiber efficiency, a strong result for a transatlantic route. Within the round's 19 outbound routes, this path ranked 7th. Its standard deviation equals 1.90% of the average, comfortably below the 3.28% median variability, and the 1.05 ms jitter points to a very stable handoff. Given Paris's role as a dense interconnection market with national and pan-European fiber paths, this RTT is a clean benchmark for traffic crossing into France. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **68.9 ms** | | Jitter | **1.05 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **57.31 ms** | | Fiber Efficiency | **83.2%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,852.7 km** | | Vacuum RTT floor | **39.05 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **57.31 ms** | | Low-latency fiber material floor | **57.08 ms** | | Engineering floor (5% path allowance) | **60.19 ms** | | Research 1.33× mapped-fiber reference | **76.23 ms** | | Estimated unamplified path loss | **1229.1 dB** | | Transparent optical spans / inline amplifiers | **77 / 76** | | Published RTT inflation over fiber floor | **1.2×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **67.48 ms** | | Average RTT | **68.9 ms** | | Maximum RTT | **73.26 ms** | | Standard deviation | **1.31 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (North America → Europe)** * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 ms * [New York to Frankfurt latency and RTT](/docs/network/latency/pairs/nyc-fra-rtt) — 73.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-par-rtt). - **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. # New York, USA → Seattle, USA RTT 🇺🇸 **New York, USA (NYC)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, New York-to-Seattle ICMP echo RTT averaged 58.7 ms, with a minimum of 56.64 ms, a maximum of 67.85 ms, and no packet loss. The 2.09 ms standard deviation and 1.34 ms jitter place the route in the excellent latency tier. Against a 3,875.5 km great-circle path, the vacuum floor is 25.85 ms and the fiber floor 37.95 ms, so the observed average is 1.55 times the fiber floor and represents 64.7% fiber efficiency. That suggests a reasonably direct transcontinental path with only a modest amount of extra distance. The route ranked 3rd among 19 outbound routes from New York, while its variability was slightly above the network's median ratio of 3.28%. Zero loss and stable jitter make the route's measured latency dependable for cross-country monitoring. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **58.7 ms** | | Jitter | **1.34 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **37.95 ms** | | Fiber Efficiency | **64.7%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,875.5 km** | | Vacuum RTT floor | **25.85 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **37.95 ms** | | Low-latency fiber material floor | **37.8 ms** | | Engineering floor (5% path allowance) | **39.85 ms** | | Research 1.33× mapped-fiber reference | **50.48 ms** | | Estimated unamplified path loss | **813.9 dB** | | Transparent optical spans / inline amplifiers | **51 / 50** | | Published RTT inflation over fiber floor | **1.55×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **56.64 ms** | | Average RTT | **58.7 ms** | | Maximum RTT | **67.85 ms** | | Standard deviation | **2.09 ms** | | Stdev / average | **3.6%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-sea-rtt). - **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. # New York, USA → Singapore RTT 🇺🇸 **New York, USA (NYC)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, 50 ICMP echo requests sent every 100 ms from New York to Singapore returned an average round-trip time of 208.7 ms, with a minimum of 197.34 ms and a maximum of 232.34 ms. There was no packet loss, but the 8.03 ms standard deviation and 7.87 ms jitter show noticeable fluctuation across the sample. Against the theoretical fiber-floor minimum of 150.29 ms, the measured average is 1.39 times that floor, a fiber efficiency of 72 percent. In the context of 19 outbound routes measured from New York, this route ranked 18th, placing it near the slow end of the set. Its standard-deviation-to-average ratio is about 3.8 percent, higher than the 3.28 percent median observed across those routes, so this path showed slightly more RTT variability than the typical New York outbound route in this round. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **208.7 ms** | | Jitter | **7.87 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **150.29 ms** | | Fiber Efficiency | **72%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,347.5 km** | | Vacuum RTT floor | **102.39 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **150.29 ms** | | Low-latency fiber material floor | **149.69 ms** | | Engineering floor (5% path allowance) | **157.83 ms** | | Research 1.33× mapped-fiber reference | **199.89 ms** | | Estimated unamplified path loss | **3223 dB** | | Transparent optical spans / inline amplifiers | **202 / 201** | | Published RTT inflation over fiber floor | **1.39×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **197.34 ms** | | Average RTT | **208.7 ms** | | Maximum RTT | **232.34 ms** | | Standard deviation | **8.03 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to New York latency and RTT](/docs/network/latency/pairs/sin-nyc-rtt) — 209.3 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-sin-rtt). - **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. # New York, USA → Sydney, Australia RTT 🇺🇸 **New York, USA (NYC)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. In round 2026-08-16T04:07:28Z, the New York-to-Sydney ICMP path averaged 192.6 ms over 50 echo samples sent at 100 ms intervals, with a floor of 185.89 ms and a ceiling of 212.11 ms. All samples arrived with 0 percent loss, and the 5.61 ms standard deviation plus 4.03 ms jitter indicate a comparatively stable RTT profile. Measured latency sits 1.23 times above the 156.57 ms fiber-floor estimate, an 81.3 percent fiber efficiency for the round. Among the 19 outbound routes from New York, this route ranked 16th. Its standard-deviation-to-average ratio is roughly 2.9 percent, below the 3.28 percent median across the route set, so the path was steadier than the typical New York outbound route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **192.6 ms** | | Jitter | **4.03 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **156.57 ms** | | Fiber Efficiency | **81.3%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,988.1 km** | | Vacuum RTT floor | **106.66 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **156.57 ms** | | Low-latency fiber material floor | **155.94 ms** | | Engineering floor (5% path allowance) | **164.42 ms** | | Research 1.33× mapped-fiber reference | **208.24 ms** | | Estimated unamplified path loss | **3357.5 dB** | | Transparent optical spans / inline amplifiers | **210 / 209** | | Published RTT inflation over fiber floor | **1.23×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **185.89 ms** | | Average RTT | **192.6 ms** | | Maximum RTT | **212.11 ms** | | Standard deviation | **5.61 ms** | | Stdev / average | **2.9%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to New York latency and RTT](/docs/network/latency/pairs/syd-nyc-rtt) — 191.9 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-syd-rtt). - **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. # New York, USA → Taipei, Taiwan RTT 🇺🇸 **New York, USA (NYC)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round from New York to Taipei produced an average ICMP RTT of 173.4 ms, with 50 samples at 100 ms intervals ranging from 169.05 ms to 186.13 ms and zero packet loss. Latency variability was tight: the standard deviation was 3.35 ms and jitter 3.23 ms. Against the 122.89 ms fiber-floor estimate, the observed average is 1.41 times higher, equivalent to a 70.9 percent fiber efficiency for this route. Within the 19 outbound routes from New York, this route ranked 14th. Its standard-deviation-to-average ratio of about 1.9 percent is well below the 3.28 percent median across the route set, making the ICMP RTT profile one of the steadier New York outbound measurements in this round. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **173.4 ms** | | Jitter | **3.23 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **122.89 ms** | | Fiber Efficiency | **70.9%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,549.1 km** | | Vacuum RTT floor | **83.72 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **122.89 ms** | | Low-latency fiber material floor | **122.4 ms** | | Engineering floor (5% path allowance) | **129.05 ms** | | Research 1.33× mapped-fiber reference | **163.44 ms** | | Estimated unamplified path loss | **2635.3 dB** | | Transparent optical spans / inline amplifiers | **165 / 164** | | Published RTT inflation over fiber floor | **1.41×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **169.05 ms** | | Average RTT | **173.4 ms** | | Maximum RTT | **186.13 ms** | | Standard deviation | **3.35 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to New York latency and RTT](/docs/network/latency/pairs/tpe-nyc-rtt) — 174.2 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-tpe-rtt). - **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. # New York, USA → Tokyo, Japan RTT 🇺🇸 **New York, USA (NYC)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes sent from New York to Tokyo at 100 ms intervals averaged 143.1 ms, with a minimum of 136.69 ms and a maximum of 171.34 ms. The standard deviation was 6.58 ms and jitter was 4.7 ms; all 50 probes returned, so packet loss was 0%. The geodesic distance is 10,872.7 km, implying a vacuum light-speed floor of 72.53 ms and a realistic fiber-path floor of 106.47 ms. The observed average is 1.34 times that fiber floor, equivalent to 74.4% efficiency relative to the theoretical minimum. This route ranks 13th among the 19 outbound routes in the same network measurement set. Its own variability is 4.6% of the average latency, noticeably above the network's median ratio of 3.28%, so although the RTT is in the Good tier and loss-free, latency variation is a bit wider than the typical route in this set. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **143.1 ms** | | Jitter | **4.7 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.47 ms** | | Fiber Efficiency | **74.4%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,872.7 km** | | Vacuum RTT floor | **72.53 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.47 ms** | | Low-latency fiber material floor | **106.05 ms** | | Engineering floor (5% path allowance) | **111.81 ms** | | Research 1.33× mapped-fiber reference | **141.61 ms** | | Estimated unamplified path loss | **2283.3 dB** | | Transparent optical spans / inline amplifiers | **143 / 142** | | Published RTT inflation over fiber floor | **1.34×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **136.69 ms** | | Average RTT | **143.1 ms** | | Maximum RTT | **171.34 ms** | | Standard deviation | **6.58 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to New York latency and RTT](/docs/network/latency/pairs/tyo-nyc-rtt) — 144.6 ms **Fastest routes departing New York (NYC)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/nyc-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/nyc-tyo-rtt). - **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. # Paris, France → Amsterdam, Netherlands RTT 🇫🇷 **Paris, France (PAR)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from Paris, France, to Amsterdam, Netherlands returned an average RTT of 7 ms, with a minimum of 6.65 ms and a maximum of 8.5 ms. No packets were lost, and jitter was 0.24 ms, so the path remained extremely steady across the 100 ms sampling interval. The measured path covers a geodesic distance of 430.9 km. Against a fiber-floor estimate of 4.22 ms, the observed average is 1.66 times that floor, a fiber efficiency of 60.3% and a relatively small gap between theoretical distance and actual round-trip time. This route ranked 2nd among 19 outbound routes. Its standard deviation of 0.33 ms is about 4.7% of the average, slightly above the median variability of 3.28% across the same route set; in absolute terms, however, the route stays within a narrow, loss-free range and remains an ultra-low-latency ICMP path. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **7 ms** | | Jitter | **0.24 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **4.22 ms** | | Fiber Efficiency | **60.3%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **430.9 km** | | Vacuum RTT floor | **2.87 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **4.22 ms** | | Low-latency fiber material floor | **4.2 ms** | | Engineering floor (5% path allowance) | **4.43 ms** | | Research 1.33× mapped-fiber reference | **5.61 ms** | | Estimated unamplified path loss | **90.5 dB** | | Transparent optical spans / inline amplifiers | **6 / 5** | | Published RTT inflation over fiber floor | **1.66×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **6.65 ms** | | Average RTT | **7 ms** | | Maximum RTT | **8.5 ms** | | Standard deviation | **0.33 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms * [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-ams-rtt). - **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. # Paris, France → Berlin, Germany RTT 🇫🇷 **Paris, France (PAR)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round sent 50 ICMP echo requests from Paris, France, to Berlin, Germany and produced an average RTT of 15.5 ms, with a minimum of 14.87 ms and a maximum of 17.28 ms. Packet loss was 0% and jitter was 0.43 ms, indicating a consistent, lossless path over the sampling window. The geodesic distance between the two cities is 880.6 km. Compared with a fiber-floor estimate of 8.62 ms, the measured average is 1.8 times higher, translating to a fiber efficiency of 55.6%; that still places the route in the ultra-low latency tier for this east–west European corridor. This route ranked 5th among 19 outbound routes. Its standard deviation of 0.57 ms is 3.7% of the average, close to the median variability of 3.28% across the same route set. The main insight is that the RTT is tightly clustered around 15.5 ms, making that average a dependable reference for this ICMP measurement round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **15.5 ms** | | Jitter | **0.43 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **8.62 ms** | | Fiber Efficiency | **55.6%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **880.6 km** | | Vacuum RTT floor | **5.87 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **8.62 ms** | | Low-latency fiber material floor | **8.59 ms** | | Engineering floor (5% path allowance) | **9.06 ms** | | Research 1.33× mapped-fiber reference | **11.47 ms** | | Estimated unamplified path loss | **184.9 dB** | | Transparent optical spans / inline amplifiers | **12 / 11** | | Published RTT inflation over fiber floor | **1.8×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **14.87 ms** | | Average RTT | **15.5 ms** | | Maximum RTT | **17.28 ms** | | Standard deviation | **0.57 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms * [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-ber-rtt). - **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. # Paris, France → Frankfurt, Germany RTT 🇫🇷 **Paris, France (PAR)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from Paris, France, to Frankfurt, Germany produced an average RTT of 7.6 ms, a minimum of 7.35 ms, and a maximum of 8.42 ms. The path lost no packets, and jitter was 0.19 ms. The geodesic distance is 479.9 km, and the fiber-floor estimate is 4.7 ms. The observed 7.6 ms average sits 1.62 times above that floor, for a fiber efficiency of 61.8% and a compact gap between physical distance and measured round-trip time. This route ranked 3rd among 19 outbound routes. Its standard deviation of 0.22 ms is 2.9% of the average, below the median variability of 3.28% across the same route set, so it is both fast and unusually steady. The useful takeaway is that Paris-to-Frankfurt ICMP RTT stays within roughly 1 ms from minimum to maximum while remaining below 8.5 ms in every sample. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **7.6 ms** | | Jitter | **0.19 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **4.7 ms** | | Fiber Efficiency | **61.8%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **479.9 km** | | Vacuum RTT floor | **3.2 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **4.7 ms** | | Low-latency fiber material floor | **4.68 ms** | | Engineering floor (5% path allowance) | **4.93 ms** | | Research 1.33× mapped-fiber reference | **6.25 ms** | | Estimated unamplified path loss | **100.8 dB** | | Transparent optical spans / inline amplifiers | **7 / 6** | | Published RTT inflation over fiber floor | **1.62×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **7.35 ms** | | Average RTT | **7.6 ms** | | Maximum RTT | **8.42 ms** | | Standard deviation | **0.22 ms** | | Stdev / average | **2.9%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms * [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-fra-rtt). - **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. # Paris, France → São Paulo, Brazil RTT 🇫🇷 **Paris, France (PAR)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Paris, France to São Paulo, Brazil averaged 175.8 ms across 50 samples, with a minimum of 173.09 ms and a maximum of 186.7 ms. No packets were lost, and jitter was 2.5 ms. This route ranked 15th among 19 outbound routes measured from Paris, putting it in the lower portion of the set. Its standard deviation is 2.78 ms, about 1.6 percent of the average RTT, well below the 3.28 percent median relative variability; the higher latency is paired with consistent timing. The great-circle distance is 9,377.8 km, and the mean RTT is about 1.91 times the estimated fiber floor, implying a fiber efficiency of 52.2%. That lower efficiency points toward a lengthier or less direct intercontinental crossing, though the zero-loss, low-jitter result shows the route remains stable at the network layer. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **175.8 ms** | | Jitter | **2.5 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.83 ms** | | Fiber Efficiency | **52.2%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,377.8 km** | | Vacuum RTT floor | **62.56 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.83 ms** | | Low-latency fiber material floor | **91.47 ms** | | Engineering floor (5% path allowance) | **96.44 ms** | | Research 1.33× mapped-fiber reference | **122.14 ms** | | Estimated unamplified path loss | **1969.3 dB** | | Transparent optical spans / inline amplifiers | **124 / 123** | | Published RTT inflation over fiber floor | **1.91×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **173.09 ms** | | Average RTT | **175.8 ms** | | Maximum RTT | **186.7 ms** | | Standard deviation | **2.78 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Europe → South America)** * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms * [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms * [Frankfurt to São Paulo latency and RTT](/docs/network/latency/pairs/fra-gru-rtt) — 181.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-gru-rtt). - **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. # Paris, France → Hong Kong RTT 🇫🇷 **Paris, France (PAR)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z collected 50 ICMP echo samples from Paris to Hong Kong, yielding an average round-trip time of 160.1 ms and a minimum of 155.89 ms. The maximum observed RTT was 182.08 ms, with a standard deviation of 4.45 ms and jitter of 2.89 ms; no packets were lost. The geodesic distance of 9,647.6 km implies a theoretical fiber-floor RTT near 94.48 ms, so the measured average sits 1.69 times above that floor. The route is running at 59% fiber efficiency, meaning the gap over the straight-line fiber ideal is substantial but the low jitter and zero loss indicate the delay profile is consistent rather than erratic. Within this round, the Paris-to-Hong Kong route ranked 13th among 19 outbound paths, and its relative variability of about 2.8% sits below the 3.28% median stability ratio for the round. For capacity planning, the route offers a stable delay profile with a clear propagation floor that dominates the observed RTT. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **160.1 ms** | | Jitter | **2.89 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **94.48 ms** | | Fiber Efficiency | **59%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,647.6 km** | | Vacuum RTT floor | **64.36 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **94.48 ms** | | Low-latency fiber material floor | **94.1 ms** | | Engineering floor (5% path allowance) | **99.21 ms** | | Research 1.33× mapped-fiber reference | **125.65 ms** | | Estimated unamplified path loss | **2026 dB** | | Transparent optical spans / inline amplifiers | **127 / 126** | | Published RTT inflation over fiber floor | **1.69×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **155.89 ms** | | Average RTT | **160.1 ms** | | Maximum RTT | **182.08 ms** | | Standard deviation | **4.45 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Paris latency and RTT](/docs/network/latency/pairs/hkg-par-rtt) — 159.4 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms * [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-rtt) — 144.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-hkg-rtt). - **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. # Paris, France → Ashburn, USA RTT 🇫🇷 **Paris, France (PAR)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of 50 ICMP probes from Paris to Ashburn returned a 75.5 ms average RTT, a 2.46 ms standard deviation, and 2.26 ms jitter. No packets were lost, and the fastest reply came in at 72.75 ms while the slowest reached 85.2 ms. That result placed the route eighth among the 19 outbound paths measured from Paris in this round. Its run-to-run spread worked out to about 3.26 percent of the average, slightly below the 3.28 percent median variability across the measured routes, so timing on the transatlantic leg stayed unusually consistent. For a 6,202 km great-circle distance, the average sits roughly 15 ms above the 60.73 ms fiber lower bound, an inflation factor of 1.24 that corresponds to about 80 percent fiber efficiency. The zero-loss sample and narrow min-max range make this a notably stable path into the Northern Virginia corridor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **75.5 ms** | | Jitter | **2.26 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **60.73 ms** | | Fiber Efficiency | **80.4%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **6,202 km** | | Vacuum RTT floor | **41.38 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **60.73 ms** | | Low-latency fiber material floor | **60.49 ms** | | Engineering floor (5% path allowance) | **63.78 ms** | | Research 1.33× mapped-fiber reference | **80.78 ms** | | Estimated unamplified path loss | **1302.4 dB** | | Transparent optical spans / inline amplifiers | **82 / 81** | | Published RTT inflation over fiber floor | **1.24×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **72.75 ms** | | Average RTT | **75.5 ms** | | Maximum RTT | **85.2 ms** | | Standard deviation | **2.46 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Paris latency and RTT](/docs/network/latency/pairs/iad-par-rtt) — 76.1 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-iad-rtt). - **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. # Paris, France → Johannesburg, South Africa RTT 🇫🇷 **Paris, France (PAR)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. On the 2026-08-16T04:07:28Z ICMP echo round, probes from Paris, France to Johannesburg, South Africa averaged 180.9 ms across 50 samples, with a minimum of 176.39 ms, a maximum of 195.6 ms and zero packet loss. Measured jitter was 3.26 ms, keeping the route stable even though its 180.9 ms average places it in the Fair latency tier. The physical reference for this 8,697.3 km route is a vacuum floor of 58.02 ms and a fiber floor of 85.17 ms. The observed average is 2.12 times the fiber floor, which translates to 47.1% fiber efficiency; that is a realistic outcome for an intercontinental path to Southern Africa and leaves meaningful headroom over the theoretical minimum. Across the network's 19 outbound routes, Paris–Johannesburg ranks 16th, so it sits on the slower end of the measured set, as its distance would suggest. Its standard deviation of 3.41 ms is about 1.9% of the average, comfortably below the network's median 3.28% dispersion, so the route's long path is paired with notably consistent timing. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **180.9 ms** | | Jitter | **3.26 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.17 ms** | | Fiber Efficiency | **47.1%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,697.3 km** | | Vacuum RTT floor | **58.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.17 ms** | | Low-latency fiber material floor | **84.83 ms** | | Engineering floor (5% path allowance) | **89.44 ms** | | Research 1.33× mapped-fiber reference | **113.28 ms** | | Estimated unamplified path loss | **1826.4 dB** | | Transparent optical spans / inline amplifiers | **115 / 114** | | Published RTT inflation over fiber floor | **2.12×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **176.39 ms** | | Average RTT | **180.9 ms** | | Maximum RTT | **195.6 ms** | | Standard deviation | **3.41 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms * [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt) — 198.5 ms **Same corridor (Europe → Africa)** * [Moscow to Johannesburg latency and RTT](/docs/network/latency/pairs/mow-jnb-rtt) — 201.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-jnb-rtt). - **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. # Paris, France → Los Angeles, USA RTT 🇫🇷 **Paris, France (PAR)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round sent 50 ICMP probes from Paris to Los Angeles and recorded a 136.5 ms average RTT, with a 5.13 ms standard deviation and 3.55 ms jitter. The fastest probe was 130.92 ms, the slowest 152.23 ms, and packet loss stayed at zero. This route ranked eleventh among the 19 outbound paths measured from Paris in the same round. Its variability was about 3.76 percent of the average, higher than the 3.28 percent median spread across the measured routes, indicating a bit more run-to-run fluctuation than most Paris outbound paths. Across the 9,107 km great-circle distance, the measured average sits about 47 ms above the 89.18 ms fiber lower bound, a 1.53x inflation that puts the route at roughly 65 percent fiber efficiency. For a path connecting Northwest Europe to the US West Coast, this indicates a meaningful gap over the geographic ideal, even though the sample recorded zero packet loss and moderate jitter. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **136.5 ms** | | Jitter | **3.55 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **89.18 ms** | | Fiber Efficiency | **65.3%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,107.2 km** | | Vacuum RTT floor | **60.76 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **89.18 ms** | | Low-latency fiber material floor | **88.83 ms** | | Engineering floor (5% path allowance) | **93.66 ms** | | Research 1.33× mapped-fiber reference | **118.62 ms** | | Estimated unamplified path loss | **1912.5 dB** | | Transparent optical spans / inline amplifiers | **120 / 119** | | Published RTT inflation over fiber floor | **1.53×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **130.92 ms** | | Average RTT | **136.5 ms** | | Maximum RTT | **152.23 ms** | | Standard deviation | **5.13 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Paris latency and RTT](/docs/network/latency/pairs/lax-par-rtt) — 135.9 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-lax-rtt). - **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. # Paris, France → London, UK RTT 🇫🇷 **Paris, France (PAR)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Paris to London averaged 6.4 ms across 50 samples, with a minimum of 6.03 ms and a maximum of 7.35 ms. No packets were lost, and jitter was 0.2 ms. This route ranked first among the 19 outbound routes from Paris measured in the same round. Its standard deviation of 0.26 ms on the 6.4 ms average gives a relative spread of about 4.1%, slightly above the 3.3% median for that route set. For the 344 km great-circle distance, the theoretical fiber floor is 3.37 ms; the measured average is about 1.9 times that floor, or 52.7% fiber efficiency. The stable minimum-to-maximum range and zero packet loss make this a useful reference point for Paris-London connectivity. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **6.4 ms** | | Jitter | **0.2 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **3.37 ms** | | Fiber Efficiency | **52.7%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **344.1 km** | | Vacuum RTT floor | **2.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **3.37 ms** | | Low-latency fiber material floor | **3.36 ms** | | Engineering floor (5% path allowance) | **3.54 ms** | | Research 1.33× mapped-fiber reference | **4.48 ms** | | Estimated unamplified path loss | **72.3 dB** | | Transparent optical spans / inline amplifiers | **5 / 4** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **6.03 ms** | | Average RTT | **6.4 ms** | | Maximum RTT | **7.35 ms** | | Standard deviation | **0.26 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms **Fastest routes departing Paris (PAR)** * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms * [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms **Same corridor (Europe → Europe)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-lon-rtt). - **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. # Paris, France → Melbourne, Australia RTT 🇫🇷 **Paris, France (PAR)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Paris to Melbourne averaged 246.4 ms, with a minimum of 232.44 ms and a maximum of 296.68 ms. The standard deviation was 11.89 ms, jitter was 11.49 ms, and all samples returned successfully with zero packet loss. At 16,787.7 km apart, the theoretical fiber-floor RTT is about 164.4 ms, placing the observed average at 1.5 times that benchmark and 66.7% fiber efficiency. The spread between minimum and maximum is 64.24 ms, which is wider than the jitter metric alone might suggest, so the route has a noticeable worst-case tail. Ranked 18th among the 19 outbound paths in this round, Paris-Melbourne sits near the high-latency end of the current Paris outbound set. Its relative variability of approximately 4.8% is above the 3.28% median stability ratio for the round, making this route one where both average delay and delay variation should be tracked together. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **246.4 ms** | | Jitter | **11.49 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **164.4 ms** | | Fiber Efficiency | **66.7%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,787.7 km** | | Vacuum RTT floor | **112 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **164.4 ms** | | Low-latency fiber material floor | **163.74 ms** | | Engineering floor (5% path allowance) | **172.64 ms** | | Research 1.33× mapped-fiber reference | **218.65 ms** | | Estimated unamplified path loss | **3525.4 dB** | | Transparent optical spans / inline amplifiers | **221 / 220** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **232.44 ms** | | Average RTT | **246.4 ms** | | Maximum RTT | **296.68 ms** | | Standard deviation | **11.89 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Paris latency and RTT](/docs/network/latency/pairs/mel-par-rtt) — 246.5 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-mel-rtt). - **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. # Paris, France → Miami, USA RTT 🇫🇷 **Paris, France (PAR)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of 50 ICMP probes from Paris to Miami produced a 106.8 ms average RTT, a 5.28 ms standard deviation, and 4.08 ms jitter. Every probe was answered, with the fastest at 101.15 ms and the slowest at 125.38 ms. This route placed ninth among the 19 outbound paths measured from Paris in the same round. Its variability came to about 4.9 percent of the average, clearly above the 3.28 percent median spread seen across the measured routes, so this leg showed more timing fluctuation than a typical Paris outbound path. For the 7,369 km great-circle distance, the average sits about 35 ms above the 72.16 ms fiber lower bound, an inflation factor of 1.48 that yields roughly 68 percent fiber efficiency. The 24 ms gap between fastest and slowest probes is wider than the jitter figure alone suggests, so the average masks a meaningful amount of variability on this gateway path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **106.8 ms** | | Jitter | **4.08 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.16 ms** | | Fiber Efficiency | **67.6%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,368.8 km** | | Vacuum RTT floor | **49.16 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.16 ms** | | Low-latency fiber material floor | **71.87 ms** | | Engineering floor (5% path allowance) | **75.78 ms** | | Research 1.33× mapped-fiber reference | **95.97 ms** | | Estimated unamplified path loss | **1547.4 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.48×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **101.15 ms** | | Average RTT | **106.8 ms** | | Maximum RTT | **125.38 ms** | | Standard deviation | **5.28 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Paris latency and RTT](/docs/network/latency/pairs/mia-par-rtt) — 106.2 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-mia-rtt). - **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. # Paris, France → Moscow, Russia RTT 🇫🇷 **Paris, France (PAR)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Paris to Moscow averaged 44.7 ms across 50 samples, with a minimum of 43.04 ms and a maximum of 51.46 ms. No packets were lost, and jitter was 1.18 ms. This route ranked sixth among the 19 outbound routes from Paris measured in the same round. The 1.56 ms standard deviation on the 44.7 ms average is a relative spread of about 3.5%, close to the 3.3% median for that route set. For the 2,494 km great-circle distance, the theoretical fiber floor is 24.42 ms; the measured average is about 1.83 times that floor, or 54.6% fiber efficiency. The zero-loss result and the bounded 43.04 to 51.46 ms range indicate a stable long-haul path, consistent with Moscow's role as an eastward backbone transit corridor toward Asia-Pacific networks. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **44.7 ms** | | Jitter | **1.18 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **24.42 ms** | | Fiber Efficiency | **54.6%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,494.1 km** | | Vacuum RTT floor | **16.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **24.42 ms** | | Low-latency fiber material floor | **24.33 ms** | | Engineering floor (5% path allowance) | **25.65 ms** | | Research 1.33× mapped-fiber reference | **32.48 ms** | | Estimated unamplified path loss | **523.8 dB** | | Transparent optical spans / inline amplifiers | **33 / 32** | | Published RTT inflation over fiber floor | **1.83×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **43.04 ms** | | Average RTT | **44.7 ms** | | Maximum RTT | **51.46 ms** | | Standard deviation | **1.56 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-mow-rtt). - **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. # Paris, France → Marseille, France RTT 🇫🇷 **Paris, France (PAR)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Paris to Marseille averaged 8.9 ms across 50 samples, with a minimum of 8.59 ms and a maximum of 9.69 ms. Packet loss was zero and jitter was 0.25 ms. This route ranked fourth among the 19 outbound routes from Paris measured in the same round. Its 0.26 ms standard deviation on the 8.9 ms average gives a relative spread of about 2.9%, below the 3.3% median for that route set. The 660.5 km great-circle path has a theoretical fiber floor of 6.47 ms; the measured average is about 1.38 times that floor, or 72.7% fiber efficiency. Given Marseille's role as France's Mediterranean submarine cable landing hub, this stable sub-10 ms corridor is especially relevant to connectivity tied to cable systems from Africa, the Middle East, and Asia. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------- | | RTT | **8.9 ms** | | Jitter | **0.25 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **6.47 ms** | | Fiber Efficiency | **72.7%** | | Latency Tier | Ultra-Low | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **660.5 km** | | Vacuum RTT floor | **4.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **6.47 ms** | | Low-latency fiber material floor | **6.44 ms** | | Engineering floor (5% path allowance) | **6.79 ms** | | Research 1.33× mapped-fiber reference | **8.6 ms** | | Estimated unamplified path loss | **138.7 dB** | | Transparent optical spans / inline amplifiers | **9 / 8** | | Published RTT inflation over fiber floor | **1.38×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ----------- | | Minimum RTT | **8.59 ms** | | Average RTT | **8.9 ms** | | Maximum RTT | **9.69 ms** | | Standard deviation | **0.26 ms** | | Stdev / average | **2.9%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Fastest routes arriving at Marseille (MRS)** * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms * [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms **Same corridor (Europe → Europe)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-mrs-rtt). - **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. # Paris, France → New York, USA RTT 🇫🇷 **Paris, France (PAR)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Paris, France to New York, USA averaged 68.9 ms across 50 samples taken at 100 ms intervals. The minimum was 66.76 ms, the maximum 73.07 ms, and no packets were lost. The route ranked 7th among 19 outbound routes measured from Paris. The standard deviation of 1.55 ms is about 2.2 percent of the average RTT, below the 3.28 percent median relative variability across the measured set, and jitter stayed at just 1.37 ms. With a great-circle distance of 5,852.7 km, the fiber-floor estimate is near 57.31 ms, and the 68.9 ms average is only 1.2 times that floor, implying 83.2% fiber efficiency. The tight alignment with the physical reference suggests an efficient intercontinental route with very stable timing. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **68.9 ms** | | Jitter | **1.37 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **57.31 ms** | | Fiber Efficiency | **83.2%** | | Latency Tier | Excellent | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,852.7 km** | | Vacuum RTT floor | **39.05 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **57.31 ms** | | Low-latency fiber material floor | **57.08 ms** | | Engineering floor (5% path allowance) | **60.19 ms** | | Research 1.33× mapped-fiber reference | **76.23 ms** | | Estimated unamplified path loss | **1229.1 dB** | | Transparent optical spans / inline amplifiers | **77 / 76** | | Published RTT inflation over fiber floor | **1.2×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **66.76 ms** | | Average RTT | **68.9 ms** | | Maximum RTT | **73.07 ms** | | Standard deviation | **1.55 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Europe → North America)** * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms * [Frankfurt to New York latency and RTT](/docs/network/latency/pairs/fra-nyc-rtt) — 74.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-nyc-rtt). - **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. # Paris, France → Seattle, USA RTT 🇫🇷 **Paris, France (PAR)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Paris, France to Seattle, USA averaged 128 ms over 50 samples, with a minimum of 123.76 ms and a maximum of 137.5 ms. Packet loss was 0 percent and jitter was 2.63 ms. This route ranked 10th among 19 outbound routes measured from Paris, placing it near the middle of that set. Its standard deviation of 3.51 ms equals about 2.7 percent of the average RTT, below the 3.28 percent median relative variability seen across the measured routes. With a great-circle distance of 8,065.2 km, the observed 128 ms average is roughly 1.62 times the fiber-floor estimate, for an implied fiber efficiency of 61.7%. The extra headroom above the floor is consistent with a longer intercontinental crossing, while the zero packet loss keeps the route clean over that distance. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **128 ms** | | Jitter | **2.63 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **78.98 ms** | | Fiber Efficiency | **61.7%** | | Latency Tier | Good | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,065.2 km** | | Vacuum RTT floor | **53.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **78.98 ms** | | Low-latency fiber material floor | **78.66 ms** | | Engineering floor (5% path allowance) | **82.94 ms** | | Research 1.33× mapped-fiber reference | **105.04 ms** | | Estimated unamplified path loss | **1693.7 dB** | | Transparent optical spans / inline amplifiers | **106 / 105** | | Published RTT inflation over fiber floor | **1.62×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **123.76 ms** | | Average RTT | **128 ms** | | Maximum RTT | **137.5 ms** | | Standard deviation | **3.51 ms** | | Stdev / average | **2.7%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america) * Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Paris latency and RTT](/docs/network/latency/pairs/sea-par-rtt) — 129.2 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Europe → North America)** * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms * [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-sea-rtt). - **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. # Paris, France → Singapore RTT 🇫🇷 **Paris, France (PAR)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z produced a Paris-to-Singapore ICMP RTT average of 150.3 ms from 50 samples, with a minimum of 144.03 ms and a maximum of 164.23 ms. Standard deviation was 4.53 ms, jitter was 4.83 ms, and packet loss remained at 0%. The straight-line distance of 10,741.6 km corresponds to a theoretical fiber floor of about 105.19 ms, so the observed average is 1.43 times that floor and the path achieves 70% fiber efficiency. This leaves a relatively modest overhead of roughly 45 ms above the ideal fiber path, with the extra delay spread evenly enough to keep jitter below 5 ms. Among the 19 Paris outbound routes in this round, Singapore ranked 12th, placing it near the middle of the distribution. Its relative variability of about 3.0% is below the 3.28% median stability ratio for the round, so this path is a steadier-than-median member of the current Paris outbound set despite its 150 ms absolute latency. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **150.3 ms** | | Jitter | **4.83 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **105.19 ms** | | Fiber Efficiency | **70%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,741.6 km** | | Vacuum RTT floor | **71.66 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **105.19 ms** | | Low-latency fiber material floor | **104.77 ms** | | Engineering floor (5% path allowance) | **110.46 ms** | | Research 1.33× mapped-fiber reference | **139.9 ms** | | Estimated unamplified path loss | **2255.7 dB** | | Transparent optical spans / inline amplifiers | **141 / 140** | | Published RTT inflation over fiber floor | **1.43×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **144.03 ms** | | Average RTT | **150.3 ms** | | Maximum RTT | **164.23 ms** | | Standard deviation | **4.53 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Paris latency and RTT](/docs/network/latency/pairs/sin-par-rtt) — 151.4 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-sin-rtt). - **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. # Paris, France → Sydney, Australia RTT 🇫🇷 **Paris, France (PAR)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo probes from Paris to Sydney during the 2026-08-16T04:07:28Z measurement window averaged 249.7 ms over 50 samples, with a low of 240.64 ms and a high of 279.37 ms. The 9.37 ms standard deviation and 7.49 ms jitter describe a fairly steady path, and every probe was returned. The measured RTT is 1.5 times the theoretical fiber-floor estimate of 166.06 ms for the 16,957.7 km great-circle separation, giving a fiber efficiency of 66.5%. The overhead is modest for such a long intercontinental path, and the zero packet loss supports the route's fair latency tier. The route is ranked 19th in the 19-route Paris outbound set, placing it at the far end. The median standard-deviation-to-average ratio for those routes is 3.28%, while this route's standard deviation is 3.75% of its average, so variability is close to the group norm. Distance, not instability, is the dominant explanation for the RTT. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **249.7 ms** | | Jitter | **7.49 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **166.06 ms** | | Fiber Efficiency | **66.5%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,957.7 km** | | Vacuum RTT floor | **113.13 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **166.06 ms** | | Low-latency fiber material floor | **165.4 ms** | | Engineering floor (5% path allowance) | **174.39 ms** | | Research 1.33× mapped-fiber reference | **220.86 ms** | | Estimated unamplified path loss | **3561.1 dB** | | Transparent optical spans / inline amplifiers | **223 / 222** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **240.64 ms** | | Average RTT | **249.7 ms** | | Maximum RTT | **279.37 ms** | | Standard deviation | **9.37 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Paris latency and RTT](/docs/network/latency/pairs/syd-par-rtt) — 250.3 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-syd-rtt). - **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. # Paris, France → Taipei, Taiwan RTT 🇫🇷 **Paris, France (PAR)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo requests from Paris to Taipei returned an average round-trip time of 171.9 ms across 50 samples. The fastest reply was 163.74 ms, the slowest 192.89 ms, and with a standard deviation of 7.09 ms and jitter of 5.24 ms the path remained consistent with zero loss. The observed RTT is 1.78 times the fiber-floor estimate of 96.42 ms for the 9,846.2 km great-circle distance, corresponding to a fiber efficiency of 56.1%. The excess over the floor represents cable routing and switching overhead, and the low jitter plus complete reply set suggest it is not driven by congestion. On the Paris outbound set of 19 routes, Taipei ranks 14th and falls on the slower side of the group. The median standard-deviation-to-average ratio for those routes is 3.28%; at 4.12% of its own average, this route's variability is only slightly above that norm, making the measured 171.9 ms a stable result for the route. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **171.9 ms** | | Jitter | **5.24 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **96.42 ms** | | Fiber Efficiency | **56.1%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,846.2 km** | | Vacuum RTT floor | **65.69 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **96.42 ms** | | Low-latency fiber material floor | **96.03 ms** | | Engineering floor (5% path allowance) | **101.26 ms** | | Research 1.33× mapped-fiber reference | **128.24 ms** | | Estimated unamplified path loss | **2067.7 dB** | | Transparent optical spans / inline amplifiers | **130 / 129** | | Published RTT inflation over fiber floor | **1.78×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **163.74 ms** | | Average RTT | **171.9 ms** | | Maximum RTT | **192.89 ms** | | Standard deviation | **7.09 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Paris latency and RTT](/docs/network/latency/pairs/tpe-par-rtt) — 173.8 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-tpe-rtt). - **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. # Paris, France → Tokyo, Japan RTT 🇫🇷 **Paris, France (PAR)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement run from Paris to Tokyo produced an average ICMP echo RTT of 204.7 ms from 50 samples, with replies ranging from 194.79 ms to 241.63 ms. Standard deviation was 9.12 ms and jitter was 7.97 ms, so the path carried some variation but did not lose a single probe. Against the fiber-floor estimate of 95.34 ms for the 9,736.1 km great-circle distance, the observed RTT is 2.15 times higher, yielding a fiber efficiency of 46.6%. That inflation is larger than the raw distance alone would explain and points to cable routing and intermediate handling costs as the main contributors to the 204.7 ms average. The route ranks 17th among the 19 outbound routes from Paris, placing it on the slower end of the set. The median standard-deviation-to-average ratio across those routes is 3.28%; at about 4.5% of its own average, Tokyo's variability is mildly elevated but not extreme, and the zero-loss result keeps the route within a fair latency tier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **204.7 ms** | | Jitter | **7.97 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.34 ms** | | Fiber Efficiency | **46.6%** | | Latency Tier | Fair | | Source Region | [Europe](/docs/network/latency/regions/europe) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,736.1 km** | | Vacuum RTT floor | **64.95 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.34 ms** | | Low-latency fiber material floor | **94.96 ms** | | Engineering floor (5% path allowance) | **100.12 ms** | | Research 1.33× mapped-fiber reference | **126.81 ms** | | Estimated unamplified path loss | **2044.6 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **2.15×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **194.79 ms** | | Average RTT | **204.7 ms** | | Maximum RTT | **241.63 ms** | | Standard deviation | **9.12 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Paris latency and RTT](/docs/network/latency/pairs/tyo-par-rtt) — 204.8 ms **Fastest routes departing Paris (PAR)** * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Europe → Asia Pacific)** * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/par-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Paris → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/par-tyo-rtt). - **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. # Seattle, USA → Amsterdam, Netherlands RTT 🇺🇸 **Seattle, USA (SEA)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo samples from Seattle to Amsterdam completed 50 runs at 100 ms intervals with no packet loss. The average RTT was 128.6 ms, the minimum 126.47 ms, and the maximum 138.71 ms. The 2.06 ms standard deviation and 1.28 ms jitter point to a consistent path over the roughly 7,848 km great-circle distance. The 128.6 ms average is 1.67 times the theoretical fiber floor, a fiber efficiency of 59.8%, so about 40% of the observed time sits above that floor. This route's average latency ranks 8th among the 19 outbound routes measured for this network. At 1.6% of its average, the standard deviation is lower than the 3.28% typical spread across those routes, making this one of the more predictable paths in the group. Zero packet loss and a tight jitter envelope make the route's consistency its standout feature for Seattle–Amsterdam monitoring, even though the absolute RTT is in line with what a transatlantic crossing would be expected to show. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **128.6 ms** | | Jitter | **1.28 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.86 ms** | | Fiber Efficiency | **59.8%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,848.5 km** | | Vacuum RTT floor | **52.36 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.86 ms** | | Low-latency fiber material floor | **76.55 ms** | | Engineering floor (5% path allowance) | **80.71 ms** | | Research 1.33× mapped-fiber reference | **102.22 ms** | | Estimated unamplified path loss | **1648.2 dB** | | Transparent optical spans / inline amplifiers | **104 / 103** | | Published RTT inflation over fiber floor | **1.67×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **126.47 ms** | | Average RTT | **128.6 ms** | | Maximum RTT | **138.71 ms** | | Standard deviation | **2.06 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Seattle latency and RTT](/docs/network/latency/pairs/ams-sea-rtt) — 130.2 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-ams-rtt). - **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. # Seattle, USA → Berlin, Germany RTT 🇺🇸 **Seattle, USA (SEA)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. The Seattle-to-Berlin round in the 2026-08-16T04:07:28Z measurement set returned an average ICMP echo RTT of 140.9 ms, with observed values between 132.69 ms and 157.15 ms and a standard deviation of 6.52 ms. None of the 50 samples were lost, and the route earned a 'Good' latency tier despite crossing roughly 8,142 km of geodesic distance. Because the physical fiber floor for this separation is about 79.7 ms, the measured path runs at 1.77 times that floor, or 56.6% fiber efficiency. The gap leaves a plausible theoretical margin for a long-haul North America-to-Europe route, while the actual round-trip time remains consistent in absolute terms. Within the 19 outbound routes measured from Seattle, this path ranked 12th in average round-trip time. Its relative variation is about 4.6% of the average, slightly above the 3.28% median for the route set, but the 5.89 ms jitter and zero packet loss still point to a stable transatlantic path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **140.9 ms** | | Jitter | **5.89 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **79.73 ms** | | Fiber Efficiency | **56.6%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,142.2 km** | | Vacuum RTT floor | **54.32 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **79.73 ms** | | Low-latency fiber material floor | **79.41 ms** | | Engineering floor (5% path allowance) | **83.73 ms** | | Research 1.33× mapped-fiber reference | **106.05 ms** | | Estimated unamplified path loss | **1709.9 dB** | | Transparent optical spans / inline amplifiers | **107 / 106** | | Published RTT inflation over fiber floor | **1.77×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **132.69 ms** | | Average RTT | **140.9 ms** | | Maximum RTT | **157.15 ms** | | Standard deviation | **6.52 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Seattle latency and RTT](/docs/network/latency/pairs/ber-sea-rtt) — 139.7 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-ber-rtt). - **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. # Seattle, USA → Frankfurt, Germany RTT 🇺🇸 **Seattle, USA (SEA)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. The Seattle-to-Frankfurt measurement round from 2026-08-16T04:07:28Z produced an average ICMP echo RTT of 133.2 ms, a minimum of 130.2 ms, and a maximum of 141.75 ms over 50 samples. No packets were lost, and the route was classified as 'Good' latency. The path spans about 8,204 km along the geodesic, against a fiber-floor estimate of roughly 80.3 ms. The measured delay sits at 1.66 times that floor, which works out to 60.3% fiber efficiency; the moderate inflation is consistent with a long-haul North America-to-Europe path rather than a sign of severe detouring. Among the 19 outbound routes measured from Seattle, this one ranked 11th in average round-trip time. Its own relative variation is about 2.0% of the average, markedly tighter than the 3.28% median for the route set, and the 2.46 ms jitter confirms that Frankfurt-bound traffic stayed on a very stable path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **133.2 ms** | | Jitter | **2.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **80.34 ms** | | Fiber Efficiency | **60.3%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **8,204 km** | | Vacuum RTT floor | **54.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **80.34 ms** | | Low-latency fiber material floor | **80.02 ms** | | Engineering floor (5% path allowance) | **84.37 ms** | | Research 1.33× mapped-fiber reference | **106.85 ms** | | Estimated unamplified path loss | **1722.8 dB** | | Transparent optical spans / inline amplifiers | **108 / 107** | | Published RTT inflation over fiber floor | **1.66×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **130.2 ms** | | Average RTT | **133.2 ms** | | Maximum RTT | **141.75 ms** | | Standard deviation | **2.72 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Seattle latency and RTT](/docs/network/latency/pairs/fra-sea-rtt) — 135.2 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-fra-rtt). - **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. # Seattle, USA → São Paulo, Brazil RTT 🇺🇸 **Seattle, USA (SEA)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Seattle to São Paulo returned an average round-trip time of 155.7 ms, with a minimum of 152.75 ms and a maximum of 163 ms. There was no packet loss, and jitter of 2.3 ms is modest for an intercontinental distance of 10,902.3 km, though the average places the route in the Fair latency tier. Against a vacuum floor of 72.73 ms and a fiber floor of 106.76 ms, the observed average is 1.46 times the fiber floor, or a fiber efficiency of 68.6%. That puts the measured mean 48.94 ms above the fiber-floor estimate for the geodesic distance. Among the 19 outbound routes measured from Seattle in this round, this path ranks 15th, so most alternatives reached São Paulo with lower latency. Its stability is better than the route-family median: the 2.37 ms standard deviation is only about 1.5% of the average versus a 3.28% median, making the latency dependable even if not the quickest. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **155.7 ms** | | Jitter | **2.3 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.76 ms** | | Fiber Efficiency | **68.6%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,902.3 km** | | Vacuum RTT floor | **72.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.76 ms** | | Low-latency fiber material floor | **106.33 ms** | | Engineering floor (5% path allowance) | **112.12 ms** | | Research 1.33× mapped-fiber reference | **142 ms** | | Estimated unamplified path loss | **2289.5 dB** | | Transparent optical spans / inline amplifiers | **144 / 143** | | Published RTT inflation over fiber floor | **1.46×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **152.75 ms** | | Average RTT | **155.7 ms** | | Maximum RTT | **163 ms** | | Standard deviation | **2.37 ms** | | Stdev / average | **1.5%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [North America to South America](/docs/network/latency/regions/north-america-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-gru-rtt). - **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. # Seattle, USA → Hong Kong RTT 🇺🇸 **Seattle, USA (SEA)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, 50 ICMP echo samples from Seattle to Hong Kong produced an average round-trip time of 130.4 ms, with a minimum of 125.05 ms and a maximum of 145.66 ms. Packet loss was 0%, while jitter of 4.02 ms and a standard deviation of 4.85 ms keep the route in the Good latency tier. The 10,435.9 km separation gives a vacuum floor of 69.62 ms and a fiber floor of 102.2 ms. The measured average is only 1.28 times the fiber floor, a fiber efficiency of 78.4%, which is a strong result for a trans-Pacific crossing. Across the 19 outbound routes measured from Seattle in this round, this path ranks 10th. Its standard deviation is about 3.7% of the average, slightly above the 3.28% median deviation-to-average of the route family, so the efficient average comes with a bit more run-to-run variation than the typical route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **130.4 ms** | | Jitter | **4.02 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **102.2 ms** | | Fiber Efficiency | **78.4%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,435.9 km** | | Vacuum RTT floor | **69.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **102.2 ms** | | Low-latency fiber material floor | **101.79 ms** | | Engineering floor (5% path allowance) | **107.32 ms** | | Research 1.33× mapped-fiber reference | **135.92 ms** | | Estimated unamplified path loss | **2191.5 dB** | | Transparent optical spans / inline amplifiers | **137 / 136** | | Published RTT inflation over fiber floor | **1.28×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **125.05 ms** | | Average RTT | **130.4 ms** | | Maximum RTT | **145.66 ms** | | Standard deviation | **4.85 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Same corridor (North America → Asia Pacific)** * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-hkg-rtt). - **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. # Seattle, USA → Ashburn, USA RTT 🇺🇸 **Seattle, USA (SEA)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, the ICMP echo path from Seattle, USA to Ashburn, USA returned a 61.5 ms average round-trip time, with all 50 samples landing between 57.92 ms and 70.85 ms and no packet loss. The measured average is 1.7 times the theoretical fiber floor for the 3,704 km span, which is consistent with an Excellent latency tier. Jitter of 2.57 ms and a standard deviation of 2.96 ms indicate a steady result, though not an ultra-tight one. This route ranks third among the 19 outbound routes in its measurement set. Its standard-deviation-to-average ratio of about 4.8 percent sits above the set-wide median of 3.28 percent, so while zero loss and a 61.5 ms average make the result useful for baseline planning, the observed spread should be expected in that estimate. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **61.5 ms** | | Jitter | **2.57 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **36.27 ms** | | Fiber Efficiency | **59%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **3,704 km** | | Vacuum RTT floor | **24.71 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **36.27 ms** | | Low-latency fiber material floor | **36.13 ms** | | Engineering floor (5% path allowance) | **38.09 ms** | | Research 1.33× mapped-fiber reference | **48.24 ms** | | Estimated unamplified path loss | **777.8 dB** | | Transparent optical spans / inline amplifiers | **49 / 48** | | Published RTT inflation over fiber floor | **1.7×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **57.92 ms** | | Average RTT | **61.5 ms** | | Maximum RTT | **70.85 ms** | | Standard deviation | **2.96 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms * [Paris to Ashburn latency and RTT](/docs/network/latency/pairs/par-iad-rtt) — 75.5 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-iad-rtt). - **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. # Seattle, USA → Johannesburg, South Africa RTT 🇺🇸 **Seattle, USA (SEA)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Seattle, USA to Johannesburg, South Africa averaged 282.1 ms round-trip, with a minimum of 273.42 ms and a maximum of 300.55 ms. The 50-sample run had no packet loss, and jitter was 5.55 ms. For a geodesic distance of 16,502.7 km, the theoretical fiber floor is roughly 161.6 ms, so the observed average is about 75% above that floor. That overhead is consistent with a very long intercontinental path that cannot follow a straight great-circle line. This route ranked 19th among the network's 19 measured outbound routes in the same round, making it the longest round-trip in the measured set. Its standard deviation is about 2.4% of the average RTT, however, which is tighter than the network's median ratio of 3.3%, so the path is very stable even though its absolute latency is high. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **282.1 ms** | | Jitter | **5.55 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **161.61 ms** | | Fiber Efficiency | **57.3%** | | Latency Tier | High | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,502.7 km** | | Vacuum RTT floor | **110.09 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **161.61 ms** | | Low-latency fiber material floor | **160.96 ms** | | Engineering floor (5% path allowance) | **169.71 ms** | | Research 1.33× mapped-fiber reference | **214.94 ms** | | Estimated unamplified path loss | **3465.6 dB** | | Transparent optical spans / inline amplifiers | **217 / 216** | | Published RTT inflation over fiber floor | **1.75×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **273.42 ms** | | Average RTT | **282.1 ms** | | Maximum RTT | **300.55 ms** | | Standard deviation | **6.9 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Seattle latency and RTT](/docs/network/latency/pairs/jnb-sea-rtt) — 281.2 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (North America → Africa)** * [New York to Johannesburg latency and RTT](/docs/network/latency/pairs/nyc-jnb-rtt) — 221.5 ms * [Ashburn to Johannesburg latency and RTT](/docs/network/latency/pairs/iad-jnb-rtt) — 228.3 ms * [Miami to Johannesburg latency and RTT](/docs/network/latency/pairs/mia-jnb-rtt) — 259.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-jnb-rtt). - **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. # Seattle, USA → Los Angeles, USA RTT 🇺🇸 **Seattle, USA (SEA)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, the ICMP echo path from Seattle, USA to Los Angeles, USA produced a 25.9 ms average round-trip time, with a minimum of 25.44 ms, a maximum of 27.56 ms, and zero packet loss across 50 samples. The measured average is about 1.71 times the fiber-floor estimate for the 1,543.6 km span, and the resulting fiber efficiency of 58.4 percent supports the Ultra-Low latency tier. Jitter of 0.33 ms and a standard deviation of 0.42 ms make this an extremely consistent echo response. This route ranks first among the 19 outbound routes in its measurement set. Its standard-deviation-to-average ratio of about 1.6 percent is well below the set-wide median of 3.28 percent, so the 25.9 ms average is a stable baseline for this corridor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **25.9 ms** | | Jitter | **0.33 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **15.12 ms** | | Fiber Efficiency | **58.4%** | | Latency Tier | Ultra-Low | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **1,543.6 km** | | Vacuum RTT floor | **10.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **15.12 ms** | | Low-latency fiber material floor | **15.06 ms** | | Engineering floor (5% path allowance) | **15.87 ms** | | Research 1.33× mapped-fiber reference | **20.1 ms** | | Estimated unamplified path loss | **324.2 dB** | | Transparent optical spans / inline amplifiers | **21 / 20** | | Published RTT inflation over fiber floor | **1.71×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **25.44 ms** | | Average RTT | **25.9 ms** | | Maximum RTT | **27.56 ms** | | Standard deviation | **0.42 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms **Fastest routes departing Seattle (SEA)** * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms **Fastest routes arriving at Los Angeles (LAX)** * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [London to Los Angeles latency and RTT](/docs/network/latency/pairs/lon-lax-rtt) — 127.5 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-lax-rtt). - **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. # Seattle, USA → London, UK RTT 🇺🇸 **Seattle, USA (SEA)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, the Seattle-to-London ICMP echo test averaged 124.1 ms, with a narrow observed range from 118.94 ms to 137.2 ms and a standard deviation of 3.96 ms. All 50 packets returned successfully, earning a 'Good' latency tier. The geodesic between Seattle and London is about 7,722.7 km, and the estimated fiber floor for that distance is around 75.6 ms. The measured average is 1.64 times that floor, equivalent to 60.9% fiber efficiency, which indicates a solidly efficient transatlantic route. Within the 19 outbound routes measured from Seattle, this path ranked 7th in average round-trip time. The observed variation of about 3.2% of the average sits just below the 3.28% median for the route set, and with 3.75 ms jitter and zero loss, the route delivered consistent transatlantic timing. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **124.1 ms** | | Jitter | **3.75 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **75.63 ms** | | Fiber Efficiency | **60.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,722.7 km** | | Vacuum RTT floor | **51.52 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **75.63 ms** | | Low-latency fiber material floor | **75.32 ms** | | Engineering floor (5% path allowance) | **79.42 ms** | | Research 1.33× mapped-fiber reference | **100.58 ms** | | Estimated unamplified path loss | **1621.8 dB** | | Transparent optical spans / inline amplifiers | **102 / 101** | | Published RTT inflation over fiber floor | **1.64×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **118.94 ms** | | Average RTT | **124.1 ms** | | Maximum RTT | **137.2 ms** | | Standard deviation | **3.96 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Seattle latency and RTT](/docs/network/latency/pairs/lon-sea-rtt) — 123.2 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-lon-rtt). - **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. # Seattle, USA → Melbourne, Australia RTT 🇺🇸 **Seattle, USA (SEA)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo measurement from Seattle to Melbourne averaged 170.1 ms over 50 samples, with a minimum of 164.93 ms and a maximum of 189.47 ms. Zero packets were lost, and the standard deviation of 4.46 ms with 3.88 ms jitter indicates a steady path; the max-min spread of 24.54 ms is narrow for a route in the Fair latency tier. At a geodesic distance of 13,166 km, the vacuum round-trip floor is 87.83 ms and the fiber floor is 128.93 ms. The observed average sits 1.32 times above the fiber floor, for a fiber efficiency of 75.8%, meaning the route carries noticeable overhead beyond the straight-line fiber path. In the 19-route outbound context from Seattle, this path is ranked 18th. The median RTT scatter across outbound routes in the round is 3.28% of average RTT, while this route's scatter is only about 2.6% of its average, so it is steadier than the typical route even though its absolute latency is relatively high. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **170.1 ms** | | Jitter | **3.88 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **128.93 ms** | | Fiber Efficiency | **75.8%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **13,166 km** | | Vacuum RTT floor | **87.83 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **128.93 ms** | | Low-latency fiber material floor | **128.41 ms** | | Engineering floor (5% path allowance) | **135.4 ms** | | Research 1.33× mapped-fiber reference | **171.48 ms** | | Estimated unamplified path loss | **2764.9 dB** | | Transparent optical spans / inline amplifiers | **173 / 172** | | Published RTT inflation over fiber floor | **1.32×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **164.93 ms** | | Average RTT | **170.1 ms** | | Maximum RTT | **189.47 ms** | | Standard deviation | **4.46 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Seattle latency and RTT](/docs/network/latency/pairs/mel-sea-rtt) — 172.1 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms **Same corridor (North America → Asia Pacific)** * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-mel-rtt). - **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. # Seattle, USA → Miami, USA RTT 🇺🇸 **Seattle, USA (SEA)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, the ICMP echo path from Seattle, USA to Miami, USA averaged 81.7 ms round-trip time, with 50 samples spanning 79.89 ms to 89.57 ms and no packet loss. That average sits about 1.9 times above the fiber-floor estimate for the 4,399.4 km span, and the route's 52.7 percent fiber efficiency places it in the Good latency tier. Jitter remains moderate at 1.22 ms, while the 1.94 ms standard deviation shows most samples cluster tightly around the average. This route ranks fourth among the 19 outbound routes in its measurement set. Its standard-deviation-to-average ratio of about 2.4 percent is below the set-wide median of 3.28 percent, and the zero-loss result with low jitter means the distance overhead does not translate into erratic echo responses. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **81.7 ms** | | Jitter | **1.22 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **43.08 ms** | | Fiber Efficiency | **52.7%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **4,399.4 km** | | Vacuum RTT floor | **29.35 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **43.08 ms** | | Low-latency fiber material floor | **42.91 ms** | | Engineering floor (5% path allowance) | **45.24 ms** | | Research 1.33× mapped-fiber reference | **57.3 ms** | | Estimated unamplified path loss | **923.9 dB** | | Transparent optical spans / inline amplifiers | **58 / 57** | | Published RTT inflation over fiber floor | **1.9×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **79.89 ms** | | Average RTT | **81.7 ms** | | Maximum RTT | **89.57 ms** | | Standard deviation | **1.94 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 ms **Same corridor (North America → North America)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-mia-rtt). - **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. # Seattle, USA → Moscow, Russia RTT 🇺🇸 **Seattle, USA (SEA)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Seattle, USA to Moscow, Russia produced an average RTT of 164.6 ms, with a minimum of 158.38 ms and a maximum of 192.7 ms. Zero packet loss and 5 ms jitter keep the route within the Fair latency tier. This route was ranked 17th among the 19 Seattle outbound routes measured in the same round. Its standard deviation of 7.23 ms is about 4.4% of the average RTT, higher than the 3.28% median variability for the route set. At a geodesic distance of 8,396.9 km, the theoretical fiber floor is 82.23 ms, so the observed RTT is twice that floor and yields 50% fiber efficiency. The lower efficiency and Fair tier suggest this route has less latency headroom than its geographic distance alone might imply. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **164.6 ms** | | Jitter | **5 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **82.23 ms** | | Fiber Efficiency | **50%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,396.9 km** | | Vacuum RTT floor | **56.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **82.23 ms** | | Low-latency fiber material floor | **81.9 ms** | | Engineering floor (5% path allowance) | **86.35 ms** | | Research 1.33× mapped-fiber reference | **109.36 ms** | | Estimated unamplified path loss | **1763.3 dB** | | Transparent optical spans / inline amplifiers | **111 / 110** | | Published RTT inflation over fiber floor | **2×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **158.38 ms** | | Average RTT | **164.6 ms** | | Maximum RTT | **192.7 ms** | | Standard deviation | **7.23 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Seattle latency and RTT](/docs/network/latency/pairs/mow-sea-rtt) — 164.8 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-mow-rtt). - **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. # Seattle, USA → Marseille, France RTT 🇺🇸 **Seattle, USA (SEA)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Seattle, USA to Marseille, France returned an average RTT of 141.2 ms, with a minimum of 134.28 ms and a maximum of 166.5 ms. Zero packet loss and 5.32 ms jitter place this route in the Good latency tier. Ranked 13th among the 19 Seattle outbound routes in the same round, this route shows a standard deviation of 6.79 ms, about 4.8% of its average. That is a bit above the 3.28% median variability for the route set, but the small loss and moderate jitter still suggest a usable intercontinental path. Against a geodesic distance of 8,707.5 km and a theoretical fiber floor of 85.27 ms, the observed RTT is 1.66 times the floor — a fiber efficiency of 60.4%. The combination of Good-tier latency and no packet loss makes this route a practical candidate for repeated ICMP polling between Seattle and Marseille. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **141.2 ms** | | Jitter | **5.32 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **85.27 ms** | | Fiber Efficiency | **60.4%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,707.5 km** | | Vacuum RTT floor | **58.09 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **85.27 ms** | | Low-latency fiber material floor | **84.93 ms** | | Engineering floor (5% path allowance) | **89.55 ms** | | Research 1.33× mapped-fiber reference | **113.41 ms** | | Estimated unamplified path loss | **1828.6 dB** | | Transparent optical spans / inline amplifiers | **115 / 114** | | Published RTT inflation over fiber floor | **1.66×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **134.28 ms** | | Average RTT | **141.2 ms** | | Maximum RTT | **166.5 ms** | | Standard deviation | **6.79 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Seattle latency and RTT](/docs/network/latency/pairs/mrs-sea-rtt) — 141.7 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-mrs-rtt). - **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. # Seattle, USA → New York, USA RTT 🇺🇸 **Seattle, USA (SEA)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo samples from Seattle to New York produced an average round-trip time of 59.5 ms, with a minimum of 57.58 ms and a maximum of 64.42 ms. Zero packets were lost, and the 1.48 ms standard deviation and 1.21 ms jitter put the route firmly in the Excellent latency tier. At 3,875.5 km apart, the theoretical vacuum floor is 25.85 ms and the fiber floor is 37.95 ms, so the observed average sits about 1.57 times above the fiber floor, a fiber efficiency of 63.8%. The measured mean is 21.55 ms above that fiber-floor estimate for the great-circle distance. Compared with the 19 outbound routes measured from Seattle in this round, this path ranks 2nd. Its standard deviation is roughly 2.5% of the average, below the 3.28% median deviation-to-average across the route family, so the route offers both strong speed and relatively low variation. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **59.5 ms** | | Jitter | **1.21 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **37.95 ms** | | Fiber Efficiency | **63.8%** | | Latency Tier | Excellent | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,875.5 km** | | Vacuum RTT floor | **25.85 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **37.95 ms** | | Low-latency fiber material floor | **37.8 ms** | | Engineering floor (5% path allowance) | **39.85 ms** | | Research 1.33× mapped-fiber reference | **50.48 ms** | | Estimated unamplified path loss | **813.9 dB** | | Transparent optical spans / inline amplifiers | **51 / 50** | | Published RTT inflation over fiber floor | **1.57×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **57.58 ms** | | Average RTT | **59.5 ms** | | Maximum RTT | **64.42 ms** | | Standard deviation | **1.48 ms** | | Stdev / average | **2.5%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms * [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms **Same corridor (North America → North America)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-nyc-rtt). - **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. # Seattle, USA → Paris, France RTT 🇺🇸 **Seattle, USA (SEA)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Seattle, USA to Paris, France returned an average RTT of 129.2 ms, with a tight range of 126.7 ms to 135.02 ms. Zero packet loss and 1.78 ms jitter put this route in the Good latency tier. This route was ranked 9th among the 19 Seattle outbound routes measured in the same round. Its standard deviation of 2.13 ms is only about 1.65% of the average, well below the 3.28% median variability for the route set. With a geodesic distance of 8,065.2 km and a theoretical fiber floor of 78.98 ms, the observed RTT is 1.64 times the floor and equals 61.1% fiber efficiency. The very stable RTT, low jitter, and zero loss make this a steady long-haul ICMP measurement route from Seattle to Paris. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **129.2 ms** | | Jitter | **1.78 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **78.98 ms** | | Fiber Efficiency | **61.1%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,065.2 km** | | Vacuum RTT floor | **53.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **78.98 ms** | | Low-latency fiber material floor | **78.66 ms** | | Engineering floor (5% path allowance) | **82.94 ms** | | Research 1.33× mapped-fiber reference | **105.04 ms** | | Estimated unamplified path loss | **1693.7 dB** | | Transparent optical spans / inline amplifiers | **106 / 105** | | Published RTT inflation over fiber floor | **1.64×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **126.7 ms** | | Average RTT | **129.2 ms** | | Maximum RTT | **135.02 ms** | | Standard deviation | **2.13 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Seattle latency and RTT](/docs/network/latency/pairs/par-sea-rtt) — 128 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (North America → Europe)** * [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms * [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms * [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-par-rtt). - **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. # Seattle, USA → Singapore RTT 🇺🇸 **Seattle, USA (SEA)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP round-trip measurement from Seattle to Singapore averaged 151.1 ms across 50 samples, with a minimum of 143.38 ms and a maximum of 172.46 ms. No packets were lost, but the standard deviation of 6.94 ms and jitter of 6.35 ms show more per-sample movement; the total spread of 29.08 ms is wider than the average alone suggests. Singapore lies about 12,991 km from Seattle, giving a vacuum round-trip floor of 86.67 ms and a fiber floor of 127.22 ms. At 151.1 ms average, this route is only 1.19 times the fiber floor, for a fiber efficiency of 84.2%, so its physical path is relatively efficient. In the 19-route outbound context from Seattle, this path is ranked 14th. The median RTT scatter in the round is 3.28% of average RTT, while this route's scatter is about 4.6% of its average, so its absolute latency is solid but its consistency is not as tight as the typical outbound path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **151.1 ms** | | Jitter | **6.35 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **127.22 ms** | | Fiber Efficiency | **84.2%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,991.1 km** | | Vacuum RTT floor | **86.67 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **127.22 ms** | | Low-latency fiber material floor | **126.71 ms** | | Engineering floor (5% path allowance) | **133.6 ms** | | Research 1.33× mapped-fiber reference | **169.2 ms** | | Estimated unamplified path loss | **2728.1 dB** | | Transparent optical spans / inline amplifiers | **171 / 170** | | Published RTT inflation over fiber floor | **1.19×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **143.38 ms** | | Average RTT | **151.1 ms** | | Maximum RTT | **172.46 ms** | | Standard deviation | **6.94 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Seattle latency and RTT](/docs/network/latency/pairs/sin-sea-rtt) — 151.5 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Same corridor (North America → Asia Pacific)** * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-sin-rtt). - **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. # Seattle, USA → Sydney, Australia RTT 🇺🇸 **Seattle, USA (SEA)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo measurement from Seattle to Sydney averaged 161.3 ms over 50 samples, with a minimum of 157.6 ms and a maximum of 177.48 ms. Zero packets were lost, and the standard deviation was only 3.32 ms with 2.66 ms jitter, making the route highly consistent; the max-min spread of 19.88 ms is notably narrow. At a geodesic distance of 12,453.7 km, the vacuum round-trip floor is 83.08 ms and the fiber floor is 121.96 ms. The observed average sits 1.32 times above the fiber floor, for a fiber efficiency of 75.6%, reflecting how close the path comes to the straight-line fiber floor. In the 19-route outbound context from Seattle, this path is ranked 16th. The median RTT scatter in the round is 3.28% of average RTT, while this route's scatter is only about 2.1% of its average, so the latency is relatively high but very stable. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **161.3 ms** | | Jitter | **2.66 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **121.96 ms** | | Fiber Efficiency | **75.6%** | | Latency Tier | Fair | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,453.7 km** | | Vacuum RTT floor | **83.08 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **121.96 ms** | | Low-latency fiber material floor | **121.47 ms** | | Engineering floor (5% path allowance) | **128.07 ms** | | Research 1.33× mapped-fiber reference | **162.2 ms** | | Estimated unamplified path loss | **2615.3 dB** | | Transparent optical spans / inline amplifiers | **164 / 163** | | Published RTT inflation over fiber floor | **1.32×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **157.6 ms** | | Average RTT | **161.3 ms** | | Maximum RTT | **177.48 ms** | | Standard deviation | **3.32 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Seattle latency and RTT](/docs/network/latency/pairs/syd-sea-rtt) — 161.9 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Same corridor (North America → Asia Pacific)** * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-syd-rtt). - **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. # Seattle, USA → Taipei, Taiwan RTT 🇺🇸 **Seattle, USA (SEA)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Seattle, USA to Taipei, Taiwan returned an average round-trip time of 114.7 ms, with a minimum of 109.75 ms and a maximum of 137.83 ms. None of the 50 samples were lost, and jitter was 4.49 ms. The observed average is about 20% above the estimated fiber floor for the 9,748 km geodesic distance, so the route is moving close to the optical-path baseline while still leaving room for real-world network constraints. The 5.07 ms standard deviation keeps most samples near the average, and zero packet loss confirms the path carried all probes without drops. Within this round, the route ranked sixth among the network's 19 measured outbound routes. The median route in the set had a standard deviation equal to about 3.3% of its average RTT; this route's standard deviation is about 4.4% of its average, so it is slightly less steady than the network midpoint but still consistent enough for a Good latency classification. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **114.7 ms** | | Jitter | **4.49 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.46 ms** | | Fiber Efficiency | **83.2%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,748.1 km** | | Vacuum RTT floor | **65.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.46 ms** | | Low-latency fiber material floor | **95.08 ms** | | Engineering floor (5% path allowance) | **100.25 ms** | | Research 1.33× mapped-fiber reference | **126.96 ms** | | Estimated unamplified path loss | **2047.1 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **1.2×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **109.75 ms** | | Average RTT | **114.7 ms** | | Maximum RTT | **137.83 ms** | | Standard deviation | **5.07 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms **Same corridor (North America → Asia Pacific)** * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-tpe-rtt). - **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. # Seattle, USA → Tokyo, Japan RTT 🇺🇸 **Seattle, USA (SEA)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Seattle, USA to Tokyo, Japan produced an average round-trip time of 85 ms, with a minimum of 81.03 ms and a maximum of 97.43 ms. All 50 samples were received, and jitter measured 2.59 ms. The average sits roughly 13% above the estimated fiber floor for the 7,715 km geodesic distance, leaving only a small overhead for a long trans-Pacific path. The 3.15 ms standard deviation keeps the round-trip times tightly grouped, making this a stable low-latency route to East Asia. The route ranked fifth among the network's 19 measured outbound routes in this round. Its standard deviation is about 3.7% of the average RTT, close to the network's median ratio of 3.3%, and packet loss was zero, so the path is both quick and dependable relative to the measured set. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **85 ms** | | Jitter | **2.59 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **75.55 ms** | | Fiber Efficiency | **88.9%** | | Latency Tier | Good | | Source Region | [North America](/docs/network/latency/regions/north-america) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,715.2 km** | | Vacuum RTT floor | **51.47 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **75.55 ms** | | Low-latency fiber material floor | **75.25 ms** | | Engineering floor (5% path allowance) | **79.34 ms** | | Research 1.33× mapped-fiber reference | **100.49 ms** | | Estimated unamplified path loss | **1620.2 dB** | | Transparent optical spans / inline amplifiers | **102 / 101** | | Published RTT inflation over fiber floor | **1.13×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **81.03 ms** | | Average RTT | **85 ms** | | Maximum RTT | **97.43 ms** | | Standard deviation | **3.15 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Fastest routes departing Seattle (SEA)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms **Same corridor (North America → Asia Pacific)** * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sea-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sea-tyo-rtt). - **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. # Singapore → Amsterdam, Netherlands RTT 🇸🇬 **Singapore (SIN)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z ICMP echo round, the Singapore-to-Amsterdam path averaged 155.8 ms with a minimum of 147.48 ms and a maximum of 172.04 ms; none of the 50 samples were lost. The measured RTT is 1.51 times the 102.86 ms fiber-floor estimate for the 10,503.4 km great-circle distance, so the route converts about 66% of that theoretical minimum into actual progress. This path ranks 12th among the 19 routes measured from Singapore, and its 6.41 ms standard deviation is about 4.1% of the average, above the 3.28% median spread across that set. Despite the slightly higher variability, the 6.07 ms jitter and zero packet loss point to a stable long-haul route; the largest measured delay was only about 16 ms above the average, so RTT stayed well contained across all 50 samples. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **155.8 ms** | | Jitter | **6.07 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **102.86 ms** | | Fiber Efficiency | **66%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,503.4 km** | | Vacuum RTT floor | **70.07 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **102.86 ms** | | Low-latency fiber material floor | **102.44 ms** | | Engineering floor (5% path allowance) | **108.01 ms** | | Research 1.33× mapped-fiber reference | **136.8 ms** | | Estimated unamplified path loss | **2205.7 dB** | | Transparent optical spans / inline amplifiers | **138 / 137** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **147.48 ms** | | Average RTT | **155.8 ms** | | Maximum RTT | **172.04 ms** | | Standard deviation | **6.41 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Singapore latency and RTT](/docs/network/latency/pairs/ams-sin-rtt) — 157.6 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-ams-rtt). - **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. # Singapore → Berlin, Germany RTT 🇸🇬 **Singapore (SIN)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round placed Singapore-to-Berlin ICMP echo RTT at 160.3 ms on average, with 152.4 ms as the minimum and 193.36 ms as the maximum over 50 samples; no packets were lost. The average is 1.65 times the 97.19 ms fiber-floor for the 9,925 km great-circle distance, putting fiber efficiency at 60.6%. This route sits 13th among the 19 routes measured from Singapore, and its 7.96 ms standard deviation is about 5.0% of the average, above the 3.28% median spread for that group. The route-specific takeaway is in the tail: the largest recorded RTT reached 193.36 ms, roughly 33 ms above the average, even though jitter is reported at only 5.38 ms. That gap suggests occasional spikes outside the typical variation, so single-sample latency can be meaningfully higher than the 160.3 ms average implies. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **160.3 ms** | | Jitter | **5.38 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **97.19 ms** | | Fiber Efficiency | **60.6%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **9,925 km** | | Vacuum RTT floor | **66.21 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **97.19 ms** | | Low-latency fiber material floor | **96.8 ms** | | Engineering floor (5% path allowance) | **102.07 ms** | | Research 1.33× mapped-fiber reference | **129.27 ms** | | Estimated unamplified path loss | **2084.3 dB** | | Transparent optical spans / inline amplifiers | **131 / 130** | | Published RTT inflation over fiber floor | **1.65×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **152.4 ms** | | Average RTT | **160.3 ms** | | Maximum RTT | **193.36 ms** | | Standard deviation | **7.96 ms** | | Stdev / average | **5.0%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Singapore latency and RTT](/docs/network/latency/pairs/ber-sin-rtt) — 158.3 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-ber-rtt). - **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. # Singapore → Frankfurt, Germany RTT 🇸🇬 **Singapore (SIN)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, the Singapore-to-Frankfurt path produced an ICMP echo RTT of 151.6 ms on average, with 145.11 ms minimum and 167.35 ms maximum across 50 samples and zero packet loss. The measured average is 1.51 times the 100.56 ms fiber-floor for the 10,268.5 km great-circle distance, equivalent to 66.3% fiber efficiency. This route ranks 10th among the 19 routes measured from Singapore, and its 5.04 ms standard deviation is 3.3% of the average, almost exactly matching the 3.28% median spread for that group. The useful insight here is consistency: the 4.7 ms jitter and 5.04 ms standard deviation fit with a total range of just over 22 ms from minimum to maximum, so the 151.6 ms average is a dependable central reference for this round's RTT behavior. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **151.6 ms** | | Jitter | **4.7 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **100.56 ms** | | Fiber Efficiency | **66.3%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,268.5 km** | | Vacuum RTT floor | **68.5 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **100.56 ms** | | Low-latency fiber material floor | **100.15 ms** | | Engineering floor (5% path allowance) | **105.6 ms** | | Research 1.33× mapped-fiber reference | **133.74 ms** | | Estimated unamplified path loss | **2156.4 dB** | | Transparent optical spans / inline amplifiers | **135 / 134** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **145.11 ms** | | Average RTT | **151.6 ms** | | Maximum RTT | **167.35 ms** | | Standard deviation | **5.04 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Singapore latency and RTT](/docs/network/latency/pairs/fra-sin-rtt) — 151.4 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-fra-rtt). - **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. # Singapore → São Paulo, Brazil RTT 🇸🇬 **Singapore (SIN)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Singapore to São Paulo, Brazil averaged 311.4 ms, with a minimum of 306.39 ms and a maximum of 332.38 ms across 50 samples. Packet loss was 0%, while the standard deviation was 5.29 ms and jitter was 3.96 ms. São Paulo is about 15,998 km from Singapore along a great circle, and the fiber-floor estimate for that distance is 156.67 ms. The observed average sits 1.99 times above that floor, translating to a fiber-path efficiency of 50.3%, so the route has considerable headroom compared with a direct-fiber estimate. This route ranked 18th among the 19 outbound routes in the network's Singapore egress set, making it one of the more demanding paths in this round. Even so, its latency spread is tight relative to the network median variation-to-average figure of 3.28%, meaning the high RTT is consistent rather than erratic. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **311.4 ms** | | Jitter | **3.96 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **156.67 ms** | | Fiber Efficiency | **50.3%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,998.2 km** | | Vacuum RTT floor | **106.73 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **156.67 ms** | | Low-latency fiber material floor | **156.04 ms** | | Engineering floor (5% path allowance) | **164.52 ms** | | Research 1.33× mapped-fiber reference | **208.37 ms** | | Estimated unamplified path loss | **3359.6 dB** | | Transparent optical spans / inline amplifiers | **210 / 209** | | Published RTT inflation over fiber floor | **1.99×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **306.39 ms** | | Average RTT | **311.4 ms** | | Maximum RTT | **332.38 ms** | | Standard deviation | **5.29 ms** | | Stdev / average | **1.7%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Asia Pacific to South America](/docs/network/latency/regions/asia-pacific-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Singapore latency and RTT](/docs/network/latency/pairs/gru-sin-rtt) — 297.1 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Asia Pacific → South America)** * [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.5 ms * [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 ms * [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-gru-rtt). - **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. # Singapore → Hong Kong RTT 🇸🇬 **Singapore (SIN)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round recorded an ICMP echo RTT of 30.8 ms on average from Singapore to Hong Kong, with all 50 samples landing between 30.29 ms and 33.37 ms. Packet loss was 0%, while standard deviation was just 0.58 ms and jitter was 0.4 ms. That average is only 1.22 times the 25.24 ms fiber-floor estimate for the 2,577 km great-circle separation, giving a fiber-path efficiency of 81.9%. This places the route close to the direct-fiber limit for a regional Asia-Pacific interconnection. It ranked first among the 19 outbound routes in the network's Singapore egress set, and its variation is much smaller than the network median variation-to-average figure of 3.28%. The combination of near-floor latency and negligible spread makes this route a clean reference for Singapore–Hong Kong round-trip time in this round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **30.8 ms** | | Jitter | **0.4 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **25.24 ms** | | Fiber Efficiency | **81.9%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,577.2 km** | | Vacuum RTT floor | **17.19 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **25.24 ms** | | Low-latency fiber material floor | **25.14 ms** | | Engineering floor (5% path allowance) | **26.5 ms** | | Research 1.33× mapped-fiber reference | **33.57 ms** | | Estimated unamplified path loss | **541.2 dB** | | Transparent optical spans / inline amplifiers | **34 / 33** | | Published RTT inflation over fiber floor | **1.22×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **30.29 ms** | | Average RTT | **30.8 ms** | | Maximum RTT | **33.37 ms** | | Standard deviation | **0.58 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-hkg-rtt). - **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. # Singapore → Ashburn, USA RTT 🇸🇬 **Singapore (SIN)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Singapore to Ashburn, USA produced an average RTT of 210 ms, with a minimum of 198.98 ms, a maximum of 248.94 ms, and zero packet loss. Jitter measured 8.9 ms and the standard deviation was 9.22 ms, so the path remained within a roughly 50 ms spread across the sample. The observed average sits 1.38 times the 152.14 ms fiber-floor estimate for a 15,535.9 km great-circle route, which puts fiber efficiency at 72.4%. This route ranked 16th among the 19 routes measured from this origin in the same round, where typical variability was 3.28% of the average RTT; the standard deviation here is about 4.4% of the mean, a comparable level of consistency. A useful detail is that the minimum RTT is only 11.02 ms below the average, yet the maximum is 38.94 ms above it, meaning the tail is more pronounced than the steady-state would suggest. With zero loss and a fair latency tier, the main consideration for this route is the 210 ms average itself rather than instability. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **210 ms** | | Jitter | **8.9 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **152.14 ms** | | Fiber Efficiency | **72.4%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,535.9 km** | | Vacuum RTT floor | **103.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **152.14 ms** | | Low-latency fiber material floor | **151.53 ms** | | Engineering floor (5% path allowance) | **159.77 ms** | | Research 1.33× mapped-fiber reference | **202.35 ms** | | Estimated unamplified path loss | **3262.5 dB** | | Transparent optical spans / inline amplifiers | **204 / 203** | | Published RTT inflation over fiber floor | **1.38×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **198.98 ms** | | Average RTT | **210 ms** | | Maximum RTT | **248.94 ms** | | Standard deviation | **9.22 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Singapore latency and RTT](/docs/network/latency/pairs/iad-sin-rtt) — 211.5 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-iad-rtt). - **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. # Singapore → Johannesburg, South Africa RTT 🇸🇬 **Singapore (SIN)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement round from Singapore to Johannesburg returned an average ICMP echo RTT of 312.6 ms, with a minimum of 303.47 ms, a maximum of 332.3 ms, and zero packet loss across 50 samples. The standard deviation was 7.16 ms (jitter 7.32 ms), about 2.3% of the average and below the 3.28% median across this network's outbound routes. The route ranks 19th out of 19 outbound routes, placing it at the high-latency end of the current profile. The physical reference puts the geodesic distance at 8,664.2 km, with a theoretical fiber minimum of 84.85 ms and a vacuum floor of 57.8 ms. The observed average is 3.68 times the fiber minimum, giving a fiber efficiency of 27.1%; that large gap is the defining feature of this route. The range from 303.47 to 332.3 ms, along with zero packet loss, indicates a stable sample set for ICMP echo. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **312.6 ms** | | Jitter | **7.32 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **84.85 ms** | | Fiber Efficiency | **27.1%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,664.2 km** | | Vacuum RTT floor | **57.8 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **84.85 ms** | | Low-latency fiber material floor | **84.51 ms** | | Engineering floor (5% path allowance) | **89.1 ms** | | Research 1.33× mapped-fiber reference | **112.85 ms** | | Estimated unamplified path loss | **1819.5 dB** | | Transparent optical spans / inline amplifiers | **114 / 113** | | Published RTT inflation over fiber floor | **3.68×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **303.47 ms** | | Average RTT | **312.6 ms** | | Maximum RTT | **332.3 ms** | | Standard deviation | **7.16 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Singapore latency and RTT](/docs/network/latency/pairs/jnb-sin-rtt) — 311.6 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Asia Pacific → Africa)** * [Hong Kong to Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt) — 316.7 ms * [Taipei to Johannesburg latency and RTT](/docs/network/latency/pairs/tpe-jnb-rtt) — 331 ms * [Tokyo to Johannesburg latency and RTT](/docs/network/latency/pairs/tyo-jnb-rtt) — 359.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-jnb-rtt). - **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. # Singapore → Los Angeles, USA RTT 🇸🇬 **Singapore (SIN)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Singapore to Los Angeles, USA averaged 168.2 ms, with a minimum of 160.69 ms, a maximum of 194.08 ms, and no packet loss. Jitter was 4.76 ms and the standard deviation 6.01 ms, showing very consistent packet timing in this sample. The average is 1.22 times the 138.43 ms fiber-floor estimate for a 14,135.8 km great-circle distance, yielding an 82.3% fiber efficiency. This route ranked 14th among the 19 routes measured from this origin in the same round; typical variability across that set was 3.28% of the average RTT, while the standard deviation here is about 3.6% of the mean. The useful takeaway is that the gap between the minimum and maximum RTT is 33.39 ms, and the minimum sits just 7.51 ms below the average, so most measurements cluster near 168 ms. With zero packet loss and a fair latency tier, this trans-Pacific route is consistent and close to the fiber floor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **168.2 ms** | | Jitter | **4.76 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **138.43 ms** | | Fiber Efficiency | **82.3%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,135.8 km** | | Vacuum RTT floor | **94.3 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **138.43 ms** | | Low-latency fiber material floor | **137.87 ms** | | Engineering floor (5% path allowance) | **145.37 ms** | | Research 1.33× mapped-fiber reference | **184.11 ms** | | Estimated unamplified path loss | **2968.5 dB** | | Transparent optical spans / inline amplifiers | **186 / 185** | | Published RTT inflation over fiber floor | **1.22×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **160.69 ms** | | Average RTT | **168.2 ms** | | Maximum RTT | **194.08 ms** | | Standard deviation | **6.01 ms** | | Stdev / average | **3.6%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Singapore latency and RTT](/docs/network/latency/pairs/lax-sin-rtt) — 167.7 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-lax-rtt). - **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. # Singapore → London, UK RTT 🇸🇬 **Singapore (SIN)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo requests sent from Singapore to London, UK, produced an average round-trip time of 155.4 ms, with a minimum of 150.37 ms, a maximum of 180.35 ms, and no packet loss across all 50 samples. The standard deviation was 5.16 ms and jitter was 3.28 ms, so the route maintained a fairly narrow, repeatable RTT profile. The straight-line separation of 10,859.7 km yields an ideal fiber-only floor of about 106.35 ms. The measured average is 1.46 times that floor, which puts distance-adjusted efficiency at 68.4%; roughly 49 ms of overhead is added beyond the theoretical minimum for this route. Across the 19 outbound routes measured from Singapore in the same round, this route ranked 11th by average RTT. Its observed variation of 5.16 ms is a slightly larger share of the mean than the network-wide median ratio of 3.28%, meaning the occasional 180 ms samples are less typical; most probes sit near the low-150s portion of the range. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **155.4 ms** | | Jitter | **3.28 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.35 ms** | | Fiber Efficiency | **68.4%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,859.7 km** | | Vacuum RTT floor | **72.45 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.35 ms** | | Low-latency fiber material floor | **105.92 ms** | | Engineering floor (5% path allowance) | **111.68 ms** | | Research 1.33× mapped-fiber reference | **141.44 ms** | | Estimated unamplified path loss | **2280.5 dB** | | Transparent optical spans / inline amplifiers | **143 / 142** | | Published RTT inflation over fiber floor | **1.46×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **150.37 ms** | | Average RTT | **155.4 ms** | | Maximum RTT | **180.35 ms** | | Standard deviation | **5.16 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Singapore latency and RTT](/docs/network/latency/pairs/lon-sin-rtt) — 156.5 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-lon-rtt). - **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. # Singapore → Melbourne, Australia RTT 🇸🇬 **Singapore (SIN)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo RTT from Singapore to Melbourne averaged 88.6 ms, with a minimum of 86.6 ms and a maximum of 94.44 ms across 50 samples. Loss was 0%, jitter was 1.59 ms, and the standard deviation was 1.9 ms, so the sample set was tightly grouped. Melbourne is roughly 6,047 km from Singapore, where the fiber-floor estimate is 59.22 ms. The observed average is 1.5 times that floor, translating to 66.8% fiber-path efficiency — a reasonable result for an intercontinental Asia-Pacific path. The route placed 4th among the 19 outbound routes in the network's Singapore egress set, and its variation-to-average figure is comfortably below the network median of 3.28%. With no packet loss and a max-to-min spread of about 7.8 ms, this route offers a dependable ICMP round-trip reference for Singapore–Melbourne connectivity in this round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **88.6 ms** | | Jitter | **1.59 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **59.22 ms** | | Fiber Efficiency | **66.8%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,046.9 km** | | Vacuum RTT floor | **40.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **59.22 ms** | | Low-latency fiber material floor | **58.98 ms** | | Engineering floor (5% path allowance) | **62.18 ms** | | Research 1.33× mapped-fiber reference | **78.76 ms** | | Estimated unamplified path loss | **1269.9 dB** | | Transparent optical spans / inline amplifiers | **80 / 79** | | Published RTT inflation over fiber floor | **1.5×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **86.6 ms** | | Average RTT | **88.6 ms** | | Maximum RTT | **94.44 ms** | | Standard deviation | **1.9 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms * [Los Angeles to Melbourne latency and RTT](/docs/network/latency/pairs/lax-mel-rtt) — 148.2 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-mel-rtt). - **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. # Singapore → Miami, USA RTT 🇸🇬 **Singapore (SIN)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Singapore to Miami averaged 221.7 ms across 50 samples, with a minimum of 212 ms and a maximum of 252.74 ms. Zero packet loss was recorded, and the 6.57 ms jitter figure stayed close to the standard deviation of 8.4 ms, indicating a fairly steady path during the test window. The raw distance between the two cities is about 16,979 km, which puts a vacuum one-way floor near 113.3 ms and a glass fiber floor near 166.3 ms. This route runs 1.33 times its fiber floor, translating to roughly 75% fiber efficiency, so the observed average is within a plausible range for a long intercontinental crossing. This path ranked 17th in the 19-route outbound set, making it one of the slower options in the group. Its spread relative to the mean is about 3.8%, slightly above the network median of 3.28%, so while latency is fair, it is not the most consistent route in the outbound set. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **221.7 ms** | | Jitter | **6.57 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **166.27 ms** | | Fiber Efficiency | **75%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,978.7 km** | | Vacuum RTT floor | **113.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **166.27 ms** | | Low-latency fiber material floor | **165.6 ms** | | Engineering floor (5% path allowance) | **174.6 ms** | | Research 1.33× mapped-fiber reference | **221.14 ms** | | Estimated unamplified path loss | **3565.5 dB** | | Transparent optical spans / inline amplifiers | **223 / 222** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **212 ms** | | Average RTT | **221.7 ms** | | Maximum RTT | **252.74 ms** | | Standard deviation | **8.4 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Singapore latency and RTT](/docs/network/latency/pairs/mia-sin-rtt) — 223.1 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-mia-rtt). - **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. # Singapore → Moscow, Russia RTT 🇸🇬 **Singapore (SIN)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Singapore to Moscow, Russia, averaged 147.7 ms, with the minimum sample at 144.38 ms and the maximum at 154.89 ms. The 50-sample run recorded no packet loss, a standard deviation of 2.64 ms, and jitter of 2.33 ms. At 8,423.2 km of straight-line distance, the ideal fiber floor is about 82.49 ms, leaving the measured average 1.79 times above that floor, or a fiber efficiency of 55.8%. This is a larger distance-adjusted overhead than pure geography alone would predict, so the measured RTT is driven more by the actual network path than by the great-circle length. Among the 19 outbound routes measured from Singapore in the same round, this route ranked 7th by average RTT. Its variability is notably controlled: the 2.64 ms standard deviation is about 1.8% of the average, well below the 3.28% network-wide median ratio, and the max-to-min gap is only 10.51 ms. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **147.7 ms** | | Jitter | **2.33 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **82.49 ms** | | Fiber Efficiency | **55.8%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,423.2 km** | | Vacuum RTT floor | **56.19 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **82.49 ms** | | Low-latency fiber material floor | **82.15 ms** | | Engineering floor (5% path allowance) | **86.62 ms** | | Research 1.33× mapped-fiber reference | **109.71 ms** | | Estimated unamplified path loss | **1768.9 dB** | | Transparent optical spans / inline amplifiers | **111 / 110** | | Published RTT inflation over fiber floor | **1.79×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **144.38 ms** | | Average RTT | **147.7 ms** | | Maximum RTT | **154.89 ms** | | Standard deviation | **2.64 ms** | | Stdev / average | **1.8%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Singapore latency and RTT](/docs/network/latency/pairs/mow-sin-rtt) — 147.3 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-mow-rtt). - **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. # Singapore → Marseille, France RTT 🇸🇬 **Singapore (SIN)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. Under the 2026-08-16T04:07:28Z measurement round, ICMP echo probes from Singapore to Marseille, France, delivered an average round-trip time of 140.6 ms, with a minimum of 138.21 ms, a maximum of 150.15 ms, and zero packet loss over 50 samples. The spread between fastest and slowest probes was just under 12 ms, with a standard deviation of 2.29 ms and jitter of 1.84 ms. On a straight-line distance of 10,598.5 km, the direct fiber floor is about 103.79 ms. The observed 140.6 ms average is 1.35 times that floor, translating to a fiber efficiency of 73.8%, a tight result for a route spanning more than 10,000 km. This route ranked 6th among the 19 outbound routes measured from Singapore in the same round. Its low standard deviation is well under the network-wide median ratio of 3.28% of average RTT, so the path is both competitive and consistently stable for ICMP echo traffic. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **140.6 ms** | | Jitter | **1.84 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **103.79 ms** | | Fiber Efficiency | **73.8%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,598.5 km** | | Vacuum RTT floor | **70.71 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **103.79 ms** | | Low-latency fiber material floor | **103.37 ms** | | Engineering floor (5% path allowance) | **108.99 ms** | | Research 1.33× mapped-fiber reference | **138.04 ms** | | Estimated unamplified path loss | **2225.7 dB** | | Transparent optical spans / inline amplifiers | **140 / 139** | | Published RTT inflation over fiber floor | **1.35×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **138.21 ms** | | Average RTT | **140.6 ms** | | Maximum RTT | **150.15 ms** | | Standard deviation | **2.29 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-mrs-rtt). - **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. # Singapore → New York, USA RTT 🇸🇬 **Singapore (SIN)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round recorded an average ICMP echo RTT of 209.3 ms from Singapore to New York, with a spread from 199.54 ms to 235.91 ms over 50 samples. No packets were lost; jitter of 7.95 ms and a standard deviation of 8.69 ms point to a path that stayed fairly level during the measurement. At roughly 15,348 km apart, the two cities have a vacuum floor of 102.39 ms and a fiber floor of 150.29 ms. The observed average is 1.39 times the fiber floor, or about 71.8% fiber efficiency, meaning the route carries a noticeable but not extreme overhead beyond the theoretical minimum. Ranked 15th among the 19 outbound routes in the measurement set, this route sits in the slower half of the group. Its standard deviation is about 4.2% of the average, above the network median of 3.28%, so occasional variation is a bit more visible here than on the median outbound path. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **209.3 ms** | | Jitter | **7.95 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **150.29 ms** | | Fiber Efficiency | **71.8%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,347.5 km** | | Vacuum RTT floor | **102.39 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **150.29 ms** | | Low-latency fiber material floor | **149.69 ms** | | Engineering floor (5% path allowance) | **157.83 ms** | | Research 1.33× mapped-fiber reference | **199.89 ms** | | Estimated unamplified path loss | **3223 dB** | | Transparent optical spans / inline amplifiers | **202 / 201** | | Published RTT inflation over fiber floor | **1.39×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **199.54 ms** | | Average RTT | **209.3 ms** | | Maximum RTT | **235.91 ms** | | Standard deviation | **8.69 ms** | | Stdev / average | **4.2%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Singapore latency and RTT](/docs/network/latency/pairs/nyc-sin-rtt) — 208.7 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-nyc-rtt). - **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. # Singapore → Paris, France RTT 🇸🇬 **Singapore (SIN)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Singapore to Paris, France averaged 151.4 ms, with a minimum of 142.1 ms, a maximum of 172.35 ms, and zero packet loss. The 6.44 ms jitter and 6.94 ms standard deviation show a stable path whose occasional longer delays sit only about 21 ms above the average. This route's 151.4 ms mean is 1.44 times the 105.19 ms fiber-floor estimate for the 10,741.6 km great-circle distance, putting fiber efficiency at 69.5%. Relative to the 19 routes measured from this origin in the same round, this path ranked 8th; the typical variability across that set was 3.28% of the average RTT, while this route's own spread was around 4.6% of its mean. A useful takeaway is that the minimum RTT is only 9.3 ms below the average, so most probes land close to the typical value; the maximum then stretches to 172.35 ms. With no packet loss in this sample, the route offers a fair latency tier and consistent behavior, though the 69.5% fiber efficiency shows it is not operating near the physical floor. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **151.4 ms** | | Jitter | **6.44 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **105.19 ms** | | Fiber Efficiency | **69.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,741.6 km** | | Vacuum RTT floor | **71.66 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **105.19 ms** | | Low-latency fiber material floor | **104.77 ms** | | Engineering floor (5% path allowance) | **110.46 ms** | | Research 1.33× mapped-fiber reference | **139.9 ms** | | Estimated unamplified path loss | **2255.7 dB** | | Transparent optical spans / inline amplifiers | **141 / 140** | | Published RTT inflation over fiber floor | **1.44×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **142.1 ms** | | Average RTT | **151.4 ms** | | Maximum RTT | **172.35 ms** | | Standard deviation | **6.94 ms** | | Stdev / average | **4.6%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Singapore latency and RTT](/docs/network/latency/pairs/par-sin-rtt) — 150.3 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-par-rtt). - **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. # Singapore → Seattle, USA RTT 🇸🇬 **Singapore (SIN)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, ICMP echo RTT from Singapore to Seattle averaged 151.5 ms across 50 samples, with a minimum of 141.74 ms and a maximum of 170.28 ms. The path was loss-free, and jitter of 7.22 ms was nearly identical to the standard deviation of 7.34 ms, suggesting a steady path during the test period. The geodesic distance of about 12,991 km corresponds to a vacuum floor of 86.67 ms and a fiber floor of 127.22 ms. At 151.5 ms, the average is 1.19 times the fiber floor, giving 84% fiber efficiency, a comparatively strong use of the physical distance between the two locations. This route ranks 9th in the 19-route outbound set, placing it near the middle of the group. Its variability is about 4.8% of the average, above the network median of 3.28%, so while overall latency is fair and comparatively efficient, the round-trip time is not the most uniform in the set. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **151.5 ms** | | Jitter | **7.22 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **127.22 ms** | | Fiber Efficiency | **84%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,991.1 km** | | Vacuum RTT floor | **86.67 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **127.22 ms** | | Low-latency fiber material floor | **126.71 ms** | | Engineering floor (5% path allowance) | **133.6 ms** | | Research 1.33× mapped-fiber reference | **169.2 ms** | | Estimated unamplified path loss | **2728.1 dB** | | Transparent optical spans / inline amplifiers | **171 / 170** | | Published RTT inflation over fiber floor | **1.19×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **141.74 ms** | | Average RTT | **151.5 ms** | | Maximum RTT | **170.28 ms** | | Standard deviation | **7.34 ms** | | Stdev / average | **4.8%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Singapore latency and RTT](/docs/network/latency/pairs/sea-sin-rtt) — 151.1 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-sea-rtt). - **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. # Singapore → Sydney, Australia RTT 🇸🇬 **Singapore (SIN)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo probes from Singapore, Singapore to Sydney, Australia recorded an average round-trip time of 94.5 ms, a minimum of 92.37 ms, and a maximum of 99.4 ms. The 50-probe sample carried zero packet loss. The path's 1.76 ms standard deviation and 1.47 ms jitter kept the latency tier at 'Good'. At 94.5 ms, the average RTT was 1.53x the 61.63 ms fiber floor for the 6,293.5 km great-circle distance, an efficiency of 65.2% relative to a direct optical path. In the 19-outbound-route set used for this round, the route ranked fifth. Its observed variability was lower than the network-wide median of 3.28% of average RTT, and the narrow 92.37–99.4 ms window points to a steady path during the measurement period. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **94.5 ms** | | Jitter | **1.47 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **61.63 ms** | | Fiber Efficiency | **65.2%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,293.5 km** | | Vacuum RTT floor | **41.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **61.63 ms** | | Low-latency fiber material floor | **61.38 ms** | | Engineering floor (5% path allowance) | **64.72 ms** | | Research 1.33× mapped-fiber reference | **81.97 ms** | | Estimated unamplified path loss | **1321.6 dB** | | Transparent optical spans / inline amplifiers | **83 / 82** | | Published RTT inflation over fiber floor | **1.53×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **92.37 ms** | | Average RTT | **94.5 ms** | | Maximum RTT | **99.4 ms** | | Standard deviation | **1.76 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-syd-rtt). - **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. # Singapore → Taipei, Taiwan RTT 🇸🇬 **Singapore (SIN)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Singapore, Singapore to Taipei, Taiwan returned an average round-trip time of 45.8 ms, with a minimum of 43.12 ms and a maximum of 50.4 ms. All 50 probes were answered, so packet loss was 0%. The latency tier is 'Excellent'. The average sits at 1.44x the 31.77 ms fiber floor for the 3,243.9 km great-circle path, an efficiency of 69.4% against a direct optical route. Ranked second among the 19 outbound paths measured in this round, the route's 1.72 ms standard deviation came to about 3.8% of its average, close to the network-wide median variability of 3.28%. Jitter of 1.86 ms and zero loss suggest consistent behavior over the sampling window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **45.8 ms** | | Jitter | **1.86 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **31.77 ms** | | Fiber Efficiency | **69.4%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,243.9 km** | | Vacuum RTT floor | **21.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **31.77 ms** | | Low-latency fiber material floor | **31.64 ms** | | Engineering floor (5% path allowance) | **33.36 ms** | | Research 1.33× mapped-fiber reference | **42.25 ms** | | Estimated unamplified path loss | **681.2 dB** | | Transparent optical spans / inline amplifiers | **43 / 42** | | Published RTT inflation over fiber floor | **1.44×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **43.12 ms** | | Average RTT | **45.8 ms** | | Maximum RTT | **50.4 ms** | | Standard deviation | **1.72 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-tpe-rtt). - **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. # Singapore → Tokyo, Japan RTT 🇸🇬 **Singapore (SIN)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z run, ICMP echo probes from Singapore, Singapore to Tokyo, Japan produced an average round-trip time of 68.9 ms, with the fastest sample at 65.47 ms and the slowest at 78.16 ms. The 50-probe sample had no packet loss. Latency tier remained 'Excellent' despite the international distance. The average is 1.32x the 52 ms fiber floor for the 5,310.2 km great-circle route, an efficiency of 75.5% relative to a direct fiber path—a good fit to the theoretical minimum. Ranked third among the 19 outbound paths measured in this round, the route's 2.72 ms standard deviation was about 3.9% of its average, close to the network-wide median variability of 3.28%. Jitter of 1.99 ms and zero packet loss point to a stable path across the measurement window. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **68.9 ms** | | Jitter | **1.99 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **52 ms** | | Fiber Efficiency | **75.5%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,310.2 km** | | Vacuum RTT floor | **35.43 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **52 ms** | | Low-latency fiber material floor | **51.79 ms** | | Engineering floor (5% path allowance) | **54.61 ms** | | Research 1.33× mapped-fiber reference | **69.16 ms** | | Estimated unamplified path loss | **1115.1 dB** | | Transparent optical spans / inline amplifiers | **70 / 69** | | Published RTT inflation over fiber floor | **1.32×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **65.47 ms** | | Average RTT | **68.9 ms** | | Maximum RTT | **78.16 ms** | | Standard deviation | **2.72 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms **Fastest routes departing Singapore (SIN)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/sin-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/sin-tyo-rtt). - **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. # Sydney, Australia → Amsterdam, Netherlands RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Sydney to Amsterdam averaged 258.9 ms, with a minimum of 249.45 ms, a maximum of 283.53 ms, and zero packet loss over 50 samples. The standard deviation was 7.86 ms (jitter 6.38 ms), about 3.0% of the average and below the 3.28% median for this network's outbound routes. The route ranks 16th out of 19 outbound routes, with only three routes in the current set returning higher latency. At a geodesic distance of 16,638.1 km, the theoretical fiber minimum is 162.93 ms and the vacuum floor is 111 ms. The observed average is 1.59 times the fiber minimum, for a fiber efficiency of 62.9%; that relatively high efficiency for an intercontinental distance indicates the measured latency does not carry an excessive detour penalty, while the small gap between minimum and average reflects a steady ICMP echo sequence. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **258.9 ms** | | Jitter | **6.38 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **162.93 ms** | | Fiber Efficiency | **62.9%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,638.1 km** | | Vacuum RTT floor | **111 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **162.93 ms** | | Low-latency fiber material floor | **162.28 ms** | | Engineering floor (5% path allowance) | **171.1 ms** | | Research 1.33× mapped-fiber reference | **216.7 ms** | | Estimated unamplified path loss | **3494 dB** | | Transparent optical spans / inline amplifiers | **219 / 218** | | Published RTT inflation over fiber floor | **1.59×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **249.45 ms** | | Average RTT | **258.9 ms** | | Maximum RTT | **283.53 ms** | | Standard deviation | **7.86 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Sydney latency and RTT](/docs/network/latency/pairs/ams-syd-rtt) — 258 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-ams-rtt). - **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. # Sydney, Australia → Berlin, Germany RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z ICMP echo round from Sydney to Berlin recorded an average RTT of 260.5 ms, with a minimum of 249.51 ms, a maximum of 293.46 ms, and no packet loss across 50 samples. The standard deviation was 9.56 ms and jitter 8.36 ms; that spread is about 3.7% of the average, above the 3.28% median for this network's outbound routes. The route ranks 17th of 19 outbound routes, leaving only two routes in the current set with higher latency. Over the 16,087.7 km geodesic distance, the theoretical fiber minimum is 157.54 ms and the vacuum floor is 107.33 ms. The observed average is 1.65 times the fiber minimum, corresponding to 60.5% fiber efficiency. The maximum-to-minimum gap of 43.95 ms, combined with a stdev-to-average ratio above the network median, makes this route slightly more variable than the typical outbound route in the current round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **260.5 ms** | | Jitter | **8.36 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **157.54 ms** | | Fiber Efficiency | **60.5%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,087.7 km** | | Vacuum RTT floor | **107.33 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **157.54 ms** | | Low-latency fiber material floor | **156.91 ms** | | Engineering floor (5% path allowance) | **165.44 ms** | | Research 1.33× mapped-fiber reference | **209.53 ms** | | Estimated unamplified path loss | **3378.4 dB** | | Transparent optical spans / inline amplifiers | **212 / 211** | | Published RTT inflation over fiber floor | **1.65×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **249.51 ms** | | Average RTT | **260.5 ms** | | Maximum RTT | **293.46 ms** | | Standard deviation | **9.56 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Sydney latency and RTT](/docs/network/latency/pairs/ber-syd-rtt) — 262.1 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-ber-rtt). - **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. # Sydney, Australia → Frankfurt, Germany RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of 50 ICMP echo probes from Sydney to Frankfurt returned an average round-trip time of 254.4 ms, with a minimum of 239.27 ms and a maximum of 292.11 ms. No packets were lost, while jitter was measured at 9.95 ms and the standard deviation at 11.5 ms. The path spans a great-circle distance of 16,478.2 km, where the theoretical fiber-floor RTT is 161.37 ms. The observed average is about 1.58 times that floor, implying a fiber efficiency of 63.4%; in other words, roughly 93 ms of the round trip is overhead beyond the ideal fiber path. This route ranked 14th of 19 outbound paths from Sydney in the same round, and its variability of about 4.5% of the average sits above the 3.28% median for that route set. The zero-loss result is encouraging, but the spread from minimum to maximum suggests the path can occasionally produce excursions beyond the typical range. These ICMP figures characterize network-layer round-trip behavior only, not application throughput. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **254.4 ms** | | Jitter | **9.95 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **161.37 ms** | | Fiber Efficiency | **63.4%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,478.2 km** | | Vacuum RTT floor | **109.93 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **161.37 ms** | | Low-latency fiber material floor | **160.72 ms** | | Engineering floor (5% path allowance) | **169.46 ms** | | Research 1.33× mapped-fiber reference | **214.62 ms** | | Estimated unamplified path loss | **3460.4 dB** | | Transparent optical spans / inline amplifiers | **217 / 216** | | Published RTT inflation over fiber floor | **1.58×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **239.27 ms** | | Average RTT | **254.4 ms** | | Maximum RTT | **292.11 ms** | | Standard deviation | **11.5 ms** | | Stdev / average | **4.5%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Sydney latency and RTT](/docs/network/latency/pairs/fra-syd-rtt) — 256 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-fra-rtt). - **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. # Sydney, Australia → São Paulo, Brazil RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round from Sydney, Australia, to São Paulo, Brazil measured an average ICMP echo RTT of 296.7 ms over 50 samples, with 0% packet loss and a high latency tier. For the 13,377 km great-circle distance, the average is 2.26 times the theoretical fiber floor, or 44.2% fiber efficiency. It placed 18th out of 19 outbound paths measured from the Sydney gateway, near the slower end of the group. Standard deviation was 13.03 ms and jitter 10.12 ms, around 4.4% of the average, above the network's median variability of 3.3%. The 59.01 ms gap between fastest and slowest samples, combined with zero loss, shows a high-latency route whose round trips varied more than the network norm during this test. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **296.7 ms** | | Jitter | **10.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **131 ms** | | Fiber Efficiency | **44.2%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **13,377 km** | | Vacuum RTT floor | **89.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **131 ms** | | Low-latency fiber material floor | **130.47 ms** | | Engineering floor (5% path allowance) | **137.57 ms** | | Research 1.33× mapped-fiber reference | **174.23 ms** | | Estimated unamplified path loss | **2809.2 dB** | | Transparent optical spans / inline amplifiers | **176 / 175** | | Published RTT inflation over fiber floor | **2.26×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **278.26 ms** | | Average RTT | **296.7 ms** | | Maximum RTT | **337.27 ms** | | Standard deviation | **13.03 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Asia Pacific to South America](/docs/network/latency/regions/asia-pacific-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Sydney latency and RTT](/docs/network/latency/pairs/gru-syd-rtt) — 265.5 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Asia Pacific → South America)** * [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.5 ms * [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 ms * [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-gru-rtt). - **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. # Sydney, Australia → Hong Kong RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Sydney, Australia, to Hong Kong averaged 135.7 ms over 50 samples, with a minimum of 124.18 ms, a maximum of 155.08 ms, and no packet loss. The measured latency tier was good. For the 7,349.1 km great-circle separation, the average is 1.89 times the theoretical fiber floor, or 53% fiber efficiency. The result placed 5th out of 19 outbound paths measured from the Sydney gateway, putting the route in the faster portion of the group. The standard deviation was 6.42 ms and jitter was 6.06 ms, about 4.7% of the average and slightly above the network's median variability of 3.3%. A 30.9 ms spread between fastest and slowest samples, with zero loss, gives a useful stability reference for this Asia-Pacific route. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **135.7 ms** | | Jitter | **6.06 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **71.97 ms** | | Fiber Efficiency | **53%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,349.1 km** | | Vacuum RTT floor | **49.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **71.97 ms** | | Low-latency fiber material floor | **71.68 ms** | | Engineering floor (5% path allowance) | **75.58 ms** | | Research 1.33× mapped-fiber reference | **95.72 ms** | | Estimated unamplified path loss | **1543.3 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.89×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **124.18 ms** | | Average RTT | **135.7 ms** | | Maximum RTT | **155.08 ms** | | Standard deviation | **6.42 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-hkg-rtt). - **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. # Sydney, Australia → Ashburn, USA RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. At 2026-08-16T04:07:28Z, the ICMP echo path from Sydney to Ashburn averaged 195.3 ms over 50 samples sent every 100 ms. The minimum RTT was 186.39 ms, the maximum 216.22 ms, and packet loss was zero. This Sydney–Ashburn route ranks 10th by average RTT among the 19 outgoing paths in this round. Its variability is slightly above the 3.28% median ratio for the set: standard deviation was 7.74 ms and jitter 6.41 ms, a spread of roughly 3.96% of the average. The geodesic distance is 15,673.1 km and the direct-fiber floor is about 153.48 ms. At 195.3 ms, the measured RTT is only 1.27 times that floor, with a fiber-efficiency score of 78.6%; the sub-200 ms average and zero packet loss make this a clean ICMP timing reference for the route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **195.3 ms** | | Jitter | **6.41 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **153.48 ms** | | Fiber Efficiency | **78.6%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,673.1 km** | | Vacuum RTT floor | **104.56 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **153.48 ms** | | Low-latency fiber material floor | **152.87 ms** | | Engineering floor (5% path allowance) | **161.18 ms** | | Research 1.33× mapped-fiber reference | **204.13 ms** | | Estimated unamplified path loss | **3291.4 dB** | | Transparent optical spans / inline amplifiers | **206 / 205** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **186.39 ms** | | Average RTT | **195.3 ms** | | Maximum RTT | **216.22 ms** | | Standard deviation | **7.74 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Sydney latency and RTT](/docs/network/latency/pairs/iad-syd-rtt) — 193.6 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-iad-rtt). - **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. # Sydney, Australia → Johannesburg, South Africa RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement window for Sydney, Australia to Johannesburg, South Africa produced an average ICMP echo RTT of 412.5 ms across 50 samples, with a minimum of 399.32 ms, a maximum of 451.86 ms, and no packet loss. The standard deviation of 12.82 ms and jitter of 9.3 ms show a path that is reachable but subject to noticeable timing variation. Over a geodesic distance of about 11,060.7 km, the observed average is 3.81 times the 108.32 ms optical fiber floor, translating to a fiber efficiency of 26.3%. The high inflation over the physical minimum is a clear sign that direct-line distance does not capture the full delay involved on a route of this length. Among the 19 routes measured in the same round, this connection ranked 19th by RTT. Its relative spread of about 3.1% sits near the 3.28% median variability across the monitored set, and the 0% loss rate suggests that the path, while slow, carried every ICMP probe without drops during the test. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **412.5 ms** | | Jitter | **9.3 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **108.32 ms** | | Fiber Efficiency | **26.3%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,060.7 km** | | Vacuum RTT floor | **73.79 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **108.32 ms** | | Low-latency fiber material floor | **107.88 ms** | | Engineering floor (5% path allowance) | **113.75 ms** | | Research 1.33× mapped-fiber reference | **144.06 ms** | | Estimated unamplified path loss | **2322.8 dB** | | Transparent optical spans / inline amplifiers | **146 / 145** | | Published RTT inflation over fiber floor | **3.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **399.32 ms** | | Average RTT | **412.5 ms** | | Maximum RTT | **451.86 ms** | | Standard deviation | **12.82 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Sydney latency and RTT](/docs/network/latency/pairs/jnb-syd-rtt) — 412.6 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Asia Pacific → Africa)** * [Singapore to Johannesburg latency and RTT](/docs/network/latency/pairs/sin-jnb-rtt) — 312.6 ms * [Hong Kong to Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt) — 316.7 ms * [Taipei to Johannesburg latency and RTT](/docs/network/latency/pairs/tpe-jnb-rtt) — 331 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-jnb-rtt). - **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. # Sydney, Australia → Los Angeles, USA RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo RTT between Sydney, Australia and Los Angeles, USA averaged 136.5 ms across 50 samples, with a minimum of 132.98 ms and a maximum of 143.81 ms. The 2.85 ms standard deviation and 2.5 ms jitter point to a stable path, and with packet loss at 0%, every probe in the round returned a response. Across the 19 outbound routes measured in the same round, this Sydney-to-Los Angeles pairing ranked 6th by average RTT. Its sample variability is about 2.1% of the average, below the 3.28% median variability for those peers, so the route held a steadier latency profile than the typical route. At a geodesic distance of 12,063.2 km, the route has a vacuum floor of 80.48 ms and an estimated fiber floor of 118.13 ms. The measured average is 1.16 times that fiber floor, an 86.5% fiber efficiency that leaves modest overhead for a trans-Pacific crossing. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **136.5 ms** | | Jitter | **2.5 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **118.13 ms** | | Fiber Efficiency | **86.5%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,063.2 km** | | Vacuum RTT floor | **80.48 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **118.13 ms** | | Low-latency fiber material floor | **117.66 ms** | | Engineering floor (5% path allowance) | **124.05 ms** | | Research 1.33× mapped-fiber reference | **157.12 ms** | | Estimated unamplified path loss | **2533.3 dB** | | Transparent optical spans / inline amplifiers | **159 / 158** | | Published RTT inflation over fiber floor | **1.16×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **132.98 ms** | | Average RTT | **136.5 ms** | | Maximum RTT | **143.81 ms** | | Standard deviation | **2.85 ms** | | Stdev / average | **2.1%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-lax-rtt). - **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. # Sydney, Australia → London, UK RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of 50 ICMP echo probes from Sydney to London produced an average round-trip time of 256.5 ms, a minimum of 243.5 ms, and a maximum of 279.39 ms. Packet loss was zero, while jitter reached 10.31 ms and standard deviation 9.98 ms. With a great-circle distance of 16,988.9 km, the theoretical fiber-floor RTT is 166.37 ms. The observed average is about 1.54 times that floor, so the route operates at roughly 64.9% fiber efficiency, leaving about 90 ms of overhead beyond the ideal fiber path. The route ranked 15th of 19 outbound paths from Sydney for this round, and its variability is around 3.9% of the average, slightly above the 3.28% median for the route set. Jitter being slightly larger than the standard deviation highlights that individual round trips varied more irregularly than the overall dispersion alone suggests; the zero-loss profile remains clean. As with any ICMP RTT view, these numbers describe network-layer round-trip delay rather than end-user application performance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **256.5 ms** | | Jitter | **10.31 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **166.37 ms** | | Fiber Efficiency | **64.9%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,988.9 km** | | Vacuum RTT floor | **113.34 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **166.37 ms** | | Low-latency fiber material floor | **165.7 ms** | | Engineering floor (5% path allowance) | **174.71 ms** | | Research 1.33× mapped-fiber reference | **221.27 ms** | | Estimated unamplified path loss | **3567.7 dB** | | Transparent optical spans / inline amplifiers | **223 / 222** | | Published RTT inflation over fiber floor | **1.54×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **243.5 ms** | | Average RTT | **256.5 ms** | | Maximum RTT | **279.39 ms** | | Standard deviation | **9.98 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Sydney latency and RTT](/docs/network/latency/pairs/lon-syd-rtt) — 258.1 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-lon-rtt). - **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. # Sydney, Australia → Melbourne, Australia RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Sydney to Melbourne averaged 9.8 ms over 50 samples taken every 100 ms, with a minimum of 9.38 ms and a maximum of 11.84 ms. The 0.46 ms standard deviation and 0.41 ms jitter describe a very stable city-to-city path, and zero packet loss was observed in this sample. Across the 713.8 km geodesic distance, the measured RTT is only 1.4 times the theoretical fiber floor, giving an effective fiber efficiency of about 71.3%. This route ranked first among the 19 outbound routes in the same round, and the network-wide median route variability stood at 3.28% of average latency. For routine measurements between these two Australian cities, the result is a clean ultra-low-latency baseline with essentially no loss. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **9.8 ms** | | Jitter | **0.41 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **6.99 ms** | | Fiber Efficiency | **71.3%** | | Latency Tier | Ultra-Low | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **713.8 km** | | Vacuum RTT floor | **4.76 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **6.99 ms** | | Low-latency fiber material floor | **6.96 ms** | | Engineering floor (5% path allowance) | **7.34 ms** | | Research 1.33× mapped-fiber reference | **9.3 ms** | | Estimated unamplified path loss | **149.9 dB** | | Transparent optical spans / inline amplifiers | **10 / 9** | | Published RTT inflation over fiber floor | **1.4×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **9.38 ms** | | Average RTT | **9.8 ms** | | Maximum RTT | **11.84 ms** | | Standard deviation | **0.46 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms **Fastest routes arriving at Melbourne (MEL)** * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms * [Los Angeles to Melbourne latency and RTT](/docs/network/latency/pairs/lax-mel-rtt) — 148.2 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-mel-rtt). - **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. # Sydney, Australia → Miami, USA RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo RTT from Sydney, Australia to Miami, USA averaged 191.5 ms over 50 samples, with a minimum of 181.12 ms and a maximum of 215.13 ms. Packet loss remained 0%, but the 7.49 ms standard deviation and 6.69 ms jitter indicate the path's transit time can vary noticeably from probe to probe. Across the 19 outbound routes measured in the same round, this route ranked 8th by average RTT. The measured variability is roughly 3.9% of the average, above the 3.28% median for the round, so Miami-bound samples spread more widely than the typical peer route. With a geodesic distance of 15,029.6 km, the route's vacuum floor is 100.27 ms and its estimated fiber floor is 147.18 ms. The observed average sits 1.30 times above that fiber floor, for 76.9% fiber efficiency, which aligns with the Fair latency tier. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **191.5 ms** | | Jitter | **6.69 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **147.18 ms** | | Fiber Efficiency | **76.9%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,029.6 km** | | Vacuum RTT floor | **100.27 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **147.18 ms** | | Low-latency fiber material floor | **146.59 ms** | | Engineering floor (5% path allowance) | **154.56 ms** | | Research 1.33× mapped-fiber reference | **195.75 ms** | | Estimated unamplified path loss | **3156.2 dB** | | Transparent optical spans / inline amplifiers | **198 / 197** | | Published RTT inflation over fiber floor | **1.3×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **181.12 ms** | | Average RTT | **191.5 ms** | | Maximum RTT | **215.13 ms** | | Standard deviation | **7.49 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Sydney latency and RTT](/docs/network/latency/pairs/mia-syd-rtt) — 191.5 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-mia-rtt). - **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. # Sydney, Australia → Moscow, Russia RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo measurements collected at 2026-08-16T04:07:28Z put the Sydney–Moscow round-trip time at 242.2 ms on average, based on 50 probes sent at 100 ms intervals. The minimum RTT was 230.07 ms, the maximum was 270.93 ms, and packet loss was zero. The route's short-term stability is contained for the distance: standard deviation was 9.04 ms and jitter 7.98 ms, or roughly 3.7% and 3.3% of the average. This Sydney–Moscow path ranks 12th by average RTT among the 19 outgoing paths measured in the same round, with variability just above the 3.28% median ratio for those paths. The great-circle distance from Sydney to Moscow is about 14,483.9 km, and a direct fiber path at the speed of light in glass would need about 141.84 ms. The observed 242.2 ms is therefore 1.71 times that floor, with a fiber-efficiency score of 58.6% — a reminder that the effective path is considerably longer than the geodesic line, even though no probes were lost and the jitter band stayed narrow. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **242.2 ms** | | Jitter | **7.98 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **141.84 ms** | | Fiber Efficiency | **58.6%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **14,483.9 km** | | Vacuum RTT floor | **96.63 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **141.84 ms** | | Low-latency fiber material floor | **141.27 ms** | | Engineering floor (5% path allowance) | **148.95 ms** | | Research 1.33× mapped-fiber reference | **188.64 ms** | | Estimated unamplified path loss | **3041.6 dB** | | Transparent optical spans / inline amplifiers | **191 / 190** | | Published RTT inflation over fiber floor | **1.71×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **230.07 ms** | | Average RTT | **242.2 ms** | | Maximum RTT | **270.93 ms** | | Standard deviation | **9.04 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Sydney latency and RTT](/docs/network/latency/pairs/mow-syd-rtt) — 241.8 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-mow-rtt). - **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. # Sydney, Australia → Marseille, France RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z round of 50 ICMP echo probes from Sydney to Marseille recorded an average round-trip time of 240.5 ms, with a minimum of 231.2 ms and a maximum of 264.13 ms. No packets were lost, and the route showed comparatively tight timing: jitter of 6.37 ms and a standard deviation of 7.87 ms. The great-circle distance is 16,891 km, and the corresponding fiber-floor RTT is 165.41 ms. The measured average is 1.45 times that floor, making this a 68.8% fiber-efficient path; the roughly 75 ms of overhead over the ideal fiber path reflects the practical cost of such a long intercontinental route. Ranked 11th of 19 outbound paths from Sydney in this round, the route's variability of about 3.3% of the average aligns almost exactly with the 3.28% median for the route set. The combination of zero loss, a 7.87 ms standard deviation, and 6.37 ms jitter points to a steady network-layer path during this probe window. These ICMP RTT values describe network-layer delay only, not the throughput users should expect from applications. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **240.5 ms** | | Jitter | **6.37 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **165.41 ms** | | Fiber Efficiency | **68.8%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **16,891 km** | | Vacuum RTT floor | **112.68 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **165.41 ms** | | Low-latency fiber material floor | **164.74 ms** | | Engineering floor (5% path allowance) | **173.7 ms** | | Research 1.33× mapped-fiber reference | **219.99 ms** | | Estimated unamplified path loss | **3547.1 dB** | | Transparent optical spans / inline amplifiers | **222 / 221** | | Published RTT inflation over fiber floor | **1.45×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **231.2 ms** | | Average RTT | **240.5 ms** | | Maximum RTT | **264.13 ms** | | Standard deviation | **7.87 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Sydney latency and RTT](/docs/network/latency/pairs/mrs-syd-rtt) — 240.6 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-mrs-rtt). - **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. # Sydney, Australia → New York, USA RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo RTT from Sydney, Australia to New York, USA averaged 191.9 ms across 50 samples, with a minimum of 183.18 ms and a maximum of 221.95 ms. Loss was 0%, but the roughly 38.8 ms gap between the fastest and slowest samples, along with a 7.82 ms standard deviation, shows the route can shift by a meaningful margin. Across the 19 outbound routes measured in the same round, this pairing ranked 9th by average RTT. Its standard deviation equals about 4.1% of the average, above the 3.28% median for the round, so the New York path had more sample-to-sample spread than its peers. At 15,988.1 km, the route's measured average is 1.23 times the estimated fiber floor of 156.57 ms, an 81.6% fiber efficiency that leaves room for improvement on a very long Sydney-to-New York crossing. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **191.9 ms** | | Jitter | **4.83 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **156.57 ms** | | Fiber Efficiency | **81.6%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **15,988.1 km** | | Vacuum RTT floor | **106.66 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **156.57 ms** | | Low-latency fiber material floor | **155.94 ms** | | Engineering floor (5% path allowance) | **164.42 ms** | | Research 1.33× mapped-fiber reference | **208.24 ms** | | Estimated unamplified path loss | **3357.5 dB** | | Transparent optical spans / inline amplifiers | **210 / 209** | | Published RTT inflation over fiber floor | **1.23×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **183.18 ms** | | Average RTT | **191.9 ms** | | Maximum RTT | **221.95 ms** | | Standard deviation | **7.82 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Sydney latency and RTT](/docs/network/latency/pairs/nyc-syd-rtt) — 192.6 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-nyc-rtt). - **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. # Sydney, Australia → Paris, France RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo measurements taken at 2026-08-16T04:07:28Z show an average Sydney–Paris round-trip time of 250.3 ms from 50 probes spaced 100 ms apart. The minimum was 243.57 ms, the maximum 268.33 ms, and all probes returned successfully. Variability on this path is low: standard deviation was 5.4 ms and jitter 3.75 ms, a spread of roughly 2.2% of the average — below the 3.28% median ratio for the 19 outgoing paths in this round. On average RTT, the route is 13th of those 19 paths. The geodesic distance between Sydney and Paris is 16,957.7 km, and the direct-fiber floor is about 166.06 ms. The measured 250.3 ms is 1.51 times that floor, corresponding to a 66.3% fiber-efficiency score, and the zero-loss, low-jitter profile makes this a clean ICMP timing reference for the route. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **250.3 ms** | | Jitter | **3.75 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **166.06 ms** | | Fiber Efficiency | **66.3%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **16,957.7 km** | | Vacuum RTT floor | **113.13 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **166.06 ms** | | Low-latency fiber material floor | **165.4 ms** | | Engineering floor (5% path allowance) | **174.39 ms** | | Research 1.33× mapped-fiber reference | **220.86 ms** | | Estimated unamplified path loss | **3561.1 dB** | | Transparent optical spans / inline amplifiers | **223 / 222** | | Published RTT inflation over fiber floor | **1.51×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **243.57 ms** | | Average RTT | **250.3 ms** | | Maximum RTT | **268.33 ms** | | Standard deviation | **5.4 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Sydney latency and RTT](/docs/network/latency/pairs/par-syd-rtt) — 249.7 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-par-rtt). - **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. # Sydney, Australia → Seattle, USA RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Sydney, Australia, to Seattle, USA averaged 161.9 ms over 50 samples, with a minimum of 153.84 ms and a maximum of 176.63 ms. Packet loss was 0%. For the 12,453.7 km great-circle separation, that average is 1.33 times the theoretical fiber-floor delay and corresponds to 75.3% fiber efficiency. The result placed 7th among the 19 outbound routes measured from the Sydney gateway, putting it in the faster portion of the group. The standard deviation was 5.72 ms and jitter was 3.81 ms, about 3.5% of the average, which sits close to the network's median variability of 3.3%. Zero packet loss and a 22.79 ms difference between best and worst samples indicate a steady trans-Pacific latency profile under the test conditions. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **161.9 ms** | | Jitter | **3.81 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **121.96 ms** | | Fiber Efficiency | **75.3%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,453.7 km** | | Vacuum RTT floor | **83.08 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **121.96 ms** | | Low-latency fiber material floor | **121.47 ms** | | Engineering floor (5% path allowance) | **128.07 ms** | | Research 1.33× mapped-fiber reference | **162.2 ms** | | Estimated unamplified path loss | **2615.3 dB** | | Transparent optical spans / inline amplifiers | **164 / 163** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **153.84 ms** | | Average RTT | **161.9 ms** | | Maximum RTT | **176.63 ms** | | Standard deviation | **5.72 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Sydney latency and RTT](/docs/network/latency/pairs/sea-syd-rtt) — 161.3 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-sea-rtt). - **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. # Sydney, Australia → Singapore RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Sydney to Singapore averaged 94.5 ms over 50 samples, with a minimum of 89.04 ms and a maximum of 106.31 ms. The 3.56 ms standard deviation and 3.48 ms jitter show a stable long-haul path, and all 50 samples returned with zero packet loss. Against the 6,293.5 km geodesic distance, the measured RTT is 1.53 times the theoretical fiber floor, corresponding to about 65.2% fiber efficiency. It ranked second among the 19 outbound routes in the same round; its standard deviation is about 3.8% of its average, slightly above the network-wide median route variability of 3.28%. A consistent sub-100 ms average and zero packet loss make this a dependable reference for long-haul RTT from Sydney to Singapore. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **94.5 ms** | | Jitter | **3.48 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **61.63 ms** | | Fiber Efficiency | **65.2%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **6,293.5 km** | | Vacuum RTT floor | **41.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **61.63 ms** | | Low-latency fiber material floor | **61.38 ms** | | Engineering floor (5% path allowance) | **64.72 ms** | | Research 1.33× mapped-fiber reference | **81.97 ms** | | Estimated unamplified path loss | **1321.6 dB** | | Transparent optical spans / inline amplifiers | **83 / 82** | | Published RTT inflation over fiber floor | **1.53×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **89.04 ms** | | Average RTT | **94.5 ms** | | Maximum RTT | **106.31 ms** | | Standard deviation | **3.56 ms** | | Stdev / average | **3.8%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-sin-rtt). - **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. # Sydney, Australia → Taipei, Taiwan RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Sydney to Taipei averaged 131.7 ms over 50 samples, with a minimum of 126.36 ms and a maximum of 151.94 ms. The 4.46 ms standard deviation and 3.58 ms jitter indicate moderate variability, while zero packet loss was recorded across the sample. The route spans 7,237.6 km and measures 1.86 times the theoretical fiber floor, an effective fiber efficiency of about 53.8%. It ranked fourth among the 19 outbound routes in the same round; its standard deviation is about 3.4% of its average, just above the network-wide median route variability of 3.28%. This positions the Sydney-Taipei route as a steady, higher-latency reference within the same measurement set, with no dropped probes despite the longer distance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **131.7 ms** | | Jitter | **3.58 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **70.88 ms** | | Fiber Efficiency | **53.8%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,237.6 km** | | Vacuum RTT floor | **48.28 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **70.88 ms** | | Low-latency fiber material floor | **70.59 ms** | | Engineering floor (5% path allowance) | **74.43 ms** | | Research 1.33× mapped-fiber reference | **94.26 ms** | | Estimated unamplified path loss | **1519.9 dB** | | Transparent optical spans / inline amplifiers | **95 / 94** | | Published RTT inflation over fiber floor | **1.86×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **126.36 ms** | | Average RTT | **131.7 ms** | | Maximum RTT | **151.94 ms** | | Standard deviation | **4.46 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-tpe-rtt). - **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. # Sydney, Australia → Tokyo, Japan RTT 🇦🇺 **Sydney, Australia (SYD)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, 50 ICMP echo samples from Sydney, Australia to Tokyo, Japan produced an average round-trip time of 101.3 ms, with a minimum of 99.25 ms and a maximum of 108.62 ms. No packets were lost, and the 1.46 ms jitter indicates a stable path throughout the test window. Measured against a geodesic distance of roughly 7,792.8 km, the observed average is only 1.33 times the optical fiber floor of 76.31 ms, giving a fiber efficiency of 75.3%. That places the route close to what a direct optical path would allow, with little excess delay over the physical minimum. Ranked third among the 19 routes in this round, Sydney–Tokyo also shows a standard deviation of 2.05 ms, or about 2.0% of its average, below the 3.28% median variability across the monitored set. The combination of a strong ranking, zero loss, and tightly grouped samples makes this one of the more consistent long-haul paths in the data. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **101.3 ms** | | Jitter | **1.46 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.31 ms** | | Fiber Efficiency | **75.3%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,792.8 km** | | Vacuum RTT floor | **51.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.31 ms** | | Low-latency fiber material floor | **76.01 ms** | | Engineering floor (5% path allowance) | **80.14 ms** | | Research 1.33× mapped-fiber reference | **101.5 ms** | | Estimated unamplified path loss | **1636.5 dB** | | Transparent optical spans / inline amplifiers | **103 / 102** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **99.25 ms** | | Average RTT | **101.3 ms** | | Maximum RTT | **108.62 ms** | | Standard deviation | **2.05 ms** | | Stdev / average | **2.0%** | ## Route Context * Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms **Fastest routes departing Sydney (SYD)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms **Fastest routes arriving at Tokyo (TYO)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/syd-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/syd-tyo-rtt). - **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. # Taipei, Taiwan → Amsterdam, Netherlands RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, the Taipei, Taiwan to Amsterdam, Netherlands path averaged 166.5 ms over 50 ICMP echo samples, with a minimum of 161.36 ms, a maximum of 179.84 ms, and 0% packet loss. The standard deviation of 3.92 ms and jitter of 3.56 ms indicate a fairly stable connection during the test. At a geodesic distance of roughly 9,467.8 km, the recorded average is 1.8 times the optical fiber floor of 92.72 ms, putting fiber efficiency at 55.7%. The extra delay over the floor is moderate for a route spanning this much geography, and the measured latency falls into the Fair tier. This route ranked 11th among the 19 routes in the same round, and its 3.92 ms standard deviation equals about 2.4% of the average, below the 3.28% median variability across the monitored set. With zero packets lost and jitter under 4 ms, the Taipei–Amsterdam path is more consistent than its middle-of-the-pack absolute latency might suggest. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **166.5 ms** | | Jitter | **3.56 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **92.72 ms** | | Fiber Efficiency | **55.7%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,467.8 km** | | Vacuum RTT floor | **63.16 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **92.72 ms** | | Low-latency fiber material floor | **92.34 ms** | | Engineering floor (5% path allowance) | **97.36 ms** | | Research 1.33× mapped-fiber reference | **123.31 ms** | | Estimated unamplified path loss | **1988.2 dB** | | Transparent optical spans / inline amplifiers | **125 / 124** | | Published RTT inflation over fiber floor | **1.8×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **161.36 ms** | | Average RTT | **166.5 ms** | | Maximum RTT | **179.84 ms** | | Standard deviation | **3.92 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Taipei latency and RTT](/docs/network/latency/pairs/ams-tpe-rtt) — 168.7 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-ams-rtt). - **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. # Taipei, Taiwan → Berlin, Germany RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z run, ICMP echo probes from Taipei, Taiwan to Berlin, Germany averaged 158.6 ms over 50 samples, with a minimum of 154.12 ms and a maximum of 170.16 ms. No packets were lost, and jitter of 3.48 ms kept the round-trip times tightly grouped. That average sits at 1.81 times the theoretical fiber-floor value for the 8,970.4 km great-circle path, which corresponds to a fiber efficiency of 55.4%. Even the fastest sample was 154.12 ms, so the floor is high: the route's Fair latency tier is shaped by geography and the optical distance that must be covered, not by sample-to-sample instability. The 3.77 ms standard deviation is only about 2.4% of the route average, calmer than the 3.28% median variability-to-average ratio seen across the 19 outbound routes in this measurement group. Ranked 9th in that group, the Taipei–Berlin path offers a consistent, loss-free ICMP RTT profile that can be treated as predictable over short observation windows. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **158.6 ms** | | Jitter | **3.48 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **87.84 ms** | | Fiber Efficiency | **55.4%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,970.4 km** | | Vacuum RTT floor | **59.84 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **87.84 ms** | | Low-latency fiber material floor | **87.49 ms** | | Engineering floor (5% path allowance) | **92.25 ms** | | Research 1.33× mapped-fiber reference | **116.83 ms** | | Estimated unamplified path loss | **1883.8 dB** | | Transparent optical spans / inline amplifiers | **118 / 117** | | Published RTT inflation over fiber floor | **1.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **154.12 ms** | | Average RTT | **158.6 ms** | | Maximum RTT | **170.16 ms** | | Standard deviation | **3.77 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Taipei latency and RTT](/docs/network/latency/pairs/ber-tpe-rtt) — 156.8 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-ber-rtt). - **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. # Taipei, Taiwan → Frankfurt, Germany RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z sample, ICMP echo requests between Taipei, Taiwan and Frankfurt, Germany returned an average round-trip time of 166 ms. The minimum was 162.67 ms, the maximum was 174.81 ms, and none of the 50 packets were lost; with a standard deviation of 2.89 ms and jitter of 2.22 ms, the route was consistent over the measurement window. The geodesic distance for this city pair is 9,390.8 km, which puts the theoretical vacuum round-trip floor at 62.65 ms and the optical-fiber floor at 91.96 ms. The measured 166 ms average is 1.81 times that fiber floor; equivalently, the fiber floor accounts for 55.4% of the observed RTT. The delay is therefore well above the floor while remaining stable and loss-free. This route was 10th of the 19 outbound paths in its measured set, placing it around the median position rather than at either extreme. Its own variability, a 2.89 ms standard deviation against a 166 ms average, is about 1.7%, lower than the 3.28% median variability ratio for the same outbound set. The useful takeaway is that, in this sample, Frankfurt-bound latency from Taipei is moderate in absolute terms but notably stable. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **166 ms** | | Jitter | **2.22 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.96 ms** | | Fiber Efficiency | **55.4%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,390.8 km** | | Vacuum RTT floor | **62.65 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.96 ms** | | Low-latency fiber material floor | **91.59 ms** | | Engineering floor (5% path allowance) | **96.57 ms** | | Research 1.33× mapped-fiber reference | **122.31 ms** | | Estimated unamplified path loss | **1972.1 dB** | | Transparent optical spans / inline amplifiers | **124 / 123** | | Published RTT inflation over fiber floor | **1.81×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **162.67 ms** | | Average RTT | **166 ms** | | Maximum RTT | **174.81 ms** | | Standard deviation | **2.89 ms** | | Stdev / average | **1.7%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Taipei latency and RTT](/docs/network/latency/pairs/fra-tpe-rtt) — 163.8 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-fra-rtt). - **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. # Taipei, Taiwan → São Paulo, Brazil RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo requests from Taipei, Taiwan to São Paulo, Brazil averaged 273 ms, with a low of 261.55 ms and a high of 292.28 ms. The path carried all 50 samples, so packet loss was 0%, while jitter reached 8.08 ms and the standard deviation was 7.67 ms. The great-circle distance between the two cities is 18,818.5 km. A vacuum path would have a theoretical floor of 125.54 ms, and a straight-line fiber path a floor of 184.29 ms; the observed average is 1.48 times that fiber floor, or 67.5% of theoretical fiber efficiency. Among the 19 outbound routes measured from Taipei in this round, this path ranked 18th for RTT, with only one route slower and 17 routes faster. The typical variation from average across those outbound paths was around 3.28%, so the 273 ms average reflects a long-haul connection that is stable in loss but sits in the High latency tier. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **273 ms** | | Jitter | **8.08 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **184.29 ms** | | Fiber Efficiency | **67.5%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **18,818.5 km** | | Vacuum RTT floor | **125.54 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **184.29 ms** | | Low-latency fiber material floor | **183.54 ms** | | Engineering floor (5% path allowance) | **193.52 ms** | | Research 1.33× mapped-fiber reference | **245.1 ms** | | Estimated unamplified path loss | **3951.9 dB** | | Transparent optical spans / inline amplifiers | **247 / 246** | | Published RTT inflation over fiber floor | **1.48×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **261.55 ms** | | Average RTT | **273 ms** | | Maximum RTT | **292.28 ms** | | Standard deviation | **7.67 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Asia Pacific to South America](/docs/network/latency/regions/asia-pacific-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Taipei latency and RTT](/docs/network/latency/pairs/gru-tpe-rtt) — 259.1 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Asia Pacific → South America)** * [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.5 ms * [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 ms * [Sydney to São Paulo latency and RTT](/docs/network/latency/pairs/syd-gru-rtt) — 296.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-gru-rtt). - **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. # Taipei, Taiwan → Hong Kong RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. Over 50 ICMP probes in measurement round 2026-08-16T04:07:28Z, the Taipei-to-Hong Kong path averaged **15.5 ms**, with a minimum of **15.09 ms** and a maximum of **17.58 ms**. The **0.41 ms** standard deviation and **0.34 ms** jitter show a very tight latency envelope, and the **0%** packet loss means every probe received a reply. The route ranks first among the 19 outbound paths measured from Taipei in this round. That top position is supported by an average only **1.95 times** the theoretical fiber floor for the 810 km great-circle distance; the measured fiber efficiency is **51.2%**. The network-wide median variability across the same 19-route outbound set is **3.28%** relative to average latency. This route's standard deviation is about **2.6%** of its average, so it is not only fast but also steadier than the typical route in the set. For a short Asia-Pacific path like this one, the main takeaway is consistent ultra-low latency with zero loss. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **15.5 ms** | | Jitter | **0.34 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **7.94 ms** | | Fiber Efficiency | **51.2%** | | Latency Tier | Ultra-Low | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------ | | WGS-84 geodesic distance | **810.3 km** | | Vacuum RTT floor | **5.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **7.94 ms** | | Low-latency fiber material floor | **7.9 ms** | | Engineering floor (5% path allowance) | **8.33 ms** | | Research 1.33× mapped-fiber reference | **10.55 ms** | | Estimated unamplified path loss | **170.2 dB** | | Transparent optical spans / inline amplifiers | **11 / 10** | | Published RTT inflation over fiber floor | **1.95×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **15.09 ms** | | Average RTT | **15.5 ms** | | Maximum RTT | **17.58 ms** | | Standard deviation | **0.41 ms** | | Stdev / average | **2.6%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms **Fastest routes arriving at Hong Kong (HKG)** * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-hkg-rtt). - **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. # Taipei, Taiwan → Ashburn, USA RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from Taipei, Taiwan, to Ashburn, USA, returned an average RTT of 171.6 ms, with a minimum of 163.88 ms and a maximum of 199.15 ms. All 50 samples completed without packet loss, while jitter measured 4.89 ms and the standard deviation was 7 ms. At a direct distance of 12,639.6 km, the average is about 1.39 times the fiber floor of 123.78 ms, giving a fiber efficiency of 72.1%. This places the route in the fair latency tier and ranks it 12th among the 19 routes in the measurement set. The spread between the fastest and slowest replies reached 35.27 ms, and the route's standard-deviation-to-average ratio of about 4.1% is higher than the 3.28% median for the 19-route set. The zero loss is positive, but the wider-than-median variability is the most distinctive characteristic of this route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **171.6 ms** | | Jitter | **4.89 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **123.78 ms** | | Fiber Efficiency | **72.1%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,639.6 km** | | Vacuum RTT floor | **84.32 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **123.78 ms** | | Low-latency fiber material floor | **123.28 ms** | | Engineering floor (5% path allowance) | **129.98 ms** | | Research 1.33× mapped-fiber reference | **164.62 ms** | | Estimated unamplified path loss | **2654.3 dB** | | Transparent optical spans / inline amplifiers | **166 / 165** | | Published RTT inflation over fiber floor | **1.39×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **163.88 ms** | | Average RTT | **171.6 ms** | | Maximum RTT | **199.15 ms** | | Standard deviation | **7 ms** | | Stdev / average | **4.1%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Taipei latency and RTT](/docs/network/latency/pairs/iad-tpe-rtt) — 172.3 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-iad-rtt). - **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. # Taipei, Taiwan → Johannesburg, South Africa RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The Taipei–Johannesburg ICMP echo run from round 2026-08-16T04:07:28Z produced a 331 ms average RTT, with a minimum of 322.36 ms, a maximum of 356.12 ms, and 5.35 ms jitter across 50 samples. Packet loss was zero, and the measured latency tier was High. For this 19-route outbound round, Taipei–Johannesburg ranked 19th by average latency. Its standard deviation was 6.31 ms, just 1.91% of the mean, well below the 3.28% median variability across the measured outbound set—so the long path was consistent despite its High latency tier. With a geodesic distance of 11,525.4 km, the observed mean is 2.93 times the 112.87 ms fiber-floor estimate, a 34.1% fiber efficiency. As Johannesburg is this network's African anchor, the profile offers a useful long-haul benchmark for Southern Africa connectivity, while ICMP RTT alone should not be treated as an application performance predictor. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **331 ms** | | Jitter | **5.35 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **112.87 ms** | | Fiber Efficiency | **34.1%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,525.4 km** | | Vacuum RTT floor | **76.89 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **112.87 ms** | | Low-latency fiber material floor | **112.41 ms** | | Engineering floor (5% path allowance) | **118.52 ms** | | Research 1.33× mapped-fiber reference | **150.11 ms** | | Estimated unamplified path loss | **2420.3 dB** | | Transparent optical spans / inline amplifiers | **152 / 151** | | Published RTT inflation over fiber floor | **2.93×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **322.36 ms** | | Average RTT | **331 ms** | | Maximum RTT | **356.12 ms** | | Standard deviation | **6.31 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt) — 329.8 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Asia Pacific → Africa)** * [Singapore to Johannesburg latency and RTT](/docs/network/latency/pairs/sin-jnb-rtt) — 312.6 ms * [Hong Kong to Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt) — 316.7 ms * [Tokyo to Johannesburg latency and RTT](/docs/network/latency/pairs/tyo-jnb-rtt) — 359.2 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-jnb-rtt). - **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. # Taipei, Taiwan → Los Angeles, USA RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from Taipei, Taiwan, to Los Angeles, USA, averaged 132 ms, with replies ranging from 129.33 ms to 144.07 ms. The measurement completed with 0% packet loss, a jitter of 1.62 ms, and a standard deviation of 2.56 ms. At a direct distance of 10,926.8 km, the average sits about 1.23 times the fiber floor of 107 ms, yielding an 81.1% fiber efficiency. This places the route in the good latency tier and ranks it 5th among the 19 routes in the measurement set. The route's standard-deviation-to-average ratio is about 1.9%, well below the 3.28% median for the 19-route set, and the max-to-min gap is only 14.74 ms. Low jitter, zero loss, and stable round-trip times make this a notably consistent long-distance ICMP route. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **132 ms** | | Jitter | **1.62 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **107 ms** | | Fiber Efficiency | **81.1%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,926.8 km** | | Vacuum RTT floor | **72.9 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **107 ms** | | Low-latency fiber material floor | **106.57 ms** | | Engineering floor (5% path allowance) | **112.37 ms** | | Research 1.33× mapped-fiber reference | **142.32 ms** | | Estimated unamplified path loss | **2294.6 dB** | | Transparent optical spans / inline amplifiers | **144 / 143** | | Published RTT inflation over fiber floor | **1.23×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **129.33 ms** | | Average RTT | **132 ms** | | Maximum RTT | **144.07 ms** | | Standard deviation | **2.56 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-lax-rtt). - **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. # Taipei, Taiwan → London, UK RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Taipei to London completed with an average RTT of 173 ms, a minimum of 165.18 ms, and a maximum of 197.84 ms. The path carried no packet loss, while its 6.02 ms standard deviation and 4.56 ms jitter suggest the latency remained fairly consistent throughout the sample. At 173 ms, the measured RTT is about 1.8 times the 95.97 ms fiber floor calculated from the 9,799.7 km great-circle distance, placing the route's fiber efficiency at roughly 55.5%. That gap is expected for an intercontinental journey, and the instability is modest rather than dramatic. Within the network's broader route set, this Taipei-to-London path ranks 13th among the 19 routes compared by typical latency. Its variability as a share of average latency is close to the network's 3.28% median coefficient of variation for such measurements, so operators can read this as a mid-ranking but steady connection for the measured ICMP traffic. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **173 ms** | | Jitter | **4.56 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.97 ms** | | Fiber Efficiency | **55.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,799.7 km** | | Vacuum RTT floor | **65.38 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.97 ms** | | Low-latency fiber material floor | **95.58 ms** | | Engineering floor (5% path allowance) | **100.78 ms** | | Research 1.33× mapped-fiber reference | **127.63 ms** | | Estimated unamplified path loss | **2057.9 dB** | | Transparent optical spans / inline amplifiers | **129 / 128** | | Published RTT inflation over fiber floor | **1.8×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **165.18 ms** | | Average RTT | **173 ms** | | Maximum RTT | **197.84 ms** | | Standard deviation | **6.02 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Taipei latency and RTT](/docs/network/latency/pairs/lon-tpe-rtt) — 173.8 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-lon-rtt). - **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. # Taipei, Taiwan → Melbourne, Australia RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. Measurement round 2026-08-16T04:07:28Z recorded 50 ICMP replies from Taipei to Melbourne with **0% packet loss**. The average RTT was **142 ms**, the minimum **135.86 ms**, and the maximum **164.91 ms**, giving a **6.17 ms** standard deviation and **5.1 ms** jitter. On the 7,377.8 km great-circle distance, the average sits about **1.97 times** the theoretical fiber floor of **72.25 ms**, corresponding to **50.9%** fiber efficiency. This places the route eighth among the 19 outbound paths measured from the same source in this round. The network-wide median variability for the 19-route set is **3.28%** of average latency; Melbourne's standard deviation is **4.3%** of its average, so the path is more variable than the set's median route. The main route-specific insight is that lossless doesn't mean perfectly steady: latency moved across a **29 ms** range even though no probes were lost. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **142 ms** | | Jitter | **5.1 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.25 ms** | | Fiber Efficiency | **50.9%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,377.8 km** | | Vacuum RTT floor | **49.22 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.25 ms** | | Low-latency fiber material floor | **71.96 ms** | | Engineering floor (5% path allowance) | **75.87 ms** | | Research 1.33× mapped-fiber reference | **96.09 ms** | | Estimated unamplified path loss | **1549.3 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.97×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **135.86 ms** | | Average RTT | **142 ms** | | Maximum RTT | **164.91 ms** | | Standard deviation | **6.17 ms** | | Stdev / average | **4.3%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Los Angeles to Melbourne latency and RTT](/docs/network/latency/pairs/lax-mel-rtt) — 148.2 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-mel-rtt). - **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. # Taipei, Taiwan → Miami, USA RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from Taipei, Taiwan, to Miami, USA, produced an average RTT of 185.7 ms, with a minimum of 175.97 ms and a maximum of 211.22 ms. No samples were lost, but jitter reached 7.6 ms and the standard deviation was 9.15 ms. At a direct distance of 13,918.7 km, the average is about 1.36 times the fiber floor of 136.3 ms, corresponding to a 73.4% fiber efficiency and a fair latency tier rating. The route ranks 17th among the 19 routes in the measurement set. On this route, the standard-deviation-to-average ratio is roughly 4.9%, above the 3.28% median for the 19-route set. The spread from the fastest to slowest reply was 35.25 ms, so while loss was zero, round-trip times fluctuated noticeably. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **185.7 ms** | | Jitter | **7.6 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **136.3 ms** | | Fiber Efficiency | **73.4%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,918.7 km** | | Vacuum RTT floor | **92.86 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **136.3 ms** | | Low-latency fiber material floor | **135.76 ms** | | Engineering floor (5% path allowance) | **143.14 ms** | | Research 1.33× mapped-fiber reference | **181.28 ms** | | Estimated unamplified path loss | **2922.9 dB** | | Transparent optical spans / inline amplifiers | **183 / 182** | | Published RTT inflation over fiber floor | **1.36×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **175.97 ms** | | Average RTT | **185.7 ms** | | Maximum RTT | **211.22 ms** | | Standard deviation | **9.15 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Taipei latency and RTT](/docs/network/latency/pairs/mia-tpe-rtt) — 185.1 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-mia-rtt). - **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. # Taipei, Taiwan → Moscow, Russia RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z test round, ICMP echo requests from Taipei, Taiwan to Moscow, Russia averaged 132.7 ms across 50 samples, with a minimum of 127.77 ms and a maximum of 145.28 ms. The route recorded zero packet loss and 3.84 ms jitter, consistent with its good latency tier. The geodesic distance of about 7,369 km implies a vacuum floor of 49.16 ms and a fiber floor of 72.16 ms; the measured path runs about 1.84 times the fiber floor, or 54.4 percent fiber efficiency. Given Moscow's role as a transit corridor between European and Asia-Pacific networks, the sub-135 ms average with zero packet loss is a notable result. Within the same 19-route outbound set, this route ranks 6th, placing it near the faster end. Its 3.91 ms standard deviation corresponds to a relative spread of about 2.9 percent, below the median variability ratio of 3.28 percent across the same set. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **132.7 ms** | | Jitter | **3.84 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **72.16 ms** | | Fiber Efficiency | **54.4%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **7,369 km** | | Vacuum RTT floor | **49.16 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **72.16 ms** | | Low-latency fiber material floor | **71.87 ms** | | Engineering floor (5% path allowance) | **75.78 ms** | | Research 1.33× mapped-fiber reference | **95.98 ms** | | Estimated unamplified path loss | **1547.5 dB** | | Transparent optical spans / inline amplifiers | **97 / 96** | | Published RTT inflation over fiber floor | **1.84×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **127.77 ms** | | Average RTT | **132.7 ms** | | Maximum RTT | **145.28 ms** | | Standard deviation | **3.91 ms** | | Stdev / average | **2.9%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms * [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-rtt) — 145.1 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-mow-rtt). - **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. # Taipei, Taiwan → Marseille, France RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z test round, ICMP echo requests from Taipei, Taiwan to Marseille, France averaged 179.5 ms across 50 samples, with a minimum of 175.71 ms and a maximum of 189.07 ms. Packet loss was 0 percent and jitter was 2.52 ms, placing the route in the fair latency tier. Marseille's role as a Mediterranean cable landing hub makes the Asia-to-France distance physically long: the geodesic distance is about 10,027 km, implying a vacuum floor of 66.9 ms and a fiber floor of 98.2 ms. The observed path runs about 1.83 times the fiber floor, or 54.7 percent fiber efficiency. Against the 19 outbound routes in the same test set, this route ranks 16th, putting it on the slower side of the round. Its 3.41 ms standard deviation works out to a relative spread of about 1.9 percent, below the median variability ratio of 3.28 percent across the same set, so the path is stable even though its average latency is fair. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **179.5 ms** | | Jitter | **2.52 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **98.2 ms** | | Fiber Efficiency | **54.7%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,027.3 km** | | Vacuum RTT floor | **66.9 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **98.2 ms** | | Low-latency fiber material floor | **97.8 ms** | | Engineering floor (5% path allowance) | **103.12 ms** | | Research 1.33× mapped-fiber reference | **130.6 ms** | | Estimated unamplified path loss | **2105.7 dB** | | Transparent optical spans / inline amplifiers | **132 / 131** | | Published RTT inflation over fiber floor | **1.83×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **175.71 ms** | | Average RTT | **179.5 ms** | | Maximum RTT | **189.07 ms** | | Standard deviation | **3.41 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Taipei latency and RTT](/docs/network/latency/pairs/mrs-tpe-rtt) — 180.9 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-mrs-rtt). - **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. # Taipei, Taiwan → New York, USA RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo requests from Taipei, Taiwan to New York, USA returned an average round-trip time of 174.2 ms, with a minimum of 165.46 ms and a maximum of 214.55 ms. None of the 50 samples were lost, and the jitter figure of 6.73 ms points to a reasonably steady path over a 12,549 km great-circle distance. At that distance, a theoretical vacuum path would take 83.72 ms and a straight-line fiber path would take 122.89 ms. The measured average runs 1.42 times the fiber floor, or about 70.5% of theoretical fiber efficiency, putting the measured average 51.3 ms above the straight-line fiber minimum. Compared with the 19 outbound routes measured from Taipei in this round, this path ranked 15th for RTT, meaning 14 routes were faster and 4 were slower. The typical variation from average across those outbound paths was about 3.28%, which helps frame the measured standard deviation of 8.46 ms. With 0% packet loss and 6.73 ms jitter, the route is stable despite an average that lands in the Fair latency tier. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **174.2 ms** | | Jitter | **6.73 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **122.89 ms** | | Fiber Efficiency | **70.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,549.1 km** | | Vacuum RTT floor | **83.72 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **122.89 ms** | | Low-latency fiber material floor | **122.4 ms** | | Engineering floor (5% path allowance) | **129.05 ms** | | Research 1.33× mapped-fiber reference | **163.44 ms** | | Estimated unamplified path loss | **2635.3 dB** | | Transparent optical spans / inline amplifiers | **165 / 164** | | Published RTT inflation over fiber floor | **1.42×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **165.46 ms** | | Average RTT | **174.2 ms** | | Maximum RTT | **214.55 ms** | | Standard deviation | **8.46 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Taipei latency and RTT](/docs/network/latency/pairs/nyc-tpe-rtt) — 173.4 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-nyc-rtt). - **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. # Taipei, Taiwan → Paris, France RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z test round, ICMP echo requests from Taipei, Taiwan to Paris, France averaged 173.8 ms over 50 samples, with a minimum of 169.08 ms and a maximum of 187.89 ms. Zero packet loss and 3.31 ms jitter accompanied the fair latency tier. Paris sits on the Northwest European corridor with dense national and pan-European fiber paths. The geodesic distance of about 9,846 km yields a vacuum floor of 65.69 ms and a fiber floor of 96.42 ms; the measured path runs about 1.8 times that fiber floor, or 55.5 percent fiber efficiency. Against the 19 outbound routes in the same test set, this route ranks 14th, toward the slower side of the round. Its 3.91 ms standard deviation equals a relative spread of about 2.3 percent, below the median variability ratio of 3.28 percent across the same set, meaning the route is predictable even if its average latency is fair. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **173.8 ms** | | Jitter | **3.31 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **96.42 ms** | | Fiber Efficiency | **55.5%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,846.2 km** | | Vacuum RTT floor | **65.69 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **96.42 ms** | | Low-latency fiber material floor | **96.03 ms** | | Engineering floor (5% path allowance) | **101.26 ms** | | Research 1.33× mapped-fiber reference | **128.24 ms** | | Estimated unamplified path loss | **2067.7 dB** | | Transparent optical spans / inline amplifiers | **130 / 129** | | Published RTT inflation over fiber floor | **1.8×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **169.08 ms** | | Average RTT | **173.8 ms** | | Maximum RTT | **187.89 ms** | | Standard deviation | **3.91 ms** | | Stdev / average | **2.2%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Taipei latency and RTT](/docs/network/latency/pairs/par-tpe-rtt) — 171.9 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-par-rtt). - **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. # Taipei, Taiwan → Seattle, USA RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, the Taipei-to-Seattle path averaged 115.8 ms, with a tight range from 111.75 ms to 128.63 ms and a standard deviation of 4.07 ms. All 50 ICMP echo samples were returned, so packet loss was 0%, and jitter stayed low at 2.57 ms. Seattle is about 9,748 km from Taipei by great-circle distance. A vacuum path would have a theoretical floor of 65.03 ms and a straight-line fiber path a floor of 95.46 ms; the measured average is 1.21 times that fiber floor, equating to 82.4% of theoretical fiber efficiency. Within the collection of 19 outbound routes measured from Taipei in this round, this path ranked 4th for RTT, with only 3 routes achieving faster times and 15 registering slower ones. The typical variation from average across those outbound paths was about 3.28%, and this path's 4.07 ms spread is roughly in line with that stable profile. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **115.8 ms** | | Jitter | **2.57 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.46 ms** | | Fiber Efficiency | **82.4%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,748.1 km** | | Vacuum RTT floor | **65.03 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.46 ms** | | Low-latency fiber material floor | **95.08 ms** | | Engineering floor (5% path allowance) | **100.25 ms** | | Research 1.33× mapped-fiber reference | **126.96 ms** | | Estimated unamplified path loss | **2047.1 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **1.21×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **111.75 ms** | | Average RTT | **115.8 ms** | | Maximum RTT | **128.63 ms** | | Standard deviation | **4.07 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms **Same corridor (Asia Pacific → North America)** * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-sea-rtt). - **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. # Taipei, Taiwan → Singapore RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. For round 2026-08-16T04:07:28Z, the Taipei-to-Singapore path returned an average of **44.3 ms** across 50 ICMP probes, with a minimum of **42.61 ms** and a maximum of **50.6 ms**. Packet loss was **0%**, with **1.64 ms** standard deviation and **1.36 ms** jitter. Over the 3,243.9 km great-circle distance, the observed average is only **1.39 times** the theoretical fiber floor of **31.77 ms**, yielding **71.7%** fiber efficiency. Within the 19 outbound routes from this source, the route ranks third. The network-wide median standard-deviation-to-average ratio is **3.28%**, while this route's ratio is about **3.7%**, so consistency is close to the set's typical level despite the strong overall ranking. The standout feature is how close the measured RTT comes to the physical distance floor for an excellent-tier Asia-Pacific route. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **44.3 ms** | | Jitter | **1.36 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **31.77 ms** | | Fiber Efficiency | **71.7%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **3,243.9 km** | | Vacuum RTT floor | **21.64 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **31.77 ms** | | Low-latency fiber material floor | **31.64 ms** | | Engineering floor (5% path allowance) | **33.36 ms** | | Research 1.33× mapped-fiber reference | **42.25 ms** | | Estimated unamplified path loss | **681.2 dB** | | Transparent optical spans / inline amplifiers | **43 / 42** | | Published RTT inflation over fiber floor | **1.39×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **42.61 ms** | | Average RTT | **44.3 ms** | | Maximum RTT | **50.6 ms** | | Standard deviation | **1.64 ms** | | Stdev / average | **3.7%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-sin-rtt). - **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. # Taipei, Taiwan → Sydney, Australia RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. The Taipei–Sydney ICMP echo run from round 2026-08-16T04:07:28Z produced a 133.2 ms average RTT over 50 samples, with a minimum of 129.47 ms, a maximum of 143.28 ms, and 2.55 ms jitter. Zero packets were lost, and the measured latency tier was Good. Across the 19 outbound routes in this round, the Sydney path ranked 7th by average latency. Its standard deviation of 3.02 ms was 2.27% of the mean, below the 3.28% median variability across the measured outbound set, so this is a steady route rather than a spike-prone one. The great-circle distance is 7,237.6 km, and the observed mean sits 1.88 times the 70.88 ms fiber-floor estimate—a 53.2% fiber efficiency. Sydney is Australia's primary internet gateway, so this round-trip profile is a useful baseline for Asia-to-Australia latency expectations, though ICMP RTT should not be read as a predictor of application performance. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **133.2 ms** | | Jitter | **2.55 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **70.88 ms** | | Fiber Efficiency | **53.2%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,237.6 km** | | Vacuum RTT floor | **48.28 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **70.88 ms** | | Low-latency fiber material floor | **70.59 ms** | | Engineering floor (5% path allowance) | **74.43 ms** | | Research 1.33× mapped-fiber reference | **94.26 ms** | | Estimated unamplified path loss | **1519.9 dB** | | Transparent optical spans / inline amplifiers | **95 / 94** | | Published RTT inflation over fiber floor | **1.88×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **129.47 ms** | | Average RTT | **133.2 ms** | | Maximum RTT | **143.28 ms** | | Standard deviation | **3.02 ms** | | Stdev / average | **2.3%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-syd-rtt). - **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. # Taipei, Taiwan → Tokyo, Japan RTT 🇹🇼 **Taipei, Taiwan (TPE)** → 🇯🇵 **Tokyo, Japan (TYO)** Measurement round: `2026-08-16T04:07:28Z`. The Taipei–Tokyo ICMP echo run from round 2026-08-16T04:07:28Z returned a 31.9 ms average RTT, with a minimum of 30.57 ms, a maximum of 35.67 ms, and 1.06 ms jitter over 50 samples. No packets were lost, and the measured latency tier was Excellent. Across the 19 outbound routes in this round, Taipei–Tokyo ranked second by average latency. The route's standard deviation was 1.12 ms, or 3.51% of the mean, slightly above the 3.28% median variability for the measured outbound set; it is very fast, with a bit more packet-level spread than its speed rank might suggest. At 2,101.2 km, the observed mean is 1.55 times the 20.58 ms fiber-floor estimate, giving a 64.5% fiber efficiency. The result aligns with Tokyo's role as East Asia's premier exchange hub and makes this short intra-Asia hop one of the strongest round-trip profiles in the round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **31.9 ms** | | Jitter | **1.06 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **20.58 ms** | | Fiber Efficiency | **64.5%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,101.2 km** | | Vacuum RTT floor | **14.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **20.58 ms** | | Low-latency fiber material floor | **20.49 ms** | | Engineering floor (5% path allowance) | **21.61 ms** | | Research 1.33× mapped-fiber reference | **27.37 ms** | | Estimated unamplified path loss | **441.3 dB** | | Transparent optical spans / inline amplifiers | **28 / 27** | | Published RTT inflation over fiber floor | **1.55×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **30.57 ms** | | Average RTT | **31.9 ms** | | Maximum RTT | **35.67 ms** | | Standard deviation | **1.12 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms **Fastest routes arriving at Tokyo (TYO)** * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Tokyo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tpe-tyo-rtt). - **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. # Tokyo, Japan → Amsterdam, Netherlands RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇳🇱 **Amsterdam, Netherlands (AMS)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo requests between Tokyo and Amsterdam returned an average RTT of 197.4 ms, with a minimum of 190.34 ms and a maximum of 220.5 ms; all 50 probes completed without loss. The moderate latency rating reflects a route whose real-world delay is about 2.16 times the theoretical fiber-path lower bound for the 9,311.4 km separation. Within the 19-route outbound set, this pair ranks 14th. Its variability, at roughly 3.4% of the average, sits just above the 3.28% median variability observed across that outbound set, so the extra delay is accompanied by slightly wider-than-typical RTT fluctuation. The 30.16 ms spread between fastest and slowest probes, alongside 5.76 ms jitter and zero packet loss, shows the route's delay varied across the sample window without dropping any replies. Despite the moderate average, Tokyo-Amsterdam delivered consistent reachability during this measurement round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **197.4 ms** | | Jitter | **5.76 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.18 ms** | | Fiber Efficiency | **46.2%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,311.4 km** | | Vacuum RTT floor | **62.12 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.18 ms** | | Low-latency fiber material floor | **90.82 ms** | | Engineering floor (5% path allowance) | **95.76 ms** | | Research 1.33× mapped-fiber reference | **121.28 ms** | | Estimated unamplified path loss | **1955.4 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **2.16×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **190.34 ms** | | Average RTT | **197.4 ms** | | Maximum RTT | **220.5 ms** | | Standard deviation | **6.74 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Amsterdam to Tokyo latency and RTT](/docs/network/latency/pairs/ams-tyo-rtt) — 198.2 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Amsterdam (AMS)** * [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms * [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms * [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms * [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms * [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Amsterdam round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-ams-rtt). - **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. # Tokyo, Japan → Berlin, Germany RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇩🇪 **Berlin, Germany (BER)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo RTT between Tokyo and Berlin in the 2026-08-16T04:07:28Z round averaged 186.1 ms, with a minimum of 174.48 ms and a maximum of 227.17 ms. The measurement carried no packet loss across 50 probes, and the moderate latency rating reflects an average that is 2.13 times the approximate fiber-path lower bound for the 8,937.7 km between the two cities. Within the 19-route outbound set, this pair ranks 12th. Its RTT variability equals about 4.9% of the average, noticeably above the 3.28% median variability for the outbound set, meaning this crossing is less stable in relative terms than its average latency alone suggests. The 52.69 ms difference between fastest and slowest replies, plus jitter of 7.88 ms, shows the path's delay profile shifted significantly during the sample window even though no probes were lost. Berlin's position as a bridge on the east-west European corridor makes it an important arrival point, and the Tokyo-to-Berlin leg should be treated as more variable than its 186.1 ms average implies. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **186.1 ms** | | Jitter | **7.88 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **87.53 ms** | | Fiber Efficiency | **47%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,937.7 km** | | Vacuum RTT floor | **59.63 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **87.53 ms** | | Low-latency fiber material floor | **87.17 ms** | | Engineering floor (5% path allowance) | **91.91 ms** | | Research 1.33× mapped-fiber reference | **116.41 ms** | | Estimated unamplified path loss | **1876.9 dB** | | Transparent optical spans / inline amplifiers | **118 / 117** | | Published RTT inflation over fiber floor | **2.13×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **174.48 ms** | | Average RTT | **186.1 ms** | | Maximum RTT | **227.17 ms** | | Standard deviation | **9.12 ms** | | Stdev / average | **4.9%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Berlin to Tokyo latency and RTT](/docs/network/latency/pairs/ber-tyo-rtt) — 187.5 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Berlin (BER)** * [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms * [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms * [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms * [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms * [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Berlin round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-ber-rtt). - **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. # Tokyo, Japan → Frankfurt, Germany RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇩🇪 **Frankfurt, Germany (FRA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, Tokyo-to-Frankfurt ICMP echo RTT averaged 193.2 ms, with replies between 189.92 ms and 203.54 ms and no packet loss across all 50 probes. The moderate latency rating is consistent with an observed delay about 2.11 times the fiber-path lower bound for the 9,354.4 km route. Within the 19-route outbound set, this connection is 13th by average latency. However, its RTT variability is only about 1.7% of the average, well below the 3.28% median variability seen across the outbound routes, so the route is notably steady for its latency tier. The entire sample fit within a 13.62 ms range, and jitter was just 2.63 ms, indicating very consistent forwarding behavior during the window. For traffic landing in Frankfurt, a central switching point on the European fiber ring, this Tokyo route offers a reliable delay profile even though the absolute RTT remains in moderate territory. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **193.2 ms** | | Jitter | **2.63 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **91.61 ms** | | Fiber Efficiency | **47.4%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,354.4 km** | | Vacuum RTT floor | **62.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **91.61 ms** | | Low-latency fiber material floor | **91.24 ms** | | Engineering floor (5% path allowance) | **96.2 ms** | | Research 1.33× mapped-fiber reference | **121.84 ms** | | Estimated unamplified path loss | **1964.4 dB** | | Transparent optical spans / inline amplifiers | **123 / 122** | | Published RTT inflation over fiber floor | **2.11×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **189.92 ms** | | Average RTT | **193.2 ms** | | Maximum RTT | **203.54 ms** | | Standard deviation | **3.37 ms** | | Stdev / average | **1.7%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Frankfurt to Tokyo latency and RTT](/docs/network/latency/pairs/fra-tyo-rtt) — 194.5 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Frankfurt (FRA)** * [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms * [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms * [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms * [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms * [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-fra-rtt). - **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. # Tokyo, Japan → São Paulo, Brazil RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇧🇷 **São Paulo, Brazil (GRU)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the Tokyo-to-São Paulo path averaged 230.5 ms across 50 ICMP probes, with a minimum of 223.65 ms and a maximum of 246.27 ms. No probes were lost, and the 5.46 ms standard deviation came with 4.64 ms jitter. The great-circle distance of 18,530.2 km puts the vacuum RTT floor at 123.62 ms and the theoretical fiber RTT floor at 181.46 ms. At 230.5 ms, the route runs 1.27 times the fiber floor, or about 78.7 percent of fiber-floor efficiency. In this round's 19-route outbound set, the pair ranked 18th, so its absolute latency is among the highest, yet its standard deviation is only about 2.4 percent of the average, below the 3.28 percent median relative variability for the set. The route's latency tier is Fair, but the low relative variability means the 230.5 ms average is a representative summary of the measurement window. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **230.5 ms** | | Jitter | **4.64 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **181.46 ms** | | Fiber Efficiency | **78.7%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [South America](/docs/network/latency/regions/south-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **18,530.2 km** | | Vacuum RTT floor | **123.62 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **181.46 ms** | | Low-latency fiber material floor | **180.73 ms** | | Engineering floor (5% path allowance) | **190.56 ms** | | Research 1.33× mapped-fiber reference | **241.34 ms** | | Estimated unamplified path loss | **3891.3 dB** | | Transparent optical spans / inline amplifiers | **244 / 243** | | Published RTT inflation over fiber floor | **1.27×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **223.65 ms** | | Average RTT | **230.5 ms** | | Maximum RTT | **246.27 ms** | | Standard deviation | **5.46 ms** | | Stdev / average | **2.4%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [South America](/docs/network/latency/regions/south-america) * Corridor overview: [Asia Pacific to South America](/docs/network/latency/regions/asia-pacific-to-south-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [São Paulo to Tokyo latency and RTT](/docs/network/latency/pairs/gru-tyo-rtt) — 230.3 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at São Paulo (GRU)** * [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms * [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms * [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms * [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms * [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms **Same corridor (Asia Pacific → South America)** * [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 ms * [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 ms * [Sydney to São Paulo latency and RTT](/docs/network/latency/pairs/syd-gru-rtt) — 296.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-gru-rtt). - **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. # Tokyo, Japan → Hong Kong RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇭🇰 **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the Tokyo-to-Hong Kong path averaged 44.8 ms over 50 ICMP probes, with a minimum of 43.35 ms and a maximum of 48.43 ms. All probes returned replies, and jitter was just 0.97 ms, with a 1.13 ms standard deviation. The great-circle distance is 2,883.5 km, giving a vacuum RTT floor of 19.24 ms and a theoretical fiber RTT floor of 28.24 ms. The measured average is 1.59 times that fiber floor, so the fiber-efficiency figure is 63 percent; excellent latency does not necessarily mean the path is close to the straight-line fiber minimum. Within this round's 19-route outbound set, this pair ranked 2nd, placing it among the fastest routes measured. Its standard deviation is about 2.5 percent of the average, below the 3.28 percent median relative variability for the set, and the 0% loss and sub-millisecond jitter reinforce an Excellent latency tier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **44.8 ms** | | Jitter | **0.97 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **28.24 ms** | | Fiber Efficiency | **63%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,883.5 km** | | Vacuum RTT floor | **19.24 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **28.24 ms** | | Low-latency fiber material floor | **28.12 ms** | | Engineering floor (5% path allowance) | **29.65 ms** | | Research 1.33× mapped-fiber reference | **37.56 ms** | | Estimated unamplified path loss | **605.5 dB** | | Transparent optical spans / inline amplifiers | **38 / 37** | | Published RTT inflation over fiber floor | **1.59×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **43.35 ms** | | Average RTT | **44.8 ms** | | Maximum RTT | **48.43 ms** | | Standard deviation | **1.13 ms** | | Stdev / average | **2.5%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms **Fastest routes arriving at Hong Kong (HKG)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms * [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms * [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms * [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms * [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-hkg-rtt). - **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. # Tokyo, Japan → Ashburn, USA RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇺🇸 **Ashburn, USA (IAD)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z run, ICMP echo RTT between Tokyo, Japan and Ashburn, USA averaged 142.9 ms, with observed samples from 137.64 ms to 155.57 ms. All 50 probes returned successfully, so packet loss was 0%, and jitter was 3.66 ms. The geodesic separation is 10,894.6 km, giving a theoretical fiber floor of 106.69 ms. At 142.9 ms, the measured average sits 1.34 times above that floor, with a fiber efficiency of 74.7% — a relatively tight fit between real-world round-trip time and the optical-path minimum. Across the 19-route outbound set, this path is 8th by average RTT. Its variation around the average is roughly 3.4%, slightly above the 3.28% median for the outbound route set, but the min-max spread is only 17.93 ms and the measured latency tier is Good. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **142.9 ms** | | Jitter | **3.66 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.69 ms** | | Fiber Efficiency | **74.7%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,894.6 km** | | Vacuum RTT floor | **72.68 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.69 ms** | | Low-latency fiber material floor | **106.26 ms** | | Engineering floor (5% path allowance) | **112.04 ms** | | Research 1.33× mapped-fiber reference | **141.9 ms** | | Estimated unamplified path loss | **2287.9 dB** | | Transparent optical spans / inline amplifiers | **143 / 142** | | Published RTT inflation over fiber floor | **1.34×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **137.64 ms** | | Average RTT | **142.9 ms** | | Maximum RTT | **155.57 ms** | | Standard deviation | **4.84 ms** | | Stdev / average | **3.4%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Ashburn to Tokyo latency and RTT](/docs/network/latency/pairs/iad-tyo-rtt) — 141.9 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Ashburn (IAD)** * [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms * [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms * [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms * [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms * [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms **Same corridor (Asia Pacific → North America)** * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Ashburn round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-iad-rtt). - **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. # Tokyo, Japan → Johannesburg, South Africa RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇿🇦 **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. The Tokyo–Johannesburg ICMP echo path averaged 359.2 ms over 50 samples taken 100 ms apart, with a minimum of 339.59 ms and a maximum of 411.36 ms. Zero packets were lost, but the 15.79 ms standard deviation and 13 ms jitter show a wide spread for a route classed in the high-latency tier. In the 2026-08-16T04:07:28Z round, this route sits at position 19 among the 19 outbound routes measured, and its standard deviation is about 4.40% of the average RTT, above the 3.28% median ratio for that same outbound set. Distance is central: the 13,537.7 km great-circle span has a line-of-sight floor of 90.31 ms and a fiber-floor reference of 132.57 ms. The measured average is 2.71 times the fiber-floor reference, so the path operates at roughly 36.9% fiber efficiency. That low efficiency, combined with a high-latency tier and notable jitter, makes consistent round-trip timing the main weakness even though loss stayed at 0%. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **359.2 ms** | | Jitter | **13 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **132.57 ms** | | Fiber Efficiency | **36.9%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **13,537.7 km** | | Vacuum RTT floor | **90.31 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **132.57 ms** | | Low-latency fiber material floor | **132.04 ms** | | Engineering floor (5% path allowance) | **139.22 ms** | | Research 1.33× mapped-fiber reference | **176.32 ms** | | Estimated unamplified path loss | **2842.9 dB** | | Transparent optical spans / inline amplifiers | **178 / 177** | | Published RTT inflation over fiber floor | **2.71×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **339.59 ms** | | Average RTT | **359.2 ms** | | Maximum RTT | **411.36 ms** | | Standard deviation | **15.79 ms** | | Stdev / average | **4.4%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Africa](/docs/network/latency/regions/africa) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Johannesburg to Tokyo latency and RTT](/docs/network/latency/pairs/jnb-tyo-rtt) — 360.5 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt) — 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt) — 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt) — 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt) — 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt) — 188.4 ms **Same corridor (Asia Pacific → Africa)** * [Singapore to Johannesburg latency and RTT](/docs/network/latency/pairs/sin-jnb-rtt) — 312.6 ms * [Hong Kong to Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt) — 316.7 ms * [Taipei to Johannesburg latency and RTT](/docs/network/latency/pairs/tpe-jnb-rtt) — 331 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-jnb.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-jnb-rtt). - **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. # Tokyo, Japan → Los Angeles, USA RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇺🇸 **Los Angeles, USA (LAX)** Measurement round: `2026-08-16T04:07:28Z`. The 2026-08-16T04:07:28Z measurement captured ICMP echo RTT from Tokyo, Japan to Los Angeles, USA at an average of 101.2 ms, with a minimum of 98.89 ms and a maximum of 105.47 ms. The 50-sample run had 0% packet loss and jitter of only 1.87 ms. The geodesic distance of 8,834.5 km puts the theoretical fiber floor at 86.51 ms. The measured average is 1.17 times that floor, and the fiber efficiency of 85.5% means the observed round trip stays close to the distance-based minimum. This path ranks 5th by average RTT among the 19 outbound routes in the set. It also shows low variability around the mean at about 1.6%, well under the 3.28% median seen across the outbound route set, with a min-max range of only 6.58 ms and a Good latency tier. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **101.2 ms** | | Jitter | **1.87 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **86.51 ms** | | Fiber Efficiency | **85.5%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,834.5 km** | | Vacuum RTT floor | **58.94 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **86.51 ms** | | Low-latency fiber material floor | **86.17 ms** | | Engineering floor (5% path allowance) | **90.85 ms** | | Research 1.33× mapped-fiber reference | **115.06 ms** | | Estimated unamplified path loss | **1855.3 dB** | | Transparent optical spans / inline amplifiers | **116 / 115** | | Published RTT inflation over fiber floor | **1.17×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **98.89 ms** | | Average RTT | **101.2 ms** | | Maximum RTT | **105.47 ms** | | Standard deviation | **1.62 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms **Fastest routes arriving at Los Angeles (LAX)** * [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms * [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms * [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms * [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms * [London to Los Angeles latency and RTT](/docs/network/latency/pairs/lon-lax-rtt) — 127.5 ms **Same corridor (Asia Pacific → North America)** * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-lax-rtt). - **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. # Tokyo, Japan → London, UK RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇬🇧 **London, UK (LON)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Tokyo to London returned an average round-trip time of 202.7 ms across 50 samples, with a minimum of 196.6 ms and a maximum of 224.34 ms. No packets were lost, and jitter was 4.9 ms. The great-circle distance between Tokyo and London is about 9,582 km. If light could travel that distance in a vacuum, the floor would be 63.93 ms; a direct fiber path would be roughly 93.84 ms. The observed average is 2.16 times that fiber floor, so this route is operating at about 46.3% of the direct-fiber ideal. This path ranked 15th among the 19 outbound routes from its starting point, placing it in the slower half of that set. Its own variation-to-average ratio was about 2.8%, below the 3.28% midpoint across the set, and the standard deviation of 5.6 ms shows stable round-trip times despite the Fair latency tier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **202.7 ms** | | Jitter | **4.9 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **93.84 ms** | | Fiber Efficiency | **46.3%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,582.1 km** | | Vacuum RTT floor | **63.93 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **93.84 ms** | | Low-latency fiber material floor | **93.46 ms** | | Engineering floor (5% path allowance) | **98.54 ms** | | Research 1.33× mapped-fiber reference | **124.8 ms** | | Estimated unamplified path loss | **2012.2 dB** | | Transparent optical spans / inline amplifiers | **126 / 125** | | Published RTT inflation over fiber floor | **2.16×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **196.6 ms** | | Average RTT | **202.7 ms** | | Maximum RTT | **224.34 ms** | | Standard deviation | **5.6 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [London (LON)](/docs/network/latency/lon-london) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [London to Tokyo latency and RTT](/docs/network/latency/pairs/lon-tyo-rtt) — 202.9 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at London (LON)** * [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms * [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms * [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms * [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms * [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → London round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-lon-rtt). - **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. # Tokyo, Japan → Melbourne, Australia RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇦🇺 **Melbourne, Australia (MEL)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z measurement round, the Tokyo-to-Melbourne path averaged 113.9 ms across 50 ICMP probes, with a minimum of 107.58 ms and a maximum of 128.46 ms. The 4.6 ms standard deviation and 4.76 ms jitter indicate a modest spread around that average, while 0% packet loss meant every probe reached its destination. The great-circle distance of 8,156.1 km yields a vacuum RTT floor of 54.41 ms and a theoretical fiber RTT floor of 79.87 ms. The observed average is 1.43 times the fiber floor, placing fiber efficiency at 70.1 percent; the minimum sample of 107.58 ms stays about 27.7 ms above that floor. In this round's 19-route outbound set, this pair ranked 7th, putting its absolute latency in the upper-middle range. However, its standard deviation is about 4.0 percent of the average, above the 3.28 percent median relative variability for the set, so the Good latency tier comes with more sample-to-sample variation than typical for the round. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **113.9 ms** | | Jitter | **4.76 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **79.87 ms** | | Fiber Efficiency | **70.1%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **8,156.1 km** | | Vacuum RTT floor | **54.41 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **79.87 ms** | | Low-latency fiber material floor | **79.55 ms** | | Engineering floor (5% path allowance) | **83.88 ms** | | Research 1.33× mapped-fiber reference | **106.23 ms** | | Estimated unamplified path loss | **1712.8 dB** | | Transparent optical spans / inline amplifiers | **108 / 107** | | Published RTT inflation over fiber floor | **1.43×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **107.58 ms** | | Average RTT | **113.9 ms** | | Maximum RTT | **128.46 ms** | | Standard deviation | **4.6 ms** | | Stdev / average | **4.0%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Melbourne (MEL)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms * [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms * [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms * [Los Angeles to Melbourne latency and RTT](/docs/network/latency/pairs/lax-mel-rtt) — 148.2 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-mel-rtt). - **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. # Tokyo, Japan → Miami, USA RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇺🇸 **Miami, USA (MIA)** Measurement round: `2026-08-16T04:07:28Z`. In the 2026-08-16T04:07:28Z round, ICMP echo probes from Tokyo to Miami averaged 156.5 ms, with a minimum of 154.18 ms and a maximum of 166.87 ms. All 50 samples were returned, so the measured packet loss was 0%. The jitter was 1.73 ms and the standard deviation was 2.45 ms, giving a spread-to-average ratio of about 1.6%. Across the 19 routes from Tokyo measured in this round, Miami ranked 10th in average latency, while the median variability ratio was 3.28%; this path was more stable than that midpoint. Tokyo is a principal East Asian exchange hub and trans-Pacific landing point, and Miami is the digital gateway between North and South America. Relative to the 12,019.9 km great-circle distance, the vacuum floor is 80.19 ms and the fiber floor is 117.71 ms; the measured average is 1.33 times that floor, or 75.2% fiber efficiency. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **156.5 ms** | | Jitter | **1.73 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **117.71 ms** | | Fiber Efficiency | **75.2%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **12,019.9 km** | | Vacuum RTT floor | **80.19 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **117.71 ms** | | Low-latency fiber material floor | **117.24 ms** | | Engineering floor (5% path allowance) | **123.61 ms** | | Research 1.33× mapped-fiber reference | **156.55 ms** | | Estimated unamplified path loss | **2524.2 dB** | | Transparent optical spans / inline amplifiers | **158 / 157** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **154.18 ms** | | Average RTT | **156.5 ms** | | Maximum RTT | **166.87 ms** | | Standard deviation | **2.45 ms** | | Stdev / average | **1.6%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Miami to Tokyo latency and RTT](/docs/network/latency/pairs/mia-tyo-rtt) — 156.3 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Miami (MIA)** * [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms * [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms * [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms * [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms * [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms **Same corridor (Asia Pacific → North America)** * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Miami round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-mia-rtt). - **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. # Tokyo, Japan → Moscow, Russia RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇷🇺 **Moscow, Russia (MOW)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo probes from Tokyo to Moscow in the 2026-08-16T04:07:28Z round recorded an average round-trip time of 161.7 ms across 50 samples, with a minimum of 155.32 ms and a maximum of 174.84 ms. Zero packets were lost, and jitter was 4.87 ms. The great-circle distance is about 7,497 km, so the vacuum floor is 50.01 ms and the direct-fiber floor is 73.42 ms. At 161.7 ms the measured average is 2.2 times the fiber floor, equivalent to about 45.4% fiber efficiency; the route's absolute latency is low, but its distance-adjusted efficiency trails that ideal. Among the 19 outbound routes from this origin, the path ranked 11th, placing it near the middle rather than the top. Its standard deviation of 4.83 ms is about 3.0% of the average, below the 3.28% midpoint across the set, so the path combines moderate rank with good consistency and no loss. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **161.7 ms** | | Jitter | **4.87 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **73.42 ms** | | Fiber Efficiency | **45.4%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | ------------- | | WGS-84 geodesic distance | **7,497 km** | | Vacuum RTT floor | **50.01 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **73.42 ms** | | Low-latency fiber material floor | **73.12 ms** | | Engineering floor (5% path allowance) | **77.1 ms** | | Research 1.33× mapped-fiber reference | **97.64 ms** | | Estimated unamplified path loss | **1574.4 dB** | | Transparent optical spans / inline amplifiers | **99 / 98** | | Published RTT inflation over fiber floor | **2.2×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **155.32 ms** | | Average RTT | **161.7 ms** | | Maximum RTT | **174.84 ms** | | Standard deviation | **4.83 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Moscow to Tokyo latency and RTT](/docs/network/latency/pairs/mow-tyo-rtt) — 162.2 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Moscow (MOW)** * [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms * [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms * [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms * [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms * [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-mow-rtt). - **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. # Tokyo, Japan → Marseille, France RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇫🇷 **Marseille, France (MRS)** Measurement round: `2026-08-16T04:07:28Z`. During the 2026-08-16T04:07:28Z round, ICMP echo probes from Tokyo to Marseille averaged 205.6 ms over 50 samples, with a minimum of 198.77 ms and a maximum of 227.7 ms. The route saw zero packet loss and jitter of 4.57 ms. Tokyo and Marseille are about 10,113 km apart by great-circle distance, giving a vacuum floor of 67.47 ms and a direct-fiber floor of 99.03 ms. The observed average is 2.08 times that fiber floor, which corresponds to roughly 48.2% fiber efficiency, a slightly better distance-adjusted result than the absolute RTT might suggest. This path ranked 17th of the 19 outbound routes from its origin, so it sits near the slower end of the route set. Its own standard deviation of 6.33 ms is about 3.1% of the average, just under the 3.28% midpoint across the set; round-trip times stayed consistent within a 28.93 ms min-max spread. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **205.6 ms** | | Jitter | **4.57 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **99.03 ms** | | Fiber Efficiency | **48.2%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,112.8 km** | | Vacuum RTT floor | **67.47 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **99.03 ms** | | Low-latency fiber material floor | **98.63 ms** | | Engineering floor (5% path allowance) | **104 ms** | | Research 1.33× mapped-fiber reference | **131.71 ms** | | Estimated unamplified path loss | **2123.7 dB** | | Transparent optical spans / inline amplifiers | **133 / 132** | | Published RTT inflation over fiber floor | **2.08×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **198.77 ms** | | Average RTT | **205.6 ms** | | Maximum RTT | **227.7 ms** | | Standard deviation | **6.33 ms** | | Stdev / average | **3.1%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Marseille to Tokyo latency and RTT](/docs/network/latency/pairs/mrs-tyo-rtt) — 203.8 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Marseille (MRS)** * [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms * [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms * [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms * [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms * [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Marseille round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-mrs-rtt). - **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. # Tokyo, Japan → New York, USA RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇺🇸 **New York, USA (NYC)** Measurement round: `2026-08-16T04:07:28Z`. ICMP echo probes from Tokyo to New York in the 2026-08-16T04:07:28Z round produced an average RTT of 144.6 ms, with a minimum of 140.04 ms and a maximum of 156.39 ms. The 50-sample run completed without loss, so packet loss was 0%. This route ranked 9th among the 19 routes from Tokyo in the round, placing it near the middle of the measured set. Its spread-to-average ratio was about 2.8%, slightly below the 3.28% median for the same set, so the latency profile was more consistent than the midpoint. The great-circle distance between Tokyo and New York is 10,872.7 km, implying a vacuum floor of 72.53 ms and a fiber floor of 106.47 ms. The observed average of 144.6 ms sits 1.36 times above the fiber floor, an efficiency of 73.6%, which indicates the expected overhead of real-world network topology. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **144.6 ms** | | Jitter | **3.26 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **106.47 ms** | | Fiber Efficiency | **73.6%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,872.7 km** | | Vacuum RTT floor | **72.53 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **106.47 ms** | | Low-latency fiber material floor | **106.05 ms** | | Engineering floor (5% path allowance) | **111.81 ms** | | Research 1.33× mapped-fiber reference | **141.61 ms** | | Estimated unamplified path loss | **2283.3 dB** | | Transparent optical spans / inline amplifiers | **143 / 142** | | Published RTT inflation over fiber floor | **1.36×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **140.04 ms** | | Average RTT | **144.6 ms** | | Maximum RTT | **156.39 ms** | | Standard deviation | **4.02 ms** | | Stdev / average | **2.8%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [New York to Tokyo latency and RTT](/docs/network/latency/pairs/nyc-tyo-rtt) — 143.1 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at New York (NYC)** * [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms * [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms * [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms * [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms * [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms **Same corridor (Asia Pacific → North America)** * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → New York round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-nyc-rtt). - **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. # Tokyo, Japan → Paris, France RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇫🇷 **Paris, France (PAR)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z measurement window, ICMP echo RTT from Tokyo, Japan to Paris, France averaged 204.8 ms, with a minimum of 196.94 ms and a maximum of 227.87 ms. The 50-sample run recorded 0% packet loss, while jitter settled at 5.58 ms. This long-haul path sits 9,736.1 km apart on the geodesic line, and the measured average is 2.15 times the theoretical fiber floor. The fiber efficiency of 46.6% means the observed round trip carries considerable headroom above the optical-path minimum, with the inflation factor of 2.15 quantifying that gap. In the outbound route set of 19 paths, Tokyo-Paris is ranked 16th by measured average RTT. Its variation around the average is about 3.2%, just below the 3.28% median seen across the network's outbound routes, so the route shows a stable result despite the higher latency tier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **204.8 ms** | | Jitter | **5.58 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **95.34 ms** | | Fiber Efficiency | **46.6%** | | Latency Tier | Fair | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Europe](/docs/network/latency/regions/europe) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **9,736.1 km** | | Vacuum RTT floor | **64.95 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **95.34 ms** | | Low-latency fiber material floor | **94.96 ms** | | Engineering floor (5% path allowance) | **100.12 ms** | | Research 1.33× mapped-fiber reference | **126.81 ms** | | Estimated unamplified path loss | **2044.6 dB** | | Transparent optical spans / inline amplifiers | **128 / 127** | | Published RTT inflation over fiber floor | **2.15×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **196.94 ms** | | Average RTT | **204.8 ms** | | Maximum RTT | **227.87 ms** | | Standard deviation | **6.58 ms** | | Stdev / average | **3.2%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Paris (PAR)](/docs/network/latency/par-paris) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Paris to Tokyo latency and RTT](/docs/network/latency/pairs/par-tyo-rtt) — 204.7 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Paris (PAR)** * [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms * [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms * [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms * [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms * [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms **Same corridor (Asia Pacific → Europe)** * [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms * [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms * [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-par.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Paris round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-par-rtt). - **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. # Tokyo, Japan → Seattle, USA RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇺🇸 **Seattle, USA (SEA)** Measurement round: `2026-08-16T04:07:28Z`. For the 2026-08-16T04:07:28Z round, ICMP echo probes from Tokyo to Seattle averaged 84.8 ms, with a minimum of 81.06 ms and a maximum of 94.31 ms. All 50 probes succeeded, yielding 0% packet loss and 2.73 ms jitter. Among the 19 routes from Tokyo measured in this round, Seattle placed 4th in average latency, putting it in the faster group. Its spread-to-average ratio was about 3.5%, above the 3.28% median for the same set, so raw speed came with slightly wider relative variation than the typical Tokyo-origin path. Tokyo and Seattle are both trans-Pacific interconnection points, and the 7,715.2 km great-circle distance gives a vacuum floor of 51.47 ms and a fiber floor of 75.55 ms. At 84.8 ms, the average RTT is only 1.12 times that fiber floor, an efficiency of 89.1%, showing the route stays close to its physical distance floor. ## Latency Summary | Metric | Value | | -------------------- | ------------------------------------------------------------ | | RTT | **84.8 ms** | | Jitter | **2.73 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **75.55 ms** | | Fiber Efficiency | **89.1%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [North America](/docs/network/latency/regions/north-america) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,715.2 km** | | Vacuum RTT floor | **51.47 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **75.55 ms** | | Low-latency fiber material floor | **75.25 ms** | | Engineering floor (5% path allowance) | **79.34 ms** | | Research 1.33× mapped-fiber reference | **100.49 ms** | | Estimated unamplified path loss | **1620.2 dB** | | Transparent optical spans / inline amplifiers | **102 / 101** | | Published RTT inflation over fiber floor | **1.12×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **81.06 ms** | | Average RTT | **84.8 ms** | | Maximum RTT | **94.31 ms** | | Standard deviation | **2.93 ms** | | Stdev / average | **3.5%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms **Fastest routes arriving at Seattle (SEA)** * [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms * [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms * [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms * [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms **Same corridor (Asia Pacific → North America)** * [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms * [Sydney to Los Angeles latency and RTT](/docs/network/latency/pairs/syd-lax-rtt) — 136.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Seattle round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-sea-rtt). - **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. # Tokyo, Japan → Singapore RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇸🇬 **Singapore (SIN)** Measurement round: `2026-08-16T04:07:28Z`. For measurement round 2026-08-16T04:07:28Z, the ICMP echo RTT from Tokyo, Japan to Singapore averages 69.4 ms, with individual samples ranging from 66.32 ms to 80.7 ms. It is the third-fastest of the 19 outbound routes measured from Tokyo in this round. The standard deviation of 3.27 ms is about 4.7% of the average, modestly above the 3.28% median standard-deviation-to-average ratio for the measured set; jitter is 2.27 ms and packet loss is 0%. The observed RTT is 1.33 times the estimated fiber-floor time of 52 ms, indicating an efficient path over the 5,310 km separation. With zero loss and stable jitter, the route sits in the Excellent latency tier for ICMP echo probes. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **69.4 ms** | | Jitter | **2.27 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **52 ms** | | Fiber Efficiency | **74.9%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **5,310.2 km** | | Vacuum RTT floor | **35.43 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **52 ms** | | Low-latency fiber material floor | **51.79 ms** | | Engineering floor (5% path allowance) | **54.61 ms** | | Research 1.33× mapped-fiber reference | **69.16 ms** | | Estimated unamplified path loss | **1115.1 dB** | | Transparent optical spans / inline amplifiers | **70 / 69** | | Published RTT inflation over fiber floor | **1.33×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **66.32 ms** | | Average RTT | **69.4 ms** | | Maximum RTT | **80.7 ms** | | Standard deviation | **3.27 ms** | | Stdev / average | **4.7%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms **Fastest routes arriving at Singapore (SIN)** * [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms * [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms * [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms * [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Singapore round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-sin-rtt). - **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. # Tokyo, Japan → Sydney, Australia RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇦🇺 **Sydney, Australia (SYD)** Measurement round: `2026-08-16T04:07:28Z`. For measurement round 2026-08-16T04:07:28Z, the ICMP echo RTT from Tokyo, Japan to Sydney averages 101.9 ms, with samples from 97.82 ms to 112.89 ms. It is the sixth-fastest of the 19 outbound routes measured from Tokyo in this round. The 3.32 ms standard deviation is about 3.3% of the average, closely matching the 3.28% median standard-deviation-to-average ratio for the measured set; jitter is 3.13 ms and packet loss is 0%. The average is 1.34 times the estimated fiber-floor time of 76.31 ms, leaving the route at roughly 74.9% fiber efficiency over the 7,793 km trans-Pacific path. Zero packet loss and a Good latency tier indicate a stable route despite the larger absolute RTT. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **101.9 ms** | | Jitter | **3.13 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **76.31 ms** | | Fiber Efficiency | **74.9%** | | Latency Tier | Good | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **7,792.8 km** | | Vacuum RTT floor | **51.99 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **76.31 ms** | | Low-latency fiber material floor | **76.01 ms** | | Engineering floor (5% path allowance) | **80.14 ms** | | Research 1.33× mapped-fiber reference | **101.5 ms** | | Estimated unamplified path loss | **1636.5 dB** | | Transparent optical spans / inline amplifiers | **103 / 102** | | Published RTT inflation over fiber floor | **1.34×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **97.82 ms** | | Average RTT | **101.9 ms** | | Maximum RTT | **112.89 ms** | | Standard deviation | **3.32 ms** | | Stdev / average | **3.3%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms **Fastest routes arriving at Sydney (SYD)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms * [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms * [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms * [Los Angeles to Sydney latency and RTT](/docs/network/latency/pairs/lax-syd-rtt) — 137.6 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-syd.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Sydney round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-syd-rtt). - **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. # Tokyo, Japan → Taipei, Taiwan RTT 🇯🇵 **Tokyo, Japan (TYO)** → 🇹🇼 **Taipei, Taiwan (TPE)** Measurement round: `2026-08-16T04:07:28Z`. For measurement round 2026-08-16T04:07:28Z, the ICMP echo RTT from Tokyo, Japan to Taipei averages 32.3 ms, with samples from 31.1 ms to 36.28 ms. It is the fastest of the 19 outbound routes measured from Tokyo in this round. The standard deviation of 0.96 ms is about 3.0% of the average, below the 3.28% median standard-deviation-to-average ratio for the measured set; jitter is 0.75 ms and packet loss is 0%. The observed RTT is 1.57 times the estimated fiber-floor time of 20.58 ms, a larger proportional overhead than long-haul paths, yet the absolute latency remains very low for the 2,101 km distance. Extremely low jitter and zero loss place this route at the top of the Excellent latency tier. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **32.3 ms** | | Jitter | **0.75 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **20.58 ms** | | Fiber Efficiency | **63.7%** | | Latency Tier | Excellent | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart. ## Download This Route's Data This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance. ## Theoretical Fiber Latency The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address. | Physical Reference | Value | | --------------------------------------------- | -------------- | | WGS-84 geodesic distance | **2,101.2 km** | | Vacuum RTT floor | **14.02 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **20.58 ms** | | Low-latency fiber material floor | **20.49 ms** | | Engineering floor (5% path allowance) | **21.61 ms** | | Research 1.33× mapped-fiber reference | **27.37 ms** | | Estimated unamplified path loss | **441.3 dB** | | Transparent optical spans / inline amplifiers | **28 / 27** | | Published RTT inflation over fiber floor | **1.57×** | Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round: | Round Statistic | Value | | ------------------ | ------------ | | Minimum RTT | **31.1 ms** | | Average RTT | **32.3 ms** | | Maximum RTT | **36.28 ms** | | Standard deviation | **0.96 ms** | | Stdev / average | **3.0%** | ## Route Context * Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo) * Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific) * Full global matrix: [Backbone Latency Matrix](/docs/network/latency) * Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency) ## Related City-Pair Routes **Reverse direction** * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms **Fastest routes departing Tokyo (TYO)** * [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms * [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms * [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms * [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms * [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms **Fastest routes arriving at Taipei (TPE)** * [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms * [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms * [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms * [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms * [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms **Same corridor (Asia Pacific → Asia Pacific)** * [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms * [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms ## About This Measurement Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA. The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).* --- ## License and attribution - **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-tpe-rtt). - **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.