asn.dev

Observed topology

AS9993 CTC-ODC ITOCHU Techno-Solutions Corporation

Hosting RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9993: 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 IPv6400
AS6939Hurricane Electric LLCTransitIPv4 IPv696
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4 IPv646
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610
AS20485Joint Stock Company TransTeleComUnclassifiedIPv49
AS9002RETN LimitedUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS38654INES Corporation.UnclassifiedIPv4296
AS55390Tokyo University of ScienceUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6620
AS38654INES Corporation.UnclassifiedIPv4296
AS6939Hurricane Electric LLCTransitIPv4 IPv6137
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4 IPv674
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615
AS20485Joint Stock Company TransTeleComUnclassifiedIPv49
AS55390Tokyo University of ScienceUnclassifiedIPv43
AS9002RETN LimitedUnclassifiedIPv61

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.