Observed topology
AS61400 NETRACK-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS61400: 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 |
|---|---|---|---|---|
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 2,720 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,435 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 428 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 268 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 180 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 108 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 84 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 81 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 80 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv6 | 30 |
Transit
Downstream networks
Networks for which AS61400 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58045 | Sportivnye Novosti LLC | Unclassified | IPv4 | 240 |
| AS214047 | New Media Production Ltd. | Unclassified | IPv4 | 166 |
| AS209406 | IpWay LLC | Unclassified | IPv4 IPv6 | 156 |
| AS200993 | Yanislav Basiuk | Hosting | IPv4 IPv6 | 95 |
| AS196780 | Russian Systems Ltd | Unclassified | IPv4 | 60 |
| AS199280 | Megapage, LLC | Unclassified | IPv4 | 60 |
| AS204553 | Topmedia LLC. | Unclassified | IPv4 | 60 |
| AS212352 | Reshenie LLC | Unclassified | IPv4 | 60 |
| AS214664 | JSC "F6" | Unclassified | IPv4 | 60 |
| AS205387 | Hybrid LLC | Unclassified | IPv4 | 55 |
Adjacency
Adjacent networks
Every AS seen directly next to AS61400 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 2,755 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,743 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 906 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 300 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 268 |
| AS58045 | Sportivnye Novosti LLC | Unclassified | IPv4 | 240 |
| AS214047 | New Media Production Ltd. | Unclassified | IPv4 | 166 |
| AS209406 | IpWay LLC | Unclassified | IPv4 IPv6 | 156 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 139 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 133 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12: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.