How it works

From readings to a verdict you can check

Your device keeps a running record of its Wi-Fi. nOversight reads that record, works out what it means, and tells you in a sentence, with every reading behind the sentence still there to inspect.

Five steps up, from readings to the story

nOversight brings the readings together so you can see what needs attention and check the evidence behind it.

  1. 1

    Raw metrics

    What the device records as it goes.

    Inside the device Chipset counters and roaming decisions, read from the device’s own logs: live on a Mac, or from a diagnostic capture.

  2. 2

    Signals

    Readings compared with your requirements.

  3. 3

    Events

    Weak patches, roams and slow periods over time.

  4. 4

    Insights

    Related events considered together.

  5. 5

    Story

    A plain summary with the evidence behind it.

Judged against what you need

You set design targets for signal, retries, speed, channel use, roaming and internet response, or start from the Home, Gaming or Enterprise preset. Each category is then marked against those targets at the level you choose: 95% or 99% of readings.

A result can meet your requirement without reaching your preferred target. A category with too few readings says so rather than passing quietly.

Retries and channel use come from the phone’s diagnostic capture.

Where the readings come from

Live on iPhone and iPad

Signal, noise, link rate, channel and access point changes, through the nOversight Shortcut.

The same phone’s diagnostic capture

Adds retries, how busy the channel was and Apple’s own roaming record. Wi-Fi delay depends on the iOS version.

On a Mac

Live readings from the Mac’s own Wi-Fi, or a connected iPhone or iPad.

Analysis runs on your device. Internet speed and response tests contact outside services. nOversight never changes router or access point settings.