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.
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.
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.
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.
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).
Signalyzr is a free, privacy-first network diagnostic tool made in India. Loading the diagnostic app…