asn.dev

Observed topology

AS205344 TELERYS-ASN

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205344: 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
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv684
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS47160MOJI SASResidentialIPv4 IPv633
AS1299Arelion Sweden ABTransitIPv4 IPv630
AS24482SG.GSHostingIPv4 IPv64
AS204092Association GRIFONUnclassifiedIPv4 IPv64
AS6696VERIXI SAUnclassifiedIPv43
AS12779IT.Gate S.p.A.UnclassifiedIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS39801France IX Services SASUUnclassifiedIPv41

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv684
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS47160MOJI SASResidentialIPv4 IPv633
AS1299Arelion Sweden ABTransitIPv4 IPv630
AS24482SG.GSHostingIPv4 IPv64
AS204092Association GRIFONUnclassifiedIPv4 IPv64
AS6696VERIXI SAUnclassifiedIPv43
AS12779IT.Gate S.p.A.UnclassifiedIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS39801France IX Services SASUUnclassifiedIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10: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.