Observed topology
AS207529 NyanLoliNetwork NYANLOLI LTD
Unclassified RIPE Educational/Research
Transit
Upstream networks
Networks observed carrying traffic for AS207529: 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 | 169 |
| AS11967 | Hop179 OU | Unclassified | IPv6 | 38 |
| AS139317 | Ningbo Dahuamao Information Technology Co Ltd | Education | IPv6 | 37 |
| AS204211 | Shanghai Yingyun Network Technology Co., Ltd. | Unclassified | IPv6 | 36 |
| AS204539 | Axivora Connect Ltd | Residential | IPv6 | 33 |
| AS47778 | Sunoaki Network LLC | Unclassified | IPv6 | 29 |
| AS174 | Cogent Communications, LLC | Transit | IPv6 | 9 |
| AS199310 | XIN BING XIAN | Hosting | IPv6 | 9 |
| AS24482 | SG.GS | Hosting | IPv6 | 8 |
| AS44324 | MoeDove LLC | Residential | IPv6 | 7 |
Transit
Downstream networks
Networks for which AS207529 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS207529 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 326 |
| AS204211 | Shanghai Yingyun Network Technology Co., Ltd. | Unclassified | IPv6 | 61 |
| AS216299 | Yang Liuchang | Unclassified | IPv6 | 59 |
| AS210352 | Yijia Xu | Residential | IPv6 | 47 |
| AS11967 | Hop179 OU | Unclassified | IPv6 | 38 |
| AS139317 | Ningbo Dahuamao Information Technology Co Ltd | Education | IPv6 | 37 |
| AS210176 | Haoyi Xiang | Unclassified | IPv6 | 37 |
| AS204539 | Axivora Connect Ltd | Residential | IPv6 | 33 |
| AS47778 | Sunoaki Network LLC | Unclassified | IPv6 | 29 |
| AS174 | Cogent Communications, LLC | Transit | IPv6 | 14 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.