asn.dev

Observed topology

AS24904 KWAOO K-Net SAS

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS24904: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv61,056
AS6939Hurricane Electric LLCTransitIPv4 IPv6296
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv635
AS24482SG.GSHostingIPv4 IPv635
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv635
AS48185team.blue NVUnclassifiedIPv4 IPv635
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv635
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv635
AS174Cogent Communications, LLCTransitIPv434
AS293ESnetUnclassifiedIPv434

All 27 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60478K-sys SAUnclassifiedIPv4 IPv696

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv61,094
AS6939Hurricane Electric LLCTransitIPv4 IPv6332
AS60478K-sys SAUnclassifiedIPv4 IPv696
AS24482SG.GSHostingIPv4 IPv637
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv637
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv637
AS33891Core-Backbone GmbHHostingIPv436
AS3303Swisscom (Schweiz) AGResidentialIPv435
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv635
AS6696VERIXI SAUnclassifiedIPv435

All 31 adjacent →

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.