You probably connected to a server from a different country. 100% your fault.
<1 192.168.1.1 (192.168.1.1) 0.528 ms 0.232 ms 0.179 ms
2 10.10.1.1 (10.10.1.1) 7.858 ms 7.359 ms 7.521 ms
3 * * *
4 170.230.88.202.asianet.co.in (202.88.230.170) 12.489 ms 11.619 ms 11.585 ms
5 21.1.1.1 (21.1.1.1) 10.657 ms * 12.506 ms
6 14.140.230.241.static-ernakulam-vsnl.net.in (14.140.230.241) 53.938 ms 52.974 ms *
7 115.255.252.130 (115.255.252.130) 59.624 ms 59.420 ms 58.402 ms
8 80.81.69.1 (80.81.69.1) 58.043 ms 59.422 ms 58.190 ms
9 xe-0-0-1.0.pjr04.ldn001.flagtel.com (85.95.26.157) 188.092 ms
if-ae-5-2.tcore1.wyn-marseille.as6453.net (80.231.217.29) 268.253 ms 270.928 ms
10 if-ae-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6) 269.648 ms 271.246 ms 268.792 ms
11 if-ae-11-2.tcore1.pvu-paris.as6453.net (80.231.153.49) 269.693 ms
ldn-bb3-link.telia.net (62.115.138.150) 278.385 ms
ldn-bb4-link.telia.net (62.115.138.154) 282.120 ms
12 80.231.153.66 (80.231.153.66) 165.224 ms 167.846 ms
nyk-bb3-link.telia.net (62.115.112.244) 285.351 ms
13 * chi-b21-link.telia.net (80.91.246.162) 282.643 ms 275.079 ms
14 * > 1 192.168.1.1 (192.168.1.1) 0.528 ms 0.232 ms 0.179 ms
2 10.10.1.1 (10.10.1.1) 7.858 ms 7.359 ms 7.521 ms
3 * * *
4 170.230.88.202.asianet.co.in (202.88.230.170) 12.489 ms 11.619 ms 11.585 ms
5 21.1.1.1 (21.1.1.1) 10.657 ms * 12.506 ms
6 14.140.230.241.static-ernakulam-vsnl.net.in (14.140.230.241) 53.938 ms 52.974 ms *
7 115.255.252.130 (115.255.252.130) 59.624 ms 59.420 ms 58.402 ms
8 80.81.69.1 (80.81.69.1) 58.043 ms 59.422 ms 58.190 ms
9 xe-0-0-1.0.pjr04.ldn001.flagtel.com (85.95.26.157) 188.092 ms
if-ae-5-2.tcore1.wyn-marseille.as6453.net (80.231.217.29) 268.253 ms 270.928 ms
10 if-ae-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6) 269.648 ms 271.246 ms 268.792 ms
11 if-ae-11-2.tcore1.pvu-paris.as6453.net (80.231.153.49) 269.693 ms
ldn-bb3-link.telia.net (62.115.138.150) 278.385 ms
ldn-bb4-link.telia.net (62.115.138.154) 282.120 ms
12 80.231.153.66 (80.231.153.66) 165.224 ms 167.846 ms
nyk-bb3-link.telia.net (62.115.112.244) 285.351 ms
13 * chi-b21-link.telia.net (80.91.246.162) 282.643 ms 275.079 ms
14 *`Preformatted text`That’s totally expected. The VPN is rerouting your connection to Blizzard, including the starting point, which is something that Battlenet keeps track of.
When ever it detects a connection from somewhere besides the general area you normally log in from, it trips the security lock. An unlock only requires is a verification step, which is usually a password reset.
If you think about it, it’s far from ridiculous, but instead is very necessary. If one consistently logs in from the same general area, like their home city for example, and then all of a sudden there’s a login on the other side of the world, that reeks of a hacked account, hence “suspicious activity”.
Placing an authenticator on your account usually prevents those security locks when logging in from new (or seemingly new due to the use of a VPN) locations.
1 Like
Still not working for me.
Loading after the character select screen took a bit longer than usual but I’m in without a vpn, and at my normal healthy looking 27 ms world and home. Let see if there are any snags.
1 Like
ok fine, i get it. just a lot of frustration after so many hours. finally logged in though. I dont know why it worked- it juts suddenly did
Can confirm. Loading screen stops at 70%, then received “World Server is down”.
1 Like
World server down still when I try log on a character.
Back to the same BS as yesterday. Stuck on loading screen.
1 Like
Hey all,
This thread was for the ISP congestion issue from yesterday.
What you’re experiencing now is a different issue that Bliz has been looking into. As of about 20 mins ago, Bliz posted an update:
Essentially, give it a try now. If it’s still not working, fully logout and try the Scan and Repair.
If you still have an issue after that, start a new thread to avoid mixing the separate issues together.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 8 ms 4 ms 6 ms 24.105.62.129
Trace complete.
Guys i found a fix, at least for me. It doesn’t involve using a VPN which puts your account at risk or having to use a hotspot which could be laggy at best. After several attempts, I was able to get to the “character select” screen. Click the settings button, then navigate to the network settings and check the "Enable IPV6 when available. I was then able to login and play without any issues.
I didn’t see this until today, so I’m not sure that you will see this reply.
I’m simplifying things a bit here, but the internet is basically just a bunch of ISPs connected together. Your ISP connects to another ISP that then connects to a larger ISP and at that stage they typically connect to the really big ISPs that are considered part of the “backbone”. If you were to map it out, it would look like a big spider web (that’s where the term comes from). What happened yesterday is that 1 connection out of thousands was acting up. And since it wasn’t completely down, the error checking systems couldn’t automatically see the issue. Also, getting companies at that level to admit they have an issue is nearly impossible.
I personally once worked for a major tech company (one of the biggest in the world) and had a client that was a part of the federal government, and it took us teaming up to get one of these companies to fix an issue they had. They never admitted fault either.
Hey all,
This issue is resolved now and this thread is being locked to prevent confusion and further discussion on entirely unrelated things.
For one last bit of information, if you are concerned about getting your account temporarily locked when using a VPN, attach an authenticator to your account. That remains the primary and best way to keep your account from being hacked, and when you have one on your account you are far less likely to receive a lockout.
You can also set up two factor authentication with your phone number. By both of these methods you can secure your account in such a way that the automatic system either doesn’t trigger, or is easier to work with. More information below.