Traceroute

Find the exact hop where your latency lives.

Traceroute (also called tracert on Windows) shows every router between your device and a destination, along with how long each hop takes. It's the diagnostic of choice when you suspect ISP routing issues — a hop deep inside your ISP's network adding 200 ms, or traffic being routed via Singapore instead of Mumbai.

Real ICMP traceroute requires raw socket access that browsers don't expose. We do an HTTP/2 approximation that shows latency to each Signalyzr probe (Mumbai, Delhi NCR) and a few well-known endpoints (Google, Cloudflare, your ISP DNS). It catches most real-world routing problems.

What this measures

  • Latency to Signalyzr Mumbai PoP
  • Latency to Signalyzr Delhi NCR PoP
  • Latency to Cloudflare (well-routed reference)
  • Latency to Google (international reference)
  • Which PoP your DNS chose for you (sanity-check geo-routing)

How it works

  1. Resolve each probe via DNS
  2. Issue a small probe request and measure round-trip
  3. Compare cross-region: should your nearest PoP be closest? (If not, ISP routing is suboptimal)
  4. Report all hops side by side

Why this matters

If signalyzr.com Mumbai is 200 ms away when you're in Delhi, your ISP is routing via Singapore. That's an ISP problem, not your problem — but you need traceroute to prove it before you complain.

Top fixes

  • If your nearest PoP isn't actually closest: contact ISP about route optimization
  • If Cloudflare is faster than Signalyzr: try changing DNS to 1.1.1.1
  • If all hops are slow: probably ISP last-mile congestion — retest at 6 AM
  • Specific hop slow consistently: capture screenshot for ISP complaint

FAQs

Why can't a browser do real traceroute?

Real traceroute uses raw ICMP packets with TTL manipulation, which requires OS-level access. Browsers don't allow this. We approximate by timing HTTP requests to well-known endpoints, which catches most ISP routing issues.

What does it mean if Mumbai is faster than Delhi for me?

It means your ISP is routing you via Mumbai even though you're in Delhi NCR. This is bad and worth complaining about. Show your ISP this screen.

Should every hop have low latency?

First few hops (your router, ISP gateway) should be under 20 ms. As you go further, latency grows. The relevant signal is whether the growth is monotonic (normal) or one hop suddenly adds 200 ms (problem).

Run traceroute →

Related

Signalyzr is a free, privacy-first network diagnostic tool made in India. Loading the diagnostic app…