Observed topology
AS8985 MSK-IX_SERVICES
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8985: 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 |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 330 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 301 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 231 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 187 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 20 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 15 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 15 |
Transit
Downstream networks
Networks for which AS8985 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3316 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 1,716 |
| AS204582 | "The Technical center of Internet" Limited Liability Company | Unclassified | IPv4 IPv6 | 1,514 |
| AS61992 | Internet Identification Center Limited Liability Company | Unclassified | IPv4 IPv6 | 684 |
| AS21416 | "The Technical center of Internet" Limited Liability Company | Unclassified | IPv4 IPv6 | 558 |
| AS61043 | Multifunctional Telecommunications Systems LTD | Unclassified | IPv4 | 406 |
| AS62261 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 367 |
| AS42385 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 215 |
| AS43832 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 185 |
| AS199070 | State Intitution "Resources of Yamala" | Unclassified | IPv4 | 168 |
| AS56564 | Webmaster Agency Ltd | Unclassified | IPv4 | 156 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8985 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 2,959 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 2,258 |
| AS3316 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 2,146 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 1,766 |
| AS204582 | "The Technical center of Internet" Limited Liability Company | Unclassified | IPv4 IPv6 | 1,662 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 1,550 |
| AS61992 | Internet Identification Center Limited Liability Company | Unclassified | IPv4 IPv6 | 684 |
| AS21416 | "The Technical center of Internet" Limited Liability Company | Unclassified | IPv4 IPv6 | 558 |
| AS61043 | Multifunctional Telecommunications Systems LTD | Unclassified | IPv4 | 464 |
| AS62261 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 IPv6 | 367 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.