asn.dev

Observed topology

AS9738 BRENNANIT-AS9738-AP Brennan IT

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9738: 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
AS17898Brennan ITResidentialIPv4 IPv66,583

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS153049Scope Aust LtdUnclassifiedIPv459
AS147313Northline Service Center Pty LtdUnclassifiedIPv458
AS137192BIDFOOD AUSTRALIA LIMITEDUnclassifiedIPv435
AS132049Endeavour FoundationUnclassifiedIPv45

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS17898Brennan ITResidentialIPv4 IPv66,740
AS153049Scope Aust LtdUnclassifiedIPv459
AS147313Northline Service Center Pty LtdUnclassifiedIPv458
AS137192BIDFOOD AUSTRALIA LIMITEDUnclassifiedIPv435
AS132049Endeavour FoundationUnclassifiedIPv45

Provenance

Where this comes from

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