Observed topology

AS17898 Brennan IT

Residential APNIC

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 5

Upstream graph Who carries AS17898, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS17898 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17898: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS9738	Brennan IT	Unclassified	IPv4 IPv6	6,581

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS9738	Brennan IT	Unclassified	IPv4 IPv6	6,738
AS7474	SingTel Optus Pty Ltd	Unclassified	IPv4	5,267
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	1,011
AS38195	Superloop	Unclassified	IPv4	127
AS24482	SG.GS	Hosting	IPv4 IPv6	111
AS64073	Vetta Group	Unclassified	IPv4 IPv6	111
AS24115	Equinix	Hosting	IPv4	110
AS35280	F5 Networks SARL	Hosting	IPv6	1

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.