asn.dev

Observed topology

AS48416 INFOLAN-AS

Unclassified ARIN

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS48416: 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
AS50509Transroute Telecom LTDUnclassifiedIPv4173
AS31500Global Network Management IncUnclassifiedIPv4159
AS35598INETCOM CARRIER LLCUnclassifiedIPv496
AS31133PJSC MegaFonMobileIPv448
AS6939Hurricane Electric LLCTransitIPv420
AS62255BiMajLink d.o.o.UnclassifiedIPv43
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42
AS56655Gigahost ASUnclassifiedIPv42

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56853Municipal educational institution The Centre of Information TechnologiesUnclassifiedIPv465

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4212
AS31500Global Network Management IncUnclassifiedIPv4169
AS35598INETCOM CARRIER LLCUnclassifiedIPv497
AS56853Municipal educational institution The Centre of Information TechnologiesUnclassifiedIPv465
AS31133PJSC MegaFonMobileIPv460
AS6939Hurricane Electric LLCTransitIPv420
AS62255BiMajLink d.o.o.UnclassifiedIPv44
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv42

All 14 adjacent →

Provenance

Where this comes from

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