Continuous Issue of being stuck on Loading Screens

Blizzard , any updates ? were you able to check the logs from your end ? dont you have logs on your servers ? or simply you guys made a terrible contract with a AWS and since you have already paid them there is nothing you can do about it, We do understand it is difficult to admit it, but admitting is better than just ignoring the matter…

Please fix this issue BLIZZARD
we can’t log in WOW and we should use VPN
then you’re gonna ban us for changing our IP

Still waiting for an official statement about the issue.

Do you guys that sitting in bllizard, know that many of us can’t even play our characters ? I have to change realm, create a new character, after some hours, this error again, and again and again and again … .
Do you know this and do nothing or just don’t care about it?

Use a vpn untill it’s fixed no other fix

Hello all o/

Im stopping by this thread to let you know that the issue is still being looked into. I highly realise that some of you want more information on what is happening and I can only apologise that I cannot share with you the in-depth analysis of what is going on.

What has been found for many is that the issue seems to stem from a routing problem initially and is compounded later on. By then going to a different shard, the routing can alter and net a better performance. This would also hint at why a VPN works for some because that naturally changes the routing yet you still hit the same Blizzard servers at the end of it.

The issue has not been dismissed despite the radio silence and I can still collect and send on any traceroutes or MTR’s that you guys want to provide. For those that have provided them already, I thank you very much as it has already helped quite a bit in painting the picture of what is happening.

For those that have simply mentioned you have the problem but not provided a connection file in this thread, I can only ask again that you provide this file as the more information we have, the better. Of course this is up to you if you want to provide it however I really do hope that you will if you have not already.

Again I know this doesnt magically fix the issue and I get that alot of you are frustrated by this. I fully understand how frustrating this issue can be and again I assure you, it is something that is being looked into.

2 Likes

So… from the point we all found it’s fixed via VPN you found out it’s related to routing, not UI! How genius!

They already know exactly what is happening they just want evidence to destroy amazon and get their money back.

1 Like

hi i know u guys working on it but we still have problem and its fix with VPN. the question is: can we use vpn without any ban until this issue completely fixed?

idk but i think with COVID-19 outbreak there comes shortage of the following:

  • phosphorous: since it took almost a decade to identify that the problem is routing related.
  • developers: since it is taking two or three more decades to debug your codes and patch the problem. (just as expected, nothing new this expansion)
  • computer and internet: since i still have no clue why an IT related problem which all employees are doing work from home is taking so long to get fixed even tho it was identified from start (not by blizzard)!

well here’s my MTR logs. hopefully it’ll help a bit.

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 57 | 57 | 0 | 0 | 10 | 0 |

| No response from host - 100 | 12 | 0 | 0 | 0 | 0 | 0 |

| 10.134.145.1 - 0 | 57 | 57 | 49 | 77 | 104 | 64 |

| 10.134.147.1 - 0 | 57 | 57 | 31 | 47 | 100 | 38 |

| 10.0.178.1 - 0 | 57 | 57 | 32 | 44 | 98 | 39 |

| 10.176.68.180 - 0 | 57 | 57 | 34 | 48 | 93 | 40 |

| 10.176.68.131 - 0 | 57 | 57 | 41 | 51 | 95 | 46 |

| 10.0.14.91 - 0 | 57 | 57 | 38 | 52 | 95 | 45 |

| 10.0.14.90 - 0 | 57 | 57 | 37 | 50 | 96 | 46 |

| 10.0.178.11 - 2 | 53 | 52 | 33 | 47 | 97 | 47 |

| 10.21.251.106 - 0 | 57 | 57 | 33 | 45 | 98 | 38 |

| 10.21.211.20 - 0 | 57 | 57 | 34 | 48 | 96 | 43 |

| et-5-0-1-0.ffttr6.-.opentransit. net - 0 | 57 | 57 | 105 | 116 | 143 | 111 |

| blizzard-2.gw.opentransit. net - 0 | 57 | 57 | 107 | 122 | 185 | 135 |

| ae1-br01-eqfr5.as57976. net - 40 | 23 | 14 | 112 | 438 | 3520 | 3520 |

| et-0-0-2-br01-eqam1.as57976. net - 40 | 23 | 14 | 121 | 416 | 2652 | 2652 |

| et-0-0-35-pe02-eqam1.as57976. net - 0 | 57 | 57 | 111 | 126 | 182 | 121 |

| 185.60.112.157 - 0 | 57 | 57 | 109 | 119 | 145 | 112 |

2

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 46 | 46 | 0 | 0 | 2 | 1 |

| No response from host - 100 | 9 | 0 | 0 | 0 | 0 | 0 |

| 10.134.145.17 - 0 | 46 | 46 | 40 | 77 | 104 | 96 |

| 10.134.147.5 - 0 | 46 | 46 | 31 | 43 | 65 | 48 |

| 10.0.10.165 - 0 | 46 | 46 | 36 | 50 | 69 | 53 |

| 10.0.178.1 - 0 | 46 | 46 | 32 | 49 | 68 | 53 |

| 10.176.68.196 - 0 | 46 | 46 | 34 | 47 | 68 | 51 |

| 10.176.68.131 - 0 | 46 | 46 | 35 | 48 | 69 | 54 |

| 10.0.14.91 - 0 | 46 | 46 | 33 | 49 | 68 | 52 |

| 10.0.14.90 - 0 | 46 | 46 | 38 | 49 | 68 | 53 |

| 10.0.178.11 - 0 | 46 | 46 | 32 | 45 | 70 | 47 |

| 10.21.251.106 - 0 | 46 | 46 | 40 | 49 | 68 | 53 |

| 10.21.211.20 - 0 | 46 | 46 | 37 | 50 | 68 | 55 |

| et-5-0-1-0.ffttr6.-.opentransit. net - 0 | 46 | 46 | 100 | 113 | 131 | 114 |

| blizzard-2.gw.opentransit. net - 0 | 46 | 46 | 105 | 118 | 151 | 117 |

| ae1-br01-eqfr5.as57976. net - 0 | 46 | 46 | 109 | 129 | 216 | 123 |

| et-0-0-2-br01-eqam1.as57976. net - 0 | 46 | 46 | 110 | 135 | 250 | 154 |

| 137.221.78.79 - 0 | 46 | 46 | 110 | 127 | 241 | 129 |

| 137.221.66.45 - 0 | 46 | 46 | 110 | 120 | 143 | 129 |

| 185.60.112.158 - 0 | 46 | 46 | 110 | 123 | 138 | 125 |

3

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 23 | 23 | 0 | 0 | 3 | 0 |

| No response from host - 100 | 5 | 0 | 0 | 0 | 0 | 0 |

| 10.134.145.1 - 0 | 23 | 23 | 45 | 85 | 111 | 91 |

| 10.134.147.1 - 0 | 23 | 23 | 31 | 40 | 65 | 37 |

| 10.0.178.1 - 0 | 23 | 23 | 37 | 51 | 66 | 46 |

| 10.176.68.196 - 0 | 23 | 23 | 35 | 46 | 60 | 39 |

| 10.176.68.131 - 0 | 23 | 23 | 41 | 49 | 64 | 49 |

| 10.0.14.91 - 0 | 23 | 23 | 35 | 49 | 62 | 47 |

| 10.0.14.90 - 0 | 23 | 23 | 34 | 44 | 64 | 42 |

| 10.0.178.11 - 0 | 23 | 23 | 35 | 46 | 64 | 47 |

| 10.21.251.106 - 0 | 23 | 23 | 44 | 53 | 65 | 49 |

| 10.21.211.20 - 0 | 23 | 23 | 38 | 49 | 64 | 42 |

| et-5-0-0-0.ffttr6.-.opentransit. net - 0 | 23 | 23 | 106 | 116 | 143 | 117 |

| blizzard-2.gw.opentransit. net - 0 | 23 | 23 | 112 | 125 | 157 | 121 |

| 137.221.80.35 - 0 | 23 | 23 | 112 | 123 | 144 | 120 |

| et-0-0-2-br01-eqpa4.as57976. net - 0 | 23 | 23 | 114 | 126 | 171 | 118 |

| be1-pe1-eqpa4.as57976. net - 0 | 23 | 23 | 121 | 130 | 154 | 126 |

| 185.60.114.159 - 0 | 23 | 23 | 119 | 130 | 155 | 120 |

1 Like

Thank you very much, it helps quite a bit. I’ll get these added to the report for you :slight_smile:

2 Likes

we are still waiting for an update …

common we have still have loading screen problem
What’s the problem with all this time?
We are wasting time

Still happening as of today,

https://pastebin.com/EDWraNGs

https://pastebin.com/di8VU4PY

https://pastebin.com/9ivKKbxv

bad news is , even my VPN is not working anymore and it keeps DC’ing me from game non-stop… , you can check my previous posts in this thread I gave 3 more MTR results back then prob want to compare them or something idk at this point man, I just want to play my damn game with all the crap I went through this year…

These nodes are fishy take a look for yourself,

137.221.80.33
137.221.65.29
137.221.65.26
81.52.179.220

The above results are from when I kept entering a dungeon instance and I was stuck in loading screen for about 3minutes or so and then re-entering and getting stuck again…

As you can clearly see in the links I provided in this post these IPs are falling behind in sent/recieve compared to other nodes, meaning they are lagging out or even losing the packet as a whole. you need to do something about these IPs… in order to solve this problem

what a surprise, same IPs are causing problem as my previous post for 18 days ago! ,

Alright since you’re under-staffed and no one cares to solve this, I’ll help you. here:

Information for 137.221.80.33:

WHOIS Source: RIPE NCC
IP Address: 137.221.80.33
Country: nlNetherlands
Network Name: BLIZZARD
Owner Name:
CIDR: 137.221.64.0/19
From IP: 137.221.64.0
To IP: 137.221.95.255
Allocated: Yes
Contact Name: Blizzard Peering
Address: 1 Blizzard Way
Email: peering@blizzard.com
Abuse Email: peering@blizzard.com
Phone: +1-949-955-1380

WHOIS Record:
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Information related to ‘137.221.64.0 - 137.221.95.255’

% Abuse contact for ‘137.221.64.0 - 137.221.95.255’ is ‘peering@blizzard.com’

inetnum: 137.221.64.0 - 137.221.95.255
netname: BLIZZARD
country: NL
admin-c: BP5978-RIPE
tech-c: BP5978-RIPE
status: ASSIGNED PA
mnt-by: MNT-BLIZZARD
created: 2018-08-27T19:57:32Z
last-modified: 2018-08-27T19:57:32Z
source: RIPE

person: Blizzard Peering
e-mail: peering@blizzard.com
address: 1 Blizzard Way
phone: +1-949-955-1380
nic-hdl: BP5978-RIPE
mnt-by: MNT-BLIZZARD
created: 2016-09-07T17:19:11Z
last-modified: 2018-08-24T18:24:09Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.97.1 (HEREFORD)

ALL THE IPs FROM 137.221.64.00 - 137.221.95.255 HAVE SAME INFORMATION.

Information for 137.221.80.33:

WHOIS Source: RIPE NCC
IP Address: 81.52.179.220
Country: frFrance
Network Name: OPENTRANSIT-BACKBONE
Owner Name: Orange - OINIS
CIDR:
From IP: 81.52.178.0
To IP: 81.52.183.255
Allocated: Yes
Contact Name: Admin Opentransit
Address: Orange, 61, rue des Archives, 75003 Paris, France
Email: *****************@list.orange.com
Abuse Email: abuse@opentransit.net
Phone:

WHOIS Record:
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Information related to ‘81.52.178.0 - 81.52.183.255’

% Abuse contact for ‘81.52.178.0 - 81.52.183.255’ is ‘gestionip.ft@orange.com’

inetnum: 81.52.178.0 - 81.52.183.255
netname: OPENTRANSIT-BACKBONE
descr: Orange - OINIS
descr: 61, rue des Archives, 75003 Paris
country: FR
admin-c: AO3173-RIPE
tech-c: NO21-RIPE
status: ASSIGNED PA
remarks: for hacking, spamming or security problems send mail to
remarks: abuse@opentransit.net
mnt-by: FT-BRX
created: 2012-03-07T11:03:32Z
last-modified: 2018-12-10T14:13:39Z
source: RIPE

role: Admin Opentransit
address: Orange
address: 61, rue des Archives
address: 75003 Paris, France
e-mail: *****************@list.orange.com
admin-c: NO21-RIPE
tech-c: NO21-RIPE
mnt-by: FTRSI
nic-hdl: AO3173-RIPE
created: 2002-06-28T14:45:30Z
last-modified: 2018-10-16T18:32:01Z
source: RIPE

role: Noc Opentransit
remarks: 24/7 Opentransit IP Product Support
phone: +44 208 321 1351
e-mail: opentransit.noc@orange.com
address: Gurgaon, India
admin-c: AO3173-RIPE
tech-c: AO3173-RIPE
nic-hdl: NO21-RIPE
mnt-by: FTRSI
created: 2002-06-14T14:12:07Z
last-modified: 2018-10-16T18:34:09Z
source: RIPE

% Information related to ‘81.52.176.0/21AS5511’

route: 81.52.176.0/21
descr: France Telecom
descr: OPENTRANSIT
origin: AS5511
mnt-by: FT-BRX
created: 2004-09-14T13:55:06Z
last-modified: 2004-09-14T13:55:06Z
source: RIPE

% This query was served by the RIPE Database Query Service version 1.97 (BLAARKOP)

1 Like

My server Aerie Peak having similar issues, taking far, far longer than usual, several minutes in fact to load the game and login.

Hey Blizzard just wanna say this issue has been around for a month now and preventing me and alot of other players from enjoying the game we all love,honestly after a month of no fix i think it’s means it will never gonna get fix.Blizzard aren’t you tired of seeing this topic at the top of support section every day?aren’t you feel it’s sucks to not be able to play the game like any other people do?how hard it is for server tech guys to understand this is pure phasing issue? I respect the effort you guys put in solving players issues but it’s been A MONTH!

2 Likes

Hey Niko , the problem is known for almost 2 months and this topic has been open since then but in order to solve the problem we need to provide solid information on our behalf (our routing path to blizzard’s final server) and then see which nodes are causing problems so they might actually get fixed…

so if you please take look at this post ,https://eu.battle.net/support/en/article/27780 and do the test and its important to do this test while you are getting stuck in the loading screen and let it run for about 5 minutes (500 sent/receive) and post your results in pastebin or other sites that allow large number of texts to be saved.

like I said before this problem seems a small problem to blizzard because its not affecting everyone and its not being taken serious, which sucks indeed but only we “players” can speed up the process by providing accurate results and information through the test linked above. other than that don’t get your hopes up for any fix.