asn.dev

Observed topology

AS48940 LINK-AS

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS48940: 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
AS12389PJSC RostelecomResidentialIPv4293
AS31133PJSC MegaFonMobileIPv4226
AS29076Citytelecom LLCHostingIPv461
AS50509Transroute Telecom LTDUnclassifiedIPv430
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv429
AS50673Serverius Holding B.V.UnclassifiedIPv426
AS28968JSC "Evrasia Telecom Ru"UnclassifiedIPv418
AS24482SG.GSHostingIPv413
AS35598INETCOM CARRIER LLCUnclassifiedIPv413
AS37721Virtual Technologies & SolutionsResidentialIPv413

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51705Moskovia Telecom OOOUnclassifiedIPv4126
AS41127LLC "Soro Telecom"UnclassifiedIPv4122
AS61396Okno-TV LLCUnclassifiedIPv4120

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4529
AS31133PJSC MegaFonMobileIPv4272
AS51705Moskovia Telecom OOOUnclassifiedIPv4126
AS41127LLC "Soro Telecom"UnclassifiedIPv4122
AS61396Okno-TV LLCUnclassifiedIPv4120
AS29076Citytelecom LLCHostingIPv479
AS50509Transroute Telecom LTDUnclassifiedIPv454
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv443
AS50673Serverius Holding B.V.UnclassifiedIPv430
AS28968JSC "Evrasia Telecom Ru"UnclassifiedIPv426

All 20 adjacent →

Provenance

Where this comes from

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