asn.dev

Observed topology

AS51273 AS-SKYNET-UA FOP Lizanchuk Yaroslav M.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51273: 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
AS35297Dataline LLCUnclassifiedIPv490
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv666
AS34867Cosmonova LLCUnclassifiedIPv458
AS28917Fiord Networks, UABUnclassifiedIPv457
AS3255LLC EKSINTECHUnclassifiedIPv447
AS50263A-Systems Sp. z o.o.UnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42195CS "AIST"UnclassifiedIPv428

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv490
AS28917Fiord Networks, UABUnclassifiedIPv485
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv666
AS34867Cosmonova LLCUnclassifiedIPv458
AS3255LLC EKSINTECHUnclassifiedIPv447
AS42195CS "AIST"UnclassifiedIPv428
AS50263A-Systems Sp. z o.o.UnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv41

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.