Reading the results¶
Open the status window (or run acutis-go -status) and you get a single, plain-English verdict plus the readings behind it.
The verdict¶
Acutis Go reduces everything to one answer:
| Verdict | Meaning |
|---|---|
| Healthy | It's not the network, and it's not the machine. |
| Network | The problem is outside the machine — the path, gateway, DNS, or Wi-Fi. |
| Machine | The problem is local — drivers, disk, NIC, or certificates. |
Confidence¶
Next to the verdict is a confidence score (for example, confidence 95%). It reflects how strongly the current readings support the verdict. This is the single number shown consistently across the status window, the fleet dashboard, and the support page — there is no separate "health score."
The readings¶
Each row shows an identifier on the left and its metric on the right:
| Row | What it tells you |
|---|---|
| Gateway | Your router's address and whether the path to it is up. |
| DNS | DNS lookup time and which DNS server is being used — a bad resolver is often the real culprit. |
| Wi-Fi | The network name (SSID) and signal/security state, when on wireless. |
| Public IP | Your outside (WAN) address as the internet sees it. |
| Latency | Round-trip time along the path. |
| Machine | Driver, disk, and NIC error counts over the last 24 hours. |
| Certs | Whether any local certificates are expiring soon. |
Status window vs. command line¶
- Status window — the friendly desktop view, with the verdict, confidence, support code, and rows. Best for end users.
acutis-go -status— the same readout in the terminal. Works fully offline and is great for scripts, SSH sessions, and headless machines.
Both compute the verdict locally, so you get an answer even with no internet.