# 🇺🇸 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-<destination>.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.