asn.dev

Observed topology

AS12654 RIPE-NCC-RIS-AS Reseaux IP Europeens Network Coordination Centre RIPE NCC

Unclassified RIPE

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

Transit

Upstream networks

All 87

Networks observed carrying traffic for AS12654: 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 IPv6424
AS35280F5 Networks SARLHostingIPv4 IPv6258
AS9002RETN LimitedUnclassifiedIPv4 IPv6130
AS35487Misaka Network, Inc.UnclassifiedIPv4 IPv6118
AS34019Hivane AssociationUnclassifiedIPv4 IPv681
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv669
AS6461Zayo BandwidthTransitIPv4 IPv668
AS2914NTT America, Inc.TransitIPv4 IPv655
AS58057Securebit AGUnclassifiedIPv4 IPv652
AS612184b42 UGUnclassifiedIPv4 IPv640

All 87 upstreams →

Transit

Downstream networks

inferred

Networks for which AS12654 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 87

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6424
AS35280F5 Networks SARLHostingIPv4 IPv6258
AS9002RETN LimitedUnclassifiedIPv4 IPv6130
AS35487Misaka Network, Inc.UnclassifiedIPv4 IPv6118
AS34019Hivane AssociationUnclassifiedIPv4 IPv681
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv669
AS6461Zayo BandwidthTransitIPv4 IPv668
AS2914NTT America, Inc.TransitIPv4 IPv655
AS58057Securebit AGUnclassifiedIPv4 IPv652
AS612184b42 UGUnclassifiedIPv4 IPv640

All 87 adjacent →

Provenance

Where this comes from

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