Observed topology

AS141721 Asia Satellite Telecommunications Co. Ltd.

Unclassified APNIC

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141721: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS141735	Core Interconnection	Unclassified	IPv4 IPv6	261

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS141735	Core Interconnection	Unclassified	IPv4 IPv6	317
AS2914	NTT America, Inc.	Transit	IPv4	127
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	99
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	51
AS4637	Telstra Global	Unclassified	IPv4	26
AS4635	Hong Kong Internet Exchange--Route Server 1	Unclassified	IPv4	7
AS24482	SG.GS	Hosting	IPv4 IPv6	5
AS8359	MTS PJSC	Mobile	IPv4	2

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-06 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.