asn.dev

Observed topology

AS35168 TNS-PLUS-CORE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35168: 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
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6228
AS6939Hurricane Electric LLCTransitIPv4 IPv6214
AS3216PJSC "Vimpelcom"MobileIPv4 IPv6133
AS9002RETN LimitedUnclassifiedIPv4 IPv682
AS35104QMOBILE JSCUnclassifiedIPv461
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv67
AS49673Truenetwork LLCUnclassifiedIPv46
AS60280Republican Unitary Enterprise "National Traffic Exchange Center"UnclassifiedIPv46

Transit

Downstream networks

All 56

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

ASNetworkTypeFamiliesPaths seen
AS21299Kar-Tel LLCUnclassifiedIPv4 IPv649,618
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv610,368
AS197556Kar-Tel LLCUnclassifiedIPv4 IPv64,727
AS48716PS Internet Company LLPUnclassifiedIPv4 IPv63,631
AS39824JSC Alma TelecommunicationsUnclassifiedIPv4 IPv62,644
AS8393"ASTEL" JSCUnclassifiedIPv42,360
AS35566Kar-Tel LLCUnclassifiedIPv42,244
AS205516NLS ASTANA LLPUnclassifiedIPv4 IPv61,881
AS58172Freedom Telecom Operations LLPUnclassifiedIPv4 IPv61,815
AS35104QMOBILE JSCUnclassifiedIPv41,665

Adjacency

Adjacent networks

All 84

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

ASNetworkTypeFamiliesPaths seen
AS21299Kar-Tel LLCUnclassifiedIPv4 IPv655,048
AS6939Hurricane Electric LLCTransitIPv4 IPv642,389
AS3216PJSC "Vimpelcom"MobileIPv4 IPv621,830
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv620,345
AS9002RETN LimitedUnclassifiedIPv4 IPv619,694
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv612,527
AS8449"ElCat" Ltd.UnclassifiedIPv4 IPv611,200
AS197556Kar-Tel LLCUnclassifiedIPv4 IPv610,316
AS35104QMOBILE JSCUnclassifiedIPv4 IPv66,468
AS60280Republican Unitary Enterprise "National Traffic Exchange Center"UnclassifiedIPv4 IPv65,757

Provenance

Where this comes from

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