Also from Norway, Telia here. We are in Trøndelag.
I have the same issue. Norway, Enivest my ISP.
The issues occur while travelling between zones, loading screens and sometimes while logging into the game I get stuck on a screen without characters, and I have to reconnect again.
delete because not relevant.
@Ælj,
I do agree that this might be a national/partly regional technical problem since Europe uses the same servers and the problem seems to be pretty regional only in a part of Europe.
My impression was that CGN is utilized quite widely, not only in Norway, but I might be mistaken. Do you have any info in regards to local/regional differences?
CGNAT is uncommon from norwegian ISPs, with the exception of mobile/4G/5G based solutions.
delete because problem seems unrelated to cgn
I can confirm that many altibox partners use CGN as default.
For their fiber customers
Huh, TIL i guess, I’m having this problem and I am definitively not on CGNAT but I am an altibox customer.
I’ve seen both. But are you sure? You can double check by logging in to altibox.no minesider and compare the ip adress there with the ip that shows up when you google whats my ip.
I’m very curious about this and would appreciate feedback so i can delete my first post 
EDIT
I’ve reached my 3 reply limit so editing here
@natsui
awesome. thanks for the info.
Yeah, I agree. Then this is most likely a rounting issue then. Level3 have had problems before if memory servers.
I’ll edit my first post as its irrelevant now.
I 100% have a public IP as I’ve been using it for port forwarding and hosting games on my home server, and have had the same IP for the last 4 years.
My bet would be on some kind of routing issue, potentially with Level3 as the issue also occurs with Diablo 4 as well. While using Mullvad VPN to Sweden it uses sthix.net as a backend, would be interesting to see if telia customers with the issue also get routed through level3
1 Like
@Ælj,
You are spot on in regards to (at least Altibox for me), my public routers IP is in the CGN range (for me 100.66..).
FindMyIP of course doesnt match, and has a general valid public IP address.
Can confirm that using a VPN solves this so once again 100% a routing issue on Blizzards end, as using a VPN to bypass the routing to access Blizzard via a different entry point works just fine.
Not exactly a good solution for most people - Personally it was the kick in the butt I needed to go get myself a VPN which I have been planning to but putting off for a while, but not very ideal for those not planning on that financial burden already.
I think rather than talking about it being on blizzards end it would be more helpful if we could get some kind of data on what routing path those of us with issues are using. if its all on Level3’s end its not directly blizzard and might be something we need to raise with our ISP if they’re the one responsible for the peering.
6 31 ms 31 ms 31 ms BLIZZARD-EN.edge7.Amsterdam1.Level3 dot net [212.72.41.90]
7 * * * Request timed out.
8 * * * Request timed out.
Altibox
Edit: Oh yeah and checked, no CGNAT
I’m not 100% sure about the ip’s for the servers. But these are the 3 in EU I found.
Altibox, public ip customer. I don’t actually play wow atm so don’t know if there are any issues
Timout after 5.
traceroute 185.60.112.157
3 217.213-167-114.customer.lyse.ne (213.167.114.217) 3.304 ms 3.188 ms 3.550 ms
4 ae65.edge1.Oslo2.Level3.ne (62.67.17.221) 3.482 ms 3.414 ms 4.105 ms
5 ae2.3204.edge7.Amsterdam1.level3.ne (4.69.162.181) 33.534 ms 32.359 ms 33.400 ms
traceroute 185.60.112.158
3 217.213-167-114.customer.lyse.ne (213.167.114.217) 3.232 ms 3.166 ms 3.201 ms
4 ae65.edge1.Oslo2.Level3.ne(62.67.17.221) 3.138 ms 4.233 ms 4.172 ms
5 ae2.3204.edge7.Amsterdam1.level3.ne (4.69.162.181) 32.392 ms 32.329 ms 32.266 ms
traceroute 185.60.114.159
3 217.213-167-114.customer.lyse.ne (213.167.114.217) 3.191 ms 3.236 ms 3.427 ms
4 ae65.edge1.Oslo2.Level3.ne(62.67.17.221) 3.116 ms 3.589 ms 3.248 ms
5 ae2.3204.edge7.Amsterdam1.level3.ne (4.69.162.181) 32.618 ms 32.558 ms 32.498 ms
While I do agree that timeouts are bad, it does not explain why this issue seems to be regional related only to a small portion of EU/Europe. As of my understanding, the Amsterdam Level3 server is not unique to Norway, or NO/SE.
So in other words, it’s strange that there are breaking timeouts only for NO customers…
@Paseshift; what happens if you do the tracert while using VPN?
Complained to them on Twitter, at least we’ve got a response there
“Hi, we’re aware and investigating, though no specific ETA at the moment. Thanks for taking the time to let us know, and hope it can be resolved soon!” - @BlizzardCSEU_EN on Twitter, 53 minutes ago
3 Likes
timeouts are normal. not every server on the way actually responds to icmp requests. no reply from something you expect a reply from would be bad. or big MS response times.
1 Like
I too have this issue, and I am also from Norway.
This started with 10.2 and was not an issue before the patch.
Actually all my trace routes are going through now with no time outs. Going to try a bit in game and check
1 Like