asn.dev

Observed topology

AS9297 COLOCITY-AS-AP Colocity Pty Ltd

Hosting APNIC Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9297: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6150
AS6939Hurricane Electric LLCTransitIPv4 IPv636
AS149515ChannelCo.UnclassifiedIPv424
AS24482SG.GSHostingIPv4 IPv64
AS64073Vetta GroupUnclassifiedIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135425CaznetResidentialIPv4181
AS148968Falcore Investments Pty LtdUnclassifiedIPv4 IPv6114
AS55419ASN for Advam Pty LtdUnclassifiedIPv450

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6509
AS135425CaznetResidentialIPv4223
AS148968Falcore Investments Pty LtdUnclassifiedIPv4 IPv6127
AS6939Hurricane Electric LLCTransitIPv4 IPv658
AS55419ASN for Advam Pty LtdUnclassifiedIPv450
AS149515ChannelCo.UnclassifiedIPv437
AS24482SG.GSHostingIPv4 IPv67
AS64073Vetta GroupUnclassifiedIPv4 IPv67

Provenance

Where this comes from

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