PING alto movistar fibra optica.

eMe_tv
Más integrado que la RDSI
PING alto movistar fibra optica.

Hola adquirí el servicio para jugar y hacer streams.

El problema lo tengo al jugar, ya que tengo unos buenos resultados de descarga y carga.

Al jugar fornite/ csgo en servidores brasileros *si no me equivoco* tengo un ping superior a 150ms, constantes que nunca bajan. La computadora no es y el internet da buenos resultados.

Quizás es un tema del módem y quería ayuda para este tema, hice el ping "FORO-PING-TRACERT.bat" hacia la ip de fornite y también a la ip 192.168.1.1. adjunto ambos resultados.

IP: fortnite.es  (resultados)


*******************************************************************************
*******************************************************************************
IP A PROBAR: fortnite.es
*******************************************************************************
*******************************************************************************

=================================================
TRACERT A LA IP fortnite.es

Tracing route to fortnite.es [217.160.230.66]
over a maximum of 20 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 2 ms 200.51.241.1
3 6 ms 7 ms 4 ms 10.192.4.2
4 8 ms 7 ms 7 ms 10.192.0.0
5 4 ms 7 ms 7 ms 200.51.208.94
6 2 ms 2 ms 2 ms 10.192.19.7
7 139 ms 141 ms 139 ms 84.16.15.160
8 139 ms 139 ms 138 ms ae-12.r04.miamfl02.us.bb.gin.ntt.net [129.250.9.85]
9 139 ms 140 ms 139 ms ae-6.r20.miamfl02.us.bb.gin.ntt.net [129.250.3.141]
10 166 ms 165 ms 165 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
11 167 ms 170 ms 168 ms ae-0.r22.asbnva02.us.bb.gin.ntt.net [129.250.3.84]
12 159 ms 160 ms 161 ms ae-5.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.148]
13 171 ms 171 ms 172 ms ae-1.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.206]
14 237 ms 238 ms 238 ms ae-9.r24.londen12.uk.bb.gin.ntt.net [129.250.2.19]
15 252 ms 259 ms 250 ms ae-1.r25.londen12.uk.bb.gin.ntt.net [129.250.2.27]
16 243 ms 240 ms 238 ms ae-7.r00.londen14.uk.bb.gin.ntt.net [129.250.3.191]
17 239 ms 240 ms 241 ms ae-1.a01.londen14.uk.bb.gin.ntt.net [129.250.2.235]
18 241 ms 252 ms 241 ms 212.119.29.78
19 263 ms 263 ms 263 ms ae-3.bb-b.thn.lon.gb.oneandone.net [212.227.120.106]
20 266 ms 263 ms 263 ms ae-4.bb-b.bap.rhr.de.oneandone.net [212.227.120.49]

Trace complete.
=================================================

================================================
PING A LA IP: fortnite.es

Pinging fortnite.es [217.160.230.66] with 32 bytes of data:
Reply from 217.160.230.66: bytes=32 time=260ms TTL=44
Reply from 217.160.230.66: bytes=32 time=260ms TTL=44
Reply from 217.160.230.66: bytes=32 time=261ms TTL=44
Reply from 217.160.230.66: bytes=32 time=261ms TTL=44
Reply from 217.160.230.66: bytes=32 time=260ms TTL=44
Reply from 217.160.230.66: bytes=32 time=260ms TTL=44
Reply from 217.160.230.66: bytes=32 time=260ms TTL=44
Reply from 217.160.230.66: bytes=32 time=260ms TTL=44
Reply from 217.160.230.66: bytes=32 time=261ms TTL=44
Reply from 217.160.230.66: bytes=32 time=261ms TTL=44

Ping statistics for 217.160.230.66:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 260ms, Maximum = 261ms, Average = 260ms
=================================================
================================================
PING DE 1400 A LA IP: fortnite.es

Pinging fortnite.es [217.160.230.66] with 1400 bytes of data:
Reply from 217.160.230.66: bytes=1400 time=263ms TTL=44
Reply from 217.160.230.66: bytes=1400 time=260ms TTL=44
Reply from 217.160.230.66: bytes=1400 time=262ms TTL=44
Reply from 217.160.230.66: bytes=1400 time=264ms TTL=44

Ping statistics for 217.160.230.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 260ms, Maximum = 264ms, Average = 262ms
=================================================
================================================
PING A LOS DNS DE MOVISTAR:

Pinging 80.58.61.254 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.58.61.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
=================================================
=================================================
PING LARGO A DNS DE MOVISTAR:

Pinging 80.58.61.254 with 1400 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.58.61.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
=================================================




=================================================
DIRECCION IP PUBLICA
IP origen desde myip.opendns
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: myip.opendns.com
Address: 191.81.75.236

--------------------------------------------
IP origen desde myaddr.l.google
Server: ns1.google.com
Address: 216.239.32.10

o-o.myaddr.l.google.com text =

"191.81.75.236"
=================================================
=================================================
INFORMACION DE LAS TARJETAS DE RED:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-0TVR67A
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek Gaming GbE Family Controller
Physical Address. . . . . . . . . : B4-2E-99-3C-D1-49
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2802:8010:109:b700:d43a:f68c:af67:efaa(Preferred)
Temporary IPv6 Address. . . . . . : 2802:8010:109:b700:412:9ee5:527e:5291(Preferred)
Link-local IPv6 Address . . . . . : fe80::d43a:f68c:af67:efaa%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.55(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : jueves, 19 de septiembre de 2019 14:12:25
Lease Expires . . . . . . . . . . : viernes, 20 de septiembre de 2019 10:36:37
Default Gateway . . . . . . . . . : fe80::ced4:a1ff:fe98:7ad1%11
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 347352729
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-F2-9C-9A-B4-2E-99-3C-D1-49
DNS Servers . . . . . . . . . . . : 186.130.128.250
186.130.129.250
NetBIOS over Tcpip. . . . . . . . : Enabled
=================================================
=================================================
VELOCIDADES DE LAS TARJETAS DE RED:
N a m e S p e e d
R e a l t e k G a m i n g G b E F a m i l y C o n t r o l l e r 1 0 0 0 0 0 0 0 0 0
ECHO is off.
=================================================
=================================================
=================================================
PRUEBA COMPLETADA
hora:
03:44
fecha:
vie. 20/09/2019

 

IP: 192.168.1.1 (resultados)

Version 2.0

USUARIO EN LA COMUNIDAD: @eMe_tv

NUMERO FIJO: 49261921

*******************************************************************************
*******************************************************************************
IP A PROBAR: 192.168.1.1
*******************************************************************************
*******************************************************************************
=================================================
TRACERT A LA IP 192.168.1.1

Tracing route to 192.168.1.1 over a maximum of 20 hops

1 <1 ms <1 ms <1 ms 192.168.1.1

Trace complete.
=================================================
=================================================
PING A LA IP: 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0ms
=================================================
=================================================
PING DE 1400 A LA IP: 192.168.1.1

Pinging 192.168.1.1 with 1400 bytes of data:
Reply from 192.168.1.1: bytes=1400 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1400 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1400 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1400 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
==============================================
==============================================
PING A LOS DNS DE MOVISTAR:

Pinging 80.58.61.254 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.58.61.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
=================================================
=================================================
PING LARGO A DNS DE MOVISTAR:

Pinging 80.58.61.254 with 1400 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.58.61.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
=================================================
=================================================
DIRECCION IP PUBLICA
IP origen desde myip.opendns
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: myip.opendns.com
Address: 191.81.75.236

--------------------------------------------
IP origen desde myaddr.l.google
Server: ns1.google.com
Address: 216.239.32.10

o-o.myaddr.l.google.com text =

"191.81.75.236"
================================================
================================================

INFORMACION DE LAS TARJETAS DE RED:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-0TVR67A
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek Gaming GbE Family Controller
Physical Address. . . . . . . . . : B4-2E-99-3C-D1-49
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2802:8010:109:b700:d43a:f68c:af67:efaa(Preferred)
Temporary IPv6 Address. . . . . . : 2802:8010:109:b700:412:9ee5:527e:5291(Preferred)
Link-local IPv6 Address . . . . . : fe80::d43a:f68c:af67:efaa%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.55(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : jueves, 19 de septiembre de 2019 14:12:25
Lease Expires . . . . . . . . . . : viernes, 20 de septiembre de 2019 10:36:37
Default Gateway . . . . . . . . . : fe80::ced4:a1ff:fe98:7ad1%11
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 347352729
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-F2-9C-9A-B4-2E-99-3C-D1-49
DNS Servers . . . . . . . . . . . : 186.130.128.250
186.130.129.250
NetBIOS over Tcpip. . . . . . . . : Enabled
=================================================
=================================================
VELOCIDADES DE LAS TARJETAS DE RED:
N a m e S p e e d
R e a l t e k G a m i n g G b E F a m i l y C o n t r o l l e r 1 0 0 0 0 0 0 0 0 0
ECHO is off.
=================================================
=================================================
=================================================
PRUEBA COMPLETADA
hora:
03:54
fecha:
vie. 20/09/2019

Mensaje 1 de 3
821 Visitas
2 RESPUESTAS 2
Theliel
Yo probé el VDSL

Buenas @eMe_tv 

 

Por la traza veo que perteneces a Movistar Argentina, mientras que este foro de soporte es para Movistar España. Dirígete al soporte de vuestro país.

 

En cualquier caso hay un nodo que da problemas.



Por privado solo asuntos privados, para lo demás la comunidad."El conocimiento nace del desacuerdo"
Mensaje 2 de 3
797 Visitas
Técnico-Movistar
Técnico Banda Ancha

¡ Hola eMe_tv !

 

Efectivamente como indica Theliel  ( muchas gracias por tu aportación), perteneces a Argentina , por lo que tienes que ponerte de acuerdo con el soporte técnico de allí para que te lo puedan comprobar.

 

Procedo a cerrar el hilo.

 

Un saludo.

 

Samuel

 

 



Si necesitas soporte técnico en averías de Móvil, Fijo, Movistar+ o Internet Fijo (cobre o fibra), puedes acceder a nuestro apartado de Soporte Técnico o rellenar este formulario. También puedes contactar con nosotros llamando al 1002.

 Si necesitas contratar Fibra Ópticacomprobar tu cobertura Adsl y Fibrao ver información sobre la instalación de la fibra visita nuestra página ADSL y Fibra en movistar.es 

Solución aceptada.png
Mensaje 3 de 3
770 Visitas