asn.dev

Observed topology

AS45809 NZRS-AS-AP ASN for .nz registry content

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45809: 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
AS9790Two Degrees Networks LimitedResidentialIPv4 IPv6314
AS55850Mercury NZ LimitedResidentialIPv4 IPv6122
AS6939Hurricane Electric LLCTransitIPv424
AS64073Vetta GroupUnclassifiedIPv4 IPv611
AS35280F5 Networks SARLHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45285ASN for anycast peeringHostingIPv4 IPv6170

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9790Two Degrees Networks LimitedResidentialIPv4 IPv6439
AS45285ASN for anycast peeringHostingIPv4 IPv6170
AS55850Mercury NZ LimitedResidentialIPv4 IPv6166
AS6939Hurricane Electric LLCTransitIPv424
AS64073Vetta GroupUnclassifiedIPv4 IPv612
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

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