asn.dev

Observed topology

AS45018 RIPN-RU-VLV Join-stock company "Internet Exchange"MSK-IX"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45018: 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
AS12389PJSC RostelecomResidentialIPv4 IPv6134
AS3316Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv458
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv657

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42385Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv695
AS41740Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv414
AS43832Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6154
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6150
AS42385Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv695
AS3316Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv458
AS41740Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv414
AS43832Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv47
AS25091IP-Max SAUnclassifiedIPv4 IPv63

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.