Observed topology

AS31732 Parsun-Network-Solutions Parsun Network Solutions PTY LTD

Unclassified RIPE

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS136557	Host Universal Pty Ltd	Unclassified	IPv4	96
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	86
AS24482	SG.GS	Hosting	IPv4 IPv6	4
AS64073	Vetta Group	Unclassified	IPv4 IPv6	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS151647	Rural Tech Development	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS136557	Host Universal Pty Ltd	Unclassified	IPv4	143
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	95
AS151647	Rural Tech Development	Unclassified	IPv4	58
AS24482	SG.GS	Hosting	IPv4 IPv6	6
AS64073	Vetta Group	Unclassified	IPv4 IPv6	6
AS49666	Telecommunication Infrastructure Company	Unclassified	IPv4	4
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	1
AS35280	F5 Networks SARL	Hosting	IPv4	1

Provenance

Where this comes from

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