asn.dev

Observed topology

AS18345 SERVERS-AUS-CUST Servers Australia Customers

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18345: 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
AS9280Servers Australia Pty LtdUnclassifiedIPv4349

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS146963STRIKE SYSTEMS PTY LIMITEDUnclassifiedIPv4 IPv6207
AS137841NET360ResidentialIPv4 IPv676
AS136432Bigfish Technology Pty LtdUnclassifiedIPv459
AS149997GreenAnt Networks Pty LtdUnclassifiedIPv459
AS133434Plesi Pty LtdUnclassifiedIPv4 IPv622
AS152699Shockbyte Pty LtdHostingIPv4 IPv66
AS13147610/50 Market StUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9280Servers Australia Pty LtdUnclassifiedIPv4 IPv6788
AS146963STRIKE SYSTEMS PTY LIMITEDUnclassifiedIPv4 IPv6207
AS137841NET360ResidentialIPv4 IPv676
AS136432Bigfish Technology Pty LtdUnclassifiedIPv459
AS149997GreenAnt Networks Pty LtdUnclassifiedIPv459
AS133434Plesi Pty LtdUnclassifiedIPv4 IPv630
AS152699Shockbyte Pty LtdHostingIPv4 IPv66
AS13147610/50 Market StUnclassifiedIPv42

Provenance

Where this comes from

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