asn.dev

Observed topology

AS400992 ZHOUYISAT-COMMUNICATIONS

Unclassified Spamhaus ASN-DROP ARIN

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 6
Upstream graph Who carries AS400992, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS400992 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS400992: 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.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,418
AS203446SMARTNET Germany GmbHUnclassifiedIPv4 IPv6648
AS49600NEAR IP, S.L.HostingIPv4 IPv6498
AS62563GLOBALTELEHOST Corp.HostingIPv4171
AS49505JSC SelectelHostingIPv458
AS60539Huicast Telecom LimitedUnclassifiedIPv4 IPv649

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50053Anton LevinUnclassifiedIPv4 IPv6566
AS213409Daniil KovalHostingIPv67

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,418
AS203446SMARTNET Germany GmbHUnclassifiedIPv4 IPv61,221
AS50053Anton LevinUnclassifiedIPv4 IPv6566
AS49600NEAR IP, S.L.HostingIPv4 IPv6498
AS62563GLOBALTELEHOST Corp.HostingIPv4171
AS49505JSC SelectelHostingIPv458
AS60539Huicast Telecom LimitedUnclassifiedIPv4 IPv649
AS213409Daniil KovalHostingIPv67

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10: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.