Observed topology
AS34123 NETORN-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS34123: 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 IPv6 | 413 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 111 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 53 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 12 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 11 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 10 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 9 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 6 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS34123 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50553 | OOO Stalnet | Unclassified | IPv4 | 251 |
| AS42148 | Beirel Telecom LLC | Unclassified | IPv4 IPv6 | 208 |
| AS58036 | LLC "SKY LINE" | Unclassified | IPv4 IPv6 | 168 |
| AS34139 | JSC DIVO | Unclassified | IPv4 | 111 |
| AS48149 | Ivanteevskie telecommunicacii Ltd | Unclassified | IPv4 | 97 |
| AS50668 | Dialog-K LLC | Unclassified | IPv4 | 95 |
| AS47711 | Line Group Ltd. | Unclassified | IPv4 | 67 |
| AS57368 | Limited Liability Company " SSTinvest" | Unclassified | IPv4 | 60 |
| AS209558 | PREMIUM KEA GRUP LLC | Unclassified | IPv4 | 49 |
| AS8395 | East Telecom Ltd. | Unclassified | IPv4 IPv6 | 43 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34123 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 1,071 |
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 IPv6 | 415 |
| AS50553 | OOO Stalnet | Unclassified | IPv4 | 251 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 216 |
| AS42148 | Beirel Telecom LLC | Unclassified | IPv4 IPv6 | 211 |
| AS58036 | LLC "SKY LINE" | Unclassified | IPv4 IPv6 | 168 |
| AS34139 | JSC DIVO | Unclassified | IPv4 IPv6 | 155 |
| AS51579 | Korporatvniy partner Ltd | Unclassified | IPv4 IPv6 | 146 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 101 |
| AS48149 | Ivanteevskie telecommunicacii Ltd | Unclassified | IPv4 | 100 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.