Here’s my bit.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 18 ms 15 ms 14 ms 86-165-89-200.fibertel.com.ar [200.89.165.86]
6 13 ms 11 ms 11 ms ae6.baires3.bai.seabone.net [185.70.203.22]
7 138 ms 133 ms 136 ms et2-1-0.miami19.mia.seabone.net [89.221.41.181]
8 131 ms 131 ms 132 ms be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17]
9 142 ms 139 ms 143 ms be3401.ccr22.mia01.atlas.cogentco.com [154.54.47.29]
10 132 ms 132 ms 131 ms be3411.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.26.42]
11 137 ms 136 ms 134 ms te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42]
12 136 ms 136 ms 134 ms gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
13 198 ms 195 ms 196 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
14 208 ms 201 ms 201 ms xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
15 198 ms 199 ms 200 ms et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
16 221 ms 203 ms 213 ms 137.221.65.122
17 211 ms 279 ms 239 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
18 205 ms 199 ms 199 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
19 209 ms 206 ms 206 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
20 203 ms 200 ms 200 ms 24.105.30.129
Trace complete.
Thanks
Thank you 
The only thing that sticks out to me so far is that the hop right before it gets to the 137...* part of the trace isn’t in anybody else’s traceroutes.
I’m using comcast on the east coast and having the same issue.
its not the isp , its the bridges they have to cross to get to blizzard, so it might mainly be verizon but not all of it obviously
I don’t think it has anything to do with type of internets right?
well i have been trying to log on for about 2 hours .I am glad that i am not the only on
That’s bunk.
If that were the case I wouldn’t be able to log in and play PTR.
Did a Windows update this morning and started having issues after that. Wonder if there is a connection…or lack of one, in this case. PLayed fine all weekend long without any hickups.
1 Like
this is why i can’t help but think this is somthin malicious. either from people in blizzard or somthin else
Blizzard confirmed it’s NOT a DDoS.
maby not the kind you think anyway lol
yes i did the windows update this morning too and after that it stated to have problem with wow too
1 Like
As of 8/19 I’ve been having this issue. Prior to this minor lag issues but never this. This is a glaring issue! I can’t play this or OW. If this effects Classic - I’m going to scream:sob:
1 Like
more like a pending update with no option to download lol
I was playing fine this moring around 6am ect and got DC figured maybe they got a head start on the maintenance its been 6 hours now still cant get in or still isn’t frozen in game
like im hearing about this windows update , but i dont even have a button to “download” it , like wut? and it says pending lol
saw an update today when i started the launcher. updated, launched, logging into servers…indefinitely for past 6 hours for me.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 1 ms 2 ms 2 ms modem.domain [192.168.0.1]
2 5 ms 7 ms 4 ms ptld-dsl-gw53.ptld.qwest.net [207.225.84.53]
3 3 ms 3 ms 3 ms ptld-agw1.inet.qwest.net [207.225.86.161]
4 4 ms 3 ms 3 ms 209-180-169-2.ptld.qwest.net [209.180.169.2]
5 7 ms 6 ms 6 ms ae-1-3513.edge1.Seattle3.Level3.net [4.69.160.69]
6 7 ms 7 ms 27 ms BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146]
7 29 ms 28 ms 28 ms ae1-br01-eqse2.as57976.net [137.221.73.33]
8 28 ms 28 ms 29 ms xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
9 29 ms 32 ms 29 ms et-0-0-29-br02-eqsv5.as57976.net [137.221.65.117]
10 31 ms 100 ms 218 ms xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
11 29 ms 28 ms 28 ms be2-pe01-eqla1.as57976.net [137.221.68.71]
12 29 ms 30 ms 31 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
13 29 ms 28 ms 28 ms
