asn.dev

Observed topology

AS41653 AQUARAY

Hosting RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS41653: 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
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6200
AS8309SIPARTECH SASUnclassifiedIPv4 IPv6178
AS55002F5, Inc.UnclassifiedIPv4 IPv6105
AS6939Hurricane Electric LLCTransitIPv470
AS35280F5 Networks SARLHostingIPv434
AS24482SG.GSHostingIPv4 IPv612
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv612
AS204092Association GRIFONUnclassifiedIPv4 IPv611
AS12779IT.Gate S.p.A.UnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61025CoCCA Registry Services (NZ) LimitedUnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6258
AS8309SIPARTECH SASUnclassifiedIPv4 IPv6178
AS55002F5, Inc.UnclassifiedIPv4 IPv6105
AS61025CoCCA Registry Services (NZ) LimitedUnclassifiedIPv4 IPv695
AS6939Hurricane Electric LLCTransitIPv478
AS35280F5 Networks SARLHostingIPv4 IPv652
AS24482SG.GSHostingIPv4 IPv614
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv614
AS204092Association GRIFONUnclassifiedIPv4 IPv613
AS12779IT.Gate S.p.A.UnclassifiedIPv411

All 15 adjacent →

Provenance

Where this comes from

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