asn.dev

Observed topology

AS25540 ALPHALINK-AS

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS25540: 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
AS1299Arelion Sweden ABTransitIPv4 IPv62,306
AS2914NTT America, Inc.TransitIPv4 IPv61,231
AS6939Hurricane Electric LLCTransitIPv4 IPv6803
AS33891Core-Backbone GmbHHostingIPv4162
AS24482SG.GSHostingIPv4 IPv687
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv687
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv687
AS6696VERIXI SAUnclassifiedIPv481
AS12779IT.Gate S.p.A.UnclassifiedIPv481
AS20766Association "Gitoyen"UnclassifiedIPv481

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202381Tel@ndCloud, S.A.S.UnclassifiedIPv4177
AS202757PLT Connectic SARLUnclassifiedIPv4175

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,472
AS2914NTT America, Inc.TransitIPv4 IPv61,317
AS6939Hurricane Electric LLCTransitIPv4 IPv6855
AS202381Tel@ndCloud, S.A.S.UnclassifiedIPv4177
AS202757PLT Connectic SARLUnclassifiedIPv4175
AS33891Core-Backbone GmbHHostingIPv4174
AS24482SG.GSHostingIPv4 IPv693
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv693
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv693
AS6696VERIXI SAUnclassifiedIPv487

All 15 adjacent →

Provenance

Where this comes from

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