Problem with traffic to Blizzard LA servers(WoW) & Tulsa OK

For the past 2 months I would have high latency and DC at the worse possible times.  
My signal is routed 1st up to an unknown provider in Kansas, and from there they route it back down to Level3 in Dallas. Where it goes through 2 of Level3's nodes(2  hops in Dallas alone mind you), before being sent off to ATT and Blizzard's servers. My normal Latency is 67 home and 67 world, with the use of  Leatrix Latency Fix, from WoWinterface.

Almost always the problem starts with hop/node 4 which is only identified by it's IP address.  4 as usual. I have talked until I am blue in the face with cox. Nobody can tell me who is owns that node, Cox, Levele3 or somebody else. All that I can find out is from the IP it is located somewhere in Kansas. Cox can't even say for sure it doesn't belong to them.

All that I know is Cox hands it off to it, and it in turn hands it off to level 3. Cox claims that they have no control over it, are just required by Blizzard/ATT to hand it off to them, even they don't know who it is.
 
Nor can they explain why, when it is routed near KC, it is then routed down to Level3 in Dallas, instead of the ATT Backbone in KC. They say once they hand it off to the unknown they have no control over it.  

This also a few issues with data loss with the 2 level3 nodes in Dallas, but not always. In any case it always starts with the 4th hop/node.

The most they have done was replace my 4 to 5 year old cable modem.

Tonight during a sha of anger fight my Latency shot up to 696 home and 612 world.

Here is the trace I ran:

Tracing route to 12.129.209.68 over a maximum of 30 hops

  1     8 ms    14 ms     8 ms  10.33.192.1
  2     9 ms     7 ms     8 ms  COX-68-12-9-76-static.coxinet.net [68.12.9.76]
  3    20 ms    19 ms     9 ms  COX-68-12-19-152-static.coxinet.net [68.12.19.152]
  4     *       22 ms     *     68.1.5.135
  5    19 ms    19 ms    21 ms  xe-11-0-0.edge4.Dallas3.Level3.net [4.71.122.21]
  6    21 ms    24 ms    22 ms  ae-1-60.edge10.Dallas1.Level3.net [4.69.145.18]
  7    38 ms    39 ms    35 ms  ATT [4.68.62.230]
  8    69 ms    65 ms    63 ms  cr2.dlstx.ip.att.net [12.123.16.110]
  9    69 ms    67 ms    71 ms  cr2.la2ca.ip.att.net [12.122.28.178]
 10    70 ms    69 ms    69 ms  gar29.la2ca.ip.att.net [12.122.129.241]
 11    66 ms    62 ms    69 ms  12-122-254-238.attens.net [12.122.254.238]
 12    64 ms    74 ms    66 ms  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Sorry I was not able to run a pathping, as it cleared up before I could do so.

Edit if anyone can find out what company owns the 4th node/hop 68.1.5.135 and let me know, I will be very grateful to know who I am talking about.