asn.dev

Observed topology

AS23783 CNA Cable Networks Akita Co.,ltd.

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23783: 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
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6611
AS2516KDDI CORPORATIONMobileIPv4 IPv6225
AS6939Hurricane Electric LLCTransitIPv4 IPv6190
AS2518BIGLOBE Inc.ResidentialIPv457
AS17676SoftBank Corp.MobileIPv4 IPv656
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv621
AS20485Joint Stock Company TransTeleComUnclassifiedIPv419

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18266Cable Networks Akita Co.,ltd.UnclassifiedIPv4 IPv6217
AS131953NPO YutopianetUnclassifiedIPv4151

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6835
AS2516KDDI CORPORATIONMobileIPv4 IPv6308
AS18266Cable Networks Akita Co.,ltd.UnclassifiedIPv4 IPv6260
AS6939Hurricane Electric LLCTransitIPv4 IPv6241
AS131953NPO YutopianetUnclassifiedIPv4151
AS2518BIGLOBE Inc.ResidentialIPv475
AS17676SoftBank Corp.MobileIPv4 IPv671
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv628
AS20485Joint Stock Company TransTeleComUnclassifiedIPv425

Provenance

Where this comes from

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