asn.dev

Observed topology

AS8615 CNT-AS Moscow, Russia

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8615: 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 RostelecomResidentialIPv4599

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS21231PJSC AeroflotUnclassifiedIPv4111
AS200515Gruppa Polyplastic LLCUnclassifiedIPv487
AS8904Bank of RussiaUnclassifiedIPv462
AS15934PJSC RostelecomUnclassifiedIPv462
AS48379I.M.Gubkin Russian State University of Oil and GasUnclassifiedIPv462
AS41257SAM-MB LLCUnclassifiedIPv461
AS52096ROSATOM MINERALS JSCUnclassifiedIPv456
AS41029State Historical MuseumUnclassifiedIPv449
AS59412JSC Wuerth RussiaUnclassifiedIPv445
AS58190Network Laboratory, LtdUnclassifiedIPv427

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv41,221
AS21231PJSC AeroflotUnclassifiedIPv4111
AS200515Gruppa Polyplastic LLCUnclassifiedIPv487
AS8904Bank of RussiaUnclassifiedIPv462
AS15934PJSC RostelecomUnclassifiedIPv462
AS48379I.M.Gubkin Russian State University of Oil and GasUnclassifiedIPv462
AS41257SAM-MB LLCUnclassifiedIPv461
AS52096ROSATOM MINERALS JSCUnclassifiedIPv456
AS41029State Historical MuseumUnclassifiedIPv449
AS59412JSC Wuerth RussiaUnclassifiedIPv445

Provenance

Where this comes from

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