asn.dev

Observed topology

AS13215 CPLUS1-AS JSC Telecommunication company "Convey Plus"

Residential RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS13215: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4205
AS57304JSC "RetnNet"UnclassifiedIPv483
AS31133PJSC MegaFonMobileIPv474
AS12389PJSC RostelecomResidentialIPv462
AS6939Hurricane Electric LLCTransitIPv619
AS62255BiMajLink d.o.o.UnclassifiedIPv415
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv41

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202642CJSC Container terminal Saint-PetersburgUnclassifiedIPv464

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4210
AS12389PJSC RostelecomResidentialIPv494
AS57304JSC "RetnNet"UnclassifiedIPv490
AS31133PJSC MegaFonMobileIPv489
AS202642CJSC Container terminal Saint-PetersburgUnclassifiedIPv464
AS6939Hurricane Electric LLCTransitIPv619
AS62255BiMajLink d.o.o.UnclassifiedIPv417
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv47
AS49673Truenetwork LLCUnclassifiedIPv47

All 12 adjacent →

Provenance

Where this comes from

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