Stuck in loading screens

1: Tracing route to 185.60.112.157 over a maximum of 30 hops

1 6 ms 4 ms 10 ms 192.168.2.1
2 11 ms 7 ms 7 ms 44.79-160-116.customer.lyse.ne.t [79.160.116.44]
3 7 ms 7 ms 7 ms 229.213-167-114.customer.lyse.ne.t [213.167.114.229]
4 9 ms * 6 ms 81.167.36.60.static.lyse.ne.t [81.167.36.60]
5 8 ms 8 ms 8 ms 217.213-167-114.customer.lyse.ne.t [213.167.114.217]
6 8 ms 7 ms 8 ms ae65.edge1.Oslo2.Level3.ne.t [62.67.17.221]
7 41 ms 42 ms 40 ms ae2.3204.edge7.Amsterdam1.level3.ne.t [4.69.162.181]
8 38 ms 39 ms 65 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.ne.t [212.72.41.90]
9 998 ms 711 ms 388 ms 137.221.78.29
10 * * * Request timed out.
11 37 ms 37 ms 37 ms 137.221.78.49
12 36 ms 35 ms 39 ms 137.221.66.43
13 38 ms 40 ms 37 ms 185.60.112.157

Trace complete.

2: Tracing route to 185.60.112.158 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.2.1
2 7 ms 6 ms 7 ms 44.79-160-116.customer.lyse.ne.t [79.160.116.44]
3 7 ms 6 ms 7 ms 229.213-167-114.customer.lyse.ne.t [213.167.114.229]
4 7 ms * 7 ms 81.167.36.60.static.lyse.ne.t. [81.167.36.60]
5 8 ms 8 ms 7 ms 217.213-167-114.customer.lyse.ne.t [213.167.114.217]
6 9 ms 11 ms 8 ms ae65.edge1.Oslo2.Level3.ne.t [62.67.17.221]
7 37 ms 37 ms 40 ms ae2.3204.edge7.Amsterdam1.level3.ne.t. [4.69.162.181]
8 40 ms 38 ms 37 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.ne.t.[212.72.41.90]
9 * * * Request timed out.
10 * * * Request timed out.
11 37 ms 38 ms 37 ms 137.221.78.51
12 37 ms 37 ms 37 ms 137.221.66.45
13 36 ms 36 ms 36 ms 185.60.112.158

Trace complete.

3:Tracing route to 185.60.114.159 over a maximum of 30 hops

1 3 ms 2 ms 2 ms 192.168.2.1
2 7 ms 7 ms 7 ms 44.79-160-116.customer.lyse.ne.t. [79.160.116.44]
3 7 ms 6 ms 7 ms 229.213-167-114.customer.lyse.ne.t. [213.167.114.229]
4 6 ms * 7 ms 81.167.36.60.static.lyse.ne.t [81.167.36.60]
5 9 ms 8 ms 8 ms 217.213-167-114.customer.lyse.ne.t. [213.167.114.217]
6 9 ms 10 ms 13 ms ae65.edge1.Oslo2.Level3.ne.t. [62.67.17.221]
7 38 ms 37 ms 37 ms ae2.3204.edge7.Amsterdam1.level3.ne.t [4.69.162.181]
8 38 ms 38 ms 38 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.ne.t. [212.72.41.90]
9 185 ms 219 ms 207 ms 137.221.78.29
10 42 ms 42 ms 42 ms et-0-0-3-br02-eqpa4.as57976.ne.t. [137.221.65.92]
11 46 ms 46 ms 44 ms bond0-vs01-eqpa4.as57976.ne.t [137.221.77.57]
12 48 ms 45 ms 45 ms 185.60.114.159

Trace complete.

Still having problems.

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 7 ms 8 ms 10.234.0.1
3 7 ms 7 ms 7 ms cm-84.208.41.86.get.no [84.208.41.86]
4 * * * Request timed out.
5 7 ms 8 ms 6 ms 213.236.142.77
6 10 ms 8 ms 9 ms 213.236.142.76
7 8 ms 8 ms 7 ms oso-b2-link.ip.twelve99.net [62.115.175.162]
8 7 ms 7 ms 6 ms oso-b1-link.ip.twelve99.net [62.115.116.90]
9 21 ms 19 ms * hbg-bb3-link.ip.twelve99.net [62.115.112.84]
10 26 ms 26 ms 26 ms adm-bb1-link.ip.twelve99.net [80.91.252.42]
11 26 ms 25 ms 25 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
12 27 ms 28 ms 25 ms blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
13 2752 ms 2639 ms 2199 ms ae1-br02-eqam1.as57976.net [137.221.78.35]
14 * * * Request timed out.
15 26 ms 27 ms 25 ms et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
16 28 ms 27 ms 27 ms 185.60.112.157

Trace complete.

Tracing route to 185.60.112.158 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 10.234.0.1
3 7 ms 9 ms 7 ms cm-84.208.41.84.get.no [84.208.41.84]
4 * * * Request timed out.
5 32 ms 19 ms 9 ms peer-as41164.san-peer2.osl.no.ip.tdc.net [109.163.76.161]
6 7 ms 7 ms 6 ms 109.163.76.160
7 8 ms 8 ms 7 ms oso-b1-link.ip.twelve99.net [62.115.175.156]
8 18 ms 19 ms * hbg-bb3-link.ip.twelve99.net [62.115.112.84]
9 26 ms 25 ms 26 ms adm-bb1-link.ip.twelve99.net [80.91.252.42]
10 29 ms 25 ms 25 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
11 26 ms 25 ms 25 ms blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
12 25 ms 25 ms 25 ms ae1-br01-eqam1.as57976.net [137.221.78.33]
13 * * * Request timed out.
14 29 ms 25 ms 27 ms bond0-vs01-eqam1.as57976.net [137.221.78.57]
15 27 ms 31 ms 28 ms 185.60.112.158

Trace complete.

Tracing route to 185.60.112.158 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 10.234.0.1
3 7 ms 9 ms 7 ms cm-84.208.41.84.get.no [84.208.41.84]
4 * * * Request timed out.
5 32 ms 19 ms 9 ms peer-as41164.san-peer2.osl.no.ip.tdc.net [109.163.76.161]
6 7 ms 7 ms 6 ms 109.163.76.160
7 8 ms 8 ms 7 ms oso-b1-link.ip.twelve99.net [62.115.175.156]
8 18 ms 19 ms * hbg-bb3-link.ip.twelve99.net [62.115.112.84]
9 26 ms 25 ms 26 ms adm-bb1-link.ip.twelve99.net [80.91.252.42]
10 29 ms 25 ms 25 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
11 26 ms 25 ms 25 ms blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
12 25 ms 25 ms 25 ms ae1-br01-eqam1.as57976.net [137.221.78.33]
13 * * * Request timed out.
14 29 ms 25 ms 27 ms bond0-vs01-eqam1.as57976.net [137.221.78.57]
15 27 ms 31 ms 28 ms 185.60.112.158

Trace complete.

Tracing route to 185.60.112.159 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 7 ms 8 ms 7 ms 10.234.0.1
3 8 ms 7 ms 9 ms cm-84.208.41.86.get.no [84.208.41.86]
4 * * * Request timed out.
5 7 ms 7 ms 7 ms 213.236.142.77
6 7 ms 7 ms 8 ms 213.236.142.76
7 7 ms 8 ms 8 ms oso-b2-link.ip.twelve99.net [62.115.175.162]
8 7 ms 7 ms 9 ms oso-b1-link.ip.twelve99.net [62.115.116.90]
9 * 19 ms 19 ms hbg-bb3-link.ip.twelve99.net [62.115.112.84]
10 26 ms 25 ms 27 ms adm-bb1-link.ip.twelve99.net [80.91.252.42]
11 25 ms 25 ms 25 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
12 30 ms 26 ms 26 ms blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
13 27 ms 25 ms 27 ms ae1-br01-eqam1.as57976.net [137.221.78.33]
14 * * * Request timed out.
15 26 ms 25 ms 25 ms et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

My ISP is: Altibox

Tracerute:

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 4 ms <1 ms 4 ms home [192.168.10.1]
2 4 ms 4 ms 4 ms 148.79-160-116.customer.lyse.net [79.160.116.148]
3 4 ms 3 ms 4 ms 217.213-167-114.customer.lyse.net [213.167.114.217]
4 9 ms 9 ms 3 ms ae65.edge1.Oslo2.Level3.net [62.67.17.221]
5 32 ms 32 ms 33 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
6 32 ms 32 ms 32 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
7 65 ms 59 ms 62 ms 137.221.78.27
8 * * * Request timed out.
9 32 ms 32 ms 36 ms bond0-vs01-eqam1.as57976.net [137.221.78.57]
10 33 ms 33 ms 33 ms 137.221.66.43
11 32 ms 32 ms 32 ms 185.60.112.157

Trace complete.

Tracing route to 185.60.112.158 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home [192.168.10.1]
2 4 ms 3 ms 4 ms 148.79-160-116.customer.lyse.net [79.160.116.148]
3 25 ms 3 ms 4 ms 217.213-167-114.customer.lyse.net [213.167.114.217]
4 5 ms 3 ms 4 ms ae65.edge1.Oslo2.Level3.net [62.67.17.221]
5 32 ms 33 ms 36 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
6 32 ms 32 ms 32 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
7 * * * Request timed out.
8 * * * Request timed out.
9 38 ms 33 ms 33 ms 137.221.78.53
10 33 ms 33 ms 33 ms 185.60.112.158

Trace complete.

Tracing route to 185.60.112.159 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home [192.168.10.1]
2 4 ms 4 ms 4 ms 148.79-160-116.customer.lyse.net [79.160.116.148]
3 6 ms 8 ms 3 ms 217.213-167-114.customer.lyse.net [213.167.114.217]
4 19 ms 12 ms 13 ms ae65.edge1.Oslo2.Level3.net [62.67.17.221]
5 31 ms 32 ms 45 ms ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
6 32 ms 32 ms 37 ms BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
7 654 ms 219 ms 220 ms 137.221.78.29
8 * * * Request timed out.
9 38 ms 33 ms 32 ms bond0-vs01-eqam1.as57976.net [137.221.78.57]
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 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I was just on the line with Telia to hear if this problem was on the radar at all and if they have any thoughts and so on. The girl I talked to told me some guy in their IT-department was playing wow and he had the same problem, but he was using Telenor. So that’s 3 ISP’s struggling in the same country. She said she does not think it has anything to do with them and that the problem lies with Blizzard.

1 Like

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 1 ms 1 ms 1 ms kabelbox.local [192.168.0.1]
2 10 ms 13 ms 7 ms ip-081-210-176-224.um21.pools.vodafone-ip.de [81.210.176.224]
3 * 12 ms 9 ms de-fra01b-rc2-ae-64-0.aorta.net [84.116.191.129]
4 16 ms 12 ms 11 ms de-bfe18a-rt01-lag-1.aorta.net [84.116.190.34]
5 11 ms 10 ms 11 ms pr01.eqfr5.blizzardonline.net [80.81.195.26]
6 20 ms 19 ms 17 ms ae1-br01-eqfr5.as57976.net [137.221.80.33]
7 66 ms 60 ms 57 ms et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
8 * * * Request timed out.
9 17 ms 16 ms 22 ms et-0-0-31-pe01-eqam1.as57976.net [137.221.78.67]
10 16 ms 14 ms 17 ms 185.60.112.157

Tracing route to 185.60.112.158 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms kabelbox.local [192.168.0.1]
2 10 ms 7 ms 7 ms ip-081-210-176-224.um21.pools.vodafone-ip.de [81.210.176.224]
3 13 ms 17 ms 18 ms de-fra01b-rc2-ae-64-0.aorta.net [84.116.191.129]
4 11 ms 16 ms 10 ms de-bfe18a-rt01-lag-1.aorta.net [84.116.190.34]
5 * * * Request timed out.
6 25 ms 15 ms 18 ms ae1-br01-eqfr5.as57976.net [137.221.80.33]
7 40 ms 18 ms 18 ms et-0-0-2-br01-eqam1.as57976.net [137.221.65.29]
8 * * * Request timed out.
9 18 ms 15 ms 15 ms 137.221.78.49
10 17 ms 15 ms 15 ms 185.60.112.158

Trace complete.

Tracing route to 185.60.114.159 over a maximum of 30 hops

1 1 ms 1 ms 1 ms kabelbox.local [192.168.0.1]
2 12 ms 9 ms 8 ms ip-081-210-176-224.um21.pools.vodafone-ip.de [81.210.176.224]
3 15 ms 11 ms 12 ms de-fra01b-rc2-ae-64-0.aorta.net [84.116.191.129]
4 18 ms 13 ms 10 ms de-bfe18a-rt01-lag-1.aorta.net [84.116.190.34]
5 * * * Request timed out.
6 22 ms 23 ms 20 ms 137.221.80.35
7 28 ms 20 ms 24 ms et-0-0-2-br01-eqpa4.as57976.net [137.221.65.26]
8 27 ms 20 ms 21 ms et-0-0-0-pe01-eqpa4.as57976.net [137.221.77.77]
9 26 ms 20 ms 25 ms 185.60.114.159

Trace complete.

Haven’t had any problems so far today, lets hope it stays like that.

1 Like

Same for me, everything seems fine

1 Like

The problems we experience with this game is ALWAYS on blizzards side, they are so quick do blame everyone else besides themselves.

They problems we had this xpac is just starting to get ridiculous.

Everything seems fine for me today. Went trough lots of loading screens and groups without trouble

Things are looking good so far today, no freezes.

Might have been a delay. But I have played for 2 hours now with a lot of portals and no freeze :partying_face:

Had the same problem here in Denmark with Altibox, but seem to be fixed today, had a some latency issues today though, only in WoW

no freezes today

I had no freezes today, but I did experience several stuck on loading screens while taking portals/HS and logging in.

Seem fixed for me, had no issues today, pogchamp!

Had ICC raid last night, 10 bosses, and any death or wipe I loaded the outdoors when I released no problem. Also did FoS, VoA, and Naxx10 earlier in the day with no real issue. However, WoW Classic Hardcore is still a bit questionable, some smaller lag spikes and one or two occurrences of NPCs being uninteractable after loading into a new zone for half a minute.
Edit: Golemagg for WotLK Classic and Nek’Rosh Classic Hardcore

I’m still dcing alot, stuck on loading screen.

Gehennas.

Tracing route to 185.60.114.159 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.1.1
2 14 ms 13 ms 16 ms be10.no-tro-vro-cr1.link.no.telia. net [80.232.81.140]
3 12 ms 13 ms 14 ms 80.232.27.47
4 13 ms 13 ms 14 ms 80.232.27.49
5 15 ms 19 ms 13 ms 85.19.121.141
6 26 ms 15 ms 15 ms telia-ic-345141.ip.twelve99-cust. net [62.115.175.163]
7 17 ms 22 ms 14 ms oso-b2-link.ip.twelve99. net [62.115.175.162]
8 14 ms 13 ms 13 ms oso-b1-link.ip.twelve99. net [62.115.116.90]
9 38 ms 31 ms * hbg-bb3-link.ip.twelve99. net [62.115.112.84]
10 31 ms 38 ms 31 ms adm-bb1-link.ip.twelve99. net [80.91.252.42]
11 32 ms 31 ms 50 ms adm-b10-link.ip.twelve99. net [62.115.120.227]
12 32 ms 36 ms 38 ms blizzard-ic-348623.ip.twelve99-cust. net [62.115.178.203]
13 179 ms 208 ms 208 ms ae1-br02-eqam1.as57976. net [137.221.78.35]
14 42 ms 53 ms 47 ms et-0-0-3-br02-eqpa4.as57976. net [137.221.65.92]
15 43 ms 42 ms 50 ms bond0-vs01-eqpa4.as57976. net [137.221.77.57]
16 41 ms 45 ms 50 ms 185.60.114.159

Trace complete.

No problem, thx blizz

I didn’t have any stuck-in-loading screen issues anymore but sometimes the NPCs would all just disappear for a second or up to 4 and then reappear.

worked fine for me since tuesday