Ping Spikes Constantly

Ping is normally around 60, but is constantly spiking to the 90s and up to around 160. If it was a consistent 90 it wouldn’t even be that bad, but its spiking so I get terrible rubber banding constantly. These are the results of the Battle.net Looking Glass Test. I’m not super tech savy, so I’m not sure how to interpret it. Can anyone help me out?
Every time it says “comcast.” it’s actually a “.net” but I removed the “.net” because it comes out as a link when I try to post it in the forum and it doesn’t allow links.

TRACEROUTE:
traceroute to 76.111.208.55 (76.111.208.55), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.338 ms 0.324 ms 0.323 ms
2 24.105.18.131 (24.105.18.131) 1.029 ms 1.039 ms 1.038 ms
3 137.221.105.12 (137.221.105.12) 5.160 ms 5.178 ms 5.179 ms
4 137.221.66.16 (137.221.66.16) 0.642 ms 0.661 ms 0.663 ms
5 137.221.83.80 (137.221.83.80) 31.278 ms 31.279 ms 31.457 ms
6 137.221.65.68 (137.221.65.68) 26.705 ms 23.104 ms 23.072 ms
7 137.221.68.32 (137.221.68.32) 6.056 ms 6.615 ms 6.621 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast. (50.242.151.165) 5.843 ms 5.899 ms 5.913 ms
9 be-11587-cr02.losangeles.ca.ibone.comcast.(68.86.83.17) 7.565 ms 6.301 ms 6.351 ms
10 be-11523-cr01.houston.tx.ibone.comcast.(68.86.87.174) 33.433 ms 33.381 ms 33.358 ms
11 be-11423-cr02.56marietta.ga.ibone.comcast.(68.86.85.21) 46.096 ms 46.094 ms 46.073 ms
12 be-1302-cs03.56marietta.ga.ibone.comcast.(96.110.32.77) 45.199 ms 44.818 ms 45.147 ms
13 96.110.43.138 (96.110.43.138) 62.624 ms 96.515 ms 96.744 ms
14 162.151.164.166 (162.151.164.166) 60.676 ms 62.640 ms 62.653 ms
15 96.110.139.202 (96.110.139.202) 61.001 ms 62.134 ms 62.021 ms

25/05/2020 03:21:02 UTC

PING:
PING 76.111.208.55 (76.111.208.55) 56(84) bytes of data.
64 bytes from 76.111.208.55: icmp_seq=1 ttl=50 time=105 ms
64 bytes from 76.111.208.55: icmp_seq=2 ttl=50 time=71.6 ms
64 bytes from 76.111.208.55: icmp_seq=3 ttl=50 time=74.0 ms
64 bytes from 76.111.208.55: icmp_seq=4 ttl=50 time=88.0 ms

— 76.111.208.55 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 71.628/84.889/105.859/13.624 ms

25/05/2020 03:21:02 UTC

MTR:
Start: Mon May 25 03:21:02 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.9 0.5 2.2 0.3
3.|-- 137.221.105.12 0.0% 10 0.9 1.0 0.8 1.2 0.0
4.|-- 137.221.66.16 0.0% 10 0.5 4.5 0.4 36.8 11.4
5.|-- 137.221.83.80 0.0% 10 11.9 6.5 5.8 11.9 1.9
6.|-- 137.221.65.68 0.0% 10 18.3 10.3 5.8 37.2 10.2
7.|-- 137.221.68.32 0.0% 10 6.0 13.1 5.9 43.4 13.4
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast. 0.0% 10 5.7 5.7 5.6 5.8 0.0
9.|-- be-11587-cr02.losangeles.ca.ibone.comcast. 0.0% 10 6.1 7.6 6.1 8.9 0.6
10.|-- be-11523-cr01.houston.tx.ibone.comcast. 0.0% 10 32.6 33.5 32.6 35.9 0.8
11.|-- be-11423-cr02.56marietta.ga.ibone.comcast. 0.0% 10 45.7 45.9 45.1 46.6 0.0
12.|-- be-1302-cs03.56marietta.ga.ibone.comcast. 0.0% 10 45.3 45.5 45.0 46.0 0.0
13.|-- 96.110.43.138 0.0% 10 66.0 63.7 62.7 66.2 1.2
14.|-- 162.151.164.166 0.0% 10 60.7 60.8 60.7 61.3 0.0
15.|-- 96.110.139.202 0.0% 10 60.9 60.9 60.8 60.9 0.0
16.|-- c-76-111-208-55.hsd1.fl.comcast. 0.0% 10 98.4 81.3 69.6 115.8 14.9

25/05/2020 03:21:02 UTC

The connection looks good until it hits your local Comcast node. You can see the worst ping of 115ms in the last line.

Hey, Espada! Could you include a WinMTR test to compare? This test is usually only helpful if we request it specifically for a mass known issue, but the spike on the comcast peering is a bit of a concern. The WinMTR test should help with narrowing down the concern.

Gather a WinMTR file until the problem occurs for 10 to 15 minutes. Copy and paste the text file created and paste it between two ~~~ like so:

~~~
WinMTR Here
~~~

If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)