Observed topology
AS17433 HNSL-AS-AP - Hytron Network Services Limited
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS17433: 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 | 13 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv6 | 12 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv6 | 6 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv6 | 1 |
| AS24482 | SG.GS | Hosting | IPv6 | 1 |
| AS44324 | MoeDove LLC | Residential | IPv6 | 1 |
| AS56755 | Securebit AG | Unclassified | IPv6 | 1 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS17433 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202662 | Hytron Network Services Limited | Unclassified | IPv4 IPv6 | 4,475 |
| AS61112 | AKILE LTD | Unclassified | IPv4 IPv6 | 4,071 |
| AS215355 | ALICE NETWORKS LTD | Unclassified | IPv4 IPv6 | 2,234 |
| AS151407 | Hytron Network Services Limited | Unclassified | IPv4 IPv6 | 1,565 |
| AS401434 | Hytron Network Services (US) LLC | Unclassified | IPv4 IPv6 | 1,131 |
| AS152320 | GOALNOW NETWORK TECHNOLOGY CO., LIMITED | Unclassified | IPv4 IPv6 | 835 |
| AS211759 | Miku Network Technology Limited | Unclassified | IPv4 IPv6 | 739 |
| AS153371 | BACK WAVES LIMITED | Residential | IPv4 IPv6 | 662 |
| AS36530 | IDC Cube | Unclassified | IPv4 IPv6 | 635 |
| AS210738 | Peng Chen | Unclassified | IPv6 | 630 |
Adjacency
Adjacent networks
Every AS seen directly next to AS17433 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 8,632 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 7,044 |
| AS202662 | Hytron Network Services Limited | Unclassified | IPv4 IPv6 | 6,075 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 5,708 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 4,433 |
| AS61112 | AKILE LTD | Unclassified | IPv4 IPv6 | 4,325 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 4,034 |
| AS154648 | TermRat Network Limited | Unclassified | IPv4 IPv6 | 2,777 |
| AS215355 | ALICE NETWORKS LTD | Unclassified | IPv4 IPv6 | 2,234 |
| AS36530 | IDC Cube | Unclassified | IPv4 IPv6 | 2,069 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.