I live in Abu Dhabi in the UAE and I have both an NA account and an EU account, both on the same battle.net account.
Yesterday I was playing on my NA account and all of a sudden was disconnected and couldn’t reconnect. Even after 24 hours, I still can’t get beyond the “Logging into game server” message.
If I connect via VPN however, it works.
Then try the EU account, and it connects fine even without the VPN.
Any ideas?
Trace route to the server. Change your DNS. Trace route again to avoid the bad hop.
Thank you for the reply! I appreciate it 
Can I post my tracerts here for you to look at?
Here’s the tracert to EU:
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.86.1
2 6 ms 6 ms 6 ms bba-92-96-136-1.alshamil.net.ae [92.96.136.1]
3 11 ms 8 ms 7 ms 10.246.255.62
4 12 ms 12 ms 12 ms 195.229.4.68
5 120 ms 121 ms 121 ms 195.229.4.235
6 124 ms 124 ms 123 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
7 127 ms 127 ms 127 ms ae1-br01-eqfr5.as57976.net [137.221.80.33]
8 133 ms 133 ms 134 ms et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
9 242 ms 139 ms 139 ms xe-0-0-1-br01-cthz1.blizzardonline.net [137.221.65.157]
10 129 ms 129 ms 129 ms 137.221.78.55
11 126 ms 127 ms 126 ms 185.60.112.157
Trace complete.
And here’s the tracert to Oceanic (I play on Frostmourne):
Tracing route to 103.4.115.248 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.86.1
2 6 ms 6 ms 6 ms bba-92-96-136-1.alshamil.net.ae [92.96.136.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 *
So next step would be to go into my router and change the DNS?
I wonder why it just randomly happened all of a sudden?
Thank you for your help!
I am currently getting the exact same thing and I live in Sharjah. Can only connect via VPN but Overwatch and Hearthstone work fine without one.
Hmm, that’s interesting.
Are you with Etisalat or Du? I’m with E.
ISPs have issues all the time. A sh!tty DNS will not route around them correctly like their supposed too.
Fair!
How do I route around the bad hop? Is there a particular DNS I should choose, or just any?
You can start with trying the big ones like Google or CloudFlare etc (8.8.8.8 or 1.1.1.1)
Thanks so much for your help! I’ll give that a go tomorrow and see if it resolves the issue.
If using a VPN fixes it, then it is an ISP issue, and you’ll need to complain to them or wait on them for a resolution. It happens on NA and not EU because the path you take to each of them is different, so whatever hop along the way is causing you the issue isn’t present on the other route.
DNS is unrelated to this and can’t fix your issue. DNS can’t change the route your traffic takes - a VPN can.
DNS routing policies ensure that traffic is distributed according to the configured weights. This includes avoiding packet loss / high ping times etc. A DNS 110% does effect routing of traffic.
i’m no expert, but it is my understanding that DNS weighting refers to where to send traffic when different servers respond to the same address. So if blizzard.com could be resolved by a server in chicago and a server in la then the dns would help determine which one should be used. but when connecting to a particular game server there is only one location. it has no power to tell your traffic what route to take to the same location, once the location IP is resolved it is not involved in the process of determining a path.
if my understanding is lacking i would welcome more explanation.
The DNS tables influence the Border Gateway Protocols / mesh’s used to route traffic. ISPs will try to force their own over what is working best. Which is why it’s very common to run into this issue and switching your DNS to less biased one works better which allows protocols and weights to actually work.
Same reason most FPS players will recommend you change to a better DNS for better ping due to better routing it ends up providing.
I can’t find anything online that is in agreement with that explanation. Border gateway protocol happens after DNS lookup, independently. A different DNS server can reduce the time it takes to resolve the ip you head to but isn’t going to impact routing to your destination. Can you find any online resources that might explain further.
cloud.google. com/dns/docs/zones/manage-routing-policies
I just wanted to follow up on this and confirm that by changing my DNS, the issue was resolved. For the record, I changed primary to 1.1.1.1 and secondary to 1.0.0.1
Thank you very much to everyone that helped, I’m very grateful.
I had this issue for the past 3 weeks and live in the UAE, only worked when I had a VPN on. Had a small update today and its now fixed and can play without a VPN, dont know if it was the update or if Etisalate did something, but all is g now.
glad it is resolved, whatever the source of the fix was. I suspect since eligos you also saw that yours was fixed today without changing the dns that this was an ISP fix. that linked source again does not indicate that changing your DNS can change your routing to a particular IP address - it is discussing that you can have multiple servers that respond to a particular DNS lookup, and you can assign a weight to which server IP is given when that particular site is looked up, not that the DNS can choose how that traffic reaches the server once the IP is given. but whoever is right, glad it is fixed.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.