asn.dev

Observed topology

AS5410 BOUYGTEL-ISP Bouygues Telecom SA

Residential RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS5410: 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 IPv6455
AS1299Arelion Sweden ABTransitIPv4 IPv6343
AS9002RETN LimitedUnclassifiedIPv4 IPv6128
AS174Cogent Communications, LLCTransitIPv4 IPv6124
AS3320Deutsche Telekom AGMobileIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv622
AS34019Hivane AssociationUnclassifiedIPv4 IPv622
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv622
AS3303Swisscom (Schweiz) AGResidentialIPv420
AS8551Bezeq International Ltd.UnclassifiedIPv420

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12844Bouygues Telecom SAUnclassifiedIPv41,258

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS12844Bouygues Telecom SAUnclassifiedIPv4 IPv62,626
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,300
AS1299Arelion Sweden ABTransitIPv4 IPv6934
AS174Cogent Communications, LLCTransitIPv4 IPv6418
AS9002RETN LimitedUnclassifiedIPv4 IPv6296
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv6165
AS33891Core-Backbone GmbHHostingIPv4155
AS24482SG.GSHostingIPv4 IPv6128
AS12552GlobalConnect ABUnclassifiedIPv4118
AS8551Bezeq International Ltd.UnclassifiedIPv4116

All 18 adjacent →

Provenance

Where this comes from

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