Observed topology

AS13378 QINGYE-CLOUD

Hosting ARIN Cable/DSL/ISP

Upstreams 2 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

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	76
AS17433	Hytron Network Services Limited	Residential	IPv4	57

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	278
AS151640	Bengbu Qingye Technology	Unclassified	IPv4	60
AS139874	Wu'an Chihong Network Technology Co., Ltd.	Unclassified	IPv4	57

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS17433	Hytron Network Services Limited	Residential	IPv4	294
AS63567	Suqian Pugongying Network Service Co.,Ltd	Unclassified	IPv4	278
AS55933	Cloudie Limited	Hosting	IPv4	193
AS400612	Qingye	Unclassified	IPv4	186
AS138997	Eons Data Communications Limited	Unclassified	IPv4 IPv6	133
AS50131	Spartan Host Ltd	Unclassified	IPv4	94
AS151640	Bengbu Qingye Technology	Unclassified	IPv4	60
AS139874	Wu'an Chihong Network Technology Co., Ltd.	Unclassified	IPv4	57

Provenance

Where this comes from

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