asn.dev

Observed topology

AS1301 FR-EDFDPT3 Electricite de France Service National

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS1301: 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
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6251
AS30781Free Pro SASHostingIPv4 IPv6214
AS6939Hurricane Electric LLCTransitIPv4 IPv6103
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv611
AS6696VERIXI SAUnclassifiedIPv410
AS20766Association "Gitoyen"UnclassifiedIPv410
AS24482SG.GSHostingIPv410
AS34927iFog GmbHHostingIPv410
AS9002RETN LimitedUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211310Enedis SAUnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6291
AS30781Free Pro SASHostingIPv4 IPv6238
AS6939Hurricane Electric LLCTransitIPv4 IPv6123
AS211310Enedis SAUnclassifiedIPv4 IPv694
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv613
AS20766Association "Gitoyen"UnclassifiedIPv411
AS24482SG.GSHostingIPv411
AS34927iFog GmbHHostingIPv411
AS6696VERIXI SAUnclassifiedIPv410

Provenance

Where this comes from

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