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

1. Before a check

Diagnose the connection you actually care about. If the problem happens on Wi-Fi, stay on that Wi-Fi. If it happens on mobile data, start on mobile data. Avoid deliberately switching links while a diagnosis is running because the result is intended to describe one active connection.

1. Go to the place where the problem occurs.
2. Confirm the intended connection is active.
3. Start the check and let the measurement window finish.
4. Avoid large changes to the device or connection during the run.

2. Simple mode

Simple mode is the default experience. The bottom navigation is organised around Check, History, Reports and Tools.

Read the result in this order: the overall message, the health score, the first suggested action, then the “What we checked” rows. A green row means that part of the measured window looked normal. Amber means it deserves another look. Red means the measured evidence indicates a problem.

3. Technical mode

Use the Simple/Technical switch at the top of the app. Technical mode exposes the detailed workspace and the underlying evidence rather than changing the completed run itself. Its bottom navigation is organised around Details, Monitor and Reports.

Technical measurements can include radio strength and stability, phone-to-router response, Internet-path response, configured website-address lookup performance, regional route evidence, service setup evidence, readiness estimates, security/integrity indicators and other supporting measurements available to the device.

4. Retest correctly

When the app recommends an action, change one thing at a time. That makes the next run easier to interpret.

1. Note the original score and main finding.
2. Perform only the first suggested action.
3. Return to the same location unless the action itself is to move.
4. Run the check again on the same intended connection.
5. Compare the main finding and the component that was expected to improve.

A small score change does not necessarily mean the main problem changed. The primary finding and component evidence matter more than chasing a single number.

5. History and trends

History helps compare completed runs. When enough comparable checks exist, the app can build a trend for the same network context and show what changed.

6. Reports

The Reports area lets you create or open report views from a completed diagnostic run.

Customer report

Choose this when the recipient needs the conclusion, score, main checks and next steps without the full technical detail. It is designed to exclude sensitive technical identifiers from the customer-facing report.

Technical report

Choose this for an ISP, IT team or advanced troubleshooting. It is the full evidence package and can contain detailed measurements plus sensitive network identifiers such as IP addresses, network names, ISP/ASN, configured DNS, approximate location, route-hop addresses, device/mobile details and exact timestamps when available. The current production report build does not include per-application traffic analytics or app-name lists.

1. Open Reports.
2. Select the completed run and the Customer or Technical report.
3. Preview the file. When sharing selected sensitive reports, read and accept the in-app sensitive-report acknowledgement only if the recipient is trusted.
4. Open the generated report and verify that it is the run you intend to share.
5. Share it only with the intended recipient.

7. Internet Monitor

The Internet Monitor is a separate, user-started technical function intended for intermittent problems and longer observation. It runs only after you start it.

1. Keep the connection you want to observe active.
2. Open Technical mode → Monitor.
3. Select the settings offered by the app and start the session.
4. Keep in mind that Android background limits, battery optimisation, device sleep, force-closing the app or link changes can reduce the amount of retained evidence.
5. Interpret coverage together with success/failure and timing statistics.

8. Tools

The Simple-mode Tools area contains supporting diagnostics that are separate from the main guided check. Some tools can contact network destinations or examine the local network when you explicitly start them. Use local-network discovery only on networks you own or are authorised to inspect.

9. Privacy before sharing

Use the least-detailed report that still solves the support problem. Before sharing a Technical report, remember that the Technical report can contain network names, IP addresses, route information, approximate location, operator/device information, timestamps and other detailed identifiers. Once a PDF leaves your device, the recipient or sharing service can retain it outside Diagnostix360.

10. 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 failed or delayed probe does not, by itself, prove which organisation is responsible.
• Device capabilities, Android restrictions, congestion, routing and remote targets can influence measurements.
• Diagnostix360 is not a certified test instrument and does not replace provider-side or professional diagnostics where those are required.

Need help interpreting a run? Contact support after reviewing the report’s privacy fields.