Observed topology
AS31257 ORIONNET-KRK Orion Telecom LLC
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS31257: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 1,422 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 1,116 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 809 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 392 |
| AS48858 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 134 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 66 |
| AS24482 | SG.GS | Hosting | IPv4 | 60 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 40 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv6 | 8 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS31257 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208221 | Orion telecom ltd | Unclassified | IPv4 | 520 |
| AS201786 | OOO ComLine | Residential | IPv4 IPv6 | 87 |
| AS59696 | Municipality of Krasnoyarsk City | Unclassified | IPv4 | 65 |
| AS60980 | 45KA LLC. | Unclassified | IPv4 | 65 |
| AS201970 | LLC Komandor-Holding | Unclassified | IPv4 | 65 |
| AS209867 | LLC Security Agency "Scorpion" | Unclassified | IPv4 | 65 |
| AS204137 | Orion telecom ltd | Residential | IPv4 IPv6 | 54 |
| AS58351 | IE Dudin Dmitriy Viktorovich | Unclassified | IPv4 | 50 |
| AS60575 | LTD SibServisSvyaz | Unclassified | IPv4 | 38 |
| AS50427 | Orion Telecom LLC | Residential | IPv6 | 33 |
Adjacency
Adjacent networks
Every AS seen directly next to AS31257 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 1,777 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 1,463 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 895 |
| AS208221 | Orion telecom ltd | Unclassified | IPv4 | 520 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 423 |
| AS48858 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 165 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 141 |
| AS201786 | OOO ComLine | Residential | IPv4 IPv6 | 87 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 83 |
| AS24482 | SG.GS | Hosting | IPv4 | 74 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.