Observed topology
AS45960 YTLCOMMS-AS-AP YTL COMMUNICATIONS SDN BHD
Mobile APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS45960: 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 | 3,226 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 2,016 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 IPv6 | 179 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 106 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 103 |
| AS55720 | Gigabit Hosting Sdn Bhd | Hosting | IPv4 | 92 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 69 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 36 |
| AS132132 | MyRepublic Ltd. | Residential | IPv4 | 36 |
| AS132354 | CELCOM TIMUR (SABAH) SDN BHD | Unclassified | IPv4 | 30 |
Transit
Downstream networks
Networks for which AS45960 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 AS45960 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,287 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 2,156 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 IPv6 | 236 |
| AS154170 | YTL AI Cloud Sdn Bhd | Unclassified | IPv4 | 118 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 109 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 103 |
| AS14789 | Cloudflare, Inc. | Unclassified | IPv4 IPv6 | 97 |
| AS55720 | Gigabit Hosting Sdn Bhd | Hosting | IPv4 | 94 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 69 |
| AS138996 | Uni Comms International Sdn Bhd | Unclassified | IPv4 | 48 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.