DNS checks from the US nodes query your authoritative nameservers directly from Miami, Dallas, and Kansas City and report the resolved records and query times. Querying authoritative servers directly bypasses recursive resolver caches, so the result shows the current record at the source — not a potentially stale cached answer. This is the correct method for confirming that a DNS change has propagated to the authoritative tier, independent of resolver TTL state.

All three US nodes are useful for validating GeoDNS configurations that route US traffic to US-region infrastructure. The three probe ASNs — AS202673 (Miami), AS201129 (Dallas), AS22295 (Kansas City) — are all US-geolocated hosting ranges. A GeoDNS rule targeting US source IPs should return US-region records from all three. If one node gets a European IP back, the GeoIP database used by your DNS provider is misclassifying that ASN. Cross-check against our Canadian node to confirm the rule boundary.

DNS query times from US nodes to authoritative servers hosted on Cloudflare, NS1, or AWS Route 53 with anycast nodes in the US should be under 5 ms from all three probe locations. If query times are consistently above 20–30 ms, the authoritative nameserver has no US anycast node and is answering from a single overseas location — common with smaller DNS providers or self-hosted BIND installations outside North America. Moving authoritative DNS to a multi-PoP provider resolves this at the DNS tier without touching the origin server.

The US internet backbone is anchored in Ashburn, Virginia, where Equinix operates the largest concentration of interconnected networks in the country. Over 500 networks peer at the Equinix campus in Ashburn, including AT&T (AS7018), Comcast (AS7922), Lumen/CenturyLink (AS3356), Cogent (AS174), and NTT (AS2914). The density of peering there means that a packet originating in Miami or Dallas often transits through Ashburn before exiting to Europe, making it the effective default gateway for US-to-Europe traffic regardless of where the origin server sits.

Our US nodes span three cities across the South, Central, and Midwest regions. Miami runs on AS202673 (Ohz Digital SL) and is the southernmost probe — useful for measuring connectivity relevant to Latin American networks and Caribbean-facing services. Dallas runs on AS201129 (Linceris International Cloud) at Dallas DC, positioned at the intersection of south-central US routes with good proximity to both Equinix Dallas peering and central US backbone routes. Kansas City runs on AS22295 (Advin Services LLC / Tierhive) in the Midwest, providing a third vantage point with direct access to central US carrier paths.

Reference RTTs from these nodes under normal load: Miami to London is approximately 120 ms, Miami to São Paulo around 85 ms. Dallas to Frankfurt typically runs 130–135 ms via transatlantic submarine cables landing on the US East Coast. Kansas City to New York is roughly 35 ms, and Kansas City to Los Angeles is in the 40–45 ms range. These figures vary by carrier — Cogent and Lumen have different peering strategies at Ashburn, which produces measurably different latency for the same destination depending on which AS the probe exits through.

Key US transit providers reachable from all three nodes include AT&T (AS7018), Comcast Business (AS7922), Lumen (AS3356), Cogent (AS174), and NTT America (AS2914). These five carriers collectively carry the majority of US internet traffic and each maintains presence in Dallas, Kansas City, and Miami in addition to Ashburn. At the IX level, DE-CIX New York and NYIIX serve the Northeast corridor. Equinix Dallas and CoreSite serve south-central US. Miami is served by the NAP of the Americas facility, a major Latin America-facing interconnect point operated by Equinix.

Running checks across all three US nodes simultaneously provides geographic diversity within a single country that matters. A server hosted on AWS us-east-1 will show different RTTs from Miami (via southeast paths), Dallas (via south-central), and Kansas City (via central US backbone). A CDN with US PoPs should show low single-digit or sub-10ms results from all three. If one node shows significantly higher latency than the others, the routing from that city or the serving carrier is suboptimal for that node's upstream transit mix.