asn.dev

Observed topology

AS205369 IYOROY-NETWORK

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205369: 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
AS34927iFog GmbHHostingIPv661
AS6939Hurricane Electric LLCTransitIPv637
AS52025ParadoxNetworks LimitedUnclassifiedIPv634
AS20473The Constant Company, LLCHostingIPv631
AS199829Akronic Network LTDAUnclassifiedIPv68
AS41051Openfactory GmbHUnclassifiedIPv66
AS47272HYEHOST LLCHostingIPv65
AS357084b42 UGUnclassifiedIPv64
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv62
AS205794JINZE YANGUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197817Nyco Cloud Network LLCUnclassifiedIPv671

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6110
AS197817Nyco Cloud Network LLCUnclassifiedIPv673
AS34927iFog GmbHHostingIPv661
AS52025ParadoxNetworks LimitedUnclassifiedIPv634
AS20473The Constant Company, LLCHostingIPv631
AS199829Akronic Network LTDAUnclassifiedIPv68
AS41051Openfactory GmbHUnclassifiedIPv66
AS47272HYEHOST LLCHostingIPv65
AS357084b42 UGUnclassifiedIPv64
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv62

All 11 adjacent →

Provenance

Where this comes from

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