Home / User guide
User guide

From “my Internet is bad” to a useful next step.

Use the guided Check for a complete diagnosis and reports. Use Live Monitoring when the issue is intermittent and you want to watch the current connection.

In this guide

1. Before a check2. Choose what you notice3. Simple and Technical4. Full Check5. Live Monitoring6. History7. Reports8. Privacy and analytics9. Limits

1. Before a check

Go to the place where the problem normally happens and keep the intended Wi-Fi or mobile connection active. A full Check is intended to describe one active connection during one measured window, so avoid deliberately switching links while it runs.

  1. Use the same place and connection where the problem occurs.
  2. Start the check and let the measurement window finish.
  3. Avoid changing several settings during the run.
  4. When the app suggests an action, change one thing and retest.

2. Choose what you notice

The first dialog asks what you are experiencing: for example general slowness, slow startup, downloads/uploads, delayed responses, buffering, call breakup or other predefined categories. Choose the symptom, not a guessed technical cause.

Symptom-led startNo free-text symptom is required for the controlled diagnostic category.

3. Simple and Technical

The compact Simple/Technical switch stays in the header throughout the app. Simple mode prioritizes the conclusion and next action. Technical mode exposes the score contribution and the underlying evidence without changing the completed run.

Path and actionSee what was measured and what to try first.
Technical score evidenceSee where points were reduced and the confidence interval around the final score.

4. Full Check

A full Check is the finite diagnostic workflow. It can examine Wi-Fi/mobile radio, Phone → Router where measurable, end-to-end and decomposed Internet paths, configured DNS, regional references, common service setup, readiness estimates and security/integrity indicators.

Score is not the diagnosis by itself. Read the primary finding and component evidence. A historical Watch does not, by itself, hard-cap the current Connection Health result.
  1. Start from Check.
  2. Select the symptom category.
  3. Let the test finish without changing the intended connection.
  4. Read the conclusion, score and first recommended action.
  5. Retest after one change and compare the relevant component.

5. Live Monitoring

Live Monitoring is a separate user-started session for intermittent problems. It can run for up to 90 minutes and keeps current quality separate from longer session evidence.

  • Current delay, jitter and packet-loss cards focus on the recent monitoring window.
  • The session graph and counters build over time so outages and changing conditions are easier to see.
  • Wi-Fi and mobile network changes are recorded as separate connection sessions instead of being blended into one network.
  • If you minimise the app or lock the screen, an ongoing Android notification keeps the user-started monitoring session visible and provides a way back to the app or to stop it.
  • When you stop, Diagnostix360 can create a compact Live Monitoring result summarising the session.
Live MonitoringReal app screen with the private Wi-Fi name replaced by a generic example.

6. History

History compares completed full Checks. When comparable runs exist, it can show score trends and repeated observations for the same network context. Historical information is context: a repeated Watch is not treated as a confirmed current fault unless the current evidence supports that conclusion.

7. Reports

The Reports area offers two audiences from a completed full Check.

Customer report

A concise one-page result intended to omit sensitive technical identifiers. It shows the health score and plain-language connection-path status.

Technical report

The detailed evidence package for an ISP, IT team or advanced troubleshooting. Depending on the report privacy settings, it can contain active network name, IP/ISP/ASN information, DNS/resolver addresses, approximate area, nearby Wi-Fi information, traceroute details, mobile operator/cell information and exact timestamps.

  1. Choose the completed run.
  2. Select Customer or Technical report.
  3. Preview the report.
  4. For a sensitive Technical report, accept the in-app acknowledgement only when the recipient is trusted.
  5. Share only the minimum detail required.

8. Privacy and analytics

There are two separate optional controls:

  • Diagnostic Data Sharing can upload an allow-listed measurement summary plus a random app-installation UUID used for distinct-installation statistics, deduplication and abuse protection. It excludes raw IP addresses, location fields, Wi-Fi names, BSSID/MAC, cell identity, nearby-network identities and the full per-second timeline.
  • Usage Analytics can enable Google Analytics for Firebase for broad product events. Diagnostix360 does not add raw diagnostic measurements, score values, ISP/ASN, report IDs, Wi-Fi/cell identifiers, GPS coordinates or its diagnostic installation UUID to Firebase event parameters. Firebase uses its own app-instance identifier and standard service data when Analytics is enabled.

Both choices can be changed independently in Settings. If a diagnostic Privacy ID already exists, turning Diagnostic Data Sharing off stops future uploads but keeps the ID locally so you can use it for a later access/deletion request. Core diagnostic lookups such as public-IP/profile, DNS and test-target requests can still occur when sharing is off because they are part of the diagnosis you start. See the Privacy Policy.

9. What the results do — and do not — mean

  • A result describes a measured window, not every moment before or after it.
  • A healthy result does not guarantee that an intermittent problem will not occur later.
  • A weak radio reading is context, not proof that radio conditions caused the observed symptom.
  • A failed or delayed ICMP probe does not, by itself, prove packet loss or which organization is responsible.
  • Readiness scores estimate path suitability; they do not run a real game, call or video session.
  • Diagnostix360 is not a certified test instrument, security audit or SLA recorder.