Ongoing Xbox Cloud Gaming Input Lag – Routing/Peering Suspected

HI!

I'm experiencing severe and persistent input lag when using Xbox Cloud Gaming, to the point where games become unplayable. It's like I'm swimming through syrup. I’ve spent considerable time isolating the issue, and I believe the problem may lie in routing or peering between the cloud servers and my ISP.

The Problem:

• Inputs are delayed by seconds, despite consistent 60fps and stable decode rate
  
• Audio of my character’s death is heard before I see it and this happens repeatedly
  
• Jitter spikes up to 20ms during these episodes, even though ping remains low (~20ms)
  

My Setup:

• ISP: TekSavvy via Rogers Cable (Ontario, Canada)
  
• Download/Upload: 150+ Mbps down, 30 Mbps up
  
• Bufferbloat: A+ (verified via waveform.com using CAKE SQM on OpenWRT)
  
• Tested Devices: Multiple PCs and mobile devices
  
• Wired and Wi-Fi tested: Including connecting my PC directly to the Modem
  
• Other Services are fine: Amazon Luna streams perfectly
  

What I’ve Tried:

• Replaced both modem and router, meaning I've already spent a large sum out of pocket to try to fix this
  
• Configured QoS and tested direct-to-modem
  
• Used multiple VPNs including Private Internet Access (WireGuard + Toronto+Montreal+Ontario exit nodes)
  
• Tested ExitLag (Toronto and Miami)
  
• Deployed WireGuard through VPS in Toronto
  
• Tested over 5G hotspot — Works but not viable due to data caps, 5G is TELUS/Bell so different backbone
  
• Traceroutes show inconsistent latency, late hops to Microsoft ASN
  

[table][tr]traceroute to xboxlive.com (20.236.44.162), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 14.793 ms 2.944 ms 2.564 ms 2 ---.cpe.teksavvy.com (---) 22.497 ms 23.375 ms 15.065 ms 3 ---.rcable-tsi.tor.teksavvy.com (---) 17.476 ms 24.642 ms 17.969 ms 4 ---.tsi-rcable.agg01.tor1.teksavvy.com (---) 19.012 ms 23.607 ms 16.915 ms 5 * * * 6 ae1-0-bdr01-tor1.teksavvy.com (206.248.153.3) 18.007 ms ae2-0-bdr01-tor1.teksavvy.com (206.248.153.9) 24.625 ms ae1-0-bdr01-tor1.teksavvy.com (206.248.153.3) 22.607 ms 7 ae62-0.yto01-96cbe-1b.ntwk.msn.net (104.44.44.97) 17.087 ms 26.448 ms 22.583 ms 8 51.10.1.152 (51.10.1.152) 16.260 ms 28.858 ms 19.583 ms 9 * * be-122-0.ibr02.yto20.ntwk.msn.net (104.44.20.167) 90.699 ms10 * * *11 51.10.4.63 (51.10.4.63) 100.723 ms 90.805 ms 96.497 ms12 51.10.20.87 (51.10.20.87) 99.943 ms 104.44.52.134 (104.44.52.134) 87.604 ms 51.10.20.87 (51.10.20.87) 92.608 ms13 51.10.9.232 (51.10.9.232) 85.873 ms 104.44.54.233 (104.44.54.233) 78.333 ms 51.10.9.232 (51.10.9.232) 90.395 ms14 * 51.10.9.213 (51.10.9.213) 88.641 ms *15 * 51.10.19.213 (51.10.19.213) 86.227 ms 51.10.17.148 (51.10.17.148) 82.137 ms16 be-2-0.ibr02.mwh01.ntwk.msn.net (104.44.16.81) 80.507 ms 82.870 ms 77.783 ms17 51.10.17.150 (51.10.17.150) 85.658 ms 94.004 ms 51.10.34.13 (51.10.34.13) 73.009 ms18 51.10.6.234 (51.10.6.234) 81.496 ms 51.10.6.210 (51.10.6.210) 82.297 ms be-1-0.ibr03.mwh01.ntwk.msn.net (104.44.16.83) 94.964 ms19 be-2-0.ibr02.mwh01.ntwk.msn.net (104.44.16.81) 88.456 ms 100.136 ms *20 51.10.34.13 (51.10.34.13) 107.063 ms * *21 51.10.6.244 (51.10.6.244) 87.069 ms * 87.871 ms22 * * *[/tr][/table]

HALP!

• Is there a known issue with Xbox Cloud Gaming routing for Canadian users (TekSavvy/Rogers)?
  
• Can anyone confirm which region or IP ranges I should be reaching when using xCloud in Ontario?
  
• Is there a way to route traffic to a more stable or nearby Azure edge server?
  

This issue has persisted for weeks and every other cloud gaming service performs normally, so I'm hoping for some guidance.

Rogers was no help, they came out, put a line filter on the cable and left. At this point my next option is to just cancel the subscription.

:)