Observed topology
AS41798 TTC-AS JSC Transtelecom
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS41798: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 8,303 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,059 |
| AS60299 | Mezhdugorodnyaya Mezhdunarodnaya Telefonnaya Stanciya Ltd. | Unclassified | IPv4 IPv6 | 700 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 201 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 184 |
| AS25091 | IP-Max SA | Unclassified | IPv4 IPv6 | 21 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS41798 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48716 | PS Internet Company LLP | Unclassified | IPv4 IPv6 | 3,844 |
| AS48503 | Mobile Telecom-Service LLP | Unclassified | IPv4 IPv6 | 1,967 |
| AS39824 | JSC Alma Telecommunications | Unclassified | IPv4 IPv6 | 1,636 |
| AS57013 | Eurasia-Star LLP | Unclassified | IPv4 | 1,560 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 IPv6 | 1,431 |
| AS57826 | Svyaz-INKOM-Servis i telekommunikatsii Ltd. | Unclassified | IPv4 | 1,098 |
| AS58172 | Freedom Telecom Operations LLP | Unclassified | IPv4 IPv6 | 894 |
| AS39318 | PS Internet Company LLP | Unclassified | IPv4 IPv6 | 843 |
| AS59583 | Network Kazakhstan LLC | Unclassified | IPv4 | 708 |
| AS14593 | Space Exploration Technologies Corporation | Residential | IPv4 IPv6 | 677 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41798 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 21,522 |
| AS60299 | Mezhdugorodnyaya Mezhdunarodnaya Telefonnaya Stanciya Ltd. | Unclassified | IPv4 IPv6 | 15,629 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 5,885 |
| AS39824 | JSC Alma Telecommunications | Unclassified | IPv4 IPv6 | 4,501 |
| AS48716 | PS Internet Company LLP | Unclassified | IPv4 IPv6 | 4,162 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,599 |
| AS48503 | Mobile Telecom-Service LLP | Unclassified | IPv4 IPv6 | 2,743 |
| AS59583 | Network Kazakhstan LLC | Unclassified | IPv4 | 2,599 |
| AS35104 | QMOBILE JSC | Unclassified | IPv4 IPv6 | 2,576 |
| AS61010 | IPNET OOO | Unclassified | IPv4 IPv6 | 2,097 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.