Connection issue with servers hop ae1-br01-eqfr5.as57976.net [137.221.80.33] losing packets

Support Technical Support
1

Hello, I am have to report connection problems with your infrastructure, specifically with the hop ae1-br01-eqfr5.as57976.net [137.221.80.33].
Tha problem cause, packet lost on the signal to degrade and therefore lag with the game server and forcing me to use a VPN to be able to play and even with that i need hope to find a server that avoid that hop.

I wonna make clear that is not an ISP Problem as the test and info i will provide will make it obvious and i already tred all possible troubleshooting.

I attach trace route and win mtr again and proof that the hop is within your infrastructure.

Let’s start with the assumption that I normally play with a ping that is at most 35, at the moment it fluctuates between 55/60 and last night between 110/120

|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   82 |   82 |    0 |    0 |    0 |    0 |
|                            151.6.140.70 -    0 |   82 |   82 |    4 |   10 |   46 |    8 |
|                            151.6.140.66 -    0 |   82 |   82 |    4 |    4 |   17 |   17 |
|                              151.6.7.24 -    0 |   82 |   82 |    7 |    8 |    9 |    8 |
|                             151.6.7.239 -    0 |   82 |   82 |    6 |    8 |   11 |    8 |
|                           80.249.208.83 -    0 |   82 |   82 |   33 |   58 |  138 |   58 |
|              ae1-br02-eqam1.as57976.net -    0 |   78 |   78 |   59 |  386 | 2798 |  600 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|         et-0-0-1-pe02-eqam3.as57976.net -    0 |   82 |   82 |   32 |   55 |   68 |   58 |
|                           137.221.66.43 -    0 |   82 |   82 |   33 |   55 |   62 |   58 |
|                          185.60.112.157 -    5 |   71 |   68 |   41 |   56 |   63 |   55 |

 1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    15 ms    12 ms    18 ms  151.6.140.70
  3     4 ms     4 ms     4 ms  151.6.140.66
  4     8 ms     8 ms     8 ms  151.6.7.24
  5     8 ms     8 ms     8 ms  151.6.7.239
  6    62 ms    62 ms    62 ms  80.249.208.83
  7   124 ms   221 ms   218 ms  ae1-br02-eqam1.as57976.net [137.221.78.35]
  8     *        *        *     Richiesta scaduta.
  9    56 ms    56 ms    56 ms  et-0-0-1-pe02-eqam3.as57976.net [137.221.78.57]
 10    58 ms    59 ms    60 ms  137.221.66.43
 11    55 ms    56 ms    56 ms  185.60.112.157

Proof that the hop is within your infrastucture

IP Information for 137.221.80.33
Quick Stats
|IP Location|Netherlands Amsterdam
|ASN|AS57976 BLIZZARD Blizzard Entertainment, Inc, US (registered Mar 23, 2012)|
|Resolve Host|ae1-br01-eqfr5.as57976.net|
|Whois Server|whois ripe net|
|IP Address|137.221.80.33|
inetnum: 137.221.64.0 - 137.221.95.255
netname: BLIZZARD
country: NL
admin-c: BP5978-RIPE
tech-c: BP5978-RIPE
status: ASSIGNED PA
mnt-by: MNT-BLIZZARD
created: 2018-08-27T19:57:32Z
last-modified: 2018-08-27T19:57:32Z
source: RIPE
person: Blizzard Peering
address: 1 Blizzard Way
phone: +1-949-955-1380
nic-hdl: BP5978-RIPE
mnt-by: MNT-BLIZZARD
created: 2016-09-07T17:19:11Z
last-modified: 2018-08-24T18:24:09Z
6 Likes
2

bump with 10 chars to bump

2 Likes
3

More people should comment and like this topic.
More and more people are complaining about this.
You could also post this kind of thing on twitter to the blizzardcs account there.

4

Bumping the post because the problem has not yet been solved.
ae1-br01-eqfr5.as57976.net [137.221.80.33]. and 80.249.208.83 continue to give problems and force the use of a VPN to play.

Can we get an answer from a BLUE? Or do we have to wait forever?

1 Like
5

Wasn’t online during the day, so don’t know if the problem persisted on my end. Now at night it seems to be ok, but that’s how it was behaving for the weekend as well

6

I have massive lag spikes (2-3 seconds) and constant disconnects during last week, today is almost impossible to play, 1-2 seconds with home and 2-3 with the world. I don’t have this lag or problems with any other game…
My ISP isn’t Vodafone…

1 Like
7

Can you do a win mtr test and a trace route test on 185.60.112.157?

So we have multiple repost of the issue and maybe blizz will fix it?

8

Another day… Problem still persist…

BLIZZARD?!

9

This is happening for the past week for me as well. Every. Damn. Night. It’s getting way worse if I’m using the launcher voice chat. It persist for 10-20 minutes then it gets back to normal.

10

I think I have the same issue. just test 100 packets:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 0 100 100 0 0 0 0
10.90.80.1 - 2 97 96 1 2 6 2
ws-gajo1-krze131.siec.internetunion.pl- 0 100 100 1 1 8 2
156-junos-gor46.siec.internetunion.pl- 0 100 100 2 2 40 3
ve126.core2.waw1.he.net- 83 23 4 7 7 8 7
port-channel10.core1.ams1.he.net- 2 96 95 24 26 85 26
178.18.236.78 - 3 93 91 32 35 91 33
ae2-br01-eqfr5.as57976.net- 4 65 63 36 881 4027 350
Request timed out. - 100 20 0 0 0 0 0
Request timed out. - 100 20 0 0 0 0 0
et-0-0-0-pe02-eqam3.as57976.net- 3 92 90 35 36 45 36
137.221.66.43 - 2 96 95 37 37 48 37
185.60.112.157 - 0 100 100 37 37 55 37
________________________________________________ ______ ______ ______ ______ ______ ______
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
11

I think you have issue even before reaching blizzard infrastructure.

You lose packet with ve126.core2.waw1.he.net- 83 that is of
Hurricane, Electric in Cali.

Then yes u start having high ping with ae2-br01-eqfr5.as57976.net
and losing few packet within Blizz infrastructure but since you are having issue even before them it may be something with an earlly node or with yor provider with that node.

12

blizzards staff claims they have fixed this issue and closed all topics related to this, i suggest unsub, i am doing the same

13

Thanks for pointing that out.
I was so focused on big numbers at the mentioned server I missed earlier ones.

14

Try see if a VPN helps out but that issue on that node make me think that you may havng issue with it…

Also have you tryed to do other test and see if it was an isolated problem on that try?