How to Diagnose High Latency

What drives latency

• Distance — light in fibre still takes time; far-away servers are inherently slower.
• Hop count — every router on the path adds a little processing delay.
• Congestion — busy links queue packets, adding variable delay (jitter).
• Last-mile — Wi-Fi, an overloaded router, or a saturated home connection.
• Server load — a busy destination takes longer to respond.

Isolate where it starts

Work outward from your own machine so each step rules out a cause:

• Ping your router/gateway — high latency here means a local problem (Wi-Fi, hardware).
• Ping a nearby well-known host (e.g. a major DNS resolver) — high here points to your ISP or last mile.
• Ping the destination from multiple global locations — if only your route is slow, it's a path/ISP issue; if everyone is slow, it's the server or its region.

Distance vs a real fault

Some latency is just physics: a server in Tokyo will always be slower from Europe than a local one. The test is comparison — if a nearby probe is fast and a distant one is slow, that's expected distance. If a nearby probe is also slow, or latency is wildly variable (high jitter), there's a fault to chase rather than geography to accept.

What actually helps

• Prefer wired over Wi-Fi for latency-sensitive work.
• Use a CDN or servers closer to your users to cut distance.
• Check for congestion at specific times of day (evening peaks).
• Escalate to your ISP if a specific hop consistently adds large delay.