reokotsae

Terrible trace routes/ packet loss while gaming

Discussion created by reokotsae on Aug 28, 2017
Latest reply on Oct 17, 2017 by darkshado

getting some monstrous bad rubberbanding in my games lately. A couple trace routes show quite a few issues not sure what's going on.

 

Tracing route to google.com [172.217.8.174]
over a maximum of 30 hops:

1 8 ms 8 ms 9 ms 70.77.96.1
2 9 ms 11 ms 9 ms rc3no-be117-1.cg.shawcable.net [64.59.134.173]
3 58 ms 60 ms 59 ms rc3ec-be13.il.shawcable.net [66.163.75.66]
4 58 ms 67 ms 58 ms rc2nr-tge0-0-0-15.wp.shawcable.net [66.163.75.226]
5 * * * Request timed out.
6 59 ms 59 ms 57 ms 72.14.232.153
7 52 ms 51 ms 48 ms ord37s08-in-f14.1e100.net [172.217.8.174]

 

Tracing route to www.bungie.net [104.20.29.30]
over a maximum of 30 hops:

1 9 ms 9 ms 8 ms 70.77.96.1
2 11 ms 10 ms 8 ms rc3no-be117-1.cg.shawcable.net [64.59.134.173]
3 25 ms 24 ms 24 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
4 30 ms 28 ms 29 ms rc1wt-be18-1.wa.shawcable.net [66.163.64.81]
5 153 ms 33 ms 28 ms six.as13335.com [206.81.81.10]
6 28 ms 29 ms 29 ms 104.20.29.30

 

Tracing route to www.battle.net [24.105.29.30]
over a maximum of 30 hops:

1 9 ms 12 ms 11 ms 70.77.96.1
2 20 ms * 9 ms rc3no-be117-1.cg.shawcable.net [64.59.134.173]
3 14 ms 10 ms 11 ms rc3so-hge0-19-0-1.cg.shawcable.net [66.163.71.118]
4 40 ms 41 ms 39 ms rc4ec-be13.il.shawcable.net [66.163.65.18]
5 70 ms 40 ms 40 ms eqix-ix-ch1.blizzard.com [206.223.119.85]
6 72 ms 72 ms 73 ms 37.244.1.33
7 75 ms 74 ms 82 ms 24.105.31.52
8 75 ms 78 ms 72 ms 37.244.0.101
9 * * * Request timed out.
10 78 ms 72 ms 72 ms 24.105.29.30

 

has more or less made the destiny 2 beta unplayable as it seems to be a packet loss issue

Outcomes