Same issue here.
Telia, Trondheim - Norway
I’m not a computer wiz, but I tried running a tracert via cmd, and I only get three hops? Same goes for pathpings. However, when using online trace routes, I usually get a lot more.
1 2 ms 2 ms 1 ms 192.168.10.1
2 8 ms 6 ms 5 ms 46.79-160-116.customer.lyse [dot] net [79.160.116.46]
3 30 ms 30 ms 30 ms 185.60.112.158
If anyone knows what I’m doing wrong, please do tell!
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 9 ms 9 ms 9 ms 192.168.0.1
2 16 ms 15 ms 15 ms 10.235.128.1
3 16 ms 14 ms 16 ms cm-84.208.41.24.get/no [84.208.41.24]
4 * * * Request timed out.
5 16 ms 17 ms 16 ms peer-as41164.san-peer2.osl.no.ip.tdc/net [109.163.76.161]
6 18 ms 17 ms 17 ms 109.163.76.160
7 20 ms 17 ms 17 ms oso-b1-link.ip.twelve99/net [62.115.175.156]
8 28 ms 25 ms 28 ms hbg-bb3-link.ip.twelve99/net [62.115.112.84]
9 36 ms 31 ms 30 ms adm-bb1-link.ip.twelve99/net [80.91.252.42]
10 77 ms 35 ms 35 ms adm-b10-link.ip.twelve99/net [62.115.120.227]
11 84 ms 36 ms 36 ms blizzard-ic-348623.ip.twelve99-cust/net [62.115.178.203]
12 * * 3407 ms ae1-br02-eqam1.as57976/net [137.221.78.35]
13 * * * Request timed out.
14 36 ms 33 ms 35 ms 137.221.78.51
15 40 ms 35 ms 35 ms 185.60.112.157
Added a / instead of . as i wasnt allowed to add links
I have been playing for 1.5-2 hours and havent had any loading screen issues yet
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 5 ms 2 ms 1 ms 224.79-160-116.customer.lyse./net [79.160.116.224]
3 2 ms 2 ms 2 ms 15.213-167-114.customer.lyse./net [213.167.114.15]
4 14 ms 14 ms 14 ms ae71.edge7.London1.Level3./net [217.163.134.165]
5 21 ms 29 ms 21 ms ae2.3204.edge7.Amsterdam1.level3./net [4.69.162.181]
6 25 ms 21 ms 21 ms BLIZZARD-EN.edge7.Amsterdam1.Level3./net [212.72.41.90]
7 2628 ms 3738 ms * 137.221.78.29
8 * * * Request timed out.
9 24 ms 24 ms 24 ms 137.221.78.47
10 24 ms 24 ms 29 ms 185.60.112.157
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 4 ms 3 ms 3 ms cm-84.210.144.46.get.no [84.210.144.46]
3 * * * Request timed out.
4 8 ms 7 ms 7 ms be61.no-kri-kir-cr1.link.no.telia.net [80.232.82.90]
5 7 ms 7 ms 7 ms ae20-0.san-p1.osl.no.ip.tdc.net [80.232.27.38]
6 13 ms 20 ms * 85.19.121.141
7 7 ms 7 ms 9 ms telia-ic-345141.ip.twelve99-cust.net [62.115.175.163]
8 7 ms 7 ms 7 ms oso-b2-link.ip.twelve99.net [62.115.175.162]
9 8 ms 7 ms 7 ms oso-b1-link.ip.twelve99.net [62.115.116.90]
10 19 ms 19 ms 19 ms hbg-bb3-link.ip.twelve99.net [62.115.112.84]
11 26 ms 25 ms 26 ms adm-bb1-link.ip.twelve99.net [80.91.252.42]
12 26 ms 26 ms 25 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
13 26 ms 26 ms 26 ms blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
14 2293 ms 3019 ms 1699 ms ae1-br01-eqam1.as57976.net [137.221.78.33]
15 * * * Request timed out.
16 25 ms 25 ms 25 ms 137.221.78.55
17 26 ms 25 ms 26 ms 185.60.112.157
Trace complete.
Unrelated, tried forcing a DC and managed to within like 2 minutes so its still broken.
weird i have no probem, maybe im just lucky today
Are you with altibox or Telia?
Norwegian, using Altibox. Tech support is showing 3 diff IPs for European traceroutes, so here’s a traceroute for each:
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 1 ms 1 ms 2 ms 192.168.1.1
2 5 ms 3 ms 3 ms 192.168.10.1
3 9 ms 8 ms 8 ms 74.79-160-116.customer.lyse [dot] net [79.160.116.74]
4 22 ms 23 ms 22 ms 219.213-167-114.customer.lyse [dot] net [213.167.114.219]
5 21 ms 21 ms 22 ms oso-b1-link.ip.twelve99 [dot] net [62.115.54.181]
6 35 ms 34 ms 33 ms hbg-bb3-link.ip.twelve99 [dot] net [62.115.112.84]
7 40 ms 41 ms 39 ms adm-bb1-link.ip.twelve99 [dot] net [80.91.252.42]
8 39 ms 40 ms 39 ms adm-b10-link.ip.twelve99 [dot] net [62.115.120.227]
9 40 ms 40 ms 40 ms blizzard-ic-348623.ip.twelve99-cust [dot] net [62.115.178.203]
10 56 ms 159 ms 217 ms ae1-br01-eqam1.as57976 [dot] net [137.221.78.33]
11 * * * Request timed out.
12 39 ms 40 ms 39 ms 137.221.78.55
13 40 ms 40 ms 39 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.1.1
2 2 ms 1 ms 2 ms 192.168.10.1
3 8 ms 8 ms 8 ms 74.79-160-116.customer.lyse [dot] net [79.160.116.74]
4 22 ms 21 ms 21 ms 219.213-167-114.customer.lyse [dot] net [213.167.114.219]
5 22 ms 21 ms 22 ms oso-b1-link.ip.twelve99 [dot] net [62.115.54.181]
6 * * * Request timed out.
7 40 ms 40 ms 41 ms adm-bb1-link.ip.twelve99 [dot] net [80.91.252.42]
8 39 ms 40 ms 41 ms adm-b10-link.ip.twelve99 [dot] net [62.115.120.227]
9 40 ms 40 ms 40 ms blizzard-ic-348623.ip.twelve99-cust [dot] net [62.115.178.203]
10 * * * Request timed out.
11 * * * Request timed out.
12 39 ms 39 ms 40 ms 137.221.78.55
13 40 ms 40 ms 39 ms 137.221.66.41
14 40 ms 40 ms 41 ms 185.60.112.158
Trace complete.
Tracing route to 185.60.112.159 over a maximum of 30 hops
1 2 ms 3 ms 2 ms 192.168.1.1
2 4 ms 1 ms 2 ms 192.168.10.1
3 9 ms 8 ms 8 ms 74.79-160-116.customer.lyse [dot] net [79.160.116.74]
4 21 ms 21 ms 21 ms 219.213-167-114.customer.lyse [dot] net [213.167.114.219]
5 21 ms 23 ms 22 ms oso-b1-link.ip.twelve99 [dot] net [62.115.54.185]
6 35 ms 34 ms 33 ms hbg-bb3-link.ip.twelve99 [dot] net [62.115.112.84]
7 40 ms 41 ms 41 ms adm-bb1-link.ip.twelve99 [dot] net [80.91.252.42]
8 40 ms 40 ms 40 ms adm-b10-link.ip.twelve99 [dot] net [62.115.120.227]
9 41 ms 40 ms 40 ms blizzard-ic-348623.ip.twelve99-cust [dot] net [62.115.178.203]
10 151 ms 219 ms 220 ms ae1-br01-eqam1.as57976 [dot] net [137.221.78.33]
11 * * * Request timed out.
12 39 ms 39 ms 39 ms bond0-vs01-eqam1.as57976 [dot] net [137.221.78.57]
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’ve had this same issue all week, opened a ticket and they suggested i try a vpn which works, but it sucks and id rather be able to play without using one, im also with Altibox.
Altibox Norway.
1 <1 ms <1 ms <1 ms TOUCH_P5-SHARE [192.168.0.1]
2 4 ms 3 ms 4 ms 132.79-160-116.customer.lyse .net [79.160.116.132]
3 3 ms 3 ms 3 ms 217.213-167-114.customer.lyse. net [213.167.114.217]
4 4 ms 3 ms 4 ms ae65.edge1.Oslo2.Level3. net [62.67.17.221]
5 31 ms 33 ms 31 ms ae2.3204.edge7.Amsterdam1.level3. net [4.69.162.181]
6 32 ms 32 ms 31 ms BLIZZARD-EN.edge7.Amsterdam1.Level3. net [212.72.41.90]
7 29 ms 28 ms 29 ms 137.221.78.27
8 * * * Request timed out.
9 28 ms 28 ms 28 ms 137.221.78.49
10 28 ms 28 ms 28 ms 185.60.112.158
Still having issues. Can’t post links here it says. Did ran a tracing route.
4 HS to Dalaran failed right after each other right now.
Had to Alt+F4 4 times before I could log on.
yea, this is taking the piss… getting really annoyed having to alt-f4 constantly.
1 Like
Is this still not fixed? OMG game is unplayable whole week… we should get 1 month free gametime for this
1 Like
'Same boat. On classic wotlk i have to alt f4 around 50 % of loading screens. And on retail around 70-80 %. Its getting real frustrating
Hey, like, can we get an updated about this ??? Raid releasing in a few days, and we still are left in the dark about this matter??? PLEASE GIVE US SOME INFO?
1 Like
Some person got told to buy VPN in his ticket.
Edit: actually saw blizz replied to this 9h ago. they looking into it atleast.
1 Like
I hope the GM intended to pay for their VPN subscription, then…
1 Like
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 1 ms 1 ms 1 ms gw-37-9-199-1.inext.cz [37.9.199.1]
3 2 ms 2 ms 2 ms be1.1019-asbr.inext.cz [212.111.1.65]
4 7 ms 6 ms 6 ms prag-b4-link.ip.twelve99. net [62.115.46.201]
5 * * 13 ms ffm-bb2-link.ip.twelve99. net [62.115.124.28]
6 21 ms 21 ms 21 ms prs-bb2-link.ip.twelve99. net [62.115.122.138]
7 22 ms 21 ms 21 ms prs-b1-link.ip.twelve99. net [62.115.125.167]
8 22 ms 22 ms 21 ms blizzard-ic-348624.ip.twelve99-cust. net [62.115.178.205]
9 28 ms 27 ms 28 ms ae1-br02-eqpa4.as57976. net [137.221.77.35]
10 * * * Request timed out.
11 377 ms 439 ms 440 ms 137.221.65.77
12 28 ms 27 ms 27 ms et-0-0-31-pe02-eqam1.as57976. net [137.221.78.69]
13 28 ms 27 ms 28 ms 137.221.66.47
14 27 ms 27 ms 28 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 1 ms 1 ms 1 ms gw-37-9-199-1.inext.cz [37.9.199.1]
3 2 ms 2 ms 3 ms be1.1019-asbr.inext.cz [212.111.1.65]
4 7 ms 6 ms 6 ms prag-b4-link.ip.twelve99. net [62.115.46.201]
5 * * * Request timed out.
6 21 ms 21 ms * prs-bb2-link.ip.twelve99. net [62.115.122.138]
7 22 ms 21 ms 22 ms prs-b1-link.ip.twelve99. net [62.115.125.167]
8 22 ms 21 ms 21 ms blizzard-ic-348624.ip.twelve99-cust. net [62.115.178.205]
9 27 ms 27 ms 27 ms ae1-br02-eqpa4.as57976. net [137.221.77.35]
10 * * * Request timed out.
11 * * * Request timed out.
12 28 ms 33 ms 29 ms 137.221.78.55
13 31 ms 28 ms 27 ms 137.221.66.41
14 27 ms 27 ms 27 ms 185.60.112.158
Trace complete.