Charter Spectrum → [Speed Issues] Slow speeds/high latency at night (WI)

Curious if this is a problem many have around here... I'm assuming it's nodes or whatnot being overloaded as seems to be a common issue with Charter and US ISPs in general...

Around 6-10pm basically every night my ping to game servers in places like Chicago and Texas become as high as 300-400. It's not 100% consistently that high, often just very rapid spikes, going up from 60 or so up to the 400 and back several times a minute. A lot of times (but I don't notice it every time) my speeds in general drop, too. I was getting about 100 kb/s only a half hour ago while trying to download things and was unable to even watch any sorts of videos in my browser.

It's really frustrating given I work around 6am-2:30, then get home and can't utilize my internet more than a few hours before it completely goes to crap until I go to sleep.

Couple traces I did to a Chicago server (for Counterstrike: Global Offensive)...

Tracing route to host.colocrossing.com [198.144.179.101]
over a maximum of 30 hops:

1 1 ms tracert 198.144.179.101

Tracing route to host.colocrossing.com [198.144.179.101]
over a maximum of 30 hops:

1 1 ms tracert 198.144.179.101

Tracing route to host.colocrossing.com [198.144.179.101]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 11 ms 7 ms 10.134.32.1
3 83 ms 120 ms 152 ms crr02fdlcwi-tge-0-4-0-4.fdlc.wi.charter.com [96.
34.20.132]
4 41 ms 42 ms 32 ms crr03fdulwi-bue-1.fdul.wi.charter.com [96.34.20.
248]
5 31 ms 29 ms 40 ms crr02euclwi-tge-0-7-0-7.eucl.wi.charter.com [96.
34.24.53]
6 81 ms 82 ms 61 ms bbr02euclwi-bue-4.eucl.wi.charter.com [96.34.2.6
]
7 210 ms 177 ms 31 ms bbr01chcgil-bue-1.chcg.il.charter.com [96.34.0.9
]
8 76 ms 54 ms 47 ms prr01chcgil-bue-2.chcg.il.charter.com [96.34.3.9
]
9 56 ms 66 ms 73 ms ae14.ar1.ord1.us.nlayer.net [69.31.111.113]
10 196 ms 214 ms 85 ms ae1-70g.cr2.ord1.us.nlayer.net [69.31.111.137]
11 40 ms 37 ms 91 ms as23352.ae6-102.cr2.ord1.us.nlayer.net [69.31.11
1.3]
12 80 ms 53 ms 64 ms ae4.cr2.ord6.us.scnet.net [204.93.204.87]
13 95 ms 107 ms 109 ms 72.ae2.ar2.ord6.us.scnet.net [204.93.204.159]
14 81 ms 91 ms 69 ms as36352.xe-0-1-0.ar2.ord6.us.scnet.net [50.31.17
0.126]
15 50 ms 37 ms 59 ms 10ge-1-3-2.fz146.cr2.chi.colocrossing.com [206.2
17.137.254]
16 39 ms 38 ms 37 ms host.colocrossing.com [205.234.152.250]
17 35 ms 48 ms 48 ms host.colocrossing.com [198.144.179.101]

There doesn't appear to be anything wrong indicated in that particular trace, which appears to be to a server in Chicago? Maybe try again when the actual problem is happening, or maybe the actual problem isn't a routing issue.