Check-Host.cc

MTR Test from Chile

1 node in Santiago · NAP Chile

Chile — 1 Node

Cities
Santiago
ISPs / ASNs
Google LLC AS396982
Datacenters
Google LLC
Internet Exchanges
NAP Chile — Neutral Access Point Chile in Santiago, primary national IX
PIT Chile — Punto de Intercambio de Tráfico Chile, secondary IX in Santiago

MTR Traceroute from Chile

MTR from our Santiago node runs continuous per-hop latency and loss measurements from AS396982 (Google LLC) toward your target. Traffic from Google Cloud in Santiago exits via Google's private backbone infrastructure rather than via standard Chilean ISP transit, using Google's submarine cable capacity on the Pacific Coast route. The path to US destinations typically runs north up the South American Pacific coast and into Google's US PoPs before reaching the destination network.

A typical MTR from Santiago to a Miami target shows: 1–2 internal Google hops adding 1–3 ms, then a submarine cable segment north along the Pacific coast and into Florida adding 100–115 ms, arriving at Miami around 108–118 ms total. A typical MTR from Santiago to Frankfurt shows the path continuing through US transit before crossing the Atlantic, arriving at Frankfurt around 230–250 ms. If the MTR shows an unusually short path to Frankfurt — say, under 200 ms — Google may be routing via a direct South America-to-Europe cable.

MTR from Santiago is particularly valuable for diagnosing connectivity issues reported by Chilean users or by services hosted in Google Cloud's South America West region. Intermediate hop asterisks on the Pacific cable segment are common and do not represent real loss. Loss that persists from a specific hop through the destination reflects real congestion or a routing fault. An MTR from Santiago is one of the few ways to visualize the South American side of a trans-Pacific path, making it useful for understanding why latency from Chile to a specific server is higher or lower than expected from geographic distance alone.

Chile Network Infrastructure

Chile is the most connected country in South America by most measurements — fiber penetration, average bandwidth, and IX maturity. Santiago hosts two significant internet exchanges: NAP Chile and PIT Chile. NAP Chile (Neutral Access Point Chile) operates the primary peering fabric used by major ISPs, CDNs, and content networks. PIT Chile (Punto de Intercambio de Tráfico) provides a complementary peering point. Together, these two exchanges give Santiago a domestic traffic anchoring capability that reduces the need for Chilean ISPs to route local traffic through Miami or New York.

International connectivity from Chile exits primarily via submarine cables running up the Pacific coast toward the United States. The South American-1 (SAm-1) and PCCS cables carry the bulk of Chile's international capacity. The primary international landing station is in Valparaíso. Santiago to Miami typically runs 105–115 ms. Santiago to Los Angeles on Pacific cable runs approximately 118–130 ms. Santiago to São Paulo sits around 48–58 ms. Santiago to New York is approximately 135–150 ms. These figures reflect Chile's geographic position at the southwestern tip of South America — closer to the US West Coast than to Europe via any submarine cable route.

The Chilean ISP market is served by Entel Chile (AS7418), Claro Chile (AS14259), Movistar Chile / Telefónica (AS7418 / AS22047), VTR (AS22047), and GTD (AS11664) among others. Antel and Telmex subsidiaries also operate in the market. The domestic backbone in Santiago is well-developed, and most Chilean carrier infrastructure concentrates in Santiago rather than distributing across the country's geographically elongated territory. Our probe node runs on Google LLC infrastructure in Santiago (AS396982).

Google Cloud's presence in Santiago (AS396982) reflects Chile's status as the main South American cloud market outside Brazil. Google operates a South America West region (Quilicura, outside Santiago) that serves Chilean and regional Latin American cloud workloads. AS396982 uses Google's global backbone for international transit, giving it better-than-average peering to most destinations compared to what a standard Chilean ISP on Entel or Claro transit would see.

Our Santiago node provides a test location inside Chile's primary carrier environment with access to Google's well-peered network. Results from this node reflect how Chilean-hosted cloud infrastructure performs — useful for diagnosing whether a service is accessible from South America's most connected country, and what latency Chilean users or Chilean-hosted workloads experience toward European, US, or Asian targets.