asn.dev

Observed topology

AS205684 ALGATHIA

Unclassified RIPE NSP

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS205684: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6128
AS6939Hurricane Electric LLCTransitIPv4 IPv643
AS39801France IX Services SASUUnclassifiedIPv4 IPv610
AS9002RETN LimitedUnclassifiedIPv64
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv64
AS12779IT.Gate S.p.A.UnclassifiedIPv43
AS20766Association "Gitoyen"UnclassifiedIPv43
AS33891Core-Backbone GmbHHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211854MEOWAN SASUUnclassifiedIPv4 IPv693
AS212783Gaetan FerezUnclassifiedIPv4 IPv672
AS209843LEONIX EVENTS SASUnclassifiedIPv459
AS210349Lurot AlexisUnclassifiedIPv4 IPv64

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6264
AS211854MEOWAN SASUUnclassifiedIPv4 IPv693
AS6939Hurricane Electric LLCTransitIPv4 IPv686
AS212783Gaetan FerezUnclassifiedIPv4 IPv672
AS209843LEONIX EVENTS SASUnclassifiedIPv459
AS39801France IX Services SASUUnclassifiedIPv4 IPv621
AS9002RETN LimitedUnclassifiedIPv611
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68

Provenance

Where this comes from

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