Stuck in loading screens

Tracing route to 185.60.112.157 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  router [192.168.10.1] 
  2     4 ms     3 ms     3 ms  150.79-160-116.customer.lyse.net [79.160.116.150] 
  3     4 ms     4 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    32 ms    32 ms    31 ms  ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181] 
  6    32 ms    33 ms    32 ms  BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90] 
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    28 ms    44 ms    28 ms  bond0-vs01-eqam1.as57976.net [137.221.78.57] 
 10    29 ms    29 ms    28 ms  137.221.66.43 
 11    28 ms    28 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  router [192.168.10.1] 
  2     4 ms     4 ms     3 ms  150.79-160-116.customer.lyse.net [79.160.116.150] 
  3     3 ms     3 ms     3 ms  217.213-167-114.customer.lyse.net [213.167.114.217] 
  4     4 ms    26 ms    12 ms  ae65.edge1.Oslo2.Level3.net [62.67.17.221] 
  5    31 ms    31 ms    47 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    28 ms    30 ms    28 ms  et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69] 
 10    28 ms    28 ms    29 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  router [192.168.10.1] 
  2     3 ms     3 ms     3 ms  150.79-160-116.customer.lyse.net [79.160.116.150] 
  3     3 ms     3 ms     3 ms  217.213-167-114.customer.lyse.net [213.167.114.217] 
  4     3 ms     3 ms     4 ms  ae65.edge1.Oslo2.Level3.net [62.67.17.221] 
  5    37 ms    36 ms    32 ms  ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181] 
  6    32 ms    32 ms    40 ms  BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90] 
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    28 ms    28 ms    28 ms  et-0-0-31-pe02-eqam1.as57976.net [137.221.78.69] 
 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.

Also experiencing the same loading screen issues. ISP is Altibox in Norway.

Here are my tracert results.

Tracing route to 185.60.112.157 over a maximum of 30 hops
  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     3 ms     2 ms     3 ms  48.79-160-116.customer.lyse.net [79.160.116.48]
  3     3 ms     3 ms     3 ms  229.213-167-114.customer.lyse.net [213.167.114.229]
  4     *        3 ms     *     81.167.37.40.static.lyse.net [81.167.37.40]
  5     4 ms     4 ms     5 ms  217.213-167-114.customer.lyse.net [213.167.114.217]
  6    13 ms    13 ms    16 ms  ae65.edge1.Oslo2.Level3.net [62.67.17.221]
  7    33 ms    33 ms    33 ms  ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
  8    33 ms    33 ms    33 ms  BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
  9  3381 ms     *        *     137.221.78.29
 10     *        *        *     Request timed out.
 11    29 ms    29 ms    29 ms  137.221.78.47
 12    29 ms    30 ms    29 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.2.1
  2     3 ms     3 ms     2 ms  48.79-160-116.customer.lyse.net [79.160.116.48]
  3     3 ms     2 ms     2 ms  229.213-167-114.customer.lyse.net [213.167.114.229]
  4     3 ms     *        3 ms  81.167.37.40.static.lyse.net [81.167.37.40]
  5     4 ms     4 ms     3 ms  217.213-167-114.customer.lyse.net [213.167.114.217]
  6    20 ms    21 ms     4 ms  ae65.edge1.Oslo2.Level3.net [62.67.17.221]
  7    33 ms    33 ms    34 ms  ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
  8    33 ms    33 ms    33 ms  BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
  9   367 ms   658 ms   715 ms  137.221.78.29
 10     *        *        *     Request timed out.
 11    29 ms    41 ms    28 ms  137.221.78.55
 12    29 ms    30 ms    30 ms  137.221.66.41
 13    29 ms    30 ms    29 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  192.168.2.1
  2     3 ms     3 ms     3 ms  48.79-160-116.customer.lyse.net [79.160.116.48]
  3     3 ms     2 ms     2 ms  229.213-167-114.customer.lyse.net [213.167.114.229]
  4     3 ms     *        3 ms  81.167.37.40.static.lyse.net [81.167.37.40]
  5     4 ms     5 ms     4 ms  217.213-167-114.customer.lyse.net [213.167.114.217]
  6     4 ms     4 ms     5 ms  ae65.edge1.Oslo2.Level3.net [62.67.17.221]
  7    34 ms    34 ms    33 ms  ae2.3204.edge7.Amsterdam1.level3.net [4.69.162.181]
  8    34 ms    34 ms    33 ms  BLIZZARD-EN.edge7.Amsterdam1.Level3.net [212.72.41.90]
  9  2143 ms   879 ms   659 ms  137.221.78.29
 10    83 ms    73 ms    58 ms  et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92]
 11    37 ms    37 ms    38 ms  et-0-0-1-pe04-eqpa4.as57976.net [137.221.77.53]
 12    38 ms    38 ms    38 ms  137.221.66.39
 13    37 ms    37 ms    37 ms  185.60.114.159
 Trace complete.

Unable to get into the game for several hours now. I’ve had issues all week, but the last two days have been brutal. 8/10 loading screens get stuck. Upon flying into new zones I also get DC/stuck with no NPCs or players around, before DC 5-10 minutes after landing. Here is my traceroute:

Tracing route to 185.60.114.159 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 1 ms 1 ms 1 ms peer-as41164.san-peer2.osl.no.ip.tdc.net [109.163.76.161]
4 1 ms 2 ms 1 ms 109.163.76.160
5 2 ms 1 ms 1 ms oso-b1-link.ip.twelve99.net [62.115.175.156]
6 * 13 ms * hbg-bb3-link.ip.twelve99.net [62.115.112.84]
7 20 ms 20 ms 20 ms adm-bb1-link.ip.twelve99.net [80.91.252.42]
8 20 ms 20 ms 20 ms adm-b10-link.ip.twelve99.net [62.115.120.227]
9 20 ms 20 ms 49 ms blizzard-ic-348623.ip.twelve99-cust.net [62.115.178.203]
10 * * * Request timed out.
11 28 ms 86 ms 28 ms et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92]
12 28 ms 28 ms 28 ms et-0-0-1-pe01-eqpa4.as57976.net [137.221.77.79]
13 29 ms 28 ms 29 ms 185.60.114.159

Trace complete.

Looks much better now for me, connecting through Altibox in Stavanger, Norway. Only 4 hours ago I had to Alt-F4 about 25 times while switching realms to check auctions, and now it was flawless while swapping between 10 realms, and I didn’t have any problems while flying around for a while on a few realms looking for treasure chests. Did anything positive happen?

1 Like

Cautious optimism, but I think altibox is good for me now. Been playing without VPN and haven’t been running into issues.

I am definately still having issues, even with VPN on. Wtf is going on?!?

1 Like

Issue is still ongoing - EU - drakthul. Its going for days for a lot of ppl.
ppl spamming with traces but at least some feedback?

Still going on for me on Stormscale. And yes, I live in Norway.

Sadly whatever hotfix was added today didn’t fix the issue. Loading screens work maybe half the time, but now my character just gets stuck with no abilities working every time I phase into a new zone :frowning_face:

Edit: Seems to have fixed itself now, fingers crossed!
Edit: Nope :joy:

1 Like

Another Norwegian poking in… Telia customer here, so none of this makes any sense.

Getting real sick and tired of the game being unplayable. ):

It is working rather fine for me atm, but my friend is still having massive disconnect problems.

Seems worse today! Are we getting free VPN soon?!

Hmmm, I have been online for about 1 hour now and no problems so far.

Welp it’s back to disconnecting and not loading… =( Time for VPN again…

I am also having the same issue. Norwegian using Altibox.

ill do it in norwegian as most ppl are from scandi:

Jeg har snakka med min ISP ( Eidsiva ) og de har meldt dette inn til Altibox som er kjent med problemet og dom jobber med saken. Er visst et større problem som gjelder mange ISP.
Ikke forvent en fix i løpet av dagen idag.

1 Like

I also contacted Telia here in Denmark but them seem rather clueless :joy:

After not having any issues yesterday, today again I’m starting to get stuck on loading screens with the bar only going halfway or full but never finishing loading.
Telia customer in Sweden.

Fix your dogs*** game getting dc constantly entering arena…

Just chiming in to say I also have issues. Most often when leaving Valdrakken on retail (“phantom” disconnect while still mounted but not able to use any abilities). Have to alt+F4 to exit game.

Howdy!

Some changes yesterday may have helped improve things made around 18:20 UTC. For those of you still affected, can you please post a new traceroute along with your ISP name and where you were in the game, what you were doing, such as taking a portal to somewhere or which zone you were in.

Thank you!