Not currently, and technically it’s still under investigation. Some players may still see some weird behavior, like more minor connection issues/disconnections or higher than normal latency due to the detour they’re taking. All we did was work with the ISPs involved and some of our other peers to route people around the issue until they can get it resolved. The backbone providers are still working on the core problems.
3 Likes
finally able to hearth out of the dungeon. thank you for all you do Blizz much respect
1 Like
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 1 ms 2 ms 1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 4 ms 2 ms 4 ms 24.105.62.129
Trace complete.
I’m able to log in and Warcraft is running great for me after the modifications that were done by the Blizzard team.
For all the people that worked on a solution to getting this to work, thank you very much.
3 Likes
Still cannot log in
Everytime i queue for something and join in my game lags out.
I joined a BG on my priest, got stuck at 75% load in, I closed and reopened my client 5 times before it let me into the BG then everything was lagged out. I could run and talk but none of my abilities would work, everyone was running in place, i couldn’t log out or exit the game without force closing. chat was still working. My world MS was 0, home MS at 47.
I switched to my mage and tried to do a LFR run. Load screen took about 3mins to load me in and i had the same problems as the BG. I can’t even log into my mage now. He’s stuck in an eternal load screen for Azshara’s palace.
I was leveling a lowbie about 3 hours ago and didn’t have any of these problems. This started about 30 mins ago.
Hi Zinjobwa
There have been some major ongoing connection issues with the game since early morning. I wonder if you are caught up in that.
can you please “work with” Cogent Communications? I’ve had 220ms for weeks. vpn brings my ms down to around 60. Please check out my post
I just got in. yay.
2 Likes
I got into the game no problem an hour or so ago… Thankyou for your assistance in fixing this. <3
1 Like
Imagine a traffic jam at the lights going into the game… that’s kind of whats happened
Yea they did their job finally, big whoop.
1 Like
A post was split to a new topic: Jyxy - Connection Issue
Great they ruined Monday morning now they extended Tuesday’s. Thanks for ruining 2 days. Wat a great service.
This is really, really dumb, and does not correlate to this situation at all. Ponder why…and get back to us.
1 Like
Issues just started for me after being fine all day. I logged into the game around 20:00 Eastern and started dc’ing about every 20 mins. When I dc, the traceroute doesn’t make it past my ISP. A successful traceroute follows.
C:\WINDOWS\system32>tracert 24.105.30.129
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 2 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms 192.168.254.254
3 30 ms 30 ms 35 ms vl-1944.dr01.bltmmdsn.cavtel.com [98.140.242.1]
4 34 ms 31 ms 38 ms ae0-100.agr01.phla03-pa.us.windstream.net [64.83.47.61]
5 32 ms 33 ms 35 ms static-66-16-64-62.dsl.cavtel.net [66.16.64.62]
6 36 ms 36 ms 36 ms xe2-1-0-0.agr01.alxn01-va.us.windstream.net [98.140.159.90]
7 38 ms 37 ms 38 ms xe2-0-0-0.agr01.rstn01-va.us.windstream.net [76.161.151.110]
8 48 ms 48 ms 49 ms static-98-140-159-38.dsl.cavtel.net [98.140.159.38]
9 49 ms 49 ms 50 ms static-98-140-159-25.dsl.cavtel.net [98.140.159.25]
10 49 ms 50 ms 49 ms ae9-0.cr01.asbn01-va.us.windstream.net [40.136.99.148]
11 * * * Request timed out.
12 114 ms 113 ms 113 ms ae1-br01-eqdc2.as57976.net [137.221.72.33]
13 114 ms 112 ms 112 ms et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
14 113 ms 115 ms 115 ms 137.221.65.132
15 131 ms 217 ms 154 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
16 114 ms 116 ms 117 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
17 119 ms 118 ms 113 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
18 114 ms 114 ms 114 ms 24.105.30.129
Trace complete.I was fine today (10:45-15:30) when everyone else had issues. Since about 20:00 Eastern, I’ve been dc’ing every 20 minutes.
I am not being allowed to access trace route page
Not really. If no packets are making it through then there’s no session. However, if only some packets make it through, you could typically log in, but the rest of functionality would be limited until the remainder of packets start transferring. A prime example of this would be lag when your ping is very high. Packets don’t arrive when expected/at all and then things jump around. Networking 101. But, being that most people have at best a surface understanding of networking, it can seem like nearly anything that makes sense. This isn’t to speak negatively about those with only a surface level understanding of networking, but to highlight that different levels of understanding can lead to different conclusions depending on the person.
If you’ve ever worked Tech Support, nearly every customer you’d deal with thinks their issues are hardware, whereas someone who has training and experience would zero in on something completely different.
Example: Cell phone is running slow.
Customer’s opinion: Phone is broke
Tech’s educated guess prior to troubleshooting: Probably an app, or software corruption.
The trick is convincing the customer (ie. The person with only a basic understanding of the technology in question) that their issue isn’t necessarily what their first thought would be.
P.S I know this reply comes hours later. Everything started working for me not too long after my post.
DO NOT USE A VPN. I just did to try and log in, and BLIZZARD LOCKED MY ACCOUNT DUE TO SUSPICIOUS ACTIvITY. This is …ridiculous…!!!