Forum Discussion
Moved within city - Crazy ping difference
Wondering if anyone else has dealt with this. I recently moved within Edmonton and my average ping to pretty much every game server went up about 40-70ms across the board (Seattle, NYC, etc.). I'm on PureFibre, hardwired in.
Testing alongside a friend still at near old address, we take completely different routes to the same servers. My traffic now seems to bounce around inefficiently before actually making its way out. I have traceroutes from both locations showing the paths diverge immediately.
I tested ExitLag as a troubleshooting step, and it recovered about 50ms, which seems to confirm the issue is in Telus's routing rather than anything on my end.
Has anyone had any luck getting Telus to look into a routing issue like this?
2 Replies
I am seeing the same issue in Edmonton on TELUS Purefibre.
There appear to be two different routing paths depending on the IP:
Some users get ~18 ms to Seattle and ~33 ms to Chicago (Also in Edmenton)
Others (including me) get ~56 ms to Seattle and ~55–70 ms to Chicago
I have confirmed this with multiple users on the same ISP.
Traceroutes show normal latency within the TELUS network, but a large increase when traffic reaches upstream transit (often NTT). This suggests the issue is not local or related to home setup.
Using a VPN (routed through Zayo) or services like ExitLag reduces my Seattle latency to ~18 ms, which confirms a better routing path exists but is not used by default.
I also understand bridge mode is sometimes suggested to rule out internal routing or NAT overhead, but in this case the latency increase appears well beyond the local network and occurs after leaving the TELUS backbone, so it likely would not impact this issue.
Has TELUS investigated whether different IP ranges are routed through different upstream providers?
TELUS_SupportOfficial Support Team
While this is most likely something to check with our Tech Support team about, one thing they'd suggest trying first would be to run a Bridge Mode test by putting your hub into Bridge Mode and using your own router. This can sometimes eliminate any internal NAT table delays that can sometimes mimic routing lag. Give that a try and let us know.
