Diagnostics

How to Diagnose Internet and Network Problems

A repeatable diagnostic order — local first, then DNS, then path, then destination — with the right command and the right CheckItNowTools page at every step. Built for the moments when 'the internet is slow' needs to become a precise root cause in under five minutes.

Quick summary

  • Diagnose in order: local link, DNS, path, destination.
  • Ping measures reachability and round-trip time.
  • Traceroute shows where latency or loss starts; treat it as a hint, not proof.
  • DNS issues mimic 'the internet is down' — always rule them out early.

Layer-by-layer diagnostic order

  1. Local — interface up, IP assigned, gateway reachable.
  2. DNS — names resolve quickly and correctly.
  3. Path — packets reach the destination without excessive latency or loss.
  4. Destination — the server is healthy, listening, and serving.

Reading ping and traceroute

Stable ping with low jitter = healthy path. Climbing RTT or sporadic timeouts = congestion or loss. In traceroute, latency that suddenly jumps at a specific hop and stays elevated for every hop after it points to congestion at that hop. A single high-latency hop followed by normal ones is usually ICMP rate-limiting on a router — ignore it.

Real-world examples

  • Video calls drop only in the evening — usually upstream congestion on residential cable; capture pings across the day.
  • One specific site is slow — likely a CDN edge or DNS issue, not your link. Test other sites first.
  • 'Internet down' after a router reboot — DHCP lease or DNS cache; flush and retry.

Troubleshooting workflow

Run through these steps in order. Each step links to the right diagnostic tool.

  1. 1

    Ping the destination

    Reachability and round-trip time.

    Open Ping
  2. 2

    Run a DNS lookup

    Confirm names resolve and TTLs make sense.

    Open DNS Lookup
  3. 3

    Trace the path

    Find where latency or loss begins.

    Open Traceroute
  4. 4

    Check open ports

    Confirm the destination is actually listening.

    Open Port Check
  5. 5

    Run a speed test

    Quantify throughput end-to-end.

    Open Speed Test

Frequently asked questions

What's the right order to diagnose a network issue?

Local link → DNS → path → destination. Start with the cheapest, fastest check; escalate only when the previous layer is clean.

What does packet loss feel like?

Intermittent failures, jittery video calls, choppy gaming, and inconsistent throughput. A ping with > 1% loss is already noticeable on real-time apps.

Why is my latency high even though my bandwidth is fine?

Bandwidth and latency are independent. A loaded uplink, congested intermediate hop, or far-away destination all add latency without saturating throughput.

Is traceroute reliable?

It's a heuristic. ICMP rate-limiting and asymmetric routing distort hops. Read it as 'where does it start hurting?' rather than 'this hop is the problem.'

When should I blame the ISP?

When local diagnostics are clean, DNS resolves, and traceroute shows latency or loss spiking inside the ISP's network. Document the trace before opening a ticket.

Monitor it continuously

Save this check, get alerts on changes, and track multiple domains in one dashboard.

Learn about monitoring