Observed topology
AS10111 ZEONET-AS-AP Zeofast Network
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS10111: 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 | IPv4 IPv6 | 595 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 303 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 302 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 278 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 60 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 59 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 19 |
| AS18013 | ASLINE LIMITED | Hosting | IPv4 | 16 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 11 |
| AS17676 | SoftBank Corp. | Mobile | IPv4 | 10 |
Transit
Downstream networks
Networks for which AS10111 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7720 | Skywolf Technology LLC | Unclassified | IPv4 IPv6 | 339 |
| AS7003 | GNET INC. | Unclassified | IPv4 | 289 |
| AS153929 | Allied Business Inc. | Unclassified | IPv4 | 263 |
| AS393446 | AlphaCore Network LLC | Unclassified | IPv4 | 174 |
| AS205610 | Huanjie Zhu | Unclassified | IPv4 IPv6 | 156 |
| AS33403 | HEIYO CLOUD CORP. | Unclassified | IPv4 | 153 |
| AS146961 | NEXET LIMITED | Hosting | IPv4 | 115 |
| AS14927 | TeraTeams Inc | Unclassified | IPv4 | 114 |
| AS132707 | NEXET LIMITED | Unclassified | IPv4 | 58 |
| AS154402 | Fredyun Network | Unclassified | IPv4 | 57 |
Adjacency
Adjacent networks
Every AS seen directly next to AS10111 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7720 | Skywolf Technology LLC | Unclassified | IPv4 IPv6 | 3,101 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,459 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 1,493 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 900 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 575 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 363 |
| AS7003 | GNET INC. | Unclassified | IPv4 | 289 |
| AS153929 | Allied Business Inc. | Unclassified | IPv4 | 263 |
| AS393446 | AlphaCore Network LLC | Unclassified | IPv4 | 174 |
| AS205610 | Huanjie Zhu | Unclassified | IPv4 IPv6 | 156 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.