asn.dev

Observed topology

AS51579 CORP-PARTNER-AS Korporatvniy partner Ltd

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51579: 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
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv6193
AS48347JSC Mediasoft ekspertUnclassifiedIPv4 IPv6169
AS34123Netorn LLCUnclassifiedIPv4 IPv632
AS50673Serverius Holding B.V.UnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49863Lite-Telecom LimitedUnclassifiedIPv4 IPv6554

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS49863Lite-Telecom LimitedUnclassifiedIPv4 IPv6554
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4 IPv6449
AS48347JSC Mediasoft ekspertUnclassifiedIPv4 IPv6309
AS34123Netorn LLCUnclassifiedIPv4 IPv6151
AS50673Serverius Holding B.V.UnclassifiedIPv426
AS24482SG.GSHostingIPv4 IPv616
AS37721Virtual Technologies & SolutionsResidentialIPv414
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv414

Provenance

Where this comes from

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