ntt
1 TopicTELUS routing issue to game servers VPN should not be necessary
Hi TELUS, I believe I am experiencing a routing/peering issue on my connection. My local network is stable, but latency to many servers including game servers is higher than what other TELUS users report. Across multiple users on the same ISP I see two routing outcomes: Some users get: ~18 ms Seattle ~33 ms Chicago Others including me get: ~1 ms Edmonton ~5–7 ms Calgary ~56 ms Seattle ~57 ms Chicago ~75 ms Los Angeles ~78 ms Dallas I confirmed this with 2 users on each path, suggesting this may be due to IP pools or upstream routing differences. Using a VPN reduces Seattle latency to ~18 ms, matching the lower latency users. The VPN routes through Zayo, suggesting a better path exists but is not used by default. Traceroutes show TELUS is stable (~1–26 ms), but latency increases by ~30 ms at a Seattle transit hop (e.g. NTT). I have tried basic troubleshooting (rebooting router) with no change. Setup: TELUS fibre, wired Ethernet, TELUS NAT Testing: in-game latency, ping, traceroute Seattle, WA (128.116.115.0/24) → ~56 ms Los Angeles, CA (128.116.116.0/24) → ~75 ms Chicago, IL (128.116.48.0/24, 128.116.84.0/24) → ~56 ms Dallas, TX (128.116.95.0/24) → ~78 ms Ashburn, VA (128.116.102.0/24) → ~74 ms Location: Edmonton, Alberta Here are some images of Traceroutes.17Views0likes1Comment