Observed topology

AS38819 HKCSL-AS-AP HKCSL GPRS NETWORK

Residential APNIC Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38819: 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
AS4760	HKT Limited	Residential	IPv4 IPv6	3,711
AS4635	Hong Kong Internet Exchange--Route Server 1	Unclassified	IPv4	537
AS9930	TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia	Unclassified	IPv4	69
AS24482	SG.GS	Hosting	IPv4	69
AS8359	MTS PJSC	Mobile	IPv4	62

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS9444	Hong Kong Telecommunications (HKT) Limited	Unclassified	IPv4	1,642

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4760	HKT Limited	Residential	IPv4 IPv6	5,161
AS9444	Hong Kong Telecommunications (HKT) Limited	Unclassified	IPv4	1,642
AS4635	Hong Kong Internet Exchange--Route Server 1	Unclassified	IPv4	668
AS9930	TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia	Unclassified	IPv4	93
AS24482	SG.GS	Hosting	IPv4	93
AS8359	MTS PJSC	Mobile	IPv4	75

Provenance

Where this comes from

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