asn.dev

Observed topology

AS64112 PIT CHILE SP

Unclassified ARIN

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 7
Upstream graph Who carries AS64112, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS64112 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS64112: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS22850PIT USUnclassifiedIPv4 IPv6232
AS6939Hurricane Electric LLCTransitIPv4 IPv6229
AS7303Telecom Argentina S.A.MobileIPv4 IPv692
AS22908Sixsigma Networks Mexico, S.A. de C.V.UnclassifiedIPv4 IPv678
AS18747IFX CorporationUnclassifiedIPv4 IPv675
AS174Cogent Communications, LLCTransitIPv615

Transit

Downstream networks

inferred

Networks for which AS64112 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS263784BYNARYA SPAUnclassifiedIPv448
AS394353B.Root-Server-OPSUnclassifiedIPv4 IPv634

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS64112 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS22850PIT USUnclassifiedIPv4 IPv6312
AS6939Hurricane Electric LLCTransitIPv4 IPv6229
AS7303Telecom Argentina S.A.MobileIPv4 IPv692
AS22908Sixsigma Networks Mexico, S.A. de C.V.UnclassifiedIPv4 IPv678
AS18747IFX CorporationUnclassifiedIPv4 IPv677
AS263784BYNARYA SPAUnclassifiedIPv448
AS394353B.Root-Server-OPSUnclassifiedIPv4 IPv634
AS174Cogent Communications, LLCTransitIPv615

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.