How it works

Your experience, measured where it happens.

A test from someone else's server measures their path. NetLucid runs on your device, over the route, resolver, proxy and Wi-Fi your own apps use, so the result describes the connection you actually have.

Experience first

Tests replay what your device really does. They use the system route, the DNS resolver your device is set to use (you can choose another), any proxy in the way and the Wi-Fi you are on. Nothing is borrowed from a lab setup.

Results are plain answers with the evidence underneath: what was measured, from where, at what time, and what the test could not see. Missing data is shown as missing, never filled in.

  1. You start a test. Nothing runs in the background on its own.
  2. It runs on your device, over your own route, resolver, proxy and Wi-Fi.
  3. You read the result, with its limits stated, and Share it if you want to.

Two ways to measure

On-demand tests

A point-in-time test you start: one check, one answer. Most tools work this way.

Bounded watch sessions

For problems that come and go. You start a session of a set length, and it tells you up front what it will cost in time, battery, mobile data and storage. When the time is up, it stops. Gaps in coverage are recorded as gaps, and the main result is a list of the incidents it saw.

On iPhone and iPad a session runs only while the app is on screen.

No always-on monitoring. There is no background mode, on any platform, that keeps measuring after a session ends.

What stays with you

There is no account and no sign-up. Results stay on your device; Standard keeps nothing after you close the result, and Advanced saves on your device only. See Privacy for what the app may contact.