Observed topology

AS133182 RRNTL-AS-AP - Running River Network Technology Limited

Unclassified APNIC

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 11

Adjacent (IPv6) 9

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS133182: 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
AS138915	Kaopu Cloud HK Limited	Hosting	IPv4 IPv6	87
AS38182	Extreme Broadband - Total Broadband Experience	Residential	IPv4	64
AS24482	SG.GS	Hosting	IPv4 IPv6	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS154315	Guangzhou Leidianyun Technology Co Ltd	Unclassified	IPv4 IPv6	89
AS136769	Guangzhou Fengyun Information Technology Co., Ltd.	Unclassified	IPv4 IPv6	4

Adjacency

Adjacent networks

All 12

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

AS	Network	Type	Families	Paths seen
AS154315	Guangzhou Leidianyun Technology Co Ltd	Unclassified	IPv4 IPv6	89
AS138915	Kaopu Cloud HK Limited	Hosting	IPv4 IPv6	87
AS38182	Extreme Broadband - Total Broadband Experience	Residential	IPv4	64
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4 IPv6	59
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	24
AS24482	SG.GS	Hosting	IPv4 IPv6	4
AS136769	Guangzhou Fengyun Information Technology Co., Ltd.	Unclassified	IPv4 IPv6	4
AS17408	AboveNet Communications Taiwan	Unclassified	IPv4 IPv6	3
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4 IPv6	2
AS2914	NTT America, Inc.	Transit	IPv4	1

All 12 adjacent →

Provenance

Where this comes from

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