asn.dev

Observed topology

AS18126 CTCX - Chubu Telecommunications Company, Inc.

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18126: 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.TransitIPv4 IPv61,125
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6794
AS2519ARTERIA Networks CorporationUnclassifiedIPv4732
AS6939Hurricane Electric LLCTransitIPv4556
AS2516KDDI CORPORATIONMobileIPv4 IPv6434
AS24482SG.GSHostingIPv4 IPv665
AS9002RETN LimitedUnclassifiedIPv463
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv662

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS146985KISSEI COMTEC Co.,LtdUnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv61,129
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6796
AS2519ARTERIA Networks CorporationUnclassifiedIPv4735
AS6939Hurricane Electric LLCTransitIPv4556
AS2516KDDI CORPORATIONMobileIPv4 IPv6434
AS24482SG.GSHostingIPv4 IPv666
AS9002RETN LimitedUnclassifiedIPv464
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv663
AS146985KISSEI COMTEC Co.,LtdUnclassifiedIPv412

Provenance

Where this comes from

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