hola buenas aqui desde argentina- buenos aires con el mismo problema arriba de 300 ms
texto en negrita
hola buenas aqui desde argentina- buenos aires con el mismo problema arriba de 300 ms
texto en negrita
Buenos dias gente. Exactamente como les pasa a los otros, hace 4 o 5 dias (no recuerdo exactamente), comence a tener latencia alta en home y world.
Pase de 160 latencia a 300 constantemente.
Podria algun blue confirmar si hace unos dias hicieron algun cambio que pudiera afectar los reinos de latinoamerica?
Mi IPS es CLARO argentina.
Buenas, me sumo al reclamo
Estamos teniendo ping superior a los 300MS cuando lo normal era 150, algo cambio en las rutas internacionales despues de brasil la cual nos hace pasar por bloques de IP 129.250.4.x donde se encuentra el problema, estos equipos tienen registro PTR de Japon pero el bloque esta asignado a NTT Comunications, una empresa asiática de Tier1 que al parecer llego a america
Blizz, pueden hacer usedes el reclamo a este proveedor?
gente el problema es para todos el mismo y es que la conexion nos pasa por japon Tokio antes de llegar a usa (blizz), no es culpa de nuestra isp, pero bueno no se hacen cargo que cambiaron algo desde el ultimo parche, tocara seguir usando vpn
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.100.1 | 0 | 93 | 93 | 0 | 0 | 3 | 0 |
186.182.228.2 | 0 | 93 | 93 | 2 | 4 | 10 | 4 |
10.2.200.190 | 0 | 93 | 93 | 4 | 6 | 10 | 6 |
10.2.201.117 | 0 | 93 | 93 | 3 | 5 | 14 | 5 |
10.2.186.121 | 0 | 93 | 93 | 5 | 9 | 18 | 5 |
be4-2-cf223-br-04-bsas.claro.com.ar | 0 | 93 | 93 | 6 | 9 | 14 | 10 |
ae0-1006.baires3.bai.seabone.net | 0 | 93 | 93 | 5 | 7 | 26 | 7 |
et0-0-2.sanpaolo8.spa.seabone.net | 0 | 93 | 93 | 31 | 37 | 91 | 42 |
ntt-verio.sanpaolo8.spa.seabone.net | 0 | 93 | 93 | 136 | 137 | 141 | 138 |
ae-8.r24.nycmny01.us.bb.gin.ntt.net | 0 | 93 | 93 | 151 | 153 | 168 | 152 |
ae-4.r22.sttlwa01.us.bb.gin.ntt.net | 2 | 89 | 88 | 216 | 217 | 224 | 217 |
ae-13.r30.tokyjp05.jp.bb.gin.ntt.net | 0 | 92 | 92 | 301 | 302 | 323 | 302 |
ae-2.r01.tokyjp08.jp.bb.gin.ntt.net | 0 | 92 | 92 | 287 | 288 | 292 | 289 |
ae-2.a00.tokyjp03.jp.bb.gin.ntt.net | 0 | 92 | 92 | 301 | 304 | 336 | 304 |
61.213.179.114 | 0 | 92 | 92 | 298 | 303 | 393 | 301 |
et-0-0-48-br01-eqty2.blizzardonline.net | 0 | 92 | 92 | 298 | 302 | 359 | 300 |
xe-0-0-0-1-br01-eqla1.as57976.net | 0 | 92 | 92 | 296 | 322 | 492 | 298 |
et-0-0-2-br01-swlv10.as57976.net | 0 | 92 | 92 | 299 | 306 | 619 | 302 |
et-0-0-31-pe01-swlv10.as57976.net | 0 | 92 | 92 | 305 | 310 | 384 | 306 |
137.221.105.2 | 0 | 92 | 92 | 296 | 298 | 301 | 298 |
No se como blizz quiere que hagamos el reclamo a un ISP de Tier1, y muchos menos que un proveedor hogareño nos escuche por problemas de tier 1…
es siempre la misma historia todos los años, un ñato le pifia un ruteo y la parimos durante meses hasta que alguno lo arregla
gran verdad veremos que pasa cuanto tiempo lleva solucionarlo
hay soluciones ya… como tanto
Dale blizzard, media pila. Esto no es un problema del ISP, le sucede algo similar a varia personas por el resto del mundo.
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.0.1 | 96 | 23 | 1 | 2 | 2 | 2 | 2 |
No response from host | 100 | 23 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 23 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 23 | 0 | 0 | 0 | 0 | 0 |
86-165-89-200.fibertel.com.ar | 0 | 111 | 111 | 8 | 14 | 36 | 11 |
ae6.baires3.bai.seabone.net | 0 | 111 | 111 | 7 | 10 | 21 | 10 |
et0-0-5.sanpaolo8.spa.seabone.net | 0 | 111 | 111 | 35 | 54 | 219 | 219 |
ntt-verio.sanpaolo8.spa.seabone.net | 0 | 111 | 111 | 35 | 37 | 44 | 37 |
ae-8.r24.nycmny01.us.bb.gin.ntt.net | 0 | 111 | 111 | 158 | 161 | 172 | 161 |
ae-4.r22.sttlwa01.us.bb.gin.ntt.net | 0 | 111 | 111 | 206 | 210 | 230 | 208 |
ae-13.r30.tokyjp05.jp.bb.gin.ntt.net | 0 | 111 | 111 | 297 | 301 | 316 | 299 |
ae-2.r00.tokyjp08.jp.bb.gin.ntt.net | 0 | 111 | 111 | 290 | 293 | 300 | 292 |
ae-1.a00.tokyjp03.jp.bb.gin.ntt.net | 0 | 111 | 111 | 302 | 309 | 334 | 307 |
61.213.179.114 | 0 | 111 | 111 | 312 | 320 | 396 | 317 |
et-0-0-48-br01-eqty2.blizzardonline.net | 1 | 107 | 106 | 316 | 321 | 417 | 318 |
xe-0-0-0-1-br01-eqla1.as57976.net | 0 | 111 | 111 | 313 | 341 | 546 | 315 |
et-0-0-2-br01-swlv10.as57976.net | 0 | 111 | 111 | 306 | 313 | 397 | 343 |
137.221.65.133 | 0 | 111 | 111 | 303 | 311 | 399 | 307 |
be1-pe01-eqch2.as57976.net | 0 | 111 | 111 | 303 | 305 | 316 | 305 |
chi-eqch2-ia-bons-02.as57976.net | 0 | 111 | 111 | 308 | 311 | 322 | 312 |
24.105.62.129 | 0 | 111 | 111 | 309 | 312 | 326 | 311 |
En si a mi me saca cada que entro, y no es mi addoms todos están actualizados, y ni mi moden
Buenas, yo también vengo con problemas desde la salida del parche 8.2, pase de jugar con 170-180 a 500+ todo el tiempo, hasta el punto que el servidor me tira en promedio cada 15min.
País: Argentina
Internet: Telecentro
Hola, tengo el mismo problema. Solía jugar entre 160 y 180 como todo latinoamericano, pero ahora anda desde 300ms hacia arriba (me ha subido hasta 5000ms). Soy de Chile y mi ISP es GTD Manquehue, pero, en esta ocasión, aquello no es muy relevante. El problema es el ruteo que se está haciendo entre medio del servidor de Blizzard y mi Net. Para testear, juego literalmente cualquier otra cosa con servidores estadounidenses y no hay problema, así que al ser asunto suyo espero que puedan solucionarlo a la brevedad.
Veo que no soy el único afectado así que decido exponer aquí mi situación, en vez de crear un hilo nuevo.
A continuación, adjunto mis tracert y WinMTR para contribuir a la investigación (¡¿se está haciendo?!).
Para la IP 24.105.62.129 (US Central):
Tracert:
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms static.190.215.168.1.gtdinternet. com [190.215.168.1]
3 2 ms 1 ms 1 ms 192.168.50.7
4 2 ms 1 ms 1 ms 192.168.50.6
5 * * * Request timed out.
6 106 ms 106 ms 110 ms ae2.santiago1.san.seabone. net [195.22.221.16]
7 140 ms 130 ms 130 ms et0-0-2.sanpaolo8.spa.seabone. net [195.22.219.3]
8 129 ms 128 ms 128 ms ntt-verio.sanpaolo8.spa.seabone. net [149.3.181.65]
9 163 ms 155 ms 155 ms ae-8.r24.nycmny01.us.bb.gin.ntt. net [129.250.2.12]
10 * 204 ms * ae-4.r22.sttlwa01.us.bb.gin.ntt. net [129.250.4.13]
11 299 ms 298 ms 303 ms ae-13.r30.tokyjp05.jp.bb.gin.ntt. net [129.250.4.143]
12 313 ms 314 ms 314 ms ae-2.r01.tokyjp08.jp.bb.gin.ntt. net [129.250.6.131]
13 320 ms 318 ms 334 ms ae-2.a00.tokyjp03.jp.bb.gin.ntt. net [129.250.5.55]
14 313 ms 314 ms 316 ms 61.213.179.114
15 298 ms 297 ms 298 ms et-0-0-48-br01-eqty2.blizzardonline. net [137.221.81.33]
16 314 ms 455 ms 439 ms xe-0-0-0-1-br01-eqla1.as57976. net [137.221.65.56]
17 299 ms 298 ms 297 ms et-0-0-2-br01-swlv10.as57976. net [137.221.65.69]
18 308 ms 305 ms 305 ms 137.221.65.133
19 295 ms 295 ms 295 ms be1-pe01-eqch2.as57976. net [137.221.69.67]
20 318 ms 319 ms 320 ms chi-eqch2-ia-bons-02.as57976. net [137.221.66.11]
21 296 ms 296 ms 296 ms 24.105.62.129
Trace complete.
WinMTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 226 | 226 | 0 | 0 | 5 | 0 |
| static.190.215.168.1.gtdinternet. com - 0 | 225 | 225 | 1 | 12 | 2174 | 1 |
| 192.168.50.7 - 0 | 226 | 226 | 1 | 1 | 7 | 1 |
| 192.168.50.6 - 0 | 226 | 226 | 1 | 3 | 67 | 1 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| ae2.santiago1.san.seabone. net - 0 | 226 | 226 | 106 | 107 | 175 | 106 |
| et0-0-2.sanpaolo8.spa.seabone. net - 0 | 226 | 226 | 129 | 134 | 214 | 131 |
| ntt-verio.sanpaolo8.spa.seabone. net - 0 | 226 | 226 | 128 | 128 | 175 | 128 |
| ae-8.r24.nycmny01.us.bb.gin.ntt. net - 0 | 226 | 226 | 154 | 156 | 213 | 155 |
| ae-4.r22.sttlwa01.us.bb.gin.ntt. net - 1 | 222 | 221 | 0 | 204 | 213 | 204 |
| ae-13.r30.tokyjp05.jp.bb.gin.ntt. net - 0 | 226 | 226 | 297 | 298 | 318 | 304 |
| ae-2.r01.tokyjp08.jp.bb.gin.ntt. net - 0 | 226 | 226 | 313 | 313 | 317 | 313 |
| ae-2.a00.tokyjp03.jp.bb.gin.ntt. net - 0 | 226 | 226 | 318 | 320 | 348 | 319 |
| 61.213.179.114 - 0 | 226 | 226 | 313 | 319 | 391 | 313 |
| et-0-0-48-br01-eqty2.blizzardonline. net - 0 | 226 | 226 | 297 | 303 | 668 | 298 |
| xe-0-0-0-1-br01-eqla1.as57976. net - 5 | 189 | 181 | 294 | 372 | 3518 | 295 |
| et-0-0-2-br01-swlv10.as57976. net - 1 | 212 | 210 | 297 | 346 | 3960 | 298 |
| 137.221.65.133 - 0 | 226 | 226 | 304 | 312 | 611 | 314 |
| be1-pe01-eqch2.as57976. net - 0 | 226 | 226 | 294 | 295 | 299 | 295 |
| chi-eqch2-ia-bons-02.as57976. net - 0 | 226 | 226 | 317 | 318 | 333 | 318 |
| 24.105.62.129 - 0 | 226 | 226 | 295 | 296 | 302 | 296 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Y para la IP 137.221.105.2 (US West):
Tracert:
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms static.190.215.168.1.gtdinternet. com [190.215.168.1]
3 1 ms 1 ms 1 ms 192.168.50.13
4 4 ms 2 ms 2 ms 192.168.50.12
5 * * * Request timed out.
6 1 ms 1 ms 2 ms ci1.ae1.ci2.gtdinternet. com [190.196.126.222]
7 106 ms 112 ms 106 ms ae2.santiago1.san.seabone. net [195.22.221.16]
8 126 ms 126 ms 127 ms et0-0-5.sanpaolo8.spa.seabone. net [195.22.219.17]
9 129 ms 129 ms 129 ms ntt-verio.sanpaolo8.spa.seabone. net [149.3.181.65]
10 155 ms 155 ms 155 ms ae-8.r24.nycmny01.us.bb.gin.ntt. net [129.250.2.12]
11 202 ms 204 ms 203 ms ae-4.r22.sttlwa01.us.bb.gin.ntt. net [129.250.4.13]
12 297 ms 296 ms 299 ms ae-13.r30.tokyjp05.jp.bb.gin.ntt. net [129.250.4.143]
13 295 ms 294 ms 295 ms ae-2.r00.tokyjp08.jp.bb.gin.ntt. net [129.250.6.127]
14 301 ms 296 ms 300 ms ae-1.a00.tokyjp03.jp.bb.gin.ntt. net [129.250.5.51]
15 312 ms 312 ms 312 ms 61.213.179.114
16 289 ms 289 ms 289 ms et-0-0-48-br01-eqty2.blizzardonline. net [137.221.81.33]
17 286 ms 286 ms 286 ms xe-0-0-0-1-br01-eqla1.as57976. net [137.221.65.56]
18 297 ms 297 ms 297 ms et-0-0-2-br01-swlv10.as57976. net [137.221.65.69]
19 289 ms 289 ms 289 ms et-0-0-31-pe01-swlv10.as57976. net [137.221.83.67]
20 286 ms 286 ms 286 ms 137.221.105.2
Trace complete.
WinMTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 219 | 219 | 0 | 0 | 5 | 0 |
| static.190.215.168.1.gtdinternet. com - 0 | 219 | 219 | 1 | 1 | 8 | 1 |
| 192.168.50.13 - 1 | 215 | 214 | 1 | 1 | 9 | 1 |
| 192.168.50.12 - 0 | 219 | 219 | 1 | 3 | 89 | 1 |
| No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 |
| ci1.ae1.ci2.gtdinternet. com - 0 | 219 | 219 | 1 | 3 | 84 | 1 |
| ae2.santiago1.san.seabone. net - 1 | 215 | 214 | 106 | 107 | 127 | 107 |
| et0-0-5.sanpaolo8.spa.seabone. net - 0 | 219 | 219 | 126 | 130 | 238 | 126 |
| ntt-verio.sanpaolo8.spa.seabone. net - 1 | 211 | 209 | 128 | 128 | 136 | 129 |
| ae-8.r24.nycmny01.us.bb.gin.ntt. net - 0 | 219 | 219 | 154 | 156 | 179 | 155 |
| ae-4.r22.sttlwa01.us.bb.gin.ntt. net - 0 | 219 | 219 | 202 | 203 | 215 | 203 |
| ae-13.r30.tokyjp05.jp.bb.gin.ntt. net - 0 | 219 | 219 | 296 | 297 | 316 | 296 |
| ae-2.r00.tokyjp08.jp.bb.gin.ntt. net - 0 | 219 | 219 | 294 | 295 | 303 | 294 |
| ae-1.a00.tokyjp03.jp.bb.gin.ntt. net - 0 | 219 | 219 | 295 | 298 | 340 | 296 |
| 61.213.179.114 - 0 | 219 | 219 | 312 | 318 | 455 | 347 |
| et-0-0-48-br01-eqty2.blizzardonline. net - 0 | 219 | 219 | 288 | 299 | 526 | 290 |
| xe-0-0-0-1-br01-eqla1.as57976. net - 12 | 138 | 122 | 285 | 578 | 3739 | 286 |
| et-0-0-2-br01-swlv10.as57976. net - 3 | 193 | 188 | 297 | 373 | 1979 | 297 |
| et-0-0-31-pe01-swlv10.as57976. net - 0 | 219 | 219 | 288 | 292 | 360 | 300 |
| 137.221.105.2 - 0 | 219 | 219 | 285 | 285 | 291 | 285 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Eso es todo. Soluciónenlo, por favor.
Buenas, como todos vienen diciendo, me da desde hace unos dias un ping elevado, el cual venia estando entre los 120 y los 180; y ahora ya el minimo es de 300, y se hace imposible hacer algunas cosas.
Soy de Cordoba, Argentina y mi proveedor es Fibertel.
Aca dejo el WinMTR de 24.105.62.129
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
No response from host | 100 | 61 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 61 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 61 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 61 | 0 | 0 | 0 | 0 | 0 |
209-165-89-200.fibertel.com.ar | 0 | 305 | 305 | 21 | 29 | 201 | 25 |
222-165-89-200.fibertel.com.ar | 0 | 305 | 305 | 20 | 34 | 202 | 30 |
249-165-89-200.fibertel.com.ar | 0 | 305 | 305 | 17 | 28 | 202 | 31 |
2-165-89-200.fibertel.com.ar | 0 | 305 | 305 | 17 | 30 | 201 | 25 |
86-165-89-200.fibertel.com.ar | 0 | 305 | 305 | 18 | 34 | 238 | 34 |
ae6.baires3.bai.seabone.net | 0 | 305 | 305 | 17 | 28 | 205 | 35 |
et0-0-5.sanpaolo8.spa.seabone.net | 0 | 305 | 305 | 48 | 77 | 353 | 59 |
ntt-verio.sanpaolo8.spa.seabone.net | 0 | 305 | 305 | 49 | 57 | 229 | 55 |
ae-8.r24.nycmny01.us.bb.gin.ntt.net | 0 | 305 | 305 | 174 | 187 | 358 | 175 |
ae-4.r22.sttlwa01.us.bb.gin.ntt.net | 2 | 285 | 280 | 0 | 224 | 482 | 216 |
ae-13.r30.tokyjp05.jp.bb.gin.ntt.net | 1 | 301 | 300 | 308 | 324 | 544 | 309 |
ae-2.r01.tokyjp08.jp.bb.gin.ntt.net | 0 | 305 | 305 | 325 | 338 | 656 | 327 |
ae-2.a00.tokyjp03.jp.bb.gin.ntt.net | 0 | 305 | 305 | 299 | 316 | 516 | 301 |
61.213.179.114 | 0 | 305 | 305 | 320 | 339 | 657 | 323 |
et-0-0-48-br01-eqty2.blizzardonline.net | 0 | 305 | 305 | 319 | 338 | 656 | 329 |
xe-0-0-0-1-br01-eqla1.as57976.net | 3 | 267 | 259 | 313 | 421 | 2639 | 319 |
et-0-0-2-br01-swlv10.as57976.net | 1 | 286 | 284 | 324 | 408 | 3741 | 408 |
137.221.65.133 | 11 | 204 | 183 | 319 | 501 | 4963 | 321 |
be1-pe01-eqch2.as57976.net | 0 | 305 | 305 | 320 | 335 | 661 | 326 |
chi-eqch2-ia-bons-02.as57976.net | 0 | 305 | 305 | 326 | 339 | 658 | 336 |
24.105.62.129 | 0 | 305 | 305 | 324 | 339 | 658 | 330 |
Aqui dejo el WinMtr de la 137.221.105.2
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
No response from host | 100 | 62 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 62 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 62 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 62 | 0 | 0 | 0 | 0 | 0 |
209-165-89-200.fibertel.com.ar | 0 | 309 | 309 | 18 | 28 | 143 | 22 |
222-165-89-200.fibertel.com.ar | 0 | 309 | 309 | 19 | 32 | 149 | 30 |
No response from host | 100 | 62 | 0 | 0 | 0 | 0 | 0 |
ae0-300G.ar5.MIA1.gblx.net | 1 | 305 | 304 | 138 | 148 | 284 | 138 |
No response from host | 100 | 62 | 0 | 0 | 0 | 0 | 0 |
No response from host | 100 | 62 | 0 | 0 | 0 | 0 | 0 |
BLIZZARD-EN.ear2.Miami1.Level3.net | 0 | 309 | 309 | 141 | 155 | 313 | 141 |
ae1-br01-eqmi2.as57976.net | 0 | 309 | 309 | 206 | 221 | 337 | 214 |
xe-0-0-1-1-br01-eqda6.as57976.net | 1 | 305 | 304 | 213 | 226 | 394 | 229 |
et-0-0-2-br02-swlv10.as57976.net | 0 | 309 | 309 | 216 | 230 | 396 | 218 |
et-0-0-67-pe02-swlv10.as57976.net | 0 | 309 | 309 | 216 | 228 | 355 | 218 |
las-swlv10-ia-bons-04.as57976.net | 0 | 309 | 309 | 208 | 220 | 339 | 210 |
137.221.105.2 | 0 | 309 | 309 | 205 | 216 | 342 | 205 |
Mismo problema relag Peru Movistar
Aqui dejo el WinMTR de 24.105.62.129 El mismo problema que todos, los paquetes se enrutan por tokyo.
Proveedor: Claro
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 294 | 294 | 0 | 0 | 1 | 0 |
| host1.181-239-208.telmex.net.ar - 0 | 293 | 293 | 1 | 2 | 6 | 3 |
| 10.2.201.93 - 0 | 294 | 294 | 23 | 24 | 27 | 23 |
| 10.2.2.9 - 0 | 294 | 294 | 23 | 26 | 43 | 25 |
| 10.2.201.133 - 0 | 294 | 294 | 24 | 27 | 47 | 26 |
| 10.2.187.173 - 0 | 293 | 293 | 21 | 27 | 41 | 32 |
| be4-2-cf223-br-04-bsas.claro.com.ar - 0 | 294 | 294 | 24 | 29 | 38 | 26 |
| -ae0-1006.baires3.bai.seabone.net - 0 | 293 | 293 | 21 | 23 | 60 | 23 |
| -et11-1-0.sanpaolo8.spa.seabone.net - 0 | 294 | 294 | 50 | 52 | 79 | 54 |
| -ntt-verio.sanpaolo8.spa.seabone.net - 0 | 293 | 293 | 155 | 156 | 161 | 157 |
| -ae-8.r24.nycmny01.us.bb.gin.ntt.net - 0 | 293 | 293 | 163 | 165 | 180 | 165 |
| -ae-4.r22.sttlwa01.us.bb.gin.ntt.net - 1 | 286 | 284 | 231 | 234 | 246 | 235 |
| -ae-13.r30.tokyjp05.jp.bb.gin.ntt.net - 0 | 293 | 293 | 322 | 325 | 341 | 324 |
| -ae-2.r01.tokyjp08.jp.bb.gin.ntt.net - 0 | 294 | 294 | 317 | 318 | 322 | 319 |
| -ae-2.a00.tokyjp03.jp.bb.gin.ntt.net - 0 | 293 | 293 | 309 | 313 | 341 | 310 |
| 61.213.179.114 - 0 | 293 | 293 | 308 | 316 | 491 | 308 |
| -et-0-0-48-br01-eqty2.blizzardonline.net - 0 | 294 | 294 | 318 | 326 | 463 | 320 |
| -xe-0-0-0-1-br01-eqla1.as57976.net - 0 | 288 | 288 | 322 | 407 | 2958 | 2395 |
| -et-0-0-2-br01-swlv10.as57976.net - 0 | 293 | 293 | 318 | 322 | 393 | 321 |
| 137.221.65.133 - 0 | 293 | 293 | 321 | 346 | 2859 | 2859 |
| -be1-pe01-eqch2.as57976.net - 0 | 294 | 294 | 316 | 318 | 323 | 319 |
| 24.105.62.129 - 0 | 293 | 293 | 318 | 320 | 323 | 320 |
|________________________________________________|______|______|______|______|______|______|
Buenas, mismo problema en chile, tengo 300 de ping y normalmente juego a 180, mi proveedor es Telefonica del sur (GTD) 200mb fibra optica, ya probe en otros juegos y el problema se presenta solo en wow
WinMTR 24.105.62.129
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.1.254 | 0 | 7 | 7 | 0 | 0 | 1 | 0 |
reverso.181.226.82.operaciones.gtdinternet.com | 0 | 7 | 7 | 1 | 1 | 2 | 2 |
192.168.4.53 | 34 | 3 | 2 | 0 | 16 | 16 | 16 |
192.168.4.54 | 0 | 7 | 7 | 15 | 21 | 57 | 15 |
No response from host | 100 | 1 | 0 | 0 | 0 | 0 | 0 |
ci1.ae1.ci2.gtdinternet.com | 0 | 7 | 7 | 16 | 16 | 16 | 16 |
ae2.santiago1.san.seabone.net | 0 | 7 | 7 | 121 | 121 | 122 | 121 |
et0-0-5.sanpaolo8.spa.seabone.net | 0 | 7 | 7 | 145 | 146 | 151 | 145 |
ntt-verio.sanpaolo8.spa.seabone.net | 0 | 7 | 7 | 150 | 150 | 150 | 150 |
ae-8.r24.nycmny01.us.bb.gin.ntt.net | 0 | 7 | 7 | 153 | 156 | 170 | 153 |
ae-4.r22.sttlwa01.us.bb.gin.ntt.net | 34 | 3 | 2 | 0 | 195 | 196 | 195 |
ae-13.r30.tokyjp05.jp.bb.gin.ntt.net | 0 | 7 | 7 | 281 | 281 | 282 | 281 |
ae-2.r01.tokyjp08.jp.bb.gin.ntt.net | 0 | 7 | 7 | 282 | 282 | 283 | 283 |
ae-2.a00.tokyjp03.jp.bb.gin.ntt.net | 0 | 7 | 7 | 282 | 283 | 288 | 282 |
61.213.179.114 | 0 | 7 | 7 | 282 | 282 | 285 | 283 |
et-0-0-48-br01-eqty2.blizzardonline.net | 0 | 6 | 6 | 308 | 389 | 787 | 787 |
No response from host | 100 | 1 | 0 | 0 | 0 | 0 | 0 |
et-0-0-2-br01-swlv10.as57976.net | 0 | 5 | 5 | 305 | 446 | 1014 | 1014 |
137.221.65.133 | 0 | 7 | 7 | 305 | 305 | 306 | 305 |
be1-pe01-eqch2.as57976.net | 0 | 7 | 7 | 308 | 308 | 309 | 308 |
24.105.62.129 | 0 | 7 | 7 | 305 | 305 | 306 | 305 |
WinMTR 137.221.105.2
WinMTR Statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.1.254 | 0 | 5 | 5 | 0 | 0 | 0 | 0 |
reverso.181.226.82.operaciones.gtdinternet.com | 0 | 5 | 5 | 1 | 1 | 1 | 1 |
192.168.4.53 | 50 | 2 | 1 | 0 | 15 | 15 | 15 |
192.168.4.54 | 0 | 5 | 5 | 15 | 15 | 16 | 15 |
No response from host | 100 | 1 | 0 | 0 | 0 | 0 | 0 |
ci1.ae1.ci2.gtdinternet.com | 0 | 5 | 5 | 16 | 16 | 16 | 16 |
ae2.santiago1.san.seabone.net | 0 | 5 | 5 | 121 | 121 | 122 | 122 |
et10-0-5.sanpaolo8.spa.seabone.net | 0 | 5 | 5 | 145 | 145 | 146 | 146 |
ntt-verio.sanpaolo8.spa.seabone.net | 0 | 5 | 5 | 150 | 150 | 151 | 150 |
ae-8.r24.nycmny01.us.bb.gin.ntt.net | 0 | 5 | 5 | 154 | 154 | 155 | 155 |
ae-4.r22.sttlwa01.us.bb.gin.ntt.net | 0 | 5 | 5 | 194 | 196 | 199 | 195 |
ae-13.r30.tokyjp05.jp.bb.gin.ntt.net | 0 | 5 | 5 | 281 | 281 | 282 | 282 |
ae-2.r01.tokyjp08.jp.bb.gin.ntt.net | 0 | 5 | 5 | 281 | 281 | 282 | 282 |
ae-2.a00.tokyjp03.jp.bb.gin.ntt.net | 0 | 5 | 5 | 283 | 286 | 298 | 283 |
61.213.179.114 | 0 | 5 | 5 | 281 | 281 | 282 | 282 |
et-0-0-48-br01-eqty2.blizzardonline.net | 0 | 5 | 5 | 299 | 303 | 310 | 310 |
xe-0-0-0-1-br01-eqla1.as57976.net | 0 | 5 | 5 | 296 | 331 | 443 | 296 |
et-0-0-2-br01-swlv10.as57976.net | 0 | 5 | 5 | 291 | 292 | 294 | 294 |
et-0-0-31-pe01-swlv10.as57976.net | 0 | 5 | 5 | 299 | 299 | 300 | 300 |
las-swlv10-ia-bons-02.as57976.net | 0 | 5 | 5 | 299 | 299 | 300 | 299 |
137.221.105.2 | 0 | 5 | 5 | 299 | 299 | 300 | 299 |
Espero se solucione pronto por que ya es injugable esto
saludos.
A mi me subio de 170 a 320 hace 6 dias.
Cuando hago ping a diferentes paginas tengo menos de 10ms de respuesta igual que siempre. Y no se pierden paquetes.
No se que paso en el medio, pero no son los provedores de internet.
Si, me pasa igual. Abrir el ticket es engorroso y solo trae respuestas genericas.
Es muy simple:
-Solo pasa en WOW, los otros juegos funcionan como de costumbre.
-Sucede independientemente del proveedor de internet.
-No es solo en Argentina.
Conclusion: Es un defecto de Blizzard. Cualquier testeo es solo para perder tiempo mientras lo solucionan. No se gasten.
Todavía no se soluciona, pensé que con el mantenimiento de hoy iban a arreglar el ruteo
Acá les dejo mis pruebas realizadas con la herramienta de Battlenet Looking Glass.
PING:
PING 201.212.158.3 (201.212.158.3) 56(84) bytes of data.
64 bytes from 201.212.158.3: icmp_seq=1 ttl=41 time=289 ms
64 bytes from 201.212.158.3: icmp_seq=2 ttl=41 time=289 ms
64 bytes from 201.212.158.3: icmp_seq=3 ttl=41 time=288 ms
64 bytes from 201.212.158.3: icmp_seq=4 ttl=41 time=285 ms
--- 201.212.158.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 285.869/288.469/289.825/1.649 ms
22/07/2019 16:25:16 UTC
--------------------
PING:
PING 201.212.158.3 (201.212.158.3) 56(84) bytes of data.
64 bytes from 201.212.158.3: icmp_seq=1 ttl=41 time=285 ms
64 bytes from 201.212.158.3: icmp_seq=2 ttl=41 time=283 ms
64 bytes from 201.212.158.3: icmp_seq=3 ttl=41 time=293 ms
64 bytes from 201.212.158.3: icmp_seq=4 ttl=41 time=286 ms
--- 201.212.158.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 283.725/287.302/293.203/3.567 ms
22/07/2019 16:25:16 UTC
--------------------
TRACEROUTE:
traceroute to 201.212.158.3 (201.212.158.3), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.512 ms 0.525 ms 0.521 ms
2 24.105.18.131 (24.105.18.131) 0.871 ms 0.878 ms 0.902 ms
3 137.221.105.16 (137.221.105.16) 0.823 ms 0.877 ms 0.992 ms
4 137.221.66.18 (137.221.66.18) 1.166 ms 1.369 ms 1.476 ms
5 137.221.83.66 (137.221.83.66) 34.559 ms 34.595 ms 34.606 ms
6 137.221.65.68 (137.221.65.68) 217.423 ms 215.740 ms 215.745 ms
7 137.221.68.32 (137.221.68.32) 8.816 ms 8.862 ms 8.498 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 8.564 ms 8.575 ms 8.242 ms
9 * * *
10 190.216.88.2 (190.216.88.2) 278.724 ms 278.035 ms 278.066 ms
11 149-165-89-200.fibertel.com.ar (200.89.165.149) 275.768 ms 275.923 ms 275.954 ms
12 162-160-89-200.fibertel.com.ar (200.89.160.162) 276.483 ms 276.617 ms 276.753 ms
13 * * *
14 * * *
15 201-212-158-3.cab.prima.net.ar (201.212.158.3) 287.123 ms 287.151 ms 286.653 ms
22/07/2019 16:25:16 UTC
--------------------
TRACEROUTE:
traceroute to 201.212.158.3 (201.212.158.3), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.472 ms 0.455 ms 0.442 ms
2 24.105.18.131 (24.105.18.131) 1.741 ms 1.742 ms 1.744 ms
3 137.221.105.16 (137.221.105.16) 1.693 ms 1.696 ms 1.696 ms
4 137.221.66.18 (137.221.66.18) 1.655 ms 1.671 ms 1.686 ms
5 137.221.83.66 (137.221.83.66) 1.686 ms 1.686 ms 1.687 ms
6 137.221.65.68 (137.221.65.68) 43.171 ms 41.286 ms 41.266 ms
7 137.221.68.32 (137.221.68.32) 6.744 ms 6.722 ms 6.711 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 6.181 ms 6.202 ms 6.202 ms
9 * * *
10 190.216.88.2 (190.216.88.2) 272.265 ms 272.290 ms 278.212 ms
11 149-165-89-200.fibertel.com.ar (200.89.165.149) 275.949 ms 275.894 ms 275.873 ms
12 162-160-89-200.fibertel.com.ar (200.89.160.162) 276.708 ms 276.662 ms 276.670 ms
13 * * *
14 * * *
15 201-212-158-3.cab.prima.net.ar (201.212.158.3) 288.228 ms 286.061 ms 290.489 ms
22/07/2019 16:25:16 UTC
--------------------
TRACEROUTE:
traceroute to 201.212.158.3 (201.212.158.3), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.832 ms 0.868 ms 0.871 ms
2 24.105.18.131 (24.105.18.131) 2.484 ms 2.494 ms 2.506 ms
3 137.221.105.16 (137.221.105.16) 2.490 ms 2.502 ms 2.504 ms
4 137.221.66.18 (137.221.66.18) 2.392 ms 2.414 ms 2.420 ms
5 137.221.83.66 (137.221.83.66) 9.886 ms 9.907 ms 9.913 ms
6 137.221.65.68 (137.221.65.68) 48.605 ms 45.737 ms 45.686 ms
7 137.221.68.32 (137.221.68.32) 6.206 ms 6.208 ms 6.211 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 5.550 ms 5.647 ms 5.644 ms
9 * * *
10 190.216.88.2 (190.216.88.2) 272.844 ms 276.712 ms 276.618 ms
11 149-165-89-200.fibertel.com.ar (200.89.165.149) 275.677 ms 275.894 ms 275.894 ms
12 162-160-89-200.fibertel.com.ar (200.89.160.162) 276.569 ms 276.620 ms 276.710 ms
13 * * *
14 * * *
15 201-212-158-3.cab.prima.net.ar (201.212.158.3) 286.234 ms 292.411 ms 292.124 ms
22/07/2019 16:25:20 UTC
--------------------
TRACEROUTE:
traceroute to 201.212.158.3 (201.212.158.3), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.348 ms 0.351 ms 0.467 ms
2 24.105.18.131 (24.105.18.131) 0.589 ms 0.704 ms 0.837 ms
3 137.221.105.16 (137.221.105.16) 0.609 ms 0.719 ms 0.854 ms
4 137.221.66.18 (137.221.66.18) 8.843 ms 8.878 ms 9.215 ms
5 137.221.83.66 (137.221.83.66) 4.139 ms 4.311 ms 4.337 ms
6 137.221.65.68 (137.221.65.68) 5.959 ms 5.937 ms 5.930 ms
7 137.221.68.32 (137.221.68.32) 5.927 ms 5.940 ms 5.941 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 5.620 ms 5.646 ms 5.501 ms
9 * * *
10 190.216.88.2 (190.216.88.2) 275.779 ms 274.227 ms 272.793 ms
11 149-165-89-200.fibertel.com.ar (200.89.165.149) 275.637 ms 275.665 ms 275.870 ms
12 162-160-89-200.fibertel.com.ar (200.89.160.162) 276.554 ms 276.512 ms 276.517 ms
13 * * *
14 * * *
15 201-212-158-3.cab.prima.net.ar (201.212.158.3) 290.787 ms 287.946 ms 287.915 ms
22/07/2019 16:25:23 UTC
--------------------
PING:
PING 201.212.158.3 (201.212.158.3) 56(84) bytes of data.
64 bytes from 201.212.158.3: icmp_seq=1 ttl=41 time=286 ms
64 bytes from 201.212.158.3: icmp_seq=2 ttl=41 time=281 ms
64 bytes from 201.212.158.3: icmp_seq=3 ttl=41 time=283 ms
64 bytes from 201.212.158.3: icmp_seq=4 ttl=41 time=283 ms
--- 201.212.158.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 281.205/283.846/286.517/1.955 ms
22/07/2019 16:25:22 UTC
--------------------
PING:
PING 201.212.158.3 (201.212.158.3) 56(84) bytes of data.
64 bytes from 201.212.158.3: icmp_seq=1 ttl=41 time=285 ms
64 bytes from 201.212.158.3: icmp_seq=2 ttl=41 time=288 ms
64 bytes from 201.212.158.3: icmp_seq=3 ttl=41 time=288 ms
64 bytes from 201.212.158.3: icmp_seq=4 ttl=41 time=284 ms
--- 201.212.158.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 284.283/286.552/288.181/1.707 ms
22/07/2019 16:25:26 UTC
--------------------
MTR:
Start: Mon Jul 22 16:25:16 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.8 0.3 4.5 1.2
2.|-- 24.105.18.131 0.0% 10 0.5 3.8 0.5 13.3 5.2
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.6 0.9 0.0
4.|-- 137.221.66.18 0.0% 10 1.0 6.0 0.8 31.0 10.1
5.|-- 137.221.83.66 0.0% 10 16.2 8.9 1.2 32.8 9.5
6.|-- 137.221.65.68 0.0% 10 25.6 82.4 5.7 372.3 119.0
7.|-- 137.221.68.32 0.0% 10 10.8 15.3 6.0 79.4 22.9
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 5.4 5.6 5.3 5.8 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 190.216.88.2 0.0% 10 272.4 274.7 272.4 278.6 2.3
11.|-- 149-165-89-200.fibertel.com.ar 0.0% 10 275.7 275.9 275.7 276.1 0.0
12.|-- 162-160-89-200.fibertel.com.ar 0.0% 10 276.7 278.3 276.5 289.4 3.9
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- 201-212-158-3.cab.prima.net.ar 0.0% 10 285.3 290.1 285.3 298.8 3.8
22/07/2019 16:25:16 UTC
--------------------
MTR:
Start: Mon Jul 22 16:25:16 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.8 0.2 4.9 1.4
2.|-- 24.105.18.131 0.0% 10 0.6 3.9 0.5 13.8 5.3
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 1.0 0.0
4.|-- 137.221.66.18 0.0% 10 1.3 6.4 0.9 31.3 10.1
5.|-- 137.221.83.66 0.0% 10 16.2 9.1 1.2 33.0 9.6
6.|-- 137.221.65.68 0.0% 10 25.5 105.2 5.8 590.5 181.1
7.|-- 137.221.68.32 0.0% 10 10.8 15.1 5.9 77.8 22.5
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 5.5 5.6 5.4 5.8 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 190.216.88.2 0.0% 10 272.4 274.8 272.4 279.0 2.3
11.|-- 149-165-89-200.fibertel.com.ar 0.0% 10 275.6 275.9 275.6 276.2 0.0
12.|-- 162-160-89-200.fibertel.com.ar 0.0% 10 276.9 278.3 276.6 289.4 3.9
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- 201-212-158-3.cab.prima.net.ar 0.0% 10 288.6 290.0 285.7 298.8 4.1
22/07/2019 16:25:16 UTC
--------------------
MTR:
Start: Mon Jul 22 16:25:19 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 0.6 0.5 0.8 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.18 0.0% 10 0.9 8.9 0.9 60.2 18.4
5.|-- 137.221.83.66 0.0% 10 6.8 6.3 2.5 12.2 2.9
6.|-- 137.221.65.68 0.0% 10 5.8 29.1 5.7 137.9 41.3
7.|-- 137.221.68.32 0.0% 10 6.0 6.0 5.9 6.2 0.0
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 5.4 7.8 5.4 26.6 6.6
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 190.216.88.2 0.0% 10 272.2 274.7 270.8 277.9 2.4
11.|-- 149-165-89-200.fibertel.com.ar 0.0% 10 275.8 275.8 275.6 275.9 0.0
12.|-- 162-160-89-200.fibertel.com.ar 0.0% 10 276.7 276.7 276.5 277.3 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- 201-212-158-3.cab.prima.net.ar 0.0% 10 284.7 286.3 284.7 289.8 1.4
22/07/2019 16:25:19 UTC
--------------------
MTR:
Start: Mon Jul 22 16:25:23 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.7 0.7 0.5 0.8 0.0
4.|-- 137.221.66.18 0.0% 10 1.2 6.9 0.9 58.5 18.1
5.|-- 137.221.83.66 0.0% 10 5.3 3.6 0.9 8.4 2.1
6.|-- 137.221.65.68 0.0% 10 100.4 62.9 5.7 225.4 87.8
7.|-- 137.221.68.32 0.0% 10 6.0 6.2 5.7 8.2 0.6
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 5.4 7.4 5.4 25.1 6.2
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 190.216.88.2 0.0% 10 276.8 275.1 271.4 278.9 2.5
11.|-- 149-165-89-200.fibertel.com.ar 0.0% 10 275.7 275.8 275.6 276.0 0.0
12.|-- 162-160-89-200.fibertel.com.ar 0.0% 10 276.6 276.7 276.5 277.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- 201-212-158-3.cab.prima.net.ar 0.0% 10 285.6 287.3 284.4 290.8 2.2
22/07/2019 16:25:23 UTC
--------------------
Gracias por todas las pruebas que han mandado. Parece que todos son afectados por la conexión siendo mandada a Japón y luego de allí a los servidores. Ya fue reportado y al momento todavía se está investigando esto. Por el momento si pueden intentar de usar un DNS diferente para ver si ayuda. Google DNS y Cloudflare son dos comunes que pueden dar buenos resultados. Cualquier novedad, los dejaremos saber.