asn.dev

Observed topology

AS9328 DATACOM-AU DATACOM SYSTEMS AU PTY LTD

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9328: 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
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv62,339
AS6939Hurricane Electric LLCTransitIPv4 IPv6449
AS7474SingTel Optus Pty LtdUnclassifiedIPv4 IPv6139
AS24482SG.GSHostingIPv4 IPv638
AS64073Vetta GroupUnclassifiedIPv4 IPv69
AS24115EquinixHostingIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17562Datacom Systems (NSW)UnclassifiedIPv4660

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4826Vocus Connect International BackboneUnclassifiedIPv4 IPv63,167
AS17562Datacom Systems (NSW)UnclassifiedIPv4937
AS6939Hurricane Electric LLCTransitIPv4 IPv6457
AS7474SingTel Optus Pty LtdUnclassifiedIPv4 IPv6237
AS24482SG.GSHostingIPv4 IPv639
AS64073Vetta GroupUnclassifiedIPv4 IPv610
AS24115EquinixHostingIPv47

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.