Observed topology

AS13378 QINGYE-CLOUD - Qingye Cloud

Hosting ARIN

Upstreams 3 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13378: 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
AS138997	Eons Data Communications Limited	Unclassified	IPv4 IPv6	151
AS17433	Hytron Network Services Limited	Residential	IPv4	121
AS49612	DDOS-GUARD LTD	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS63567	Suqian Pugongying Network Service Co.,Ltd	Unclassified	IPv4	290

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS55933	Cloudie Limited	Hosting	IPv4	564
AS17433	Hytron Network Services Limited	Residential	IPv4	384
AS63658	Jangsu Bangrun Network Technology Co.,Ltd.	Unclassified	IPv4	354
AS63567	Suqian Pugongying Network Service Co.,Ltd	Unclassified	IPv4	290
AS400612	Qingye	Unclassified	IPv4	156
AS138997	Eons Data Communications Limited	Unclassified	IPv4 IPv6	151
AS201674	Wen ZhangYu	Unclassified	IPv4	114
AS50131	Spartan Host Ltd	Unclassified	IPv4	89
AS153911	DuoTu Cloud	Unclassified	IPv4	2
AS49612	DDOS-GUARD LTD	Unclassified	IPv4	1

Provenance

Where this comes from

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