Observed topology

AS152320 GOALNOW-AS-AP GOALNOW NETWORK TECHNOLOGY CO., LIMITED

Unclassified APNIC

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152320: 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
AS17433	Hytron Network Services Limited	Residential	IPv4 IPv6	800
AS137409	GSL Networks Pty LTD	Unclassified	IPv6	209
AS48266	Catixs Ltd	Unclassified	IPv4	134
AS17476	CloudRadium (HK) Limited	Residential	IPv4	74
AS138997	Eons Data Communications Limited	Unclassified	IPv4 IPv6	36
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	14

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS154010	Xi'an WeiShiJi Network Technology LTD	Hosting	IPv4 IPv6	100

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS17433	Hytron Network Services Limited	Residential	IPv4 IPv6	877
AS137409	GSL Networks Pty LTD	Unclassified	IPv6	209
AS48266	Catixs Ltd	Unclassified	IPv4	143
AS154010	Xi'an WeiShiJi Network Technology LTD	Hosting	IPv4 IPv6	100
AS17476	CloudRadium (HK) Limited	Residential	IPv4	79
AS138997	Eons Data Communications Limited	Unclassified	IPv4 IPv6	43
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	16

Provenance

Where this comes from

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