Firstly, I just wanted to thank you for your detailed response. I also agree that hop 9 is an issue and I have actually tried to get something done about it via TWC's direct forums on DSL reports. However, the main issue over the past few days has been on hop's 16-19. Here is a pathping that shows what my connection normally looks like:
Code:
Computing statistics for 475 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           xxxxxx.socal.rr.com [192.168.1.115]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2   11ms     0/ 100 =  0%     0/ 100 =  0%  cpe-104-33-160-1.socal.res.rr.com[104.33.160.1]
                                0/ 100 =  0%   |
  3   11ms     0/ 100 =  0%     0/ 100 =  0%  24.30.170.13
                                0/ 100 =  0%   |
  4   17ms     0/ 100 =  0%     0/ 100 =  0%  agg33.tustcaft01r.socal.rr.com [72.129.27.66]
                                0/ 100 =  0%   |
  5   17ms     0/ 100 =  0%     0/ 100 =  0%  107.14.19.30
                                0/ 100 =  0%   |
  6   19ms     0/ 100 =  0%     0/ 100 =  0%  107.14.19.121
                                0/ 100 =  0%   |
  7   17ms     0/ 100 =  0%     0/ 100 =  0%  te0-0-0-29.ccr23.lax05.atlas.cogentco.com [154.54.10.249]
                                0/ 100 =  0%   |
  8   17ms     0/ 100 =  0%     0/ 100 =  0%  be2180.ccr21.lax01.atlas.cogentco.com [154.54.41.57]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%   100/ 100 =100%  be2065.ccr21.iah01.atlas.cogentco.com [154.54.5.65]
                                0/ 100 =  0%   |
 10   67ms     0/ 100 =  0%     0/ 100 =  0%  be2172.ccr41.atl01.atlas.cogentco.com [154.54.29.17]
                                0/ 100 =  0%   |
 11   78ms     0/ 100 =  0%     0/ 100 =  0%  be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
                                0/ 100 =  0%   |
 12   84ms     0/ 100 =  0%     0/ 100 =  0%  be2518.ccr41.jfk02.atlas.cogentco.com [154.54.80.161]
                                0/ 100 =  0%   |
 13  ---     100/ 100 =100%   100/ 100 =100%  be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
                                0/ 100 =  0%   |
 14   92ms     0/ 100 =  0%     0/ 100 =  0%  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
                                0/ 100 =  0%   |
 15   86ms     0/ 100 =  0%     0/ 100 =  0%  38.122.42.34
                                0/ 100 =  0%   |
 16  ---     100/ 100 =100%   100/ 100 =100%  10.2.2.1
                                0/ 100 =  0%   |
 17   96ms     0/ 100 =  0%     0/ 100 =  0%  192.34.76.2
                                0/ 100 =  0%   |
 18   94ms     0/ 100 =  0%     0/ 100 =  0%  199.91.189.234
                                0/ 100 =  0%   |
 19   94ms     0/ 100 =  0%     0/ 100 =  0%  199.91.189.42

Trace complete.
As you can see, everything before hop 16 is about the same as the pathping I posted last night. The main difference is that hop 16+ is around 95ms, which is what I usually play at. When it was at its worst last night, hop 17 was at 367ms and hop 19 was 633ms.