asn.dev

Observed topology

AS54082 MULTICABLE-NETWORK-GT-LLC

Unclassified ARIN Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS54082: 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
AS1299Arelion Sweden ABTransitIPv450
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv640

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS263725MULTICABLE DE HONDURASUnclassifiedIPv4 IPv61,509
AS64150PIT HONDURAS S. DE R.L. DE C.V.ResidentialIPv4110

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263725MULTICABLE DE HONDURASUnclassifiedIPv4 IPv62,499
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv61,666
AS1299Arelion Sweden ABTransitIPv4 IPv61,127
AS64150PIT HONDURAS S. DE R.L. DE C.V.ResidentialIPv4 IPv6201
AS52468UFINET PANAMA S.A.UnclassifiedIPv437

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.