asn.dev

Observed topology

AS8985 MSK-IX_SERVICES

Unclassified RIPE

Upstreams 7 carry this network
Downstreams 30 this network carries
Adjacent (IPv4) 37
Adjacent (IPv6) 18
Upstream graph Who carries AS8985, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS8985 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6330
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6301
AS8359MTS PJSCMobileIPv4 IPv6231
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv4187
AS24482SG.GSHostingIPv4 IPv620
AS9002RETN LimitedUnclassifiedIPv415
AS49673Truenetwork LLCUnclassifiedIPv415

Transit

Downstream networks

All 30

Networks for which AS8985 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS3316Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv61,716
AS204582"The Technical center of Internet" Limited Liability CompanyUnclassifiedIPv4 IPv61,514
AS61992Internet Identification Center Limited Liability CompanyUnclassifiedIPv4 IPv6684
AS21416"The Technical center of Internet" Limited Liability CompanyUnclassifiedIPv4 IPv6558
AS61043Multifunctional Telecommunications Systems LTDUnclassifiedIPv4406
AS62261Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv6367
AS42385Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv6215
AS43832Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv6185
AS199070State Intitution "Resources of Yamala"UnclassifiedIPv4168
AS56564Webmaster Agency LtdUnclassifiedIPv4156

Adjacency

Adjacent networks

All 37

Every AS seen directly next to AS8985 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv62,959
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv62,258
AS3316Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv62,146
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv41,766
AS204582"The Technical center of Internet" Limited Liability CompanyUnclassifiedIPv4 IPv61,662
AS8359MTS PJSCMobileIPv4 IPv61,550
AS61992Internet Identification Center Limited Liability CompanyUnclassifiedIPv4 IPv6684
AS21416"The Technical center of Internet" Limited Liability CompanyUnclassifiedIPv4 IPv6558
AS61043Multifunctional Telecommunications Systems LTDUnclassifiedIPv4464
AS62261Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv6367

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.