asn.dev

Observed topology

AS18081 KCN - Kintetsu Cable Network Co., Ltd.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18081: 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 IPv61,334
AS4637Telstra GlobalUnclassifiedIPv4 IPv6354
AS6939Hurricane Electric LLCTransitIPv4342
AS2516KDDI CORPORATIONMobileIPv4 IPv6110
AS24482SG.GSHostingIPv4 IPv639
AS17639Converge ICT Solutions Inc.UnclassifiedIPv438
AS20485Joint Stock Company TransTeleComUnclassifiedIPv438
AS9002RETN LimitedUnclassifiedIPv4 IPv623

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS10011advanscope inc.ResidentialIPv4 IPv629

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv61,334
AS4637Telstra GlobalUnclassifiedIPv4 IPv6370
AS6939Hurricane Electric LLCTransitIPv4342
AS2516KDDI CORPORATIONMobileIPv4 IPv6123
AS24482SG.GSHostingIPv4 IPv639
AS17639Converge ICT Solutions Inc.UnclassifiedIPv438
AS20485Joint Stock Company TransTeleComUnclassifiedIPv438
AS10011advanscope inc.ResidentialIPv4 IPv629
AS9002RETN LimitedUnclassifiedIPv4 IPv623

Provenance

Where this comes from

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