Skip to main content

AS17435

ONENZ-AS-AP

ASN for Trusted Partner Peering

Registry

Authoritative registration data

AS number
17435
Name
ONENZ-AS-AP
Organisation
ASN for Trusted Partner Peering
Country
Flag of New Zealand NZ New Zealand
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS17435
118.90.0.0/16 IPv4 /16 not checked
182.154.0.0/16 IPv4 /16 not checked
58.28.0.0/16 IPv4 /16 not checked
2001:e20::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS17435
Address families
APE 1,000 Mbps IPv4 · IPv6
WIX-NZ 100 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS17435 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS17435 in AS paths

Observed upstreams
Families
AS9500 ONENZ-TRANSIT-AS 292 1,243
v4 v6
AS64073 VETTA 1 3
v4
AS4768 ONENZ-INET-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS17435 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS61138 ZAPPIE-HOST-AS 1 3
v4
AS132847 NETSG-AS-AP 1 3
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.