Observed topology

AS9294 GNETINC-AS-AP - GNET INC.

Unclassified APNIC

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9294: 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
AS2914	NTT America, Inc.	Transit	IPv4	8,462
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	3,358
AS18013	ASLINE LIMITED	Hosting	IPv4	3,271
AS9002	RETN Limited	Unclassified	IPv4	401
AS22427	GNET INC.	Unclassified	IPv4	50
AS58453	China Mobile International Limited	Unclassified	IPv4	15
AS23764	CTGNet	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS22427	GNET INC.	Unclassified	IPv4	1,864

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS2914	NTT America, Inc.	Transit	IPv4	9,313
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	3,665
AS18013	ASLINE LIMITED	Hosting	IPv4	3,271
AS22427	GNET INC.	Unclassified	IPv4	1,914
AS9002	RETN Limited	Unclassified	IPv4	1,107
AS58453	China Mobile International Limited	Unclassified	IPv4	15
AS23764	CTGNet	Unclassified	IPv4	1

Provenance

Where this comes from

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