Support

Probably not. That pattern usually means the problem is at the far end, not at yours. NetHelper deliberately tests five independent services so you can tell those apart.

If one is poor and four are healthy, your connection is fine and that one service is having a bad day. If all five are poor, the problem is on your side — your Wi-Fi, your router, or your provider.

These measure different things, and the difference is the whole point.

A speed test measures how much data you can move in a burst. NetHelper measures how much of it arrives. A connection can pull a fast number and still drop traffic steadily — which is exactly what makes calls choppy and video blocky while every speed test you run looks reassuring.

Both numbers are right; they describe different stretches of the journey.

The Connectivity tab shows the link speed between your device and your router — often well over a gigabit on modern Wi-Fi. Your internet plan governs the next leg, from the router out to the world. The smaller of the two is what you actually get.

That location is worked out from your public IP address, and it points at wherever your provider routes that address — which can be a town or two away, or a different city entirely.

It is not your device's GPS location, and NetHelper never asks for that. If you use a VPN, you'll see the VPN's location instead, which is a useful way to confirm the VPN is actually doing its job.

By design, that tab only lists connections that are actually in use. An iPhone on Wi-Fi with no VPN shows one row, not four empty ones.

If something you expect is missing, it isn't active right now — worth knowing in itself when you thought the VPN was connected.

Run a check, then use the share button. NetHelper hands the report to the standard iOS share sheet, so it goes anywhere you'd normally send a file: Messages, Mail, Slack, or saved to Files.

The report travels straight from your device to whoever you send it to. It doesn't pass through us, and we never see it.

No. It doesn't collect, log, store or share any personal information, analytics or usage data. There's no account and nothing to opt out of.

The full detail, including the one piece of infrastructure involved, is in the privacy policy.

• Run the check twice. A single bad run can be a passing blip.
• Move closer to the router and run it again — if the ratings improve, it's Wi-Fi coverage, not your provider.
• Turn Wi-Fi off and run it on cellular. If cellular is healthy, the problem is in your home network.
• Turn off any VPN and retest. A VPN routes everything through another network, and its problems become yours.
• Restart the router if every target is poor. It fixes more than it should.

If none of that changes the picture, send us a report from a bad run and we'll read it.

Purchases go through Apple, so refunds do too. Request one at reportaproblem.apple.com and Apple handles it directly.

We'd rather fix the problem than lose you over it, so tell us what went wrong either way — it's the only way the app gets better.

Yes, and they get read by the person who writes the code. NetHelper exists because network tools are built for network engineers; if something in it still needs explaining, that's a bug in the design and we want to hear about it.