asn.dev

Observed topology

AS35104 KTC-AS QMOBILE JSC

Unclassified RIPE NSP

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS35104: 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
AS43727JSC KVANT-TELEKOMResidentialIPv41,916
AS3216PJSC "Vimpelcom"MobileIPv41,687
AS35168TNS-Plus LLPUnclassifiedIPv41,641
AS41798JSC TranstelecomUnclassifiedIPv4 IPv61,391
AS31253Sovemennye Telekommunikatsionnye Sistemy LLPUnclassifiedIPv41,260
AS12389PJSC RostelecomResidentialIPv4 IPv61,211
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6478
AS9002RETN LimitedUnclassifiedIPv4 IPv6354
AS31133PJSC MegaFonMobileIPv4279
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv696

All 22 upstreams →

Transit

Downstream networks

All 40

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

ASNetworkTypeFamiliesPaths seen
AS29355Kcell JSCUnclassifiedIPv46,324
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv63,998
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv63,164
AS48988Modern Server Solutions LLPUnclassifiedIPv4 IPv62,008
AS56568X-COMMUNICATION LLPUnclassifiedIPv4 IPv6956
AS41371BiKaDa TOOUnclassifiedIPv4930
AS31525Satti Telecom LLCUnclassifiedIPv4691
AS211644QazCloud LLPUnclassifiedIPv4 IPv6345
AS205516NLS ASTANA LLPUnclassifiedIPv4 IPv6315
AS211028Spetsavtomatikaservice LLPUnclassifiedIPv4310

All 40 downstreams →

Adjacency

Adjacent networks

All 65

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

ASNetworkTypeFamiliesPaths seen
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv612,073
AS9002RETN LimitedUnclassifiedIPv4 IPv68,387
AS3216PJSC "Vimpelcom"MobileIPv4 IPv66,491
AS29355Kcell JSCUnclassifiedIPv46,324
AS35168TNS-Plus LLPUnclassifiedIPv4 IPv66,255
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv65,408
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv63,164
AS31253Sovemennye Telekommunikatsionnye Sistemy LLPUnclassifiedIPv42,582
AS41798JSC TranstelecomUnclassifiedIPv4 IPv62,531
AS48988Modern Server Solutions LLPUnclassifiedIPv4 IPv62,008

All 65 adjacent →

Provenance

Where this comes from

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