Observed topology
AS35168 TNS-PLUS-CORE
Unclassified RIPE
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 228 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 214 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 133 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 82 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 | 61 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 IPv6 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 7 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 6 |
| AS60280 | Republican Unitary Enterprise "National Traffic Exchange Center" | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS35168 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS21299 | Kar-Tel LLC | Unclassified | IPv4 IPv6 | 49,618 |
| AS48503 | Mobile Telecom-Service LLP | Unclassified | IPv4 IPv6 | 10,368 |
| AS197556 | Kar-Tel LLC | Unclassified | IPv4 IPv6 | 4,727 |
| AS48716 | PS Internet Company LLP | Unclassified | IPv4 IPv6 | 3,631 |
| AS39824 | JSC Alma Telecommunications | Unclassified | IPv4 IPv6 | 2,644 |
| AS8393 | "ASTEL" JSC | Unclassified | IPv4 | 2,360 |
| AS35566 | Kar-Tel LLC | Unclassified | IPv4 | 2,244 |
| AS205516 | NLS ASTANA LLP | Unclassified | IPv4 IPv6 | 1,881 |
| AS58172 | Freedom Telecom Operations LLP | Unclassified | IPv4 IPv6 | 1,815 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 | 1,665 |
Adjacency
Adjacent networks
Every AS seen directly next to AS35168 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS21299 | Kar-Tel LLC | Unclassified | IPv4 IPv6 | 55,048 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 42,389 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 21,830 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 20,345 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 19,694 |
| AS48503 | Mobile Telecom-Service LLP | Unclassified | IPv4 IPv6 | 12,527 |
| AS8449 | "ElCat" Ltd. | Unclassified | IPv4 IPv6 | 11,200 |
| AS197556 | Kar-Tel LLC | Unclassified | IPv4 IPv6 | 10,316 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 IPv6 | 6,468 |
| AS60280 | Republican Unitary Enterprise "National Traffic Exchange Center" | Unclassified | IPv4 IPv6 | 5,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.