Problems connecting to Blizzard Games

I am having the same problems from Henderson, NV.

Also having the same problem. any notice when the problem will be tended to?  (henderson, NV)

same I am in Tulsa Oklahoma and I can't stay connected to world of warcraft for more than a minute and it disconnects me plz fix cox

Having the same issue here in Omaha, NE . I spoke with an online customer service rep about 4 hours ago, who acknowledged the issue but said there is no time estimate for the fix. Hopefully this gets resolved soon.

Same in Gilbert AZ

Same. Sierra Vista, AZ. Everyone I know that live in this same area has issues as well.

Same problem here

Wichita Kansas

I am having the same issues in RI.

This is getting very annoying please fix this asap. GA

Same problem, Mesa AZ

Same issues. Going on since about 10pm, and it's now approaching 4:30am. Cox states it's a Blizzard issue. Since Las Vegas is nothing but a simple hop to Blizzards servers, and you can't even perform a tracert, I think someone screwed up somewhere.

Blizzards support hours are pretty lax, but during a nationwide service issue like this it should be at Tier III support and resolved by now. So much for ToS.

Did a tracert, does show it's exiting Cox network, looks like it's hanging at ATT in San Diego. Similar results from Blizzard forum posters as well. The network equipment is owned by ATT.

C:\>tracert 12.129.209.68   (Aman'Thul)

Tracing route to 12.129.209.68 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  NAS [192.168.1.1]
  2     9 ms     7 ms     7 ms  10.67.64.1
  3    10 ms     9 ms     7 ms  24-234-16-149.ptp.lvcm.net [24.234.16.149]
  4     9 ms    12 ms     8 ms  24-234-6-29.ptp.lvcm.net [24.234.6.29]
  5     7 ms     7 ms     7 ms  24-234-6-222.ptp.lvcm.net [24.234.6.222]
  6    21 ms    14 ms    13 ms  langbprj01-ae1.rd.la.cox.net [68.1.1.13]
  7    21 ms    21 ms    21 ms  xe-7-3-1.edge2.LosAngeles9.Level3.net [4.53.230.41]
  8    24 ms    23 ms    23 ms  vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
  9    17 ms    19 ms    18 ms  ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5]
 10    17 ms    17 ms    18 ms  ae-6-6.ebr1.Tustin1.Level3.net [4.69.153.222]
 11    25 ms    23 ms    23 ms  ae-107-3507.bar2.Tustin1.Level3.net [4.69.158.106]
 12    28 ms    27 ms    31 ms  192.205.37.145
 13    30 ms    27 ms    28 ms  cr2.la2ca.ip.att.net [12.122.129.106]
 14    87 ms    24 ms    23 ms  gar29.la2ca.ip.att.net [12.122.129.241]
 15    25 ms    23 ms    23 ms  12-122-254-234.attens.net [12.122.254.234]
 16    18 ms    19 ms    19 ms  mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
 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.

Already lost 1.3 million....

OK I have been using pingplotter Which gives real time pings every few seconds, constant  trice updates. Normally I am connection goes Tulsa to Oklahoma City and on to Cox's major Hub near Atlanta GA. IP # 68.1.2.109. From there I am routed to Level3 in Dallas, and from there it5 goes to the At&t's backbone, and on to Blizzard's servers in LA. For a normal total of about 13 hop.

Pingplotter is not showing unusual with packet loss as long as this rout remains steady. However all of a sudden the routing will change, from Cox in Atlanta - Level3 in Dallas, to from Cox in Atlanta - Verizon in New York City, &/or Level3 in New York. From there it takes several hops  until it hits AT&T's backbone somewhere NY State, and from there on to Blizzard in LA rising  the number of hops to 16 - 18.

It is these odd side trips though NY and that AT&T backbone, where it starts to show high packet loss on each of the hops between NY & LA.
                               

Between the forums here and the forums on blizzard I'm not sure who is at fault and I don't really care but someone needs to stop playing the blame game and get it fixed.....People posting Cox says it's an issue with Blizzard and Blizzard saying its an issue with Cox....I wish one of the companies would post something about being aware of the issue and give us more information, this is really frustrating!

I am having isues as well in OKC, OK  from what I have gathered there is a eastern Hub that has lost power and this is the root cause of the issues, as of yet unaware of a timeframe of fix .