asn.dev

Observed topology

AS212372 COOLNET-AS COOLNET LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS212372: 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
AS3255LLC EKSINTECHUnclassifiedIPv4378
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv4 IPv6125
AS35297Dataline LLCUnclassifiedIPv4 IPv668
AS15895"Kyivstar" PJSCMobileIPv4 IPv628
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv620
AS24482SG.GSHostingIPv4 IPv611
AS49824PC "Astra-net"ResidentialIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv49
AS49673Truenetwork LLCUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210327FOP Hordiiuk Petro VasulyovuchUnclassifiedIPv49

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3255LLC EKSINTECHUnclassifiedIPv4378
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv4 IPv6125
AS35297Dataline LLCUnclassifiedIPv4 IPv672
AS15895"Kyivstar" PJSCMobileIPv4 IPv628
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv622
AS49824PC "Astra-net"ResidentialIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv611
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS49673Truenetwork LLCUnclassifiedIPv410
AS210327FOP Hordiiuk Petro VasulyovuchUnclassifiedIPv49

Provenance

Where this comes from

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