Expert

Re: High Latency Issues

That looks like overloaded servers beyond the node.

 

 what does a plain command level tracert to google look like?

 

 Where is this imgur screen grab? under an IPv6 tab?

http://imgur.com/nZrTCXZ

Observer

Re: High Latency Issues

Those are the only options under the IPv6 tab, yes.

 

As for overloaded servers, it isn't the issue most of the day.  Maybe in Overwatch's case since it's still new but certainly not for League, Path of Exile, Battlefield, Warframe, or CS:GO.  Especially when I play with friends in my city who have zero issues in the same games.

 

I'm still more concerned about the TWC nodes, since those are the ones causing problems consistently.

 

Edit:

As for the tracert test: completed at 3:43pm

 

 

Expert

Re: High Latency Issues

hop 8 looks like it has an issue, maybe 10 as well, and since 4 does, it's possible you have something on your lan hoarding bandwidth in bursts, like Itunesync, onedrive.

 

Highlighted
Expert

Re: High Latency Issues

to copy, rt click, click on select all, hit enter

paste here as normal

 

 

Observer

Re: High Latency Issues

Sorry, the format gets really messy but I can see the use of plain text over an image.

 

OW

Tracing route to 37.244.0.3 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 14 ms 10 ms 21 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 15 ms 9 ms 10 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 86 ms 83 ms 92 ms tge0-0-8.snaxtxfp02h.texas.rr.com [24.28.134.37]
5 10 ms 8 ms 8 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 12 ms 10 ms 13 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 92 ms 100 ms 98 ms 24.175.33.4
8 115 ms 118 ms 92 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 58 ms 55 ms 63 ms bu-ether12.tustca4200w-bcr00.tbone.rr.com [66.109.6.0]
10 151 ms 152 ms 119 ms agg5.tustcaft01r.socal.rr.com [66.109.1.219]
11 55 ms 52 ms 57 ms 66.109.9.161
12 55 ms 61 ms 59 ms 37.244.0.3

 

PoE

Tracing route to speedtest.dal01.softlayer.com [74.86.116.210]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 14 ms 12 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 16 ms 15 ms 8 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 104 ms 80 ms 74 ms tge0-0-8.snaxtxfp02h.texas.rr.com [24.28.134.37]
5 13 ms 10 ms 18 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 11 ms 15 ms 9 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 101 ms 89 ms 88 ms 24.175.33.4
8 104 ms 89 ms 92 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 44 ms 35 ms 43 ms 0.ae3.pr0.dfw10.tbone.rr.com [66.109.6.209]
10 57 ms 45 ms 54 ms po21.bbr02.eq01.dal01.networklayer.com [66.109.9.222]
11 54 ms 51 ms 50 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.18.211]
12 90 ms 99 ms 86 ms po1.fcr03.sr04.dal01.networklayer.com [66.228.118.186]
13 60 ms 52 ms 50 ms speedtest.dal01.softlayer.com [74.86.116.210]

 

Valve East (Using this as I connect to it faster than their west server)

Tracing route to iad.valve.net [208.78.164.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 15 ms 15 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 12 ms 12 ms 12 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 22 ms 101 ms 32 ms tge0-0-9.snaxtxfp02h.texas.rr.com [24.28.132.77]
5 12 ms 13 ms 15 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 14 ms 10 ms 10 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 26 ms 22 ms 49 ms agg23.dllatxl301r.texas.rr.com [24.175.32.146]
8 86 ms 85 ms 98 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 55 ms 56 ms 63 ms bu-ether24.chctilwc00w-bcr00.tbone.rr.com [66.109.9.40]
10 126 ms 141 ms 146 ms bu-ether13.vinnva0510w-bcr00.tbone.rr.com [66.109.10.0]
11 106 ms 101 ms 91 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
12 50 ms 45 ms 60 ms 0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
13 55 ms 60 ms 57 ms 66.109.7.230
14 * * * Request timed out.
15 55 ms 53 ms 52 ms 208.78.164.2

  

All completed between 5:05pm and 5:10pm.

Expert

Re: High Latency Issues

Looks like this TWC server has issues:

24.28.134.37

Observer

Re: High Latency Issues

Yeah, in almost all cases it is at least one of the problematic hops. Looks like a server housed in Wichita, Kansas. A few others tend to be consistently dodgy as well, particularly 24.28.134.37.
Expert

Re: High Latency Issues

might not be in Witchita, TWC has most IP's geolocation wrong or set to one place

 

Observer

Re: High Latency Issues

Very true.  Thought it was odd the geo location on several sites pointed to the middle of a lake.

Just updating with trace routes from 9:55pm to show time variability

 

LoL

Tracing route to 104.160.131.3 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 8 ms 15 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 60 ms 13 ms 15 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 27 ms 21 ms 30 ms tge0-0-9.snaxtxfp02h.texas.rr.com [24.28.132.77]
5 11 ms 21 ms 10 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 16 ms 14 ms 11 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 53 ms 41 ms 36 ms 24.175.33.4
8 174 ms 175 ms 151 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 20 ms 20 ms 22 ms 0.ae4.pr1.dfw10.tbone.rr.com [107.14.19.97]
10 195 ms 255 ms 242 ms 24.27.236.233
11 37 ms 42 ms 46 ms 104.160.134.35
12 38 ms 45 ms 40 ms ae35-br02.chi01.riotdirect.net [104.160.159.24]
13 50 ms 39 ms 38 ms 104.160.131.3

 

OW

Tracing route to 37.244.0.3 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 9 ms 12 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 11 ms 11 ms 23 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 210 ms 206 ms 190 ms tge0-0-8.snaxtxfp02h.texas.rr.com [24.28.134.37]
5 10 ms 13 ms 12 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 9 ms 10 ms 10 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 50 ms 49 ms 39 ms 24.175.33.4
8 252 ms 199 ms 175 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 64 ms 62 ms 56 ms bu-ether12.tustca4200w-bcr00.tbone.rr.com [66.109.6.0]
10 159 ms 154 ms 160 ms agg5.tustcaft01r.socal.rr.com [66.109.1.219]
11 57 ms 58 ms 55 ms 66.109.9.161
12 70 ms 64 ms 77 ms 37.244.0.3

 

Valve West

Tracing route to eat.valve.net [192.69.96.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 22 ms 14 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 20 ms 8 ms 15 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 80 ms 84 ms 80 ms tge0-0-8.snaxtxfp02h.texas.rr.com [24.28.134.37]
5 11 ms 13 ms 10 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 9 ms 12 ms 11 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 51 ms 50 ms 47 ms 24.175.33.4
8 86 ms 103 ms 86 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 18 ms 21 ms 25 ms 0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
10 20 ms 22 ms 16 ms be-202-pe03.1950stemmons.tx.ibone.comcast.net [50.248.118.169]
11 72 ms 21 ms 22 ms hu-0-4-0-6-cr02.dallas.tx.ibone.comcast.net [68.86.86.153]
12 211 ms 240 ms 228 ms be-11724-cr02.denver.co.ibone.comcast.net [68.86.84.229]
13 127 ms 113 ms 117 ms be-10817-cr01.seattle.wa.ibone.comcast.net [68.86.84.206]
14 149 ms 139 ms 138 ms hu-0-12-0-1-pe05.seattle.wa.ibone.comcast.net [68.86.84.66]
15 70 ms 68 ms 70 ms as32590-1-c.seattle.wa.ibone.comcast.net [66.208.233.26]
16 * * * Request timed out.
17 * * * Request timed out.
18 74 ms 73 ms 78 ms eat.valve.net [192.69.96.1]

 

Valve East

Tracing route to iad.valve.net [208.78.164.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 14 ms 4 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
3 12 ms 15 ms 14 ms cpe-72-190-128-1.satx.res.rr.com [72.190.128.1]
4 30 ms 20 ms 27 ms tge0-0-9.snaxtxfp02h.texas.rr.com [24.28.132.77]
5 11 ms 13 ms 10 ms agg24.snaptx1902r.texas.rr.com [24.175.33.100]
6 15 ms 13 ms 11 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 29 ms 46 ms 50 ms agg23.dllatxl301r.texas.rr.com [24.175.32.146]
8 64 ms 55 ms 71 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
9 87 ms 88 ms 93 ms bu-ether24.chctilwc00w-bcr00.tbone.rr.com [66.109.9.40]
10 101 ms 86 ms 80 ms bu-ether13.vinnva0510w-bcr00.tbone.rr.com [66.109.10.0]
11 264 ms 301 ms 283 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
12 55 ms 49 ms 54 ms 0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
13 61 ms 81 ms 67 ms 66.109.7.230
14 * * * Request timed out.
15 52 ms 54 ms 55 ms 208.78.164.2

 

Lots of problems running through Roadrunner addresses (as well as Comcast, but that's their business, not TWC's), alongside 24.28.134.37 as well.  

As for possible bandwidth hogs, I don't have many things like that running on my network.  I run a few game clients like Origin and Steam and generally have Teamspeak and Skype running in the background, but they run all day and aren't at all a problem before and after the window of downtime between 3-12ish.

Expert

Re: High Latency Issues

turn them off when gaming.

 Oh, you found the ip addresses for central NY that geolocate to the middle of lake Erie? Woman LOL