>From Prescott Valley by way of AT&T dial up account:
offspring:/home/bucky# ping -c 5 mume.pvv.org
PING fire.pvv.org (129.241.210.221): 56 data bytes
64 bytes from 129.241.210.221: icmp_seq=0 ttl=225 time=369.3 ms
64 bytes from 129.241.210.221: icmp_seq=1 ttl=225 time=409.9 ms
64 bytes from 129.241.210.221: icmp_seq=2 ttl=225 time=360.1 ms
64 bytes from 129.241.210.221: icmp_seq=3 ttl=225 time=410.1 ms
64 bytes from 129.241.210.221: icmp_seq=4 ttl=225 time=360.0 ms
--- fire.pvv.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 360.0/381.8/410.1 ms
offspring:/home/bucky# ping -c 5
www.hartinger.ws
PING hartinger.ws (216.92.236.40): 56 data bytes
64 bytes from 216.92.236.40: icmp_seq=0 ttl=240 time=229.1 ms
64 bytes from 216.92.236.40: icmp_seq=1 ttl=240 time=229.9 ms
64 bytes from 216.92.236.40: icmp_seq=2 ttl=240 time=230.0 ms
64 bytes from 216.92.236.40: icmp_seq=3 ttl=240 time=230.0 ms
64 bytes from 216.92.236.40: icmp_seq=4 ttl=240 time=230.0 ms
--- hartinger.ws ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 229.1/229.8/230.0 ms
offspring:/home/bucky# traceroute mume.pvv.org
traceroute to fire.pvv.org (129.241.210.221), 30 hops max, 38 byte
packets
1 165.238.67.72 (165.238.67.72) 136.824 ms 129.544 ms 130.045 ms
2 1.phoenix-16-17rs.az.dial-access.att.net (12.72.38.1) 128.960 ms
119.459 ms 129.389 ms
3 165.238.127.21 (165.238.127.21) 149.934 ms 139.866 ms 139.943 ms
4 gbr1-a31s4.la2ca.ip.att.net (12.127.12.181) 140.044 ms 149.568 ms
130.108 ms
5 gbr3-p70.la2ca.ip.att.net (12.122.1.173) 139.943 ms 148.581 ms
141.068 ms
6 ggr1-p360.la2ca.ip.att.net (12.123.28.129) 149.934 ms 139.862 ms
139.928 ms
7 att-gw.la.teleglobe.net (192.205.32.222) 149.943 ms 149.619 ms
129.982 ms
8 if-10-0.core1.NewYork.Teleglobe.net (207.45.223.101) 219.800 ms
219.822 ms 219.842 ms
9 if-0-2.core2.London.Teleglobe.net (195.219.0.189) 289.970 ms
283.006 ms 286.706 ms
10 if-4-0.core1.London.Teleglobe.net (195.219.96.69) 289.925 ms
289.854 ms 289.966 ms
11 if-10-0.core1.Paris.Teleglobe.net (195.219.96.90) 299.899 ms
299.857 ms 299.938 ms
12 if-0-0.core1.Paris2.Teleglobe.net (195.219.96.98) 299.937 ms
299.812 ms 299.932 ms
13 if-8-0.core1.Frankfurt2.Teleglobe.net (195.219.15.206) 309.946 ms
299.840 ms 299.952 ms
14 if-1-0.core2.Stockholm.Teleglobe.net (195.219.96.18) 339.907 ms
329.833 ms 329.946 ms
15 e-gw.teleglobe.net (195.219.88.194) 339.932 ms 329.786 ms 329.925
ms
16 no-gw.nordu.net (193.10.68.30) 330.089 ms 341.425 ms 339.947 ms
17 oslo-gw1.uninett.no (193.10.68.50) 339.922 ms 339.847 ms 339.945
ms
18 trd-gw.uninett.no (128.39.0.250) 349.941 ms 349.794 ms 349.944 ms
19 ntnu-gw2.ntnu.no (158.38.0.222) 350.056 ms 339.922 ms 329.880 ms
20 sb-gw.ntnu.no (129.241.76.130) 340.039 ms 350.366 ms 340.072 ms
21 fire.pvv.org (129.241.210.221) 339.780 ms 349.623 ms 340.133 ms
offspring:/home/bucky# traceroute
www.hartinger.ws
traceroute to hartinger.ws (216.92.236.40), 30 hops max, 38 byte packets
1 165.238.67.72 (165.238.67.72) 126.499 ms 129.568 ms 129.882 ms
2 1.phoenix-16-17rs.az.dial-access.att.net (12.72.38.1) 129.887 ms
119.619 ms 129.928 ms
3 165.238.127.21 (165.238.127.21) 149.899 ms 139.746 ms 139.369 ms
4 gbr1-a31s4.la2ca.ip.att.net (12.127.12.181) 145.841 ms 139.767 ms
129.615 ms
5 gbr3-p70.la2ca.ip.att.net (12.122.1.173) 129.887 ms 139.753 ms
129.967 ms
6 ggr1-p360.la2ca.ip.att.net (12.123.28.129) 149.889 ms 139.833 ms
139.964 ms
7 att-gw.la.sprint.net (192.205.32.186) 140.525 ms 149.460 ms
139.908 ms
8 sl-bb20-ana-15-0.sprintlink.net (144.232.1.178) 149.946 ms 148.622
ms 140.916 ms
9 sl-bb20-sj-5-0.sprintlink.net (144.232.18.182) 149.929 ms 139.568
ms 159.851 ms
10 sl-bb22-rly-12-0.sprintlink.net (144.232.9.217) 209.891 ms 199.837
ms 199.922 ms
11 sl-gw8-rly-4-0-0.sprintlink.net (144.232.7.246) 209.928 ms 209.627
ms 219.932 ms
12 sl-pairnet-1-0-0.sprintlink.net (144.232.190.142) 219.933 ms
219.851 ms 209.938 ms
13 * * *
14 hartinger.ws (216.92.236.40) 219.928 ms 216.805 ms 221.375 ms
HTH,
Armand
Armin Hartinger wrote:
>
> Hello plug-discuss,
>
> Cox@Home is finally available in my area and I wanted to know how
> the latency of it is. If you use Cox, plz reply to me with ping and
> traceroute results to
>
> mume.pvv.org
> www.hartinger.ws
>
> Thanks in advance and sorry for the trouble!
>
> --
> Best regards,
> Armin mailto:armin@pctechware.com