[Balticom, Latvia] Connection issues with game and Blizzard website

Segden-2744 · April 26, 2019, 9:43am

The problem is solved. Thanks everyone for participation, both Blizzard and Provider did well, as well as people that responded to this topic, it contributed a lot.

Dear developers,
Since the event has started not only me but also a lot of other people have problems related to the connection. I asked a lot of my friends in real life to check whether they also have a problem with connection to exclude possible problems with provider. I found out that all of them have problems but they happen only with blizzard, so by that, I mean that we have stable connection with other games and websites but when it comes to blizzard problems are happening both in-game and in blizzard website. I didn’t do any tests to check stage-by stage connection and where problems occur exactly (like it is provider’s fault or host server) but it is clear even without it because as I see by forum and by people from other countries that I asked, problems occur with everyone and everywhere.
And final remark is that all problems started when the event was added to the client. Thus I would like to encourage administration to do something because event is going on and a half or even majority of players do not have stable connection to be able participate in event. More than 10 days are gone and nothing has been changed. What are you waiting for, Blizzard? How long you will tell us that it is our problem, but not yours, when all webpages are loading but blizzard’s - not?
P.S. do not send me to Troubleshooting Connection post to reboot my router, I did it for many times and the problem is NOT WITH PROVIDER, PROBLEM IS WITH BLIZZARD SERVERS.
How many more people have to complain about connection problem to be heard?

Etsu-21928 · April 26, 2019, 10:07am

I have the same problem. Can you do something please? I also can’t play all this time since the event had started.

Nekolone-21207 · April 26, 2019, 10:22am

I have the same problem…

Segden-2744 · April 27, 2019, 9:00am

I’ve tried to play through VPN and to my wonder it helped, no disconnects for 3 hours session. So the problem might be with access of my provider to Blizzard’s servers. I sent this data to my provider and they replied that problems begin exactly when it comes to access to Blizard servers.

Vyraneer · April 27, 2019, 1:38pm

Guys, what is your location and what provider you are using?

Please add also your traceroute and pathping results to this thread, as well as a WinMTR test.

This usually indicates that issue is not within our game servers or pages, Sedgen. A VPN does not affect the destination (our services), but it does modify the path your connection takes to reach them, thus often bypassing your provider’s infrastructures.
We’ll be happy to have a more in-depth look, but we need the information I requested above.

Important: Please note that the use of a VPN is not advised and it can cause further connection issues.

If you are in the same country/city/using the same provider, this may be a local issue. However, I can’t tell for sure without any other information.

Feedback? Blizzard EU - Customer Service Forum Representatives Surveys - Vyraneer

Nekolone-21207 · April 27, 2019, 7:02pm

results

WinMTR test

WinMTR Statistics

WinMTR statistics

Host	%	Sent	Recv	Best	Avrg	Wrst	Last
192.168.108.254	0	1361	1361	0	0	38	0
10.49.133.126	0	1361	1361	1	3	78	1
te-2401-29-72-65.balticom.lv	27	669	495	2	155	1867	406
No response from host	100	273	0	0	0	0	0
ge-te-s22-64-253.balticom.lv	0	1362	1362	2	2	76	2
85.254.1.19	1	1346	1342	2	7	208	55
No response from host	100	273	0	0	0	0	0
No response from host	100	273	0	0	0	0	0
No response from host	100	273	0	0	0	0	0
No response from host	100	273	0	0	0	0	0
No response from host	100	273	0	0	0	0	0
blizzard.demarc.cogentco.com	0	1361	1361	37	38	156	37
No response from host	100	273	0	0	0	0	0
et-0-0-67-pe02-eqam1.as57976.net	1	1326	1317	51	52	148	51
185.60.112.157	1	1326	1317	53	54	125	54

traceroute

’а ббЁа®ўЄ ¬ аиагв Є 185.60.112.157 б ¬ ЄбЁ¬ «мл¬ зЁб«®¬ Їал¦Є®ў 30

1 <1 ¬б 1 ms 1 ms 192.168.108.254
2 1 ms 1 ms 1 ms 10.49.133.126
3 151 ms * * te-2401-29-72-65.balticom.lv [82.193.72.65]
4 2 ms 1 ms 1 ms r06-69-198.balticom.lv [82.193.69.198]
5 2 ms 2 ms 2 ms ge-te-s22-64-253.balticom.lv [82.193.64.253]
6 2 ms 2 ms 2 ms 85.254.1.19
7 2 ms 2 ms 2 ms te0-3-1-7.rcr51.rix01 .atlas.cogentco.com [149.14.74.25]
8 9 ms 10 ms 9 ms be3734.ccr21.sto03 .atlas.cogentco.com [154.54.59.53]
9 28 ms 28 ms 28 ms be2281.ccr41.ham01 .atlas.cogentco.com [154.54.63.1]
10 37 ms 37 ms 37 ms be2815.ccr41.ams03 .atlas.cogentco.com [154.54.38.205]
11 37 ms 38 ms 38 ms be2322.rcr21.b021535-1 .ams03.atlas.cogentco.com [130.117.50.82]
12 37 ms 39 ms 37 ms blizzard.demarc .cogentco.com [149.6.128.9]
13 37 ms 49 ms 37 ms ae1-br02-eqam1 .as57976.net [137.221.78.35]
14 51 ms 52 ms 51 ms et-0-0-67-pe02-eqam1 .as57976.net [137.221.78.73]
15 53 ms 54 ms 54 ms 185.60.112.157

’а ббЁа®ўЄ § ўҐаиҐ .

pathping

’а ббЁа®ўЄ ¬ аиагв Є 185.60.112.157 б ¬ ЄбЁ¬ «мл¬ зЁб«®¬ ЇҐаҐе®¤®ў 30

0 Nekolone .zyxel.com [192.168.108.40]
1 192.168.108.254
2 10.49.133.126
3 te-2401-29-72-65.balticom.lv [82.193.72.65]
4 r06-69-198.balticom.lv [82.193.69.198]
5 ge-te-s22-64-253.balticom.lv [82.193.64.253]
6 85.254.1.19
7 te0-3-1-7.rcr51.rix01.atlas.cogentco .com [149.14.74.25]
8 be3734.ccr21.sto03.atlas.cogentco .com [154.54.59.53]
9 be2281.ccr41.ham01.atlas.cogentco .com [154.54.63.1]
10 be2815.ccr41.ams03.atlas.cogentco .com [154.54.38.205]
11 be2322.rcr21.b021535-1.ams03.atlas.cogentco .com [130.117.50.82]
12 blizzard.demarc.cogentco .com [149.6.128.9]
13 ae1-br02-eqam1.as57976 .net [137.221.78.35]
14 et-0-0-67-pe02-eqam1.as57976 .net [137.221.78.73]
15 185.60.112.157

Џ®¤бзҐв бв вЁбвЁЄЁ § : 375 бҐЄ. …
€бе®¤л© г§Ґ« Њ аиагвл© г§Ґ«
Џал¦®Є RTT “вҐа./ЋвЇа. % “вҐа./ЋвЇа. % Ђ¤аҐб
0 Nekolone.zyxel .com [192.168.108.40]
0/ 100 = 0% |
1 1¬б 0/ 100 = 0% 0/ 100 = 0% 192.168.108.254
0/ 100 = 0% |
2 2¬б 0/ 100 = 0% 0/ 100 = 0% 10.49.133.126
0/ 100 = 0% |
3 2¬б 0/ 100 = 0% 0/ 100 = 0% te-2401-29-72-65.balticom.lv [82.193.72.65]
0/ 100 = 0% |
4 2¬б 0/ 100 = 0% 0/ 100 = 0% r06-69-198.balticom.lv [82.193.69.198]
0/ 100 = 0% |
5 2¬б 0/ 100 = 0% 0/ 100 = 0% ge-te-s22-64-253.balticom.lv [82.193.64.253]
0/ 100 = 0% |
6 5¬б 2/ 100 = 2% 2/ 100 = 2% 85.254.1.19
0/ 100 = 0% |
7 2¬б 0/ 100 = 0% 0/ 100 = 0% te0-3-1-7.rcr51.rix01.atlas.cogentco .com [149.14.74.25]
0/ 100 = 0% |
8 10¬б 0/ 100 = 0% 0/ 100 = 0% be3734.ccr21.sto03.atlas.cogentco .com [154.54.59.53]
0/ 100 = 0% |
9 32¬б 0/ 100 = 0% 0/ 100 = 0% be2281.ccr41.ham01.atlas.cogentco .com [154.54.63.1]
0/ 100 = 0% |
10 37¬б 0/ 100 = 0% 0/ 100 = 0% be2815.ccr41.ams03.atlas.cogentco .com [154.54.38.205]
0/ 100 = 0% |
11 37¬б 0/ 100 = 0% 0/ 100 = 0% be2322.rcr21.b021535-1.ams03.atlas.cogentco .com [130.117.50.82]
0/ 100 = 0% |
12 37¬б 0/ 100 = 0% 0/ 100 = 0% blizzard .demarc.cogentco.com [149.6.128.9]
0/ 100 = 0% |
13 43¬б 0/ 100 = 0% 0/ 100 = 0% ae1-br02-eqam1 .as57976.net [137.221.78.35]
0/ 100 = 0% |
14 52¬б 0/ 100 = 0% 0/ 100 = 0% et-0-0-67-pe02-eqam1 .as57976.net [137.221.78.73]
0/ 100 = 0% |
15 54¬б 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157

’а ббЁа®ўЄ § ўҐаиҐ .

Segden-2744 · April 27, 2019, 7:08pm

All of us from Latvia, Riga with one provider - balticom . lv
It seems like problem started to occur less often, but still occurs time to time
Russian forum already has the topic with the same issue related to disconnects in Latvia, so there you can see more data if needed:

As you asked, I collected all the things you have mentioned above:

My traceroute:

Summary

1 <1 ¬б <1 ¬б <1 ¬б 192.168.11.1
2 18 ms 6 ms 16 ms balticom-16-126.balticom .lv [77.93.16.126]
3 201 ms * 4 ms te-2401-29-72-65.balticom .lv [82.193.72.65]
4 3 ms 3 ms 3 ms r03-69-195.balticom .lv [82.193.69.195]
5 4 ms 4 ms 3 ms ge-te-s5-64-254.balticom .lv [82.193.64.254]
6 5 ms 3 ms 3 ms te4-4.tv.riga.globalcom .lv [85.254.1.133]
7 4 ms 5 ms 6 ms te0-2-1-7.rcr51.rix01.atlas.cogentco .com [149.14.74.17]
8 12 ms 14 ms 12 ms be3735.ccr22.sto03.atlas.cogentco .com [154.54.59.57]
9 27 ms 27 ms 26 ms be2282.ccr42.ham01.atlas.cogentco .com [154.54.72.105]
10 39 ms 39 ms 41 ms be2816.ccr42.ams03.atlas .cogentco.com [154.54.38.209]
11 40 ms 38 ms 41 ms be2447.rcr21.b021535-1.ams03.atlas.cogentco .com [130.117.50.250]
12 45 ms 40 ms 41 ms blizzard.demarc.cogentco .com [149.6.128.9]
13 817 ms 1099 ms 1320 ms ae1-br02-eqam1.as57976 .net [137.221.78.35]
14 64 ms 62 ms 54 ms et-0-0-67-pe01-eqam1.as57976 .net [137.221.78.71]
15 50 ms 50 ms 50 ms 185.60.112.157

My pathping

Summary

0 Win10.zyxel .com [192.168.11.43]
1 192.168.11.1
2 balticom-16-126.balticom .lv [77.93.16.126]
3 te-2401-29-72-65.balticom .lv [82.193.72.65]
4 r03-69-195.balticom .lv [82.193.69.195]
5 ge-te-s5-64-254.balticom .lv [82.193.64.254]
6 te1-2.501.tv.riga.globalcom .lv [85.254.1.135]
7 te0-2-1-7.rcr51.rix01.atlas.cogentco .com [149.14.74.17]
8 be3734.ccr21.sto03.atlas.cogentco .com [154.54.59.53]
9 be2281.ccr41.ham01.atlas.cogentco .com [154.54.63.1]
10 be2815.ccr41.ams03.atlas.cogentco .com [154.54.38.205]
11 be2322.rcr21.b021535-1.ams03.atlas.cogentco .com [130.117.50.82]
12 blizzard.demarc.cogentco .com [149.6.128.9]
13 ae1-br02-eqam1.as57976 .net [137.221.78.35]
14 et-0-0-3-br02-eqpa4.as57976 .net [137.221.65.92]
15 be2-pe01-eqpa4.as57976 .net [137.221.77.71]

My winMTR

Summary

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.11.1 - 0 | 4084 | 4084 | 0 | 1 | 34 | 1 |

| balticom-16-126.balticom .lv - 0 | 4083 | 4083 | 2 | 4 | 58 | 4 |

| te-2401-29-72-65.balticom .lv - 31 | 1847 | 1290 | 3 | 207 | 3310 | 481 |

| No response from host - 100 | 818 | 0 | 0 | 0 | 0 | 0 |

| ge-te-s5-64-254.balticom .lv - 1 | 4079 | 4078 | 3 | 4 | 55 | 3 |

| te1-2.501.tv.riga.globalcom .lv - 1 | 4049 | 4040 | 3 | 9 | 215 | 3 |

| No response from host - 100 | 818 | 0 | 0 | 0 | 0 | 0 |

| blizzard.demarc.cogentco .com - 1 | 4053 | 4045 | 38 | 41 | 78 | 42 |

| No response from host - 100 | 818 | 0 | 0 | 0 | 0 | 0 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

JustDeb-2282 · April 28, 2019, 3:22am

I have the same issue for months now, its not my internet, its not my PC ether, i changed to the best internet and built a new PC , its not from my side, i cant play properly for months

Vyraneer · April 28, 2019, 8:37am

@Nekolone & @Sedgen

Thank you for your replies, guys!

Much appreciated, thank you!
I’ll go through the thread and gather the information for our network team now. However, I recommend you get in touch with your ISP again and ask them to have another look. The reason for this is that, unfortunately, the issue does not start when it comes to access Blizzard servers but way before that.

Please, have a look here:

Note: Your pathping is missing the second part, the one with the percentages. ^^

As you can see, the hop highlighted (the same for you both) is within your ISP’s network infrastructure - we’ll still collect this data but it’s important that you inform your provider of the issue, so they can run the investigation required on their side as well. This can greatly speed the resolution process.

This said, thank you both again for the information provided, please don’t hesitate to add here any additional updates on the issue you might have.

Feedback? Blizzard EU - Customer Service Forum Representatives Surveys - Vyraneer

Vyraneer · April 28, 2019, 8:46am

Hi JustDeb,

Unless you have the same provider and you are in the same city/country indicated in this thread, please start your own discussion. This way we won’t create confusion between 2 potentially very different issues.

If you have the same provider and the same issue

Please provide the data I asked for here.

If you have a different provider/country

Please open a new thread, explain what happens and when the issue started, and indicated any troubleshooting steps you already tried yourself.
Please add a copy of your WinMTR test and of your traceroute & pathping tests (both should be done during a problematic moment or immediately after a disconnection).

Thank you!

Feedback? Blizzard EU - Customer Service Forum Representatives Surveys - Vyraneer

oslja-2130 · April 28, 2019, 8:49am

Same problem here. Also balticom, Latvia.
Because of that i’ve already received an exp penalty.

Vyraneer · April 28, 2019, 9:03am

And same request for you as well then! ^^

I appreciate you joining this thread, oslja, but we do need the data requested to investigate the issue.
As a note, if you have the same issue you’ll most likely need to report it to your IPS as well (please see my reply here for more details)- it’s easier if you have the data you can refer to.

Feedback? Blizzard EU - Customer Service Forum Representatives Surveys - Vyraneer

WarSword-21590 · April 29, 2019, 9:33am

Hello
According to MTR result problem is in Blizzard infrastructure between 137.221.78.33 and 137.221.78.67 (see below). Both IP addresses are assigned to Blizzard.
On Apr 25, 2019, got a reply from Mr. Alan Gonzalez (Senior Network Engineer at Blizzard Entertainment). There was information about some problems with one of Blizzard’s connections. He wrote that “We have taken the affected link out of service”.
I have checked and answered that the problem still exists but had no answer after that.

R-10G-12.balticom.lv (0.0.0.0) Fri Apr 26 10:21:53 2019
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev

82.193.64.253 0.0% 6664 0.4 0.3 0.3 47.7 1.4
85.254.1.19 0.0% 6664 0.5 3.8 0.4 311.4 23.8
149.14.74.25 0.0% 6664 0.5 0.5 0.4 1.1 0.0
154.54.59.53 0.0% 6664 8.0 7.8 7.8 12.7 0.2
154.54.63.1 0.0% 6664 23.0 24.6 22.8 30.7 1.3
154.54.38.205 0.0% 6663 31.6 31.6 31.5 38.6 0.3
130.117.50.82 0.0% 6663 32.2 33.8 32.0 41.6 1.3
149.6.128.9 0.0% 6663 32.0 32.0 31.8 71.9 2.7
9. 137.221.78.33 0.0% 6663 32.1 56.3 32.0 12209 358.3
10. 137.221.78.67 3.9% 6663 47.4 47.2 47.2 78.1 1.4
137.221.66.43 4.0% 6663 51.1 51.0 50.9 53.7 0.3
185.60.112.157 4.0% 6663 47.2 47.1 47.1 49.7 0.0

WarSword-21590 · April 29, 2019, 9:36am

As you can see - there is no packet loss to next hop after this one. This means, that there is just a CPU protection enabled on equipment with IP 82.193.72.65

SomaZ-2723 · April 29, 2019, 7:43pm

Adding my WinMTR here since I’m having the same issue with the same internet provider. Seems the issue is with a blizzard server/point since the relevant loss occurred near the end of the route. It happened right exactly when I got disconnected from the server. Ignore the 3rd point from the top, it’s one of those “100% loss” points basically.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  282 |  282 |    0 |    2 |  107 |    1 |
|                            10.49.97.254 -    0 |  282 |  282 |    0 |    2 |   66 |    1 |
|                            82.193.72.65 -   62 |  282 |  108 | 63274 | 29235 | 72425 | 63274 |
|                  r06-69-198.balticom.lv -    0 |  282 |  282 |    1 |    3 |   84 |    2 |
|            ge-te-s22-64-253.balticom.lv -    0 |  282 |  282 |    1 |    4 |  137 |    2 |
|                             85.254.1.17 -    0 |  282 |  282 |    1 |    9 |  222 |    3 |
|te0-3-1-7.rcr51.rix01.atlas.cogentco.com -    0 |  282 |  282 |    1 |    5 |  121 |    3 |
|   be3734.ccr21.sto03.atlas.cogentco.com -    0 |  281 |  281 |    9 |   13 |  131 |   11 |
|   be2281.ccr41.ham01.atlas.cogentco.com -    1 |  281 |  280 |   28 |   32 |  242 |   28 |
|   be2815.ccr41.ams03.atlas.cogentco.com -    0 |  281 |  281 |   33 |   36 |  159 |   36 |
|be2322.rcr21.b021535-1.ams03.atlas.cogentco.com -    0 |  281 |  281 |   36 |   56 |  172 |   62 |
|            blizzard.demarc.cogentco.com -    0 |  281 |  281 |   36 |   53 |  264 |   69 |
|              ae1-br02-eqam1.as57976.net -   11 |  281 |  251 |   54 |   77 |  403 |   64 |
|         et-0-0-3-br02-eqpa4.as57976.net -    0 |  281 |  281 |   42 |  458 | 12500 |   64 |
|              be2-pe01-eqpa4.as57976.net -   11 |  281 |  251 |   57 |   67 |  247 |   67 |
|                   No response from host -  100 |  281 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|

Segden-2744 · April 30, 2019, 2:30pm

In order, if administration thinks that problem somehow disappeared, let me remind that no, problem still is not solved and we still have no chance to play overwatch while event is going on.

guliver-2478 · April 30, 2019, 6:33pm

HI, I have the same disconnects. From same Balticom ISP but I’m not sure that Balticom are guilty.
There are 2 results.
In both cases te-2401-29-72-65,balticom,lv has a lot packet’s lost but it doesn’t affect playing overwatch. But problem’s starts only when there are lost packets after blizzard,demarc,cogentco,com or et-0-0-3-br02-eqpa4,as57976,net.
Those disconnect happens quite often - like every hour or half an hour and longs for 1-3 minutes.

1. When everything is OK

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host	%	Sent	Recv	Best	Avrg	Wrst	Last
NBG6616,zyxel,com	0	609	609	0	0	3	0
10,49,55,190	0	609	609	0	1	30	0
te-2401-29-72-65,balticom,lv	37	247	157	0	288	1688	1608
r07-69-199,balticom,lv	1	594	590	0	0	4	1
ge-te-s22-64-253,balticom,lv	1	605	604	0	0	10	0
85,254,1,19	2	586	580	0	5	205	1
te0-3-1-7,rcr51,rix01,atlas,cogentco,com	0	609	609	1	1	5	1
be3734,ccr21,sto03,atlas,cogentco,com	0	609	609	8	8	11	8
be2281,ccr41,ham01,atlas,cogentco,com	1	606	605	30	30	35	30
be2815,ccr41,ams03,atlas,cogentco,com	1	594	590	35	36	43	36
be2322,rcr21,b021535-1,ams03,atlas,cogentco,com	1	594	590	39	40	43	40
blizzard,demarc,cogentco,com	0	609	609	39	40	70	40
ae1-br02-eqam1,as57976,net	1	597	594	60	81	1101	60
et-0-0-3-br02-eqpa4,as57976,net	0	609	609	48	54	183	48
be2-pe02-eqpa4,as57976,net	0	609	609	62	62	65	63
185,60,114,159	1	602	600	60	60	83	61
________________________________________________	______	______	______	______	______	______

2. And when I disconnected and even can't login to blizzard app or overwatch

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host	%	Sent	Recv	Best	Avrg	Wrst	Last
NBG6616,zyxel,com	0	237	237	0	0	2	0
10,49,55,190	0	237	237	0	0	14	0
te-2401-29-72-65,balticom,lv	58	69	29	0	744	2875	120
r07-69-199,balticom,lv	0	237	237	0	0	3	0
ge-te-s22-64-253,balticom,lv	1	234	233	0	0	8	0
85,254,1,19	1	234	233	0	6	191	1
te0-3-1-7,rcr51,rix01,atlas,cogentco,com	0	237	237	1	1	5	1
be3734,ccr21,sto03,atlas,cogentco,com	0	237	237	8	8	11	8
be2281,ccr41,ham01,atlas,cogentco,com	0	237	237	30	30	35	30
be2815,ccr41,ams03,atlas,cogentco,com	0	237	237	35	36	44	36
be2322,rcr21,b021535-1,ams03,atlas,cogentco,com	0	237	237	39	40	43	40
blizzard,demarc,cogentco,com	0	237	237	39	40	58	39
No response from host	100	47	0	0	0	0	0
et-0-0-3-br02-eqpa4,as57976,net	0	237	237	48	54	399	49
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
No response from host	100	47	0	0	0	0	0
________________________________________________	______	______	______	______	______	______

PS. I replace all dot’s with commas because I got message “You cannot post links”

SomaZ-2723 · April 30, 2019, 9:21pm

As a temporary work-around, using a VPN solves the issue (which indicates further that it’s not an issue with the ISP or the internet connection, but with blizzard).

Segden-2744 · May 1, 2019, 8:46am

I’m so much confused with solution of this problem. In russian topic administrator instead of collecting data replies all the time that problem is from provider side, not by blizzard, while my provider replied me via email that problem is from blizzard side. Instead of solving the problem which exists already for more than 2 weeks they blame each other because no one wants to admit on which side is a problem. GG, both.

LoGo-2156 · May 1, 2019, 3:19pm

Same thing here but with lattelecom, or maybe there is no difference, no idea.
Not getting disconnect though, just higher ping than i used to and now it is noticeably annoying. ~75

tracert

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms dsldevice.lan [192.168.1.254]
2 2 ms 1 ms 1 ms 81.198.8.1
3 2 ms 2 ms 1 ms 195.122.0.162
4 2 ms 1 ms 2 ms 87.110.223.130
5 75 ms 47 ms 47 ms pr01.eqfr5.blizzardonline .net [80.81.195.26]
6 48 ms 50 ms 49 ms ae1-br01-eqfr5.as57976 .net [137.221.80.33]
7 43 ms 42 ms 43 ms et-0-0-2-br01-eqam1.as57976 .net [137.221.65.29]
8 49 ms 49 ms 49 ms et-0-0-31-pe01-eqam1.as57976 .net [137.221.78.67]
9 49 ms 49 ms 49 ms 185.60.112.157
Trace complete.

pathping

Tracing route to 185.60.112.157 over a maximum of 30 hops

0 LoGo-PC [192.168.1.100]
1 dsldevice.lan [192.168.1.254]
2 81.198.8.1
3 195.122.0.162
4 87.110.223.130
5 pr01.eqfr5.blizzardonline .net [80.81.195.26]
6 ae1-br01-eqfr5.as57976 .net [137.221.80.33]
7 et-0-0-2-br01-eqam1.as57976 .net [137.221.65.29]
8 et-0-0-31-pe01-eqam1.as57976 .net [137.221.78.67]
9 185.60.112.157

Computing statistics for 225 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 LoGo-PC [192.168.1.100]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% dsldevice.lan [192.168.1.254]
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% 81.198.8.1
0/ 100 = 0% |
3 1ms 0/ 100 = 0% 0/ 100 = 0% 195.122.0.162
0/ 100 = 0% |
4 1ms 0/ 100 = 0% 0/ 100 = 0% 87.110.223.130
0/ 100 = 0% |
5 33ms 0/ 100 = 0% 0/ 100 = 0% pr01.eqfr5.blizzardonline .net [80.81.195.26]
0/ 100 = 0% |
6 56ms 0/ 100 = 0% 0/ 100 = 0% ae1-br01-eqfr5.as57976 .net [137.221.80.33]
0/ 100 = 0% |
7 56ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-2-br01-eqam1.as57976 .net [137.221.65.29]
0/ 100 = 0% |
8 — 100/ 100 =100% 100/ 100 =100% et-0-0-31-pe01-eqam1.as57976 .net [137.221.78.67]
0/ 100 = 0% |
9 49ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157

Trace complete.

winmtr

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| dsldevice.lan - 0 | 118 | 118 | 0 | 0 | 1 | 0 |

| 81.198.8.1 - 0 | 118 | 118 | 1 | 2 | 6 | 2 |

| 195.122.0.162 - 0 | 118 | 118 | 1 | 1 | 6 | 2 |

| 87.110.223.130 - 0 | 118 | 118 | 1 | 1 | 6 | 2 |

| pr01.eqfr5.blizzardonline .net - 0 | 118 | 118 | 46 | 47 | 75 | 47 |

| ae1-br01-eqfr5.as57976 .net - 0 | 118 | 118 | 48 | 53 | 130 | 50 |

| et-0-0-2-br01-eqam1.as57976 .net - 0 | 107 | 107 | 42 | 217 | 4620 | 43 |

| et-0-0-31-pe01-eqam1.as57976 .net - 0 | 118 | 118 | 47 | 48 | 58 | 48 |

| 185.60.112.157 - 0 | 118 | 118 | 48 | 49 | 54 | 49 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider