asn.dev

Observed topology

AS51520 RH "Datalogika" Ltd.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51520: 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
AS31500Global Network Management IncUnclassifiedIPv494
AS5467Non state educational institution "Educational Scientific and Experimental Center of Moscow Institute of Physics and Technology"EducationIPv412
AS6939Hurricane Electric LLCTransitIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49828LLC DARNETUnclassifiedIPv4240
AS51017STOLICA LLCUnclassifiedIPv4120

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS31500Global Network Management IncUnclassifiedIPv4400
AS49828LLC DARNETUnclassifiedIPv4240
AS51017STOLICA LLCUnclassifiedIPv4120
AS6939Hurricane Electric LLCTransitIPv454
AS5467Non state educational institution "Educational Scientific and Experimental Center of Moscow Institute of Physics and Technology"EducationIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv48

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.