Disconnection issue

Technical Support
1 2 3 12 Next
Highly Rated
For about a week now, more or less, while playing a ranked match the servers are kicking the players. It has gotten more and more often, yesterday I even saw 5 players getting kicked at the same time. I have already lost 100p due to this issue. This is an embarrassment.
Many SA players have decided not to play ranked matches anymore until this is fixed. On top of that, today my account was blocked for suspicious activity, the reason for that I believe it is because of the constant logins that need to be made after getting constantly kicked.

Please fix the SA servers connection issues.
Thank you for reading.
Hey, Syn!

We are seeing a lot of players in Argentina having issues. We are collecting information on it right now.

I would like for you to collect a Trace Route and a Path Ping and reply to this post with both.
Tracer route:

Traza a la direcci¢n ec2-18-231-9-225.sa-east-1.compute.amazonaws.com [18.231.9.225]
sobre un m ximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Tiempo de espera agotado para esta solicitud.
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 12 ms 16 ms 15 ms 137-161-89-200.fibertel.com.ar [200.89.161.137]
7 11 ms 15 ms 16 ms 150-165-89-200.fibertel.com.ar [200.89.165.150]
8 19 ms 19 ms 14 ms ae6.baires3.bai.seabone.net [185.70.203.22]
9 37 ms 38 ms 37 ms ae7.sanpaolo8.spa.seabone.net [195.22.219.17]
10 39 ms 39 ms 38 ms amazon.sanpaolo8.spa.seabone.net [195.22.219.137]
11 * * * Tiempo de espera agotado para esta solicitud.
12 * * * Tiempo de espera agotado para esta solicitud.
13 * * * Tiempo de espera agotado para esta solicitud.
14 38 ms 37 ms 38 ms 54.240.244.179
15 38 ms 43 ms 43 ms 54.240.244.210
16 39 ms 40 ms 41 ms 54.240.244.223
17 49 ms 47 ms 46 ms 54.240.244.9
18 * * * Tiempo de espera agotado para esta solicitud.
19 * * * Tiempo de espera agotado para esta solicitud.
20 * * * Tiempo de espera agotado para esta solicitud.
21 * * * Tiempo de espera agotado para esta solicitud.
22 * * * Tiempo de espera agotado para esta solicitud.
23 * * * Tiempo de espera agotado para esta solicitud.
24 * * * Tiempo de espera agotado para esta solicitud.
25 * * * Tiempo de espera agotado para esta solicitud.
26 * * * Tiempo de espera agotado para esta solicitud.
27 * * * Tiempo de espera agotado para esta solicitud.
28 * * * Tiempo de espera agotado para esta solicitud.
29 * * * Tiempo de espera agotado para esta solicitud.
30 * * * Tiempo de espera agotado para esta solicitud.

Traza completa.

Path píng

Seguimiento de ruta a ec2-18-231-9-225.sa-east-1.compute.amazonaws.com [18.231.9.225]
sobre un m ximo de 30 saltos:
0 DESKTOP-P8J7HBC [192.168.0.22]
1 192.168.0.1
2 * * *
Procesamiento de estad¡sticas durante 25 segundos...
Origen hasta aqu¡ Este Nodo/V¡nculo
Salto RTT Perdido/Enviado = Pct Perdido/Enviado = Pct Direcci¢n
0 DESKTOP-P8J7HBC [192.168.0.22]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1

Traza completa.
Im having the same issue, ill leave my files here too.

TraceRT

Traza a la direcci¢n ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]
sobre un m ximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 192.168.0.1
3 * * * Tiempo de espera agotado para esta solicitud.
4 * * * Tiempo de espera agotado para esta solicitud.
5 * * * Tiempo de espera agotado para esta solicitud.
6 * * * Tiempo de espera agotado para esta solicitud.
7 * * * Tiempo de espera agotado para esta solicitud.
8 33 ms 33 ms 34 ms 81-161-89-200.fibertel.com.ar [200.89.161.81]
9 23 ms 29 ms 29 ms 86-165-89-200.fibertel.com.ar [200.89.165.86]
10 21 ms 29 ms 29 ms ae5.baires3.bai.seabone.net [185.70.203.20]
11 57 ms 69 ms 81 ms ae7.sanpaolo8.spa.seabone.net [195.22.219.17]
12 93 ms 63 ms 59 ms amazon.sanpaolo8.spa.seabone.net [195.22.219.137]
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
15 * * * Tiempo de espera agotado para esta solicitud.
16 62 ms 59 ms 60 ms 54.240.244.163
17 62 ms 59 ms 59 ms 54.240.244.242
18 64 ms 58 ms 59 ms 54.240.244.249
19 53 ms 64 ms 54 ms 177.72.240.153
20 * * * Tiempo de espera agotado para esta solicitud.
21 * * * Tiempo de espera agotado para esta solicitud.
22 * * * Tiempo de espera agotado para esta solicitud.
23 54 ms 57 ms 59 ms ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]

Traza completa.

Pathping

Seguimiento de ruta a ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]
sobre un m ximo de 30 saltos:
0 Roy-PC [192.168.1.170]
1 192.168.1.1
2 192.168.0.1
3 * * *
Procesamiento de estad¡sticas durante 50 segundos...
Origen hasta aqu¡ Este Nodo/V¡nculo
Salto RTT Perdido/Enviado = Pct Perdido/Enviado = Pct Direcci¢n
0 Roy-PC [192.168.1.170]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1

Traza completa.
I cant even connect to the blizzard app now and it has disconnected me while playing competitive.
I just got kicked from a ranked and wouldnt let me reconnect. It just says PLAY, not REJOIN MATCH and I automatically lost points... pls Blizaard, fix this ASAP!
having the same problem aswell been kicked out and doesn't matter which mode i play
11/12/2017 04:38 PMPosted by Ibaraius
Hey, Syn!

We are seeing a lot of players in Argentina having issues. We are collecting information on it right now.

I would like for you to collect a [url="https://us.battle.net/support/article/7870"]Trace Route[/url] and a [url="https://us.battle.net/support/article/7871"]Path Ping[/url] and reply to this post with both.


Could this also be affecting other Blizzard games? I've played D3 and SC2 during this week and I've noticed lag spikes at some points

Anyways here are my files

Tracert

Tracing route to ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]
over a maximum of 30 hops:

1 9 ms 13 ms 10 ms 10.32.32.1
2 11 ms 9 ms 12 ms 10.242.2.137
3 10 ms 13 ms 23 ms global-crossing-argentina-s-a.xe-0-1-0.ar3.eze1.gblx.net [208.178.195.210]
4 27 ms 13 ms 9 ms xe-0-1-0.ar3.eze1.gblx.net [208.178.195.209]
5 37 ms 40 ms 39 ms ae0-0-40G.ar5.GRU1.gblx.net [67.16.156.78]
6 51 ms 42 ms 40 ms amazon-com.xe-5-2-1.ar4.gru1.gblx.net [64.214.62.142]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 40 ms 43 ms 48 ms 177.72.240.119
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 238 ms 45 ms 51 ms ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]

Trace complete.


Pathping
Tracing route to ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]
over a maximum of 30 hops:
0 GLaDOS [192.168.0.10]
1 10.32.32.1
2 10.242.2.137
3 global-crossing-argentina-s-a.xe-0-1-0.ar3.eze1.gblx.net [208.178.195.210]
4 xe-0-1-0.ar3.eze1.gblx.net [208.178.195.209]
5 ae0-0-40G.ar5.GRU1.gblx.net [67.16.156.78]
6 amazon-com.xe-5-2-1.ar4.gru1.gblx.net [64.214.62.142]
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GLaDOS [192.168.0.10]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 10.32.32.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.242.2.137
0/ 100 = 0% |
3 24ms 0/ 100 = 0% 0/ 100 = 0% global-crossing-argentina-s-a.xe-0-1-0.ar3.eze1.gblx.net [208.178.195.210]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% xe-0-1-0.ar3.eze1.gblx.net [208.178.195.209]
100/ 100 =100% |
5 --- 100/ 100 =100% 0/ 100 = 0% ae0-0-40G.ar5.GRU1.gblx.net [67.16.156.78]
0/ 100 = 0% |
6 --- 100/ 100 =100% 0/ 100 = 0% amazon-com.xe-5-2-1.ar4.gru1.gblx.net [64.214.62.142]

Trace complete.


11/12/2017 05:03 PMPosted by Tsukumi
I cant even connect to the blizzard app now and it has disconnected me while playing competitive.


If I were you, I'd wait until the problems are fixed before playing competitive to prevent bans
Thanks for the files so far, everyone.

Can people from Argentina please collect a WinMTR and post it here, also? Please run it for at least 10 minutes.
Again, thats 100 points lost now...
SolidGround

Stop playing competitive. If you know there is a connection issue, you should stop playing competitive. If you can provide the requested files, it would be helpful.
Im having the same issue. I think it started after the update from yesterday (the one in advance). I must have played between 10 and 15 competitives games since the update and this post, and there was disconections in at least 8 of those games (mines and from other players).
Ive lost around 100 and 150 points because of this, and i will stop playing competitive. Hope you can fix this soon.
Im leaving the data requested here.

TraceRT

Traza a la dirección ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]
sobre un máximo de 30 saltos:

1 <1 ms <1 ms 1 ms hitronhub.home [192.168.0.1]
2 9 ms 7 ms 7 ms 10.95.0.1
3 63 ms 71 ms 69 ms 10.171.0.65
4 71 ms 64 ms 79 ms 10.170.0.13
5 74 ms 77 ms 76 ms xe1-2-2.baires5.bai.seabone.net [195.22.220.62]
6 93 ms 97 ms 84 ms et4-1-0.sanpaolo8.spa.seabone.net [195.22.219.75]
7 100 ms 98 ms 98 ms amazon.sanpaolo8.spa.seabone.net [195.22.219.137]
8 * * * Tiempo de espera agotado para esta solicitud.
9 * * * Tiempo de espera agotado para esta solicitud.
10 * * * Tiempo de espera agotado para esta solicitud.
11 91 ms 90 ms 90 ms 54.240.244.227
12 101 ms 109 ms 106 ms 54.240.244.210
13 91 ms 102 ms 108 ms 54.240.244.217
14 98 ms 103 ms 105 ms 177.72.240.153
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 104 ms 100 ms 95 ms ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]

Traza completa.

Pathping

Seguimiento de ruta a ec2-54-207-107-12.sa-east-1.compute.amazonaws.com [54.207.107.12]
sobre un máximo de 30 saltos:
0 DESKTOP-L4O0QOO.hitronhub.home [192.168.0.13]
1 hitronhub.home [192.168.0.1]
2 10.95.0.1
3 10.171.0.65
4 10.170.0.13
5 xe1-2-2.baires5.bai.seabone.net [195.22.220.62]
6 et4-1-0.sanpaolo8.spa.seabone.net [195.22.219.75]
7 amazon.sanpaolo8.spa.seabone.net [195.22.219.137]
8 * * *
Procesamiento de estadísticas durante 175 segundos...
Origen hasta aquí Este Nodo/Vínculo
Salto RTT Perdido/Enviado = Pct Perdido/Enviado = Pct Dirección
0 DESKTOP-L4O0QOO.hitronhub.home [192.168.0.13]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% hitronhub.home [192.168.0.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 10.95.0.1
0/ 100 = 0% |
3 64ms 0/ 100 = 0% 0/ 100 = 0% 10.171.0.65
0/ 100 = 0% |
4 69ms 0/ 100 = 0% 0/ 100 = 0% 10.170.0.13
1/ 100 = 1% |
5 78ms 2/ 100 = 2% 1/ 100 = 1% xe1-2-2.baires5.bai.seabone.net [195.22.220.62]
0/ 100 = 0% |
6 100ms 1/ 100 = 1% 0/ 100 = 0% et4-1-0.sanpaolo8.spa.seabone.net [195.22.219.75]
99/ 100 = 99% |
7 --- 100/ 100 =100% 0/ 100 = 0% amazon.sanpaolo8.spa.seabone.net [195.22.219.137]

Traza completa

PD: I havent had any issues on the PTR, just in the latin server.
having the same problem except im not from SA. here are mine
Tracing route to 24.105.62.129 over a maximum of 30 hops

1 4 ms 5 ms 5 ms 192.168.2.1
2 32 ms 103 ms 10 ms 10.11.16.105
3 * 8 ms 5 ms 10.178.206.164
4 5 ms 13 ms 7 ms 10.178.206.165
5 30 ms 40 ms 40 ms tcore3x-quebec14_0-4-0-2.net.bell.ca [64.230.87.104]
6 22 ms 28 ms 21 ms tcore4-montreal02_hundredgige2-12-0-1.net.bell.ca [64.230.40.170]
7 26 ms 23 ms 22 ms tcore4-newoyrkaa_hundredgige0-8-0-0.net.bell.ca [64.230.79.150]
8 23 ms 20 ms 22 ms bx7-newyork83_hundredgige0-7-0-0.net.bell.ca [64.230.79.91]
9 25 ms 29 ms 24 ms nyc2-brdr-01.inet.qwest.net [205.171.1.33]
10 * * * Request timed out.
11 18 ms 18 ms 17 ms 65.124.186.34
12 21 ms 20 ms 20 ms ae1-br01-eqny8.blizzardonline.net [137.221.71.33]
13 * * * Request timed out.
14 41 ms 34 ms 46 ms be2-pe02-eqch2.blizzardonline.net [137.221.69.73]
15 * * * Request timed out.
16 40 ms 41 ms 35 ms 24.105.62.129

Trace complete.
0 PersonalPC.home [192.168.2.17]
1 mynetwork.home [192.168.2.1]
2 10.11.16.105
3 10.178.206.164
4 10.178.206.165
5 tcore3x-quebec14_0-4-0-2.net.bell.ca [64.230.87.104]
6 tcore4-montreal02_hundredgige2-12-0-1.net.bell.ca [64.230.40.170]
7 tcore4-newoyrkaa_hundredgige0-8-0-0.net.bell.ca [64.230.79.150]
8 bx7-newyork83_hundredgige0-7-0-0.net.bell.ca [64.230.79.91]
9 nyc2-brdr-01.inet.qwest.net [205.171.1.33]
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PersonalPC.home [192.168.2.17]
0/ 100 = 0% |
1 25ms 0/ 100 = 0% 0/ 100 = 0% mynetwork.home [192.168.2.1]
0/ 100 = 0% |
2 32ms 0/ 100 = 0% 0/ 100 = 0% 10.11.16.105
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 10.178.206.164
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 10.178.206.165
0/ 100 = 0% |
5 38ms 0/ 100 = 0% 0/ 100 = 0% tcore3x-quebec14_0-4-0-2.net.bell.ca [64.230.87.104]
0/ 100 = 0% |
6 45ms 0/ 100 = 0% 0/ 100 = 0% tcore4-montreal02_hundredgige2-12-0-1.net.bell.ca [64.230.40.170]
0/ 100 = 0% |
7 40ms 1/ 100 = 1% 1/ 100 = 1% tcore4-newoyrkaa_hundredgige0-8-0-0.net.bell.ca [64.230.79.150]
0/ 100 = 0% |
8 38ms 0/ 100 = 0% 0/ 100 = 0% bx7-newyork83_hundredgige0-7-0-0.net.bell.ca [64.230.79.91]
0/ 100 = 0% |
9 48ms 0/ 100 = 0% 0/ 100 = 0% nyc2-brdr-01.inet.qwest.net [205.171.1.33]

Trace complete.
Here's my WinMTR file

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.32.32.1 - 16 | 381 | 322 | 9 | 43 | 1223 | 14 |
| 10.242.2.137 - 16 | 381 | 323 | 0 | 48 | 1471 | 10 |
|global-crossing-argentina-s-a.xe-0-1-0.ar3.eze1.gblx.net - 33 | 266 | 179 | 0 | 33 | 654 | 19 |
| xe-0-1-0.ar3.eze1.gblx.net - 59 | 183 | 76 | 0 | 223 | 2965 | 15 |
| ae0-0-40G.ar5.GRU1.gblx.net - 80 | 147 | 30 | 0 | 87 | 951 | 51 |
| amazon-com.xe-5-2-1.ar4.gru1.gblx.net - 91 | 133 | 12 | 0 | 121 | 914 | 44 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| 177.72.240.119 - 97 | 127 | 5 | 0 | 44 | 66 | 38 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 123 | 0 | 0 | 0 | 0 | 0 |
|ec2-54-207-107-12.sa-east-1.compute.amazonaws.com - 1 | 593 | 588 | 37 | 86 | 1373 | 39 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
These are mine

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 404 | 404 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| mail.camoyte.com - 0 | 404 | 404 | 13 | 17 | 25 | 16 |
| 150-165-89-200.fibertel.com.ar - 0 | 404 | 404 | 14 | 19 | 30 | 16 |
| ae5.baires3.bai.seabone.net - 0 | 404 | 404 | 14 | 16 | 44 | 16 |
| ae7.sanpaolo8.spa.seabone.net - 0 | 404 | 404 | 40 | 46 | 177 | 79 |
| amazon.sanpaolo8.spa.seabone.net - 0 | 404 | 404 | 40 | 43 | 87 | 43 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| 54.240.244.161 - 0 | 404 | 404 | 41 | 42 | 68 | 42 |
| 54.240.244.208 - 0 | 404 | 404 | 43 | 50 | 109 | 55 |
| 54.240.244.223 - 0 | 404 | 404 | 43 | 45 | 55 | 46 |
| 54.240.244.11 - 0 | 404 | 404 | 43 | 45 | 58 | 46 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 81 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|

Trace:
Tracing route to ec2-18-231-9-225.sa-east-1.compute.amazonaws.com [18.231.9.225]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 18 ms 15 ms 15 ms mail.camoyte.com [200.89.166.25]
7 19 ms 15 ms 15 ms 150-165-89-200.fibertel.com.ar [200.89.165.150]
8 16 ms 15 ms 16 ms ae5.baires3.bai.seabone.net [185.70.203.20]
9 45 ms 44 ms 44 ms ae7.sanpaolo8.spa.seabone.net [195.22.219.17]
10 41 ms 41 ms 41 ms amazon.sanpaolo8.spa.seabone.net [195.22.219.137]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 43 ms 43 ms 41 ms 54.240.244.161
15 46 ms 54 ms 49 ms 54.240.244.208
16 47 ms 45 ms 48 ms 54.240.244.223
17 44 ms 44 ms 46 ms 54.240.244.11
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.

pathping:

Tracing route to ec2-18-231-9-225.sa-east-1.compute.amazonaws.com [18.231.9.225]
over a maximum of 30 hops:
0 Fran.fibertel.com.ar [192.168.0.3]
1 192.168.0.1
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Fran.fibertel.com.ar [192.168.0.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1

Trace complete.
11/12/2017 05:25 PMPosted by Ibaraius
Thanks for the files so far, everyone.

Can people from Argentina please collect a [url="https://us.battle.net/support/en/article/27780"]WinMTR[/url] and post it here, also? Please run it for at least 10 minutes.


Here's the WinMTR
I ran it for 10 minutes, got disconnected from the server once while running it.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 587 | 587 | 0 | 0 | 4 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| 137-161-89-200.fibertel.com.ar - 0 | 587 | 587 | 5 | 19 | 258 | 10 |
| 150-165-89-200.fibertel.com.ar - 0 | 587 | 587 | 6 | 19 | 262 | 12 |
| ae6.baires3.bai.seabone.net - 0 | 587 | 587 | 10 | 19 | 247 | 18 |
| ae7.sanpaolo8.spa.seabone.net - 0 | 587 | 587 | 34 | 43 | 279 | 39 |
| amazon.sanpaolo8.spa.seabone.net - 0 | 587 | 587 | 36 | 44 | 284 | 37 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| 54.240.244.179 - 0 | 587 | 587 | 32 | 43 | 284 | 38 |
| 54.240.244.210 - 0 | 587 | 587 | 38 | 50 | 293 | 43 |
| 54.240.244.223 - 0 | 587 | 587 | 35 | 46 | 285 | 41 |
| 54.240.244.9 - 0 | 587 | 587 | 37 | 45 | 285 | 40 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Thank everyone for posting their MTRs and Traceroutes. While I am not one of the Support Agents, I am reading the results confident to say there is something screwy with the Internet node after the one Amazon Web Services IP. So please if you live in the South Amercian region (particularly Argentina), keep testing and posting results here.

As always, avoid competitive play if you are seeing these issues, Blizzard will not restore any lost SR or reverse any penalty per to competitive rules.
11/12/2017 05:32 PMPosted by Ibaraius
SolidGround

Stop playing competitive. If you know there is a connection issue, you should stop playing competitive. If you can provide the requested files, it would be helpful.


When the issue is considered fixed, could some kind of announcement be made public? That way all the players that aren't currently playing can go back to the game.

Join the Conversation

Return to Forum