Observed topology

AS24545 HKTEL-AS-AP 8F.,Sino Favour Centre ,1 OnYip StreetChaiWan

Unclassified APNIC

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

Upstream graph Who carries AS24545, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS24545 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24545: 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
AS140570	Hong Kong Beecloud System Technology Services Limited	Hosting	IPv4	440
AS4635	Hong Kong Internet Exchange--Route Server 1	Unclassified	IPv4	83
AS45250	Vocom International Telecommunications AP Area	Hosting	IPv4	42
AS24482	SG.GS	Hosting	IPv4	9
AS9930	TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia	Unclassified	IPv4	8

Transit

Downstream networks

inferred

Networks for which AS24545 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS58932	Palau Mobile Communications Inc.	Unclassified	IPv4	118

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS24545 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS140570	Hong Kong Beecloud System Technology Services Limited	Hosting	IPv4	486
AS58932	Palau Mobile Communications Inc.	Unclassified	IPv4	118
AS45250	Vocom International Telecommunications AP Area	Hosting	IPv4	98
AS4635	Hong Kong Internet Exchange--Route Server 1	Unclassified	IPv4	96
AS24482	SG.GS	Hosting	IPv4	11
AS9930	TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia	Unclassified	IPv4	9

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.