asn.dev

Observed topology

AS15401 EOLAS-AS

Unclassified RIPE NSP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS15401: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6938
AS6939Hurricane Electric LLCTransitIPv4 IPv6177
AS3215Orange S.A.MobileIPv4 IPv670
AS174Cogent Communications, LLCTransitIPv457
AS6696VERIXI SAUnclassifiedIPv423
AS34927iFog GmbHHostingIPv419
AS204092Association GRIFONUnclassifiedIPv419
AS33891Core-Backbone GmbHHostingIPv411
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42970Mezcalito SCOP-SARLUnclassifiedIPv4 IPv6211
AS60595Neptune Internet Services SASUnclassifiedIPv4 IPv6154

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,176
AS6939Hurricane Electric LLCTransitIPv4 IPv6229
AS42970Mezcalito SCOP-SARLUnclassifiedIPv4 IPv6211
AS60595Neptune Internet Services SASUnclassifiedIPv4 IPv6154
AS3215Orange S.A.MobileIPv4 IPv6107
AS174Cogent Communications, LLCTransitIPv463
AS6696VERIXI SAUnclassifiedIPv426
AS204092Association GRIFONUnclassifiedIPv4 IPv624
AS34927iFog GmbHHostingIPv422
AS24482SG.GSHostingIPv4 IPv615

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