Disconnect Issues while Multiboxing After DDoS.

[Xeneres]

Well I have an update to my original post.

I tried using a Proxy/VPN service and set it to Texas and I can now play the game once again without being disconnected.

The service I'm trying out is called WTFast and its a free for 30 days(don't have to enter payment info or anything). To any of you boxing a 10+ toons and have had disconnect issues since the DDoS give it a try and see if it solves your issues.

Obviously these services are hit or miss and can either help or hurt(generally hurt) your latency and connection to the game. It raised my latency from 80-90 to 95-110.

I found it on this thread:

http://us.battle.net/wow/en/forum/topic/14058226328

Here is my response on the thread:

I do not have the mount/character not found issue but I tried using WTFast this and I think it has solved my issue!

Please lets give this thread more attention!

I'm a 15 boxer and i have been unable to play since the DDoS. Whenever I attempted to enter old raids or pull trash or even take portals to say Dalaran or Orgrimmar I'm disconnected on 4 to all 15 of my toons at random, instantly.

I live in WV and when I use my normal connection or use WTFast proxy and set it to Chicago I disconnect when I use that to connect to the game. Chicago gives me the best ping so its probably also the path to where my ISP routes traffic to get to the LA datacenters.

I tested changing WTFast to a hub in Texas and I can log in much faster and I Don't disconnect when I pull trash, take portals, or engage bosses.

This is a not an optimal solution as I can know play but it does raise my ping 10-40 more. I also shouldn't have to use a proxy/VPN service to stay connected to this game...

I'm playing on the Blackrock server which is on the LA datacenter.

Its looking like there is an issue with our path to the LA datacenter or an issue on blizzards system side or ISP problems.

Here is my tracert:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 10 ms 8 ms 10.227.0.1
3 13 ms 8 ms 9 ms 173-219-252-2-link.sta.suddenlink.net [173.219.252.2]
4 11 ms 9 ms 8 ms 173-219-252-208-link.sta.suddenlink.net [173.219.252.208]
5 26 ms 25 ms 25 ms 173-219-252-188-link.sta.suddenlink.net [173.219.252.188]
6 26 ms 33 ms 27 ms 66-76-232-41.tyrd.suddenlink.net [66.76.232.41]
7 27 ms 32 ms 27 ms chi-b21-link.telia.net [213.248.71.45]
8 28 ms 47 ms 28 ms att-ic-155020-chi-b21.c.telia.net [213.248.87.254]
9 81 ms 83 ms 81 ms cr1.cgcil.ip.att.net [12.122.133.34]
10 81 ms 83 ms 83 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 86 ms 85 ms 84 ms cr1.slkut.ip.att.net [12.122.30.25]
12 87 ms 86 ms 84 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 242 ms 124 ms 83 ms gar5.lsrca.ip.att.net [12.122.85.33]
14 85 ms 81 ms 80 ms 12-122-254-226.attens.net [12.122.254.226]
15 80 ms 81 ms 80 ms 206.16.68.42
16 83 ms 84 ms 83 ms paxonix-placeholder.lax1.attens.net [12.129.248.118]
17 82 ms 82 ms 81 ms 12.129.209.68

Trace complete.

Let me know if this has also helped you with connection issues that started since the DDoS