High Latency Issues

[jgknightjr]

I've been having some really wonky ping issues for the past several months usually between the peak hours of 3pm and 12am.  It's gotten to the point where I can't play games, watch videos, or stream with friends anymore during daytime hours.

League of Legends WinMTR: 

| 192.168.0.1 - 0 | 246 | 246 | 0 | 0 | 0 | 0 |
| cpe-72-190-128-1.satx.res.rr.com - 1 | 243 | 241 | 7 | 14 | 161 | 7 |
| cpe-72-190-128-1.satx.res.rr.com - 0 | 246 | 246 | 6 | 20 | 153 | 10 |
| tge0-0-9.snaxtxfp02h.texas.rr.com - 0 | 246 | 246 | 13 | 30 | 115 | 23 |
| agg24.snaptx1902r.texas.rr.com - 0 | 246 | 246 | 7 | 12 | 37 | 11 |
| agg22.snantxvy01r.texas.rr.com - 0 | 246 | 246 | 8 | 12 | 34 | 14 |
| 24.175.33.4 - 0 | 246 | 246 | 21 | 137 | 285 | 59 |
| bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 0 | 246 | 246 | 19 | 60 | 171 | 94 |
| 0.ae4.pr1.dfw10.tbone.rr.com - 0 | 246 | 246 | 14 | 20 | 78 | 19 |
| 24.27.236.233 - 0 | 246 | 246 | 16 | 57 | 167 | 91 |
| 104.160.134.35 - 0 | 246 | 246 | 33 | 38 | 60 | 38 |
| ae35-br02.chi01.riotdirect.net - 0 | 246 | 246 | 34 | 38 | 62 | 36 |
| 104.160.131.3 - 0 | 246 | 246 | 34 | 38 | 48 | 40 |

Path of Exile WinMTR: 

| 192.168.0.1 - 0 | 100 | 100 | 0 | 0 | 0 | 0 |
| cpe-72-190-128-1.satx.res.rr.com - 2 | 97 | 96 | 8 | 14 | 87 | 12 |
| cpe-72-190-128-1.satx.res.rr.com - 0 | 100 | 100 | 7 | 17 | 107 | 14 |
| tge0-0-8.snaxtxfp02h.texas.rr.com - 0 | 100 | 100 | 21 | 78 | 196 | 124 |
| agg24.snaptx1902r.texas.rr.com - 0 | 100 | 100 | 7 | 11 | 23 | 14 |
| agg22.snantxvy01r.texas.rr.com - 0 | 100 | 100 | 8 | 12 | 34 | 11 |
| 24.175.33.4 - 0 | 100 | 100 | 54 | 143 | 217 | 202 |
| bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 0 | 100 | 100 | 20 | 76 | 209 | 124 |
| 0.ae3.pr0.dfw10.tbone.rr.com - 0 | 100 | 100 | 48 | 142 | 256 | 108 |
| po21.bbr02.eq01.dal01.networklayer.com - 0 | 100 | 100 | 49 | 142 | 256 | 109 |
| ae0.dar01.sr01.dal01.networklayer.com - 0 | 100 | 100 | 51 | 140 | 216 | 197 |
| po1.fcr03.sr04.dal01.networklayer.com - 0 | 100 | 100 | 52 | 140 | 217 | 197 |
| speedtest.dal01.softlayer.com - 0 | 100 | 100 | 49 | 142 | 257 | 108 |

Overwatch WinMTR:

| 192.168.0.1 - 0 | 110 | 110 | 0 | 0 | 2 | 0 |
| cpe-72-190-128-1.satx.res.rr.com - 0 | 110 | 110 | 7 | 12 | 43 | 11 |
| cpe-72-190-128-1.satx.res.rr.com - 0 | 110 | 110 | 4 | 18 | 172 | 8 |
| tge0-0-8.snaxtxfp02h.texas.rr.com - 0 | 110 | 110 | 50 | 113 | 233 | 136 |
| agg24.snaptx1902r.texas.rr.com - 0 | 110 | 110 | 7 | 12 | 34 | 12 |
| agg22.snantxvy01r.texas.rr.com - 0 | 110 | 110 | 8 | 12 | 35 | 11 |
| 24.175.33.4 - 0 | 110 | 110 | 111 | 231 | 390 | 317 |
| bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 0 | 110 | 110 | 46 | 109 | 224 | 113 |
| bu-ether12.tustca4200w-bcr00.tbone.rr.com - 0 | 110 | 110 | 53 | 58 | 67 | 62 |
| agg5.tustcaft01r.socal.rr.com - 1 | 106 | 105 | 78 | 142 | 254 | 148 |
| 66.109.9.161 - 0 | 110 | 110 | 51 | 55 | 79 | 54 |
| 37.244.0.3 - 0 | 110 | 110 | 150 | 265 | 423 | 342 |

The intermittent latency comes from the same few nodes in almost all of my tests.  With a little research, the rr.com domains and 24.175.33.4 address belong to TWC, so hopefully my curiosity is justified in the problem being an issue with the ISP itself rather than the game companies.

My signal levels: 

Startup Procedure

Procedure Status Comment Acquire Downstream Channel 549000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode IPv6 Only ipv6Only(1)

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 4 549000000 Hz 10.2 dBmV 44.6 dB 0 0 2 Locked QAM256 2 537000000 Hz 10.5 dBmV 44.7 dB 0 0 3 Locked QAM256 3 543000000 Hz 10.1 dBmV 44.6 dB 0 0 4 Locked QAM256 1 531000000 Hz 10.7 dBmV 45.1 dB 0 0 5 Locked QAM256 5 555000000 Hz 10.2 dBmV 44.6 dB 0 0 6 Locked QAM256 6 561000000 Hz 10.4 dBmV 44.6 dB 0 0 7 Locked QAM256 10 585000000 Hz 10.3 dBmV 44.6 dB 0 0 8 Locked QAM256 8 573000000 Hz 10 dBmV 44.6 dB 0 0

Upstream Bonded Channels

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 24200000 Hz 43.5 dBmV 2 Locked TDMA 1 2560 Ksym/sec 19400000 Hz 43.5 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 30600000 Hz 44.5 dBmV 4 Locked ATDMA 4 2560 Ksym/sec 37000000 Hz 43.5 dBmV

[MsRaye]

Signal page looks good... Good luck getting that server/hop fixed....

Try reporting it to TWC's NOC....

[charliejuliet]

Looks like you're getting ipv6 provisioning which has been known for causing connection issues on gaming systems at least on TWCs network. For instance, I enabled ipv6 on my router and my xbox live dns servers were getting an ipv6 dns address like this one: 2001:f4f4::::0046. I played matches online and it kept getting dropped. I disabled ipv6 on my router and went back to TWC ipv4 dns address such as 209.18.47.61; no more connection issues. Understand that I could not change my ipv6 xbox dns server addresses through my xbox 1. I had to change everything over through the router for my xbox from ipv6 to ipv4. Hope this helps.  

[MsRaye]

correct, IPv6 has multipleissues and I believe the one that's affecting you is the fact that TWC is regionally handling IPv4 out of at least 5 regional data centers whereas IPv6 is only handled by one through several more hops.

TWC has been trying to hide the routing but the IPv4 points are probably Atlanta, NYC, Columbus, Dallas, Chicago, LA and IPv6 is only handled by Witchita resulting in a 10x delay in DNS/  best routing  resolution updates

 second possibility other have found is that one device running IPv6 drasticly slows down other devices running IPv6. I have no reason why this is happenning but it is somewhere between customer devices and the nearest regional data center.

[jgknightjr]

So essentially disabling the IPv6 connection on my router could potentially remedy the issue for the time being? Sounds good, except the current unit I'm using doesn't seem to have an option to do so. From what I've read on the internet, Netgear modems/routers seem to lack the ability to disable IPv6 at large, so it may just be that I need to swap the unit for something better, which I've been looking to do for quite some time anyway.

Unless there are workarounds for disabling IPv6 elsewhere, I've run out of ideas.

[MsRaye]

Workaround is turn off the ipv6 in the computers network connection or ethernet/ wireless adapter to see if that solves the lag, if not, then power down all of them. If that solves the issue, it's more likely a cloud, onedrive, dropbox,Itune sync issue on one of them or malware/ trojan/virus.

Also, setting qos limits on cloud, onedrive, dropbox,Itune sync will prevent those devices from stealing all available bandwidth. 

 There are also some routers that have game versus media stream optimization.WMM support, etc.

If you have wireless, make sure there's no unauthorized guests and that WPS and the guest account is off.

 If wireless is showing channel changes from interference, lock it on ch 3 or 8 or turn wireless off

[jgknightjr]

I unticked the ethernet IPv6 off in Windows earlier. I'll have to test it tonight to make sure. I've also returned to using the default TWC DNS servers as well just in case, but from my experience there's little difference between it and the Google DNS I normally have on.

Will report back with findings. Thanks for the ideas thus far.

[MsRaye]

If you are on a peer to peer interconnected game and some are IPv4 and others IPv6, it will be messed up timing  thanks to the seperate paths/ locations of TWC's "pipeline" to servers and transport provider portals.

If restricting to IPv4 only helps, then,  do a command level netstat -an , it will show all the active connections, see what the difference is when running just the desktop vs your web  browser vs, the game

On the desktop, you'll see the antivirus listenning for virus definitions, if there's anything else active, like cloud or sync, they need to be disabled when gaming

[charliejuliet]

Well I have a Netgear Nighthawk R7000 router. I logged into routerlogin.net and signed in. Clicked on the tab Advanced. Next, I went to advanced setup, and the option for IPV6 was there.  At that point, it should say Internet Connection Type and I chose Disabled and clicked Apply. Afterwards, I refreshed everything to verify the change went through. 

[jgknightjr]

Here's what my IPv6 setup looks like.  No disable button.

http://i.imgur.com/nZrTCXZ.png

Edit:

Ran OW and tried playing while tracing the hops using MTR at three diferent times:

First run:

| 192.168.0.1 - 0 | 340 | 340 | 0 | 0 | 4 | 0 |
| cpe-72-190-128-1.satx.res.rr.com - 1 | 329 | 326 | 8 | 27 | 198 | 31 |
| cpe-72-190-128-1.satx.res.rr.com - 0 | 340 | 340 | 4 | 30 | 166 | 107 |
| tge0-0-8.snaxtxfp02h.texas.rr.com - 0 | 340 | 340 | 19 | 90 | 233 | 110 |
| agg24.snaptx1902r.texas.rr.com - 0 | 340 | 340 | 5 | 22 | 76 | 24 |
| agg22.snantxvy01r.texas.rr.com - 0 | 340 | 340 | 5 | 22 | 61 | 35 |
| 24.175.33.4 - 0 | 340 | 340 | 58 | 176 | 311 | 105 |
| bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 0 | 340 | 340 | 20 | 87 | 221 | 98 |
| bu-ether12.tustca4200w-bcr00.tbone.rr.com - 0 | 340 | 340 | 53 | 72 | 113 | 97 |
| agg5.tustcaft01r.socal.rr.com - 1 | 336 | 335 | 53 | 117 | 253 | 136 |
| 66.109.9.161 - 0 | 340 | 340 | 52 | 70 | 119 | 95 |
| 37.244.0.3 - 0 | 340 | 340 | 88 | 210 | 336 | 115 |

Second Run:

| 192.168.0.1 - 0 | 2241 | 2241 | 0 | 0 | 14 | 0 |
| cpe-72-190-128-1.satx.res.rr.com - 2 | 2143 | 2118 | 0 | 17 | 175 | 10 |
| cpe-72-190-128-1.satx.res.rr.com - 0 | 2240 | 2240 | 3 | 20 | 192 | 13 |
| tge0-0-8.snaxtxfp02h.texas.rr.com - 1 | 2205 | 2196 | 27 | 153 | 773 | 160 |
| agg24.snaptx1902r.texas.rr.com - 1 | 2237 | 2236 | 3 | 14 | 65 | 12 |
| agg22.snantxvy01r.texas.rr.com - 0 | 2240 | 2240 | 4 | 14 | 64 | 16 |
| 24.175.33.4 - 0 | 2240 | 2240 | 29 | 181 | 484 | 124 |
| bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 0 | 2240 | 2240 | 23 | 149 | 664 | 176 |
| bu-ether12.tustca4200w-bcr00.tbone.rr.com - 1 | 2237 | 2236 | 49 | 61 | 116 | 62 |
| agg5.tustcaft01r.socal.rr.com - 1 | 2225 | 2221 | 58 | 181 | 800 | 193 |
| 66.109.9.161 - 1 | 2237 | 2236 | 47 | 58 | 112 | 53 |
| 37.244.0.3 - 0 | 2240 | 2240 | 65 | 215 | 513 | 141 |

Third run:

| 192.168.0.1 - 0 | 221 | 221 | 0 | 0 | 4 | 0 |
| cpe-72-190-128-1.satx.res.rr.com - 2 | 212 | 209 | 0 | 16 | 90 | 16 |
| cpe-72-190-128-1.satx.res.rr.com - 0 | 221 | 221 | 7 | 21 | 151 | 10 |
| tge0-0-8.snaxtxfp02h.texas.rr.com - 0 | 221 | 221 | 51 | 137 | 355 | 93 |
| agg24.snaptx1902r.texas.rr.com - 0 | 221 | 221 | 8 | 16 | 51 | 10 |
| agg22.snantxvy01r.texas.rr.com - 0 | 221 | 221 | 7 | 16 | 49 | 12 |
| 24.175.33.4 - 0 | 221 | 221 | 92 | 178 | 369 | 183 |
| bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 0 | 221 | 221 | 49 | 131 | 337 | 86 |
| bu-ether12.tustca4200w-bcr00.tbone.rr.com - 0 | 221 | 221 | 53 | 62 | 103 | 60 |
| agg5.tustcaft01r.socal.rr.com - 0 | 221 | 221 | 78 | 166 | 379 | 118 |
| 66.109.9.161 - 0 | 221 | 221 | 48 | 58 | 92 | 55 |
| 37.244.0.3 - 0 | 221 | 221 | 116 | 213 | 410 | 212 |

This is after internally disabling IPv6 on the connection via Windows, so not much is different from before.