Observed topology

AS58879 Shanghai ruisu network technology co.,LTD

Unclassified APNIC

Upstreams 0 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58879: 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 AS58879 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS132813	HK AISI CLOUD COMPUTING LIMITED	Unclassified	IPv4	443
AS149014	bo jing	Unclassified	IPv4	260
AS150706	Hong Kong Zhengxing Technology Co., Ltd.	Unclassified	IPv4	49
AS208628	ChangLian Network Technology Co.,Limited	Unclassified	IPv4	23
AS206888	HanMing HK Limited	Unclassified	IPv4	20

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	643
AS132813	HK AISI CLOUD COMPUTING LIMITED	Unclassified	IPv4	443
AS149014	bo jing	Unclassified	IPv4	260
AS24482	SG.GS	Hosting	IPv4	83
AS9002	RETN Limited	Unclassified	IPv4	79
AS150706	Hong Kong Zhengxing Technology Co., Ltd.	Unclassified	IPv4	49
AS208628	ChangLian Network Technology Co.,Limited	Unclassified	IPv4	23
AS206888	HanMing HK Limited	Unclassified	IPv4	20
AS154309	Intelligent Cloud Limited	Unclassified	IPv4	10

Provenance

Where this comes from

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