Observed topology

AS328482 SKY TREND NETWORKS LIMITED - SKY TREND NETWORKS LIMITED

Unclassified APNIC

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328482: 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
AS58453	China Mobile International Limited	Unclassified	IPv4	218
AS6939	Hurricane Electric LLC	Transit	IPv4	42
AS328977	Wavex Internet Service Provider LTD	Residential	IPv4	5
AS60171	AFR-IX TELECOM S.A.	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS328953	TAYOCOM	Unclassified	IPv4	61
AS329411	Yala Kenya Limited	Residential	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS58453	China Mobile International Limited	Unclassified	IPv4	279
AS328953	TAYOCOM	Unclassified	IPv4	61
AS6939	Hurricane Electric LLC	Transit	IPv4	42
AS328977	Wavex Internet Service Provider LTD	Residential	IPv4	5
AS60171	AFR-IX TELECOM S.A.	Unclassified	IPv4	2
AS329411	Yala Kenya Limited	Residential	IPv4	1

Provenance

Where this comes from

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