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