Por si fuera poco

El BW de prodigy el dia de hoy deja mucho que desear…

Lo bueno es que estamos pagando 1mb x 256…

Aunque ya investigando un poquito mas parece ser que la cosa esta gruesa…
mhh…

avalon:~$ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 64.233.187.99
traceroute to www.l.google.com (64.233.187.99), 30 hops max, 38 byte packets
1 dsl-mex-ermita-1-l0.uninet.net.mx (148.223.225.117) 10.429 ms 8.966 ms 9.715 ms
2 inet-mex-popocatepetl-20-pos3-2.uninet.net.mx (148.223.225.110) 9.418 ms 9.700 ms 9.730 ms
3 bb-mex-vallejo-10-pos1-1.uninet.net.mx (200.38.132.90) 9.925 ms 9.507 ms 9.715 ms
4 inet-tex-bryan-2-pos3-0.uninet.net.mx (200.38.193.126) 98.411 ms 97.919 ms 97.943 ms
5 66.138.193.149 (66.138.193.149) 98.607 ms 98.603 ms 98.644 ms
6 * * bb1-g7-3.rcsntx.sbcglobal.net (151.164.190.250) 99.618 ms
7 core1-p5-0.crdltx.sbcglobal.net (151.164.42.178) 103.397 ms * 99.900 ms
8 core3-p8-0.crdltx.sbcglobal.net (151.164.242.117) 257.080 ms * 253.553 ms
9 core1-p3-0.crhstx.sbcglobal.net (151.164.240.190) 104.838 ms * 105.656 ms
10 core2-p8-0.crhstx.sbcglobal.net (151.164.188.102) 104.876 ms 103.771 ms 104.126 ms
11 core1-p9-0.cratga.sbcglobal.net (151.164.191.192) 272.485 ms 262.050 ms 259.063 ms
12 core2-p1-0.cratga.sbcglobal.net (151.164.241.82) 117.468 ms 117.973 ms 116.223 ms
13 bb2-p12-0.altnga.sbcglobal.net (151.164.189.18) 118.728 ms * 117.180 ms
14 ex1-p11-1.pxatga.sbcglobal.net (151.164.42.17) 117.895 ms 117.957 ms 116.212 ms
15 asn15169-google.pxatga.sbcglobal.net (151.164.250.138) 917.605 ms 911.199 ms *
16 72.14.236.173 (72.14.236.173) 1244.965 ms 1251.667 ms 1245.003 ms
17 216.239.49.222 (216.239.49.222) 1242.710 ms 216.239.49.226 (216.239.49.226) 916.826 ms 922.107 ms
18 64.233.187.99 (64.233.187.99) 919.283 ms 925.686 ms 937.028 ms

avalon:~$ ping www.google.com
PING www.l.google.com (64.233.187.104): 56 data bytes
64 bytes from 64.233.187.104: icmp_seq=0 ttl=239 time=1098.0 ms
64 bytes from 64.233.187.104: icmp_seq=1 ttl=239 time=1092.1 ms
64 bytes from 64.233.187.104: icmp_seq=2 ttl=239 time=1092.5 ms
64 bytes from 64.233.187.104: icmp_seq=3 ttl=239 time=1084.3 ms
— www.l.google.com ping statistics —
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 1084.3/1091.7/1098.0 ms

Esto esta muy alto…

Veamos nuestro GW

ping 148.223.225.117
PING 148.223.225.117 (148.223.225.117): 56 data bytes
64 bytes from 148.223.225.117: icmp_seq=0 ttl=255 time=12.5 ms
64 bytes from 148.223.225.117: icmp_seq=1 ttl=255 time=12.1 ms
64 bytes from 148.223.225.117: icmp_seq=2 ttl=255 time=11.1 ms
64 bytes from 148.223.225.117: icmp_seq=3 ttl=255 time=13.2 ms
64 bytes from 148.223.225.117: icmp_seq=4 ttl=255 time=11.8 ms

— 148.223.225.117 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 11.1/12.1/13.2 ms

Bien, aqui no es…

avalon:~$ping www.upn.mx
PING webb.ajusco.upn.mx (200.23.113.55): 56 data bytes
64 bytes from 200.23.113.55: icmp_seq=0 ttl=58 time=38.3 ms
64 bytes from 200.23.113.55: icmp_seq=1 ttl=58 time=72.8 ms
64 bytes from 200.23.113.55: icmp_seq=2 ttl=58 time=31.8 ms
64 bytes from 200.23.113.55: icmp_seq=3 ttl=58 time=31.5 ms
64 bytes from 200.23.113.55: icmp_seq=4 ttl=58 time=42.9 ms

— webb.ajusco.upn.mx ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 31.5/43.4/72.8 ms

avalon:~$ dig ns

; <<>> DiG 9.2.4 <<>> ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8510
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13

;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 495447 IN NS E.ROOT-SERVERS.NET.
. 495447 IN NS F.ROOT-SERVERS.NET.
. 495447 IN NS G.ROOT-SERVERS.NET.
. 495447 IN NS H.ROOT-SERVERS.NET.
. 495447 IN NS I.ROOT-SERVERS.NET.
. 495447 IN NS J.ROOT-SERVERS.NET.
. 495447 IN NS K.ROOT-SERVERS.NET.
. 495447 IN NS L.ROOT-SERVERS.NET.
. 495447 IN NS M.ROOT-SERVERS.NET.
. 495447 IN NS A.ROOT-SERVERS.NET.
. 495447 IN NS B.ROOT-SERVERS.NET.
. 495447 IN NS C.ROOT-SERVERS.NET.
. 495447 IN NS D.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
A.ROOT-SERVERS.NET. 581847 IN A 198.41.0.4
B.ROOT-SERVERS.NET. 581847 IN A 192.228.79.201
C.ROOT-SERVERS.NET. 581847 IN A 192.33.4.12
D.ROOT-SERVERS.NET. 581847 IN A 128.8.10.90
E.ROOT-SERVERS.NET. 581847 IN A 192.203.230.10
F.ROOT-SERVERS.NET. 581847 IN A 192.5.5.241
G.ROOT-SERVERS.NET. 581847 IN A 192.112.36.4
H.ROOT-SERVERS.NET. 581847 IN A 128.63.2.53
I.ROOT-SERVERS.NET. 581847 IN A 192.36.148.17
J.ROOT-SERVERS.NET. 581847 IN A 192.58.128.30
K.ROOT-SERVERS.NET. 581847 IN A 193.0.14.129
L.ROOT-SERVERS.NET. 581847 IN A 198.32.64.12
M.ROOT-SERVERS.NET. 581847 IN A 202.12.27.33

;; Query time: 9 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Dec 14 08:33:48 2005
;; MSG SIZE rcvd: 436

avalon:~$ ping 198.41.0.4
PING 198.41.0.4 (198.41.0.4): 56 data bytes

— 198.41.0.4 ping statistics —
3 packets transmitted, 0 packets received, 100% packet loss
avalon:~$ ping 192.228.79.201
PING 192.228.79.201 (192.228.79.201): 56 data bytes

— 192.228.79.201 ping statistics —
2 packets transmitted, 0 packets received, 100% packet loss
avalon:~$ ping 193.0.14.129
PING 193.0.14.129 (193.0.14.129): 56 data bytes
64 bytes from 193.0.14.129: icmp_seq=0 ttl=49 time=1332.9 ms
64 bytes from 193.0.14.129: icmp_seq=1 ttl=49 time=1341.9 ms
64 bytes from 193.0.14.129: icmp_seq=2 ttl=49 time=1330.8 ms

— 193.0.14.129 ping statistics —
5 packets transmitted, 3 packets received, 40% packet loss
round-trip min/avg/max = 1330.8/1335.2/1341.9 ms

Bueeno… creo que entonces mas bien es con la salida a EU… a ver si en el dia mejora la cosa… ya ni pensar en llamar a sotorpe… no me imagino explicandoles el problema con los enlaces… en fin vamos a esperar un rato.

Salu2