asn.dev

Observed topology

AS25152 K-ROOT-SERVER Reseaux IP Europeens Network Coordination Centre RIPE NCC

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

All 74

Networks observed carrying traffic for AS25152: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv659
AS1103SURF B.V.UnclassifiedIPv4 IPv611
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS61461Airtek Solutions C.A.UnclassifiedIPv4 IPv610
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv610
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv69
AS1403EBOXResidentialIPv4 IPv68
AS2914NTT America, Inc.TransitIPv48
AS11170Roller Network LLCHostingIPv48
AS32098Transtelco IncUnclassifiedIPv4 IPv68

All 74 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 74

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv659
AS1103SURF B.V.UnclassifiedIPv4 IPv611
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS61461Airtek Solutions C.A.UnclassifiedIPv4 IPv610
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv610
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv69
AS1403EBOXResidentialIPv4 IPv68
AS2914NTT America, Inc.TransitIPv48
AS11170Roller Network LLCHostingIPv48
AS32098Transtelco IncUnclassifiedIPv4 IPv68

All 74 adjacent →

Provenance

Where this comes from

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