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