Oceania routing coverage

New Zealand Proxies

7,517+ residential and mobile proxy IPs in New Zealand. City-level geo-targeting, rotating and sticky sessions, HTTP, HTTPS & SOCKS5. Plans from $0.90/GB.

Pay as you go from 1 GB. Dataset updated June 2026; live availability varies by network type.

Oceania relay chain

  1. Australia458,747
  2. Fiji11,572
  3. New Caledonia11,212
  4. French Polynesia8,191
  5. Papua New Guinea7,904
  6. New Zealand7,517
  7. Vanuatu6,860
  8. American Samoa6,401

17 ASNs published for New Zealand.

Published Oceania pool counts from the locations dataset, updated . Live availability can change.
7,517+
Published IPs in New Zealand
2
Live network types
17
Autonomous systems
#6
Pool rank in Oceania
7,517+ published IPs in New Zealand99.9%+ uptime targetCountry, city, GPS & ASN targetingHTTP, HTTPS & SOCKS5Databay Trust Center
Live coverage

New Zealand network coverage

The proxy networks reported for New Zealand, with global catalogue size, network origin, and volume-plan entry price.

  • ISP-origin IPs for authorized regional sampling and workflows that require a consumer-network route.

    Global pool
    34M+ IPs
    Network origin
    ISP-classified
    From
    $0.90/GB (1 TB plan)
  • 4G and 5G carrier-network IPs for authorized app testing and mobile-network checks.

    Global pool
    800K+ IPs
    Network origin
    Mobile carrier
    From
    $2.50/GB (512 GB plan)

A network shows as Live only when it is currently serving traffic in New Zealand. Global pool sizes are catalog-wide; browse the live community proxy list for New Zealand to sample real endpoints.

Geo-targeting

Target New Zealand down to the city and ASN

Set countryCode-nz in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.

  • Country routing

    One flag, countryCode-nz, requests an exit geolocated to New Zealand, subject to live availability.

  • City, ZIP & GPS requests

    Request a narrower residential location, then verify the observed exit because live supply and geolocation can vary.

  • ASN targeting request

    Request an autonomous system by AS number, subject to network support and current eligible exits.

  • Rotating or sticky

    Request gateway-selected exits or a sticky target up to 120 minutes; connections and availability affect reuse.

  • Country, city, ZIP, GPS, and ASN targeting included on every plan
  • Gateway-selected exits or sticky session targets, subject to availability
  • HTTP, HTTPS, and SOCKS5 on one gateway, no allowlisting
  • Every flag set in the proxy username, no code changes

Sample of 17 autonomous systems covered in New Zealand

  • AS56030 VOYAGERNET-AS-AP Voyager Internet Ltd.
  • AS58610 TELNET-AS-AP Telnet Telecommunication Limited
  • AS132449 WIRELESSNATION-NZ Wireless Nation
  • AS132815 EWL-AS-AP Evolution Wireless Ltd
  • AS133192 UBB-AS-AP Ultimate Mobile limited
  • AS4768 ONENZ-INET-AS One New Zealand Group Limited
  • AS4771 SPARKNZ Spark New Zealand Trading Ltd.
  • AS9500 ONENZ-TRANSIT-AS One New Zealand Group Limited
  • AS9790 TWO-DEGREES-AS-AP Two Degrees Networks Limited
  • AS17705 INSPIRENET-AS-AP InSPire Net Ltd
  • AS23655 TWODEGREES-NZ-AS 2degrees Networks Limited
  • AS45177 DEVOLI-AS-AP Devoli

Select any country, city, or AS number directly in the proxy username. ASN availability varies by network type and real-time device counts.

# Rotating residential proxy in New Zealand
curl -x http://USER-zone-residential-countryCode-nz:PASS@gw.databay.co:8888 \
     https://databay.com/cdn-cgi/trace

# Sticky session (30 minutes) in New Zealand
curl -x http://USER-zone-residential-countryCode-nz-sessionId-abc123:PASS@gw.databay.co:8888 \
     https://databay.com/cdn-cgi/trace

# Datacenter proxy in New Zealand
curl -x http://USER-zone-datacenter-countryCode-nz:PASS@gw.databay.co:8888 \
     https://databay.com/cdn-cgi/trace

Pricing for New Zealand: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include country targeting for New Zealand at no extra cost. See documentation.

Network performance

Network-wide operating targets for New Zealand routes

These catalogue-wide figures describe the service target, not a country-specific guarantee. Measure the exact route and workload before relying on it.

Uptime target
99.9%+
Network-wide availability
Residential latency
~1.1s
Median response time
Datacenter latency
~780ms
Median response time
Max sticky target
120 min
Subject to live exit availability

Latency and uptime are network-wide medians and targets. See how Databay benchmarks its network.

Field guide

Need rotating IPs with city and ASN targeting? Get residential proxies in New Zealand (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for New Zealand (refreshed every 5 minutes).

Reading the published New Zealand address count

Databay's June 9, 2026 paid-network catalogue assigns 7,517 addresses to New Zealand. That places New Zealand number 153 of 195 locations worldwide and number 6 of 8 in Oceania. The New Zealand allocation represents <0.05% of the global catalogue and 1.5% of the Oceania total. For New Zealand, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The New Zealand count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live New Zealand coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. New Zealand pricing is determined by network and plan rather than by inflating the country count into a performance promise.

Build a controlled New Zealand location test

The gateway flag countryCode-nz requests an exit geolocated to New Zealand, subject to current supply and the selected network. For New Zealand, it changes one input: the apparent network origin seen by the destination. An exit geolocated to New Zealand does not set a browser language, currency, time zone, delivery address, tax jurisdiction, account country, cookie history, device profile, or legal eligibility. For a useful comparison involving New Zealand, write down the hypothesis first and hold those other inputs constant. Check the New Zealand exit with a diagnostic endpoint you trust, save the timestamp and effective settings, and compare the observation with a direct or controlled reference. If city, ZIP, coordinate, or ASN precision in New Zealand matters, validate that narrower result separately; country success does not prove subnational accuracy.

Plan New Zealand sessions from the actual pool scale

New Zealand has a limited but material published allocation. Design New Zealand work for repeat exits: pace requests, use sticky sessions for multi-step authorized flows, and avoid multiplying concurrency merely because the gateway can rotate. If a narrow New Zealand filter returns no suitable exit, broaden the test or stop rather than claiming unavailable coverage. New Zealand pool depth also cannot authorize collection: the destination's terms, robots guidance, contracts, authentication boundaries, rate controls, and applicable law remain the controlling constraints. Treat a block, CAPTCHA, quota, or explicit denial as a stop or review signal across the whole New Zealand pool rather than rotating around it. Record New Zealand failures as data; do not hide them with unlimited retries.

New Zealand in its Oceania comparison set

The immediately larger Oceania catalogue entry than New Zealand is Papua New Guinea at 7,904 addresses, and the next smaller is Vanuatu at 6,860. In the New Zealand comparison set, the regional leader is Australia with 458,747. These New Zealand capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose New Zealand when the research question specifically needs a network-origin observation from New Zealand. Choose a different country from New Zealand only when it is a valid control or a separate market in the study. Combining New Zealand observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested New Zealand route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.

A reproducible New Zealand validation checklist

Before using a New Zealand result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-nz setting; the observed exit IP, ASN, and geolocation source; the browser, account, language, currency, address, cookie, and device state; and the UTC timestamp plus response evidence. Repeat the New Zealand check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential New Zealand price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This New Zealand workflow makes the 7,517-address catalogue figure useful as coverage context without pretending it proves a resident's experience.

New Zealand proxies

Frequently asked questions

How many proxy IPs does Databay have in New Zealand?
Databay offers 7,517+ residential and mobile proxy IPs in New Zealand, with city-level and ASN geo-targeting.
What types of proxies are available in New Zealand?
Databay provides residential and mobile proxies in New Zealand, all with rotating and sticky sessions over HTTP, HTTPS, and SOCKS5.
Which networks and ASNs are covered in New Zealand?
Coverage in New Zealand spans 17 autonomous systems across 2 network types, selectable by ASN in the proxy username.
How do I authenticate with Databay proxies?
Authentication is by username and password over the gateway. Country, city, ASN, and session are all selected with flags in the username, so no IP allowlisting is required.
Which protocols are supported?
HTTP, HTTPS, and SOCKS5 are supported on the same gateway, with both rotating and sticky sessions.
Is there an API?
Yes. Proxies are delivered through a single gateway endpoint; pool, geo, and session are controlled entirely through the username flags, so any HTTP client or scraping framework works unchanged.
How do I get started?
Create an account, choose a plan, and the dashboard issues gateway credentials you can use immediately.
Do you offer reseller or volume plans?
Yes. Volume and reseller pricing is available for larger commitments. Contact sales for a quote.

Start using New Zealand proxies

Review live New Zealand coverage and access the published pool under the selected plan and service limits.

Pricing, order minimums, and traffic validity vary by product.