Observed topology
AS205369 iYoRoy-Network LI YIRAN
Unclassified RIPE Educational/Research
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 92 |
| AS34927 | iFog GmbH | Hosting | IPv6 | 47 |
| AS41051 | Openfactory GmbH | Unclassified | IPv6 | 21 |
| AS20473 | The Constant Company, LLC | Hosting | IPv6 | 9 |
| AS52025 | ParadoxNetworks Limited | Unclassified | IPv6 | 9 |
| AS35708 | 4b42 UG | Unclassified | IPv6 | 4 |
| AS47272 | HYEHOST LLC | Hosting | IPv6 | 4 |
| AS205794 | JINZE YANG | Unclassified | IPv6 | 3 |
Transit
Downstream networks
Networks for which AS205369 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197817 | Nyco Cloud Network LLC | Unclassified | IPv6 | 140 |
Adjacency
Adjacent networks
Every AS seen directly next to AS205369 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 295 |
| AS197817 | Nyco Cloud Network LLC | Unclassified | IPv6 | 206 |
| AS34927 | iFog GmbH | Hosting | IPv6 | 47 |
| AS41051 | Openfactory GmbH | Unclassified | IPv6 | 21 |
| AS20473 | The Constant Company, LLC | Hosting | IPv6 | 9 |
| AS52025 | ParadoxNetworks Limited | Unclassified | IPv6 | 9 |
| AS47272 | HYEHOST LLC | Hosting | IPv6 | 7 |
| AS35708 | 4b42 UG | Unclassified | IPv6 | 4 |
| AS205794 | JINZE YANG | Unclassified | IPv6 | 3 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.