asn.dev

Observed topology

AS34659 KEYYO

Unclassified RIPE NSP

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS34659: 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
AS35280F5 Networks SARLHostingIPv4598
AS1299Arelion Sweden ABTransitIPv4 IPv6188
AS6939Hurricane Electric LLCTransitIPv4 IPv6176
AS3356Level 3 Parent, LLCTransitIPv4 IPv6148
AS12844Bouygues Telecom SAUnclassifiedIPv4 IPv662
AS24482SG.GSHostingIPv4 IPv624
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv624
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv624
AS204092Association GRIFONUnclassifiedIPv4 IPv624
AS6696VERIXI SAUnclassifiedIPv422

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13193Keyyo SAUnclassifiedIPv4 IPv61,088
AS201084Generis System Telecom SASUnclassifiedIPv458

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS13193Keyyo SAUnclassifiedIPv4 IPv61,136
AS35280F5 Networks SARLHostingIPv41,127
AS1299Arelion Sweden ABTransitIPv4 IPv6347
AS6939Hurricane Electric LLCTransitIPv4 IPv6338
AS3356Level 3 Parent, LLCTransitIPv4 IPv6274
AS12844Bouygues Telecom SAUnclassifiedIPv4 IPv6119
AS201084Generis System Telecom SASUnclassifiedIPv458
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv648
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv648
AS24482SG.GSHostingIPv4 IPv645

All 16 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.