Guide 19
Separate local connection problems from upstream problems
Measure the symptom, compare like-for-like conditions and draw a conclusion supported by the recorded evidence.
Where you will workConnection details · Continuous latency · DNS
AllowDepends on the symptom and observation period
Watch the key steps
This related overview shows find clues when your connection feels slow. Follow the question-specific steps below to complete your investigation.
A 46-second narrated overview. Follow the full instructions below when you try it.
Read the video transcript
Choose the right check. Open Tools on the connection you want to investigate. Use Speedtest for an active performance check only when you can allow substantial traffic.
Compare delay and DNS. Use Latency to inspect response timing and DNS lookup to examine name resolution. Keep the destination and connection consistent when repeating checks.
Inspect details and route. Connection details identifies the interface and configuration. Route trace follows responding hops. An unanswered hop can simply mean a router ignores probes.
Review the saved evidence. Review each produced summary in Activity Log. Tools work over Ethernet too. These are momentary checks; compare them alongside recorded Wi-Fi history before choosing a network.
Open the app view at full size to inspect its controls.
Before you start
Give your result a useful basis
- Use only networks and devices you are authorized to investigate.
- Record the location, time and active connection. Keep useful history and compare similar observation conditions.
Measure
Identify the actual connection and gateway in connection details. Test gateway and remote reachability separately with continuous latency; use DNS checks when names fail, and route trace for responding path information.
Compare
Repeat with a second authorized device, then compare Wi-Fi and Ethernet through the same router where available. Keep destinations and workload comparable. Change one variable at a time and retain both successful and failed results.
Interpret
A problem confined to one device suggests checking that device; problems shared by wired and wireless clients suggest checking shared router or upstream services. Healthy IP access with failed DNS suggests investigating name resolution.
Check what you gained
You can now check that
- You have measurements and a comparison relevant to your question, with observation gaps and uncertainties preserved.
Updated by Hotspot Observer · 2 November 2026