Spikes Spikes and more Spikes, been happening since the Retribution update, and it causes rubberbanding, i dont whats going on, bets i can tell you is that, when ever i press CTRL-SHIFT-N, it has orange bars whenever spikes happen
Hey iFlameDragon,
With the high IND and the packet loss (orange bars) it does look like there is some kind of connection issue going on here.
To help find where the connection trouble is happening, please post the results from a pathping, trace route and a Looking-Glass. Paste the pathping, trace route and the Looking-Glass into the post, select and highlight everything you just pasted, and hit the “code” button (</>). That’ll make the information much more readable.
TRACEROUTE:
traceroute to 72.74.144.8 (72.74.144.8), 15 hops max, 60 byte packets
1 10.56.70.56 (10.56.70.56) 0.284 ms 0.282 ms 0.283 ms
2 37.244.22.3 (37.244.22.3) 0.804 ms 0.829 ms 0.832 ms
3 24.105.30.158 (24.105.30.158) 1.064 ms 2.653 ms 2.684 ms
4 137.221.66.0 (137.221.66.0) 2.693 ms 2.695 ms 2.696 ms
5 137.221.68.70 (137.221.68.70) 49.543 ms 49.628 ms 49.639 ms
6 137.221.68.34 (137.221.68.34) 2.676 ms 1.375 ms 1.367 ms
7 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 1.735 ms 1.387 ms 1.406 ms
8 uunet.lax05.atlas.cogentco.com (154.54.13.86) 1.169 ms 1.196 ms 1.182 ms
9 * * *
10 ae204-0.BSTNMA-VFTTP-307.verizon-gni.net (100.41.214.65) 71.850 ms 71.856 ms 71.855 ms
11 pool-72-74-144-8.bstnma.fios.verizon.net (72.74.144.8) 75.524 ms 77.928 ms 78.361 ms
24/05/2018 21:17:51 UTC
--------------------
PING:
PING 72.74.144.8 (72.74.144.8) 56(84) bytes of data.
64 bytes from 72.74.144.8: icmp_seq=1 ttl=51 time=33.7 ms
64 bytes from 72.74.144.8: icmp_seq=2 ttl=51 time=35.1 ms
64 bytes from 72.74.144.8: icmp_seq=3 ttl=51 time=34.2 ms
64 bytes from 72.74.144.8: icmp_seq=4 ttl=51 time=33.2 ms
--- 72.74.144.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 33.275/34.103/35.179/0.708 ms
24/05/2018 21:17:52 UTC
--------------------
PING:
PING 72.74.144.8 (72.74.144.8) 56(84) bytes of data.
64 bytes from 72.74.144.8: icmp_seq=1 ttl=50 time=79.5 ms
64 bytes from 72.74.144.8: icmp_seq=2 ttl=50 time=75.7 ms
64 bytes from 72.74.144.8: icmp_seq=3 ttl=50 time=75.3 ms
64 bytes from 72.74.144.8: icmp_seq=4 ttl=50 time=76.8 ms
--- 72.74.144.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 75.304/76.860/79.518/1.664 ms
24/05/2018 21:17:51 UTC
--------------------
TRACEROUTE:
traceroute to 72.74.144.8 (72.74.144.8), 15 hops max, 60 byte packets
1 10.57.68.13 (10.57.68.13) 0.279 ms 0.266 ms 0.263 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 ae-4.r08.chcgil09.us.bb.gin.ntt.net (129.250.4.157) 2.461 ms 2.477 ms 2.477 ms
9 ae-31.a00.chcgil09.us.bb.gin.ntt.net (129.250.3.159) 8.160 ms 8.196 ms 8.202 ms
10 0.xe-10-2-0.BR3.CHI13.ALTER.NET (204.255.168.69) 1.688 ms 1.726 ms 1.730 ms
11 * * *
12 ae204-0.BSTNMA-VFTTP-307.verizon-gni.net (100.41.214.65) 27.441 ms 27.461 ms 27.868 ms
13 pool-72-74-144-8.bstnma.fios.verizon.net (72.74.144.8) 35.775 ms 33.232 ms 37.532 ms
24/05/2018 21:17:52 UTC
--------------------
MTR:
Start: Thu May 24 21:17:52 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.56.70.56 0.0% 10 0.3 0.3 0.2 0.6 0.0
2.|-- 37.244.22.3 0.0% 10 0.4 0.6 0.4 1.1 0.0
3.|-- 24.105.30.158 0.0% 10 0.9 1.0 0.8 2.2 0.3
4.|-- 137.221.66.0 0.0% 10 1.7 1.6 1.5 1.8 0.0
5.|-- 137.221.68.70 0.0% 10 1.4 2.9 1.3 15.7 4.5
6.|-- 137.221.68.34 0.0% 10 1.3 1.3 1.1 1.6 0.0
7.|-- te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 1.5 1.5 1.4 1.9 0.0
8.|-- uunet.lax05.atlas.cogentco.com 0.0% 10 1.7 5.5 1.2 11.8 4.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ae204-0.BSTNMA-VFTTP-307.verizon-gni.net 0.0% 10 69.8 69.9 69.6 71.1 0.3
11.|-- pool-72-74-144-8.bstnma.fios.verizon.net 0.0% 10 76.8 76.4 75.1 78.7 0.9
24/05/2018 21:17:51 UTC
--------------------
MTR:
Start: Thu May 24 21:17:52 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.57.68.13 0.0% 10 0.5 0.4 0.3 0.6 0.0
2.|-- 37.244.23.2 80.0% 10 0.6 0.6 0.6 0.6 0.0
3.|-- 24.105.62.146 0.0% 10 1.2 1.4 1.2 1.9 0.0
4.|-- 137.221.66.12 80.0% 10 2.7 2.6 2.6 2.7 0.0
5.|-- 137.221.69.72 0.0% 10 2.4 2.4 2.3 2.6 0.0
6.|-- 137.221.69.34 0.0% 10 2.3 2.9 1.7 12.5 3.3
7.|-- xe-0-0-16-2.a02.chcgil09.us.bb.gin.ntt.net 70.0% 10 2.5 2.7 2.0 3.8 0.7
8.|-- ae-4.r08.chcgil09.us.bb.gin.ntt.net 0.0% 10 2.4 3.4 2.4 11.6 2.8
9.|-- ae-31.a00.chcgil09.us.bb.gin.ntt.net 0.0% 10 8.1 11.4 2.3 31.2 9.2
10.|-- 0.xe-10-2-0.BR3.CHI13.ALTER.NET 0.0% 10 1.6 1.7 1.6 2.3 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ae204-0.BSTNMA-VFTTP-307.verizon-gni.net 0.0% 10 27.4 27.6 27.4 28.2 0.0
13.|-- pool-72-74-144-8.bstnma.fios.verizon.net 0.0% 10 34.3 34.2 33.2 35.4 0.3
24/05/2018 21:17:52 UTC
--------------------
Here is what i got from the Looking Glass
Sorry for the delay. The Looking glass does look good. Please post the results from the trace route and pathping too.
lets just say i dont know the password end of story, dont wanna go into detail, so idk. Im getting an internet upgrade soon so hopefully it will fix, thanks for your help 
its not horribly bad anymore and just happens every now and then, it was worse when i posted, again thanks for your help