yrithinnd
30/07/2009, 12:53
Parece que ya se ha vuelto a estabilizar
Gracias!
Gracias!
Ping inestable con telefónica
admin OVH
30/07/2009, 11:18
Un problema de encaminamiento en Telefónica.
Están haciendo pasar 1 vez cada 2 el tráfico por Nueva York.
Ya hemos señalado el problema.
traceroute ping
traceroute to ping.ovh.net (213.186.33.13), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.690 ms 0.476 ms 0.464 ms
2 1.Red-213-4-0.staticIP.rima-tde.net (213.4.0.1) 32.693 ms 29.818 ms 31.378 ms
3 130.Red-81-46-39.staticIP.rima-tde.net (81.46.39.130) 39.078 ms 31.464 ms 29.873 ms
4 So7-0-0-0-grtmadde2.red.telefonica.wholesale.net (84.16.8.113) 81.016 ms 32.711 ms 32.762 ms
5 So-1-3-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.12.49) 30.798 ms So4-3-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.12.206) 127.127 ms So-1-3-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.12.49) 48.249 ms
6 So6-3-0-0-grtlontl3.red.telefonica-wholesale.net (213.140.43.254) 132.047 ms So2-2-0-0-grtlontl1.red.telefonica-wholesale.net (213.140.36.122) 57.862 ms 54.946 ms
aquí las 2 rutas están bien
7 if-11-2.mse1.LVX-London.as6453.net (195.219.92.9) 58.351 ms
^^^ aquí ok
7 So5-0-0-0-grtnycpt2.red.telefonica-wholesale.net (213.140.43.42) 128.131 ms 137.243 ms
^^^ Nueva York !!
8 GE6-1-0-0-grtnycpt3.red.telefonica-wholesale.net (213.140.38.130) 129.525 ms 129.103 ms 129.132 ms
luego vuelve
9 Vlan463.icore1.LDN-London.as6453.net (195.219.195.38) 72.005 ms So3-1-0-0-grtlontl1.red.telefonica-wholesale.net (213.140.36.205) 131.397 ms 126.147 ms
luego vuelve
10 20g.ldn-1-6k.routers.ovh.net (94.23.122.121) 102.959 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.74) 188.790 ms if-11-2.mse1.LVX-London.as6453.net (195.219.92.9) 127.289 ms
11 if-13-1-0.mcore3.LDN-London.as6453.net (195.219.195.49) 129.606 ms 129.125 ms 20g.rbx-2-6k.routers.chtix.eu (213.251.130.57) 78.750 ms
12 160g.th2-1-6k.routers.chtix.eu (213.186.32.202) 66.647 ms * Vlan463.icore1.LDN-London.as6453.net (195.219.195.38) 142.171 ms
13 20g.ldn-1-6k.routers.ovh.net (94.23.122.121) 156.383 ms 205.001 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.74) 211.585 ms
14 * 20g.rbx-2-6k.routers.chtix.eu (213.251.130.57) 131.325 ms 132.252 ms
15 160g.th2-1-6k.routers.chtix.eu (213.186.32.202) 145.104 ms ping (213.186.33.13) 77.078 ms 160g.th2-1-6k.routers.chtix.eu (213.186.32.202) 132.054 ms
Están haciendo pasar 1 vez cada 2 el tráfico por Nueva York.
Ya hemos señalado el problema.
traceroute ping
traceroute to ping.ovh.net (213.186.33.13), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.690 ms 0.476 ms 0.464 ms
2 1.Red-213-4-0.staticIP.rima-tde.net (213.4.0.1) 32.693 ms 29.818 ms 31.378 ms
3 130.Red-81-46-39.staticIP.rima-tde.net (81.46.39.130) 39.078 ms 31.464 ms 29.873 ms
4 So7-0-0-0-grtmadde2.red.telefonica.wholesale.net (84.16.8.113) 81.016 ms 32.711 ms 32.762 ms
5 So-1-3-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.12.49) 30.798 ms So4-3-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.12.206) 127.127 ms So-1-3-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.12.49) 48.249 ms
6 So6-3-0-0-grtlontl3.red.telefonica-wholesale.net (213.140.43.254) 132.047 ms So2-2-0-0-grtlontl1.red.telefonica-wholesale.net (213.140.36.122) 57.862 ms 54.946 ms
aquí las 2 rutas están bien
7 if-11-2.mse1.LVX-London.as6453.net (195.219.92.9) 58.351 ms
^^^ aquí ok
7 So5-0-0-0-grtnycpt2.red.telefonica-wholesale.net (213.140.43.42) 128.131 ms 137.243 ms
^^^ Nueva York !!
8 GE6-1-0-0-grtnycpt3.red.telefonica-wholesale.net (213.140.38.130) 129.525 ms 129.103 ms 129.132 ms
luego vuelve
9 Vlan463.icore1.LDN-London.as6453.net (195.219.195.38) 72.005 ms So3-1-0-0-grtlontl1.red.telefonica-wholesale.net (213.140.36.205) 131.397 ms 126.147 ms
luego vuelve
10 20g.ldn-1-6k.routers.ovh.net (94.23.122.121) 102.959 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.74) 188.790 ms if-11-2.mse1.LVX-London.as6453.net (195.219.92.9) 127.289 ms
11 if-13-1-0.mcore3.LDN-London.as6453.net (195.219.195.49) 129.606 ms 129.125 ms 20g.rbx-2-6k.routers.chtix.eu (213.251.130.57) 78.750 ms
12 160g.th2-1-6k.routers.chtix.eu (213.186.32.202) 66.647 ms * Vlan463.icore1.LDN-London.as6453.net (195.219.195.38) 142.171 ms
13 20g.ldn-1-6k.routers.ovh.net (94.23.122.121) 156.383 ms 205.001 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.74) 211.585 ms
14 * 20g.rbx-2-6k.routers.chtix.eu (213.251.130.57) 131.325 ms 132.252 ms
15 160g.th2-1-6k.routers.chtix.eu (213.186.32.202) 145.104 ms ping (213.186.33.13) 77.078 ms 160g.th2-1-6k.routers.chtix.eu (213.186.32.202) 132.054 ms
yrithinnd
29/07/2009, 16:19
Desde ayer el ping a las redes de telefónicas es sospechósamente inestable. No hay perdida de paquetes ni se aprecia una degradación del servicio pero ocurre algo raro.
http://smokeping.ovh.net/ovh-server-...i?target=Spain
http://smokeping.ovh.net/ovh-server-...ain.Telefonica
En condiciones normales ando entre 76-84ms y ahora es sorprendente porque los rápidos bajan de los 75ms cosa que antes ni por asomo.
¿Alguen tiene idea de porqué podría ocurrir esto?
http://smokeping.ovh.net/ovh-server-...i?target=Spain
http://smokeping.ovh.net/ovh-server-...ain.Telefonica
En condiciones normales ando entre 76-84ms y ahora es sorprendente porque los rápidos bajan de los 75ms cosa que antes ni por asomo.
Código:
64 bytes from nevasport.com (94.23.84.233): icmp_seq=483 ttl=51 time=73.3 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=484 ttl=51 time=142 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=485 ttl=51 time=70.5 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=486 ttl=51 time=139 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=487 ttl=51 time=142 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=488 ttl=51 time=142 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=489 ttl=51 time=139 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=490 ttl=51 time=145 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=491 ttl=51 time=139 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=492 ttl=51 time=74.3 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=493 ttl=51 time=140 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=494 ttl=51 time=74.5 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=495 ttl=51 time=142 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=496 ttl=51 time=71.0 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=497 ttl=51 time=70.3 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=498 ttl=51 time=143 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=499 ttl=51 time=70.2 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=500 ttl=51 time=145 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=501 ttl=51 time=70.3 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=502 ttl=51 time=73.2 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=503 ttl=51 time=70.7 ms 64 bytes from nevasport.com (94.23.84.233): icmp_seq=504 ttl=51 time=68.5 ms ^C64 bytes from nevasport.com (94.23.84.233): icmp_seq=505 ttl=51 time=145 ms --- nevasport.com ping statistics --- 505 packets transmitted, 505 received, 0% packet loss, time 509249ms rtt min/avg/max/mdev = 67.341/109.817/149.137/35.716 ms
Código:
$ traceroute nevasport.com traceroute to nevasport.com (94.23.84.233), 30 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 0.684 ms 0.981 ms 1.262 ms 2 192.168.153.1 (192.168.153.1) 35.032 ms 38.445 ms 42.594 ms 3 177.Red-81-46-36.staticIP.rima-tde.net (81.46.36.177) 46.597 ms 49.957 ms 53.156 ms 4 So-5-0-0-0-grtmadpe3.red.telefonica-wholesale.net (84.16.9.161) 83.004 ms 83.290 ms 83.508 ms 5 So2-2-0-0-grtlontl1.red.telefonica-wholesale.net (213.140.36.122) 110.027 ms So6-3-0-0-grtlontl3.red.telefonica-wholesale.net (213.140.43.254) 185.942 ms 189.045 ms 6 if-11-2.mse1.LVX-London.as6453.net (195.219.92.9) 121.087 ms So6-0-0-0-grtnycpt2.red.telefonica-wholesale.net (213.140.43.46) 145.943 ms if-11-2.mse1.LVX-London.as6453.net (195.219.92.9) 71.708 ms 7 if-13-1-0.mcore3.LDN-London.as6453.net (195.219.195.49) 73.090 ms 76.477 ms GE6-1-0-0-grtnycpt3.red.telefonica-wholesale.net (213.140.38.130) 151.923 ms 8 So3-1-0-0-grtlontl1.red.telefonica-wholesale.net (213.140.36.205) 153.336 ms Vlan463.icore1.LDN-London.as6453.net (195.219.195.38) 93.698 ms 107.650 ms 9 if-11-2.mse1.LVX-London.as6453.net (195.219.92.9) 172.200 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.121) 104.719 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.74) 113.792 ms 10 20g.rbx-1-6k.routers.chtix.eu (91.121.131.13) 112.829 ms * * 11 rbx-38-m1.routers.ovh.net (213.251.191.110) 123.156 ms 126.475 ms Vlan463.icore1.LDN-London.as6453.net (195.219.195.38) 156.408 ms 12 nevasport.com (94.23.84.233) 70.321 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.74) 149.325 ms 20g.ldn-1-6k.routers.ovh.net (94.23.122.121) 151.706 ms
¿Alguen tiene idea de porqué podría ocurrir esto?