Last week around the time of the patch I started getting random dropouts from the Asia server. US and EU have been stable throughout.
Fast forward about two straight days of troubleshooting through everything Blizzard has published or could offer over live chat and my support ticket, not to mention testing every conceivable configuration of every device I have - I am coming to the conclusion that it may be a routing issue.
As such I decided to trial a VPN to see if I could route around the issue.
I've conducted a number of tracert functions on the various VPN IPs and have noticed a trend in that the signal seems to "disappear" once it hits the 211.174.x.x or 182.162.x.x subnet which are both in Korea. I was able to confirm with another player in Germany that he also gets the same results. It would be handy to have a little more data from people to verify this isn't part of the problem. The only relevant info would be from around hop 10 onwards, I'm not interested in anyone's personal IP details
After trying about 7-8 different VPN servers, I found one that has been stable for about 2hrs. Considering I would often drop from the menu upon login and would have to reconnect after each game this is promising. It's also posed a few questions:
Why would so many VPN servers around the world drop, but then one work? (I'm in Australia, server is in NZ) Can someone educate me on how to read the tracert data properly? High ping and time outs are easy to see, but pinpointing where issues may be is not! Can anyone suggest a reliable free (or cheap) VPN that I could use if this is indeed a work around?
I've noticed that the VPN servers that ARE dropping last ping the 211.17x.x.x subnet whereas the one that has worked for me last pinged the 211.234.x.x subnet. Could this be an indicator that there's something wrong either phyiscally or whatever at the 211.17x.x.x subnet? (I'm showing my n00bness here)
Any help is greatly appreciated. This is extremely frustrating!
So, you "contacted" blizz through chat and couldn't resolve? what did they tell you? Have you contacted your ISP? Have you tried to replace something on your equipment? (cable, router, etc) Are you using wifi, or cable connection?
"We" as if there's a crack team sitting there just waiting to solve the issue LOL
Support ticket, live chat - they threw their hands in the air. The guy was helpful in live chat, but just ran out of ideas.
My ISP is the biggest useless bunch of f*cktards ever to inhabit this planet. It took dozens of calls and months of hassling them just to send a tech out last year (who literally did nothing) for an unrelated issue. I'd be better cutting my left nut off than trying to communicate with them.
I've tried replacing EVERYTHING. I've tested every conceivable connection and device and configuration of hardware imaginable to man.
The conclusion I have come to is that there is a routing issue - as stated. Without any more information regarding tracerts from other people them I'm pretty much f&cked for trying to make a conclusion. Though for the time being I have found a free (limited) VPN that successfully routes via NZ (from Aust) that maintains a stable connection.
I noticed a slight change with the issue today. The connection would maintain it's stability until I interacted with the game. Doesn't help my situation, but it was interesting to discover that it would sit in the menu for a long time, but often if I tried to click through any menu options it would disconnect. It was still forcing me to reconnect after each game regardless.
Anyway, thanks for at least taking the time to respond. There are others reporting the same issue in the Blizzard tech forum. Blizzard do not seem to look at their tech forum though. Pathetic "customer support" there.
Without a complete understanding of how to read a tracert I cannot be sure, bit the more things I test the more I'm inclined to think that this is an issue closer to the Blizzard server end in Korea.
root@un64u:/mnt/hdd# traceroute -n 182.162.132.1 traceroute to 182.162.132.1 (182.162.132.1), 30 hops max, 60 byte packets <removed> 7 84.116.136.98 23.180 ms 84.116.135.50 17.506 ms 20.875 ms 8 129.250.66.101 21.532 ms 17.522 ms 21.800 ms 9 129.250.4.125 23.780 ms 24.074 ms 25.943 ms 10 129.250.2.18 114.596 ms 108.080 ms 108.098 ms 11 129.250.3.207 104.093 ms 105.511 ms 110.394 ms 12 129.250.2.149 107.881 ms 101.569 ms 106.823 ms 13 129.250.3.189 176.113 ms 166.810 ms 172.823 ms 14 129.250.6.49 169.551 ms 171.004 ms 174.508 ms 15 129.250.2.214 183.665 ms 182.407 ms 176.003 ms 16 168.143.229.202 170.698 ms 176.663 ms 176.813 ms 17 211.118.180.149 159.702 ms 211.118.180.169 162.397 ms 1.213.145.25 163.231 ms 18 1.208.104.89 280.701 ms 287.661 ms 1.208.146.17 309.033 ms 19 211.53.88.178 291.754 ms 1.208.145.154 286.461 ms 1.208.175.94 276.133 ms 20 1.208.145.25 747.218 ms 1.213.151.109 295.018 ms 1.208.145.53 298.261 ms 21 203.233.117.210 298.069 ms 1.213.150.6 298.001 ms 203.233.117.186 294.978 ms 22 211.174.48.62 308.103 ms 110.45.128.74 287.197 ms 110.45.128.78 299.049 ms 23 182.162.152.238 303.611 ms 182.162.152.162 301.182 ms 182.162.152.226 309.063 ms 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
Hope that helps mate. I play on Asia too and haven't noticed problems. I'm in the UK on home broadband.
Hope that helps mate. I play on Asia too and haven't noticed problems. I'm in the UK on home broadband.
Thanks mate. I think that might have blown my latest theory out of the water a bit as you're going through the 211.17x.x.x subnet that I thought may have been causing the issue.
Wish I knew how to read these tracert reports properly!!
Hope that helps mate. I play on Asia too and haven't noticed problems. I'm in the UK on home broadband.
Thanks mate. I think that might have blown my latest theory out of the water a bit as you're going through the 211.17x.x.x subnet that I thought may have been causing the issue.
Wish I knew how to read these tracert reports properly!!
Thanks mate. I think that might have blown my latest theory out of the water a bit as you're going through the 211.17x.x.x subnet that I thought may have been causing the issue.
Wish I knew how to read these tracert reports properly!!
In fairness I've not been playing on Asia loads but here's the last games I played with UK timestamps in case it's an intermittent issue.
The output from my trace route is linux and probably formatted slightly differently.
(I did well in this screenshot but was lucky. with matchups)
Nice run man! I'm guessing by the game durations that's the "Beast Hunter" as I think it should be called in HSreplay.net at least. There actually is a Midrange Hunter deck that still exists, spells, spellstones, Zul'jin & a garbage WR LOL
It doesn't feel intermittent. It feels more like a routing issue. I can guarantee any time I log in with my standard connection I'll drop, and I can guarantee that if I connect through the VPN it'll remain stable.
As eliasfajardo says, might need to do some googling about it.
Nice run man! I'm guessing by the game durations that's the "Beast Hunter" as I think it should be called in HSreplay.net at least. There actually is a Midrange Hunter deck that still exists, spells, spellstones, Zul'jin & a garbage WR LOL
It doesn't feel intermittent. It feels more like a routing issue. I can guarantee any time I log in with my standard connection I'll drop, and I can guarantee that if I connect through the VPN it'll remain stable.
As eliasfajardo says, might need to do some googling about it.
Does sound like routing to me also.
You could leave a ping running to some of those nodes and see where the break happens when you lose connection.
Thanks:) The deck does run spell stones. So maybe midrange is not the right title it's just what I call it.
I'd definitely call that Midrange - it's the decks without secrets/spellstones that should be called "Beast Hunter" IMHO. There's nothing midrange about those aggro face smashing decks!
If you're referring to ping 182.162.132.1 -t then it straight up times out. I haven't seen a single tracert get all the way to the destination IP.
I pinged the last known IP from my tracert (182.162.152.170) but it doesn't change results when the connection drops.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Last week around the time of the patch I started getting random dropouts from the Asia server. US and EU have been stable throughout.
Fast forward about two straight days of troubleshooting through everything Blizzard has published or could offer over live chat and my support ticket, not to mention testing every conceivable configuration of every device I have - I am coming to the conclusion that it may be a routing issue.
As such I decided to trial a VPN to see if I could route around the issue.
I've conducted a number of tracert functions on the various VPN IPs and have noticed a trend in that the signal seems to "disappear" once it hits the 211.174.x.x or 182.162.x.x subnet which are both in Korea. I was able to confirm with another player in Germany that he also gets the same results. It would be handy to have a little more data from people to verify this isn't part of the problem. The only relevant info would be from around hop 10 onwards, I'm not interested in anyone's personal IP details
tracert 182.162.132.1
Refer Blizzard support documentation - https://us.battle.net/support/en/article/000007870
After trying about 7-8 different VPN servers, I found one that has been stable for about 2hrs. Considering I would often drop from the menu upon login and would have to reconnect after each game this is promising. It's also posed a few questions:
Why would so many VPN servers around the world drop, but then one work? (I'm in Australia, server is in NZ)
Can someone educate me on how to read the tracert data properly? High ping and time outs are easy to see, but pinpointing where issues may be is not!
Can anyone suggest a reliable free (or cheap) VPN that I could use if this is indeed a work around?
I've noticed that the VPN servers that ARE dropping last ping the 211.17x.x.x subnet whereas the one that has worked for me last pinged the 211.234.x.x subnet. Could this be an indicator that there's something wrong either phyiscally or whatever at the 211.17x.x.x subnet? (I'm showing my n00bness here)
Any help is greatly appreciated. This is extremely frustrating!
OK so maybe if I start whinging about something stupid about the game I'll get some replies?
So, you "contacted" blizz through chat and couldn't resolve?
what did they tell you?
Have you contacted your ISP?
Have you tried to replace something on your equipment? (cable, router, etc)
Are you using wifi, or cable connection?
This is the type of information we need to know
"We" as if there's a crack team sitting there just waiting to solve the issue LOL
Support ticket, live chat - they threw their hands in the air. The guy was helpful in live chat, but just ran out of ideas.
My ISP is the biggest useless bunch of f*cktards ever to inhabit this planet. It took dozens of calls and months of hassling them just to send a tech out last year (who literally did nothing) for an unrelated issue. I'd be better cutting my left nut off than trying to communicate with them.
I've tried replacing EVERYTHING. I've tested every conceivable connection and device and configuration of hardware imaginable to man.
The conclusion I have come to is that there is a routing issue - as stated. Without any more information regarding tracerts from other people them I'm pretty much f&cked for trying to make a conclusion. Though for the time being I have found a free (limited) VPN that successfully routes via NZ (from Aust) that maintains a stable connection.
I noticed a slight change with the issue today. The connection would maintain it's stability until I interacted with the game. Doesn't help my situation, but it was interesting to discover that it would sit in the menu for a long time, but often if I tried to click through any menu options it would disconnect. It was still forcing me to reconnect after each game regardless.
Anyway, thanks for at least taking the time to respond. There are others reporting the same issue in the Blizzard tech forum. Blizzard do not seem to look at their tech forum though. Pathetic "customer support" there.
Without a complete understanding of how to read a tracert I cannot be sure, bit the more things I test the more I'm inclined to think that this is an issue closer to the Blizzard server end in Korea.
.
Thanks mate. I think that might have blown my latest theory out of the water a bit as you're going through the 211.17x.x.x subnet that I thought may have been causing the issue.
Wish I knew how to read these tracert reports properly!!
nothing that google can't help with
In fairness I've not been playing on Asia loads but here's the last games I played with UK timestamps in case it's an intermittent issue.
The output from my trace route is linux and probably formatted slightly differently.
(I did well in this screenshot but was lucky. with matchups)
.
Nice run man! I'm guessing by the game durations that's the "Beast Hunter" as I think it should be called in HSreplay.net at least. There actually is a Midrange Hunter deck that still exists, spells, spellstones, Zul'jin & a garbage WR LOL
It doesn't feel intermittent. It feels more like a routing issue. I can guarantee any time I log in with my standard connection I'll drop, and I can guarantee that if I connect through the VPN it'll remain stable.
As eliasfajardo says, might need to do some googling about it.
Does sound like routing to me also.
You could leave a ping running to some of those nodes and see where the break happens when you lose connection.
Thanks:) The deck does run spell stones. So maybe midrange is not the right title it's just what I call it.
Sucks against odd mage and odd pally I found.
.
I'd definitely call that Midrange - it's the decks without secrets/spellstones that should be called "Beast Hunter" IMHO. There's nothing midrange about those aggro face smashing decks!
If you're referring to ping 182.162.132.1 -t then it straight up times out. I haven't seen a single tracert get all the way to the destination IP.
I pinged the last known IP from my tracert (182.162.152.170) but it doesn't change results when the connection drops.