asn.dev

Observed topology

AS204818 HOSTEUR-NET-CORE Hosteur NETWORK CORE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204818: 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
AS34177Celeste SASResidentialIPv4 IPv6162
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6151
AS6461Zayo BandwidthTransitIPv4 IPv6140
AS174Cogent Communications, LLCTransitIPv4 IPv6129
AS3356Level 3 Parent, LLCTransitIPv4 IPv6121
AS21351Canal + Telecom SASMobileIPv4118
AS8554TAS France SASUnclassifiedIPv459
AS207758Hosteur SAUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48809Hosteur SASUnclassifiedIPv455

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34177Celeste SASResidentialIPv4 IPv6169
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6163
AS6461Zayo BandwidthTransitIPv4 IPv6153
AS174Cogent Communications, LLCTransitIPv4 IPv6138
AS3356Level 3 Parent, LLCTransitIPv4 IPv6135
AS21351Canal + Telecom SASMobileIPv4118
AS8554TAS France SASUnclassifiedIPv459
AS48809Hosteur SASUnclassifiedIPv455
AS207758Hosteur SAUnclassifiedIPv45

Provenance

Where this comes from

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