asn.dev

Observed topology

AS8304 ECRITEL-FRANCE ISP and web hosting.

Hosting RIPE NSP

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

Transit

Upstream networks

All 43

Networks observed carrying traffic for AS8304: 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 IPv61,257
AS174Cogent Communications, LLCTransitIPv4 IPv6436
AS6461Zayo BandwidthTransitIPv4243
AS6939Hurricane Electric LLCTransitIPv4 IPv6171
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv676
AS22652Videotron LteeResidentialIPv472
AS5511Orange S.A.TransitIPv4 IPv664
AS24482SG.GSHostingIPv4 IPv621
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv621
AS1836green.ch AGResidentialIPv4 IPv620

All 43 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197914Ecritel SASUUnclassifiedIPv4 IPv6162
AS197138Owliance SASUnclassifiedIPv4118
AS32555Centre de Recherche Informatique de MontrealUnclassifiedIPv46

Adjacency

Adjacent networks

All 46

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,364
AS174Cogent Communications, LLCTransitIPv4 IPv6476
AS6461Zayo BandwidthTransitIPv4243
AS6939Hurricane Electric LLCTransitIPv4 IPv6198
AS197914Ecritel SASUUnclassifiedIPv4 IPv6162
AS197138Owliance SASUnclassifiedIPv4118
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv687
AS5511Orange S.A.TransitIPv4 IPv680
AS22652Videotron LteeResidentialIPv478
AS24482SG.GSHostingIPv4 IPv625

All 46 adjacent →

Provenance

Where this comes from

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