asn.dev

Observed topology

AS18117 NTTIP-AS-AP NTT Australia Solutions Pty Ltd

Unclassified APNIC Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18117: 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
AS23918NTT Australia Solutions Pty LtdUnclassifiedIPv4313
AS2914NTT America, Inc.TransitIPv4231
AS6939Hurricane Electric LLCTransitIPv484
AS38561NTT Australia Solutions Pty LtdHostingIPv428
AS2764AAPT LimitedUnclassifiedIPv421
AS7575Australian Academic and Research Network (AARNet)EducationIPv49
AS24482SG.GSHostingIPv49
AS64073Vetta GroupUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136804Wireless Innovation Pty LtdUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23918NTT Australia Solutions Pty LtdUnclassifiedIPv4327
AS2914NTT America, Inc.TransitIPv4264
AS6939Hurricane Electric LLCTransitIPv493
AS136804Wireless Innovation Pty LtdUnclassifiedIPv459
AS38561NTT Australia Solutions Pty LtdHostingIPv428
AS2764AAPT LimitedUnclassifiedIPv421
AS7575Australian Academic and Research Network (AARNet)EducationIPv410
AS24482SG.GSHostingIPv410
AS64073Vetta GroupUnclassifiedIPv410

Provenance

Where this comes from

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