asn.dev

Observed topology

AS401783 TOKALA-COMMUNICATIONS

Unclassified DROP-listed space ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS401783: 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
AS135377UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDUnclassifiedIPv415,363
AS984OCTOPUS WEB SOLUTION INCHostingIPv44,836
AS21859Zenlayer IncHostingIPv42,382
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv42,313
AS20473The Constant Company, LLCHostingIPv4480
AS139327UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDUnclassifiedIPv4333

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS135377UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDUnclassifiedIPv415,363
AS984OCTOPUS WEB SOLUTION INCHostingIPv44,836
AS21859Zenlayer IncHostingIPv42,382
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv42,313
AS20473The Constant Company, LLCHostingIPv4480
AS139327UCLOUD INFORMATION TECHNOLOGY (HK) LIMITEDUnclassifiedIPv4333

Provenance

Where this comes from

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