Observed topology
AS42291 ISTRANET-AS Istranet LLC AS
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS42291: 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 |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 304 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 83 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 51 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 48 |
| AS12389 | PJSC Rostelecom | Residential | IPv6 | 19 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 9 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 8 |
| AS24482 | SG.GS | Hosting | IPv4 | 8 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 8 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 8 |
Transit
Downstream networks
Networks for which AS42291 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS216363 | OOO Istra.net | Unclassified | IPv4 IPv6 | 360 |
| AS205439 | IP PARK LLC | Unclassified | IPv4 IPv6 | 230 |
| AS216247 | OOO SITI LAJT | Unclassified | IPv4 IPv6 | 165 |
| AS47213 | "IKA Telecom" LTD | Unclassified | IPv4 | 68 |
| AS62046 | Naitex LLC | Unclassified | IPv4 | 62 |
| AS49825 | Lantek LLC | Unclassified | IPv4 | 51 |
| AS62426 | JSC ESTEIT INVEST | Unclassified | IPv4 | 47 |
| AS44093 | JSC ESTEIT INVEST | Unclassified | IPv4 | 43 |
| AS47860 | OOO "OTC" | Unclassified | IPv4 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42291 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 692 |
| AS216363 | OOO Istra.net | Unclassified | IPv4 IPv6 | 360 |
| AS205439 | IP PARK LLC | Unclassified | IPv4 IPv6 | 230 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 226 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 165 |
| AS216247 | OOO SITI LAJT | Unclassified | IPv4 IPv6 | 165 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 153 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 132 |
| AS12389 | PJSC Rostelecom | Residential | IPv6 | 77 |
| AS47213 | "IKA Telecom" LTD | Unclassified | IPv4 | 68 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.