Ookla Speed Test in NZ: How to Use Speedtest.net and Read Your Results

Ookla’s Speedtest is the test most people run when the internet feels slow, and the one most likely to be quoted back at a provider. It is a good tool, but it answers a narrower question than people think, and from New Zealand its result depends heavily on which server it picks. This guide explains how it works here, why its numbers differ from the Chorus test and the Commerce Commission’s figures, and how to get a result you can act on.

How Speedtest.net works from New Zealand

When you open speedtest.net or the Speedtest app, Ookla picks a nearby host from its network of volunteer servers — in New Zealand that usually means one run by a provider or data centre in Auckland, Wellington or Christchurch. It then opens several connections at once and measures how much data moves in a few seconds, reporting download, upload, ping and, in the apps, jitter and packet loss.

Two design choices matter. Multiple parallel connections mean Speedtest shows the ceiling of your line rather than what a single download achieves. And a server on your own provider’s network sits one hop away, so the ping and speed it reports can be better than what you get to the wider internet. Neither is wrong; they are just measuring something specific.

Ookla, Chorus and Cloudflare compared

Results within about ten per cent of each other are normal. If Ookla says 500 Mbps and the Cloudflare test says 480 Mbps, nothing is wrong. If Ookla says 500 Mbps and everything else says 90 Mbps, Ookla has found a server inside your provider’s network and the rest of the internet is reaching you through a slower path — worth mentioning when you call.

What your plan should show

The Commerce Commission’s Report 28, from tests in April 2026, gives these national averages. A well-run Ookla test on a wired connection should land close to them or a little above.

If your plan is Fibre 500 and Ookla reports 94 Mbps over a cable, something in the chain is limited to 100 Mbps — an old switch, a powerline adapter, a cable. If it reports 300 Mbps, check whether Chorus’s June 2025 upgrade of the 300/100 plan to 500/100 has been applied by your provider. Our fibre speeds guide covers each tier.

Getting a result you can trust

1. Wired, not Wi-Fi. Over Wi-Fi you are testing your modem’s radio, not the connection. Wi-Fi 5 hardware rarely passes 300 Mbps in a real room. To measure the Wi-Fi itself, use our Wi-Fi speed test guide.
2. Choose the server deliberately. Tap the server name and pick one in your nearest city that is not your own provider, then run a second test on your provider’s server. The gap between them is informative.
3. Nothing else running. A 4K stream takes 25 Mbps; a console update takes everything.
4. Test at peak. Between 7pm and 11pm is when congestion shows. Fibre barely changes; fixed wireless drops around a fifth.
5. Repeat three times and keep the results. Screenshots with the server name and time are what a provider’s support team wants to see.

Reading ping, jitter and loss in the app

Ookla’s apps report latency in three states: idle, during download and during upload. The idle number is your baseline — 5 to 8 ms on fibre to a local server. The loaded numbers show how much the connection degrades under use, which is what causes a video call to break up while someone else downloads. A big jump under load points to a modem with no traffic management or an upload allowance being saturated. Our ping test guide goes deeper on latency, including why Sydney adds about 30 ms and Los Angeles about 140 ms regardless of your plan.

Packet loss above one per cent on a wired fibre connection is a fault, not a tuning problem. Check the fibre box — our Chorus ONT guide explains the lights — and if the LOS light is red or flashing, log it with your provider rather than re-testing.

What to do with a bad result

Work through the causes in order rather than calling straight away: our guide to slow internet starts with the one-minute checks and ends with the network fault. If the wired result matches your plan and the problem is only in certain rooms, the extender and mesh guide is the fix. And if the connection is fine but a single service is slow, that service is the bottleneck — a speed test cannot tell you anything about it. Our main speed test guide compares the tools side by side.

Frequently asked questions

Is Ookla Speedtest accurate in New Zealand?

Yes for what it measures: the maximum your line delivers to a nearby server over several connections at once. Run it wired, pick the server deliberately, and compare it with a second test before drawing conclusions.

Which Speedtest server should I choose in NZ?

One in your nearest main city. Run it once on a server outside your own provider’s network and once on your provider’s server; if only the provider’s server is fast, the bottleneck is upstream of them.

Why is Speedtest faster than my actual downloads?

Speedtest uses several parallel connections and a nearby server. A single download from an overseas site is limited by that site and by distance, so it will usually be slower than the test.

What speed should Fibre 500 show on Speedtest?

About 500 to 520 Mbps down and 100 to 110 Mbps up on a wired test. Over Wi-Fi, considerably less, depending on the modem.

Why does Ookla show a different result from the Chorus test?

Different servers and different methods. Chorus tests to its own server; Ookla to a volunteer host, often on your provider’s network. Results within ten per cent are normal.

Does the Speedtest app measure packet loss?

The mobile and desktop apps report jitter and packet loss alongside loaded latency; the website version reports ping and speed only.