asn.dev

Observed topology

AS23918 NTTIP-AS-AP NTT Australia Solutions Pty Ltd

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23918: 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 IPv6535
AS1221Telstra LimitedMobileIPv4 IPv6154
AS24482SG.GSHostingIPv4 IPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18117NTT Australia Solutions Pty LtdUnclassifiedIPv4313
AS133045NSW Electricity Networks Operations Pty LimitedUnclassifiedIPv4 IPv6176
AS24061NTT Australia Pty LtdUnclassifiedIPv4146
AS55845Tradeweb Australia Pty LtdUnclassifiedIPv446
AS23760Xpedite SystemsUnclassifiedIPv436
AS132299Applied Satellite Technology Australia Pty LtdUnclassifiedIPv432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6950
AS1221Telstra LimitedMobileIPv4 IPv6535
AS18117NTT Australia Solutions Pty LtdUnclassifiedIPv4327
AS133045NSW Electricity Networks Operations Pty LimitedUnclassifiedIPv4 IPv6217
AS24061NTT Australia Pty LtdUnclassifiedIPv4146
AS55845Tradeweb Australia Pty LtdUnclassifiedIPv446
AS23760Xpedite SystemsUnclassifiedIPv436
AS132299Applied Satellite Technology Australia Pty LtdUnclassifiedIPv432
AS24482SG.GSHostingIPv4 IPv610

Provenance

Where this comes from

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