Well, I play on the EU servers, but the 1.8 patch fvcked us over pretty good too.
Wasn't so much the realm servers themselves, they were mostly fine, though the one I'm on crashed once or twice in the days after the patch, but it's EXTREMELY overloaded, so I'm not surprised.
The instance servers got majorly fvcked up, we canceled every MC and BWL raid due to the lag, there was just no way to play, people getting freeze lag, disconnects, or just good ole 5k+ pings.
Heh, we even wiped twice at Lucifron for the first time since we first beat him a long time ago because the priests/mages couldn't dispell.
Has gotten much better since this weekend though, we did a BWL raid the other day, worked fine.
Did a traceroute to the US datacenter just for...well don't know why, fun?
Oh and Blizzard did admit that it was mostly an internal problem on the public forums, guess it could be a different issue than in the US, but they do sound awfully similar...
Wasn't so much the realm servers themselves, they were mostly fine, though the one I'm on crashed once or twice in the days after the patch, but it's EXTREMELY overloaded, so I'm not surprised.
The instance servers got majorly fvcked up, we canceled every MC and BWL raid due to the lag, there was just no way to play, people getting freeze lag, disconnects, or just good ole 5k+ pings.
Heh, we even wiped twice at Lucifron for the first time since we first beat him a long time ago because the priests/mages couldn't dispell.
Has gotten much better since this weekend though, we did a BWL raid the other day, worked fine.
Did a traceroute to the US datacenter just for...well don't know why, fun?
Not too horrible given that I'm across the Atlantic 😉1 <1 ms <1 ms <1 ms 192.168.201.1
2 1 ms <1 ms 1 ms ua-213-114-177-194.cust.bredbandsbolaget.se [213.114.177.194]
3 1 ms 1 ms 1 ms vlan3.dr2.sto22.se.bredband.com [195.54.116.34]
4 1 ms 1 ms 1 ms vlan2.dr1.sto22.se.bredband.com [195.54.116.117]
5 1 ms 1 ms 1 ms port-channel15.cr1.sto3.se.bredband.com [195.54.116.121]
6 2 ms 2 ms 1 ms ge12-0.cr2.sto2.se.bredband.com [195.54.123.41]
7 2 ms 2 ms 2 ms pos13-0.cr1.sto1.se.bredband.com [195.54.123.105]
8 1 ms 1 ms 2 ms pos9-0.br3.sto1.se.bredband.com [195.54.123.186]
9 2 ms 2 ms 2 ms 64.215.185.81
10 111 ms 111 ms 110 ms so1-2-0-2488M.ar1.DCA3.gblx.net [67.17.67.53]
11 105 ms 105 ms 104 ms 208.50.13.254
12 170 ms 170 ms 171 ms tbr1-p014001.wswdc.ip.att.net [12.123.9.82]
13 170 ms 170 ms 170 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
14 173 ms 173 ms 173 ms tbr2-cl2.sffca.ip.att.net [12.122.10.42]
15 173 ms 172 ms 172 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
16 181 ms 180 ms 181 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255.254]
17 181 ms 181 ms 181 ms mdf1-bi8k-1-eth-2-3.lax1.attens.net [12.129.192.126]
Oh and Blizzard did admit that it was mostly an internal problem on the public forums, guess it could be a different issue than in the US, but they do sound awfully similar...