AS393885 — HAVILAND-TEL - Haviland Telephone Company, Inc.
🇺🇸 United States · ARIN region · approx. 37.62, -99.11
HAVILAND-TEL - Haviland Telephone Company, Inc. (AS393885) in United States has 2 direct BGP neighbours, ranked #50541 of 88104 by observed links.
Network intelligence
Neighbourhood
What's directly and indirectly (up to two hops) connected to AS393885 — the same force-directed layout as the main Topology view, computed fresh on every page load (reload for a different arrangement), with AS393885 itself always centred. Drag to pan, scroll/pinch to zoom, click a dot to jump to that AS's own page. Explore the full interactive map →
Announced prefixes
RPKI route-origin validity badge per prefix, from this instance's self-hosted Routinator (see Credits). The full, de-duplicated set seen across every BGP collector this snapshot imports — usually more than the “IPv4/IPv6 prefixes” counts above, which only reflect a single collector's own routing table.
- 64.71.208.0/21 RPKI Valid
- 64.71.216.0/23 RPKI Valid
- 64.71.218.0/23 RPKI Valid
- 64.71.220.0/22 RPKI Valid
- 67.22.144.0/20 RPKI Valid
- 2604:4a00::/36 RPKI Valid
- 2604:4a00:1000::/36 RPKI Valid
- 2604:4a00:2000::/36 RPKI Valid
- 2604:4a00:3000::/36 RPKI Valid
- 2604:4a00:4000::/36 RPKI Valid
- 2604:4a00:5000::/36 RPKI Valid
- 2604:4a00:6000::/36 RPKI Valid
- 2604:4a00:7000::/36 RPKI Valid
- 2604:4a00:8000::/36 RPKI Valid
- 2604:4a00:9000::/36 RPKI Valid
- 2604:4a00:a000::/36 RPKI Valid
- 2604:4a00:b000::/36 RPKI Valid
- 2604:4a00:c000::/36 RPKI Valid
- 2604:4a00:d000::/36 RPKI Valid
- 2604:4a00:e000::/36 RPKI Valid
No loaded prefix matches that filter. Try loading more below, or narrow/widen the filter text.
...and 1 more.
Upstream providers (2)
Networks that this AS is a customer of (inferred from public BGP data by BGPKIT's as2rel dataset, a heuristic, not ground truth).
Geographic footprint
Geolocated (estimated) country of every prefix AS393885 announces, via IP geolocation against DB-IP City Lite — not AS393885's RIR registration country (see the stats above), and not necessarily where its infrastructure physically sits.