frequent disconnects from mmorpg

Where is the ISP problem? That tracert looks great. The two request time out are likely firewalls just denieing the ICMP packet. If the traffic was effected the tracert would have ended at hop 2 or 9. The biggest jump I see is between hop 5 and 6 but it doesn't seem anything worrisome. But thats showing a ping of 68-73 which should be fine. What kind of ping do you get in game?

Also, what do you have your router plugged into? A standalone modem? A gateway? Another router?

Last, perhaps a pingpath will show more. Try these instructions.

I was just told it was an ISP problem when I contacted Blizzard about the issue and gave them that info as they requested.

I have a cisco linksys WRT120N router plugged into a cisco DPC3010 cable modem. I did run a pingpath as well. I will post it below as well. It just annoys me that having a 50 Mbps internet speed and I get disconnected randomly. Also my computer is connected straight into the router.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 MattandToni.ok.cox.net [192.168.1.100]
1 192.168.1.1
2 10.32.224.1
3 COX-68-12-9-160-static.coxinet.net [68.12.9.160]
4 COX-68-12-19-5-static.coxinet.net [68.12.19.5]
5 COX-68-12-19-4-static.coxinet.net [68.12.19.4]
6 68.1.2.122
7 xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
8 vlan60.csw1.Dallas1.Level3.net [4.69.145.62]
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 MattandToni.ok.cox.net [192.168.1.
100]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 10.32.224.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% COX-68-12-9-160-static.coxinet.net
[68.12.9.160]
0/ 100 = 0% |
4 13ms 0/ 100 = 0% 0/ 100 = 0% COX-68-12-19-5-static.coxinet.net
[68.12.19.5]
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% COX-68-12-19-4-static.coxinet.net
[68.12.19.4]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% 68.1.2.122
0/ 100 = 0% |
7 24ms 0/ 100 = 0% 0/ 100 = 0% xe-5-1-0.edge5.Dallas3.Level3.net
[4.59.32.93]
1/ 100 = 1% |
8 24ms 1/ 100 = 1% 0/ 100 = 0% vlan60.csw1.Dallas1.Level3.net [4.
69.145.62]

Trace complete.

What I find strange is how close a connection you have. Even with the router it only takes you 8 hops, and mine takes 17.Your traffic totally skips ATT network which is what your would expect. It gets out of Cox by Hop 7, 0 packet loss and only 24 MS. The only packet  loss is 1% at hop 8, which is the Wow server itself. So if anything is shown in the path ping, its a issue within Blizzaed. Are you VPN or Proxy someway?

Then on top of that, there doesn.t seem to be the same  ICMP firewall either. See article here. That is strange. Those two strange things could have something to do with your issue, but they are two positive things so..

"Because of the safeguards that protect our Battle.net servers, you may notice later hops in your trace route failing with an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. You may also see inflated latency numbers. You can ignore any error messages you receive after contacting our servers as they do not indicate a problem with your internet connection. To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net. 

My Pathping for comparsion

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 XXX-PC.ri.cox.net [68.1.x.x]
1 10.2.48.1
2 68.9.9.149
3 ip98-190-33-125.ri.ri.cox.net [98.190.33.125]
4 68.1.5.157
5 xe-9-2-0.edge1.NewYork1.Level3.net [4.71.186.25]
6 ae-3-80.edge3.NewYork1.Level3.net [4.69.155.145]
7 att-level3.newyork1.level3.net [4.68.63.142]
8 cr1.n54ny.ip.att.net [12.122.131.102]
9 cr2.cgcil.ip.att.net [12.122.1.2]
10 cr1.cgcil.ip.att.net [12.122.2.53]
11 cr2.dvmco.ip.att.net [12.122.31.85]
12 cr1.slkut.ip.att.net [12.122.30.25]
13 cr2.la2ca.ip.att.net [12.122.30.30]
14 gar5.lsrca.ip.att.net [12.122.85.33]
15 12-122-254-226.attens.net [12.122.254.226]
16 206.16.68.50
17 12.129.209.68

Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 XXX-PC.ri.cox.net [68.1.x.x]
0/ 100 = 0% |
1 10ms 0/ 100 = 0% 0/ 100 = 0% 10.2.48.1
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 68.9.9.149
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% ip98-190-33-125.ri.ri.cox.net [98.
190.33.125]
0/ 100 = 0% |
4 18ms 0/ 100 = 0% 0/ 100 = 0% 68.1.5.157
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% xe-9-2-0.edge1.NewYork1.Level3.net
[4.71.186.25]
0/ 100 = 0% |
6 21ms 0/ 100 = 0% 0/ 100 = 0% ae-3-80.edge3.NewYork1.Level3.net
[4.69.155.145]
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% att-level3.newyork1.level3.net [4.
68.63.142]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr1.n54ny.ip.att.net [12.122.131.1
02]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% cr2.cgcil.ip.att.net [12.122.1.2]

0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.2.53]

0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr2.dvmco.ip.att.net [12.122.31.85
]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% cr1.slkut.ip.att.net [12.122.30.25
]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.30.30
]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% gar5.lsrca.ip.att.net [12.122.85.3
3]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-226.attens.net [12.122.
254.226]
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% 206.16.68.50
0/ 100 = 0% |
17 90ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.

You do have two timeouts in your trace. Could be temporary issue with hops to them from your connection. Try hooking up your modem directly if you don't already have it set up that way.  Try the trace every time WoW dumps you and see if you have any timeouts at that time, if so probly an intermittent issue beyond Cox or Blizzard's control. But if it continues maybe Blizzard can work with ATT to notify them of a potential issue.