Observed topology
AS64050 BGNL-HK - BGP Network Limited
Hosting Spamhaus ASN-DROP APNIC Network Services
Transit
Upstream networks
Networks observed carrying traffic for AS64050: 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 |
|---|---|---|---|---|
| AS4766 | Korea Telecom | Mobile | IPv4 | 1,572 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 1,485 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,307 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 775 |
| AS7473 | Singapore Telecommunications Ltd | Unclassified | IPv4 | 616 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 337 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 101 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 | 96 |
| AS55720 | Gigabit Hosting Sdn Bhd | Hosting | IPv4 | 93 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 85 |
Transit
Downstream networks
Networks for which AS64050 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS138995 | Antbox Networks Limited | Hosting | IPv4 | 1,308 |
| AS398823 | PEG TECH INC | Hosting | IPv4 | 981 |
| AS139923 | ABCCLOUD SDN.BHD. | Unclassified | IPv4 | 971 |
| AS210528 | Navox co.,Ltd | Unclassified | IPv4 | 838 |
| AS398478 | PEG TECH INC | Unclassified | IPv4 | 813 |
| AS394432 | PEG TECH INC | Unclassified | IPv4 | 797 |
| AS25820 | IT7 Networks Inc | Hosting | IPv4 | 589 |
| AS48589 | Tiger Network Limited | Unclassified | IPv4 | 588 |
| AS138968 | rainbow network limited | Unclassified | IPv4 | 527 |
| AS398993 | PEG TECH INC | Unclassified | IPv4 | 376 |
Adjacency
Adjacent networks
Every AS seen directly next to AS64050 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 4,072 |
| AS4766 | Korea Telecom | Mobile | IPv4 | 3,434 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 2,881 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 1,877 |
| AS138995 | Antbox Networks Limited | Hosting | IPv4 | 1,354 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 1,069 |
| AS48589 | Tiger Network Limited | Unclassified | IPv4 | 1,052 |
| AS399195 | PEG TECH INC | Unclassified | IPv4 | 1,017 |
| AS398823 | PEG TECH INC | Hosting | IPv4 | 981 |
| AS139923 | ABCCLOUD SDN.BHD. | Unclassified | IPv4 | 971 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.