Forum Discussion
Intermittent Jitter on TELUS Vancouver - Seattle Backbone 154.11.15.xx
Hi everyone, I’m experiencing intermittent jitter and minor packet loss on the Vancouver - Seattle route, affecting latency-sensitive apps. Tests confirm the issue is not from my home network. ...
As I mentioned above, here are the test results showing the jitter and minor packet loss on the Vancouver -> Seattle route, which may indicate congestion on the backbone.
Apologies for the image quality
The issue occurs even though I am not behind CGNAT, confirming that the packet loss/jitter is not caused by NAT.
Nighthawk
Community Power User
Community Power UserCan you be more specific when you say latency sensitive apps? Which apps or games specifically? What are the issues you are experiencing while using those apps / games? I'm not seeing spikes high enough in any screenshot that should cause any issues. Which router are you using as well? When I try testing from my PC using the Telus hardware, the first IP is always the LAN IP for the gateway. Not an external Telus IP. I'm also not seeing any jitter results on any screenshot posted.
Your first screenshot is testing to a Valve owned IP. It's not one that will respond to testing. If I'm reading it right you're seeing 1.2% packet loss between your PC and the first IP (your router/gateway)? That loss doesn't show up after that in the other screenshots so I wonder if PingPlotter has an issue.
The traceroutes to 1.1.1.1 and 8.8.8.8 only ping 3 times each attempt so they aren't a good measure of latency over a longer period of time. The results they do show seem fine. The second traceroute to 8.8.8.8 shows no sign of any issue.
The WinMTR you posted looks fine to me. You should be looking closer at the Average latency not the one off spike when it first starts the test. The IP on #6 (162.158.144.11) is a Cloudflare IP. Run the test more than once after launching WinMTR. It should smooth out that initial spike.
Thanks a lot for reviewing the screenshots
I’m using only the Nokia ONT. Previously, I had the TELUS NH20T modem+router, but its dual-layer setup added latency and lacked QoS, so I requested an ONT-only setup. I also tested an Asus GT-BE98 Pro using only the 10 Gbps LAN port, but returned it because it could not stabilize jitter. The first hop corresponds to the ONT’s IP. Even with this setup, I still experience teleporting, inconsistent recoil, and jitter spikes in fast-paced games like PUBG, especially during hotdrop moments.
The TSL.exe test IP does not respond to ICMP, so PingPlotter may show inconsistent pings — this is expected and not the main issue. In WinMTR tests, the first hop showed Best=0, Avg=0, Worst=2, Last=1. Minor local packet loss is possible; although two technicians confirmed the main line is clean, worst local values never exceeded 3 ms. Sudden spikes begin at the backbone, with the Last column showing instantaneous values from 2–44 ms. Multiple tests confirm the jitter originates on the Vancouver → Seattle segment.
Although WinMTR does not show packet loss, I am including a screenshot of an email from PUBG confirming packet loss during gameplay. This serves as additional evidence that packet loss occurred during real-time use. I am also including the results of two long-duration WinMTR tests to 1.1.1.1 and one long-duration test to 8.8.8.8 at the end of this post. The spikes starting with the IP addresses 154.11.15.73 for 1.1.1.1 and 154.11.15.192 for 8.8.8.8, which accumulate cumulatively, clearly indicate that the latency and jitter issues begin on the Vancouver → Seattle segment within the TELUS backbone and increase cumulatively from that point onward.
Thanks again for taking the time to look into this.
I got a Content Not Published – maximum number of posts error when trying to share the photos in my second message. So I’m uploading the test results and packet loss screenshots from a new profile. Sorry for the image quality.
I’ve attached the supporting screenshots separately:
Two long-duration WinMTR tests to 1.1.1.1
One long-duration WinMTR test to 8.8.8.8
Screenshot of the email from PUBG confirming packet loss
These demonstrate that the jitter and latency issues start on the Vancouver → Seattle segment within the TELUS backbone.
Thank you for taking the time to review everything.
