asn.dev

Observed topology

AS35401 SUNLINK-AS AO "Tele-Service Tula"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35401: 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
AS3216PJSC "Vimpelcom"MobileIPv4507
AS12389PJSC RostelecomResidentialIPv4 IPv6477
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6178
AS24482SG.GSHostingIPv419
AS37721Virtual Technologies & SolutionsResidentialIPv419
AS9002RETN LimitedUnclassifiedIPv414
AS6939Hurricane Electric LLCTransitIPv410
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219413ServiceCom Ltd.UnclassifiedIPv49
AS56939Credo-S Ltd.UnclassifiedIPv47
AS43740Secure Telecommunication LLCUnclassifiedIPv46
AS48938Guard-Inform Ltd.UnclassifiedIPv46

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4521
AS12389PJSC RostelecomResidentialIPv4 IPv6477
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6191
AS24482SG.GSHostingIPv419
AS37721Virtual Technologies & SolutionsResidentialIPv419
AS9002RETN LimitedUnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv410
AS219413ServiceCom Ltd.UnclassifiedIPv49
AS56939Credo-S Ltd.UnclassifiedIPv47
AS43740Secure Telecommunication LLCUnclassifiedIPv46

Provenance

Where this comes from

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