Observed topology
AS31208 MF-CENTER-AS PJSC MegaFon
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS31208: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 3,206 |
Transit
Downstream networks
Networks for which AS31208 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35479 | ActiveBusinessConsult LLC | Unclassified | IPv4 | 133 |
| AS62461 | JSC "Road Service" | Unclassified | IPv4 | 60 |
| AS213681 | IE Batov Aleksandr Aleksandrovich | Unclassified | IPv4 | 59 |
| AS209794 | Noviy Format TK Ltd. | Unclassified | IPv4 | 48 |
| AS60346 | AO "Sudokhodnaya kompaniya "Volzhskoye parokhodstvo" | Unclassified | IPv4 | 37 |
| AS211714 | BUZ Orlovskoy oblasti MIAC | Unclassified | IPv4 | 29 |
| AS20772 | OOO Kurier | Unclassified | IPv4 | 17 |
| AS197717 | JSC Mikhailovsky GOK im. A.V. Varicheva | Unclassified | IPv4 | 15 |
| AS15370 | Citadel LLC | Unclassified | IPv4 | 12 |
| AS198369 | Consumer Internet Cooperative "Melenki.Net" | Unclassified | IPv4 | 12 |
Adjacency
Adjacent networks
Every AS seen directly next to AS31208 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 3,632 |
| AS35479 | ActiveBusinessConsult LLC | Unclassified | IPv4 | 133 |
| AS62461 | JSC "Road Service" | Unclassified | IPv4 | 60 |
| AS213681 | IE Batov Aleksandr Aleksandrovich | Unclassified | IPv4 | 59 |
| AS209794 | Noviy Format TK Ltd. | Unclassified | IPv4 | 48 |
| AS60346 | AO "Sudokhodnaya kompaniya "Volzhskoye parokhodstvo" | Unclassified | IPv4 | 37 |
| AS211714 | BUZ Orlovskoy oblasti MIAC | Unclassified | IPv4 | 29 |
| AS20772 | OOO Kurier | Unclassified | IPv4 | 17 |
| AS197717 | JSC Mikhailovsky GOK im. A.V. Varicheva | Unclassified | IPv4 | 15 |
| AS15370 | Citadel LLC | Unclassified | IPv4 | 12 |
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.