asn.dev

Observed topology

AS51973 KOLT-AS Koltushsky Internet Ltd

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51973: 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 LLCUnclassifiedIPv476
AS20764CJSC RASCOMUnclassifiedIPv4 IPv674
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201511ScPA Starline LLCUnclassifiedIPv4 IPv672
AS49954Progress Technology LLCUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4114
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6109
AS201511ScPA Starline LLCUnclassifiedIPv4 IPv672
AS49954Progress Technology LLCUnclassifiedIPv46
AS62255BiMajLink d.o.o.UnclassifiedIPv45
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv42

Provenance

Where this comes from

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