asn.dev

Observed topology

AS400619 AROSS-AS - AROSSCLOUD INC.

Unclassified DROP-listed space ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS400619: 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
AS2914NTT America, Inc.TransitIPv414,440
AS3491PCCW Global (HK) Ltd.TransitIPv44,910
AS8796FASTNET DATA INCHostingIPv42,716
AS3223Voxility LLPHostingIPv4171
AS10099China Unicom GlobalUnclassifiedIPv419

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138644FASTMOS CO., LIMITEDUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv414,444
AS3491PCCW Global (HK) Ltd.TransitIPv44,910
AS8796FASTNET DATA INCHostingIPv42,716
AS3223Voxility LLPHostingIPv4171
AS10099China Unicom GlobalUnclassifiedIPv419
AS138644FASTMOS CO., LIMITEDUnclassifiedIPv44

Provenance

Where this comes from

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