Re[2]: do you use cox@home?

I just checked it again this morning and now the ping times are good. It
must have been some temporary problem.

Brian Cluff

[brian@napita brian]$ ping 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=234 time=249.7 ms
64 bytes from 129.241.210.221: icmp_seq=1 ttl=234 time=227.2 ms
64 bytes from 129.241.210.221: icmp_seq=2 ttl=234 time=224.3 ms
64 bytes from 129.241.210.221: icmp_seq=3 ttl=234 time=215.9 ms
64 bytes from 129.241.210.221: icmp_seq=4 ttl=234 time=223.2 ms
64 bytes from 129.241.210.221: icmp_seq=5 ttl=234 time=216.8 ms
64 bytes from 129.241.210.221: icmp_seq=6 ttl=234 time=251.8 ms
64 bytes from 129.241.210.221: icmp_seq=7 ttl=234 time=256.8 ms
64 bytes from 129.241.210.221: icmp_seq=8 ttl=234 time=217.6 ms

--- fire.pvv.org ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 215.9/231.4/256.8 ms

[brian@napita brian]$ traceroute mume.pvv.org
traceroute to fire.pvv.org (129.241.210.221), 30 hops max, 38 byte packets
1 10.78.66.1 (10.78.66.1) 14.167 ms 8.007 ms 7.741 ms
2 10.0.211.101 (10.0.211.101) 9.469 ms 9.949 ms 12.864 ms
3 c1-pos4-0.phnxaz1.home.net (24.7.74.165) 8.967 ms 13.167 ms 7.855 ms
4 c1-pos2-0.sndgca1.home.net (24.7.65.134) 19.375 ms 15.930 ms 15.618
ms
5 c1-pos1-0.anhmca1.home.net (24.7.64.69) 17.749 ms 42.281 ms 27.545 ms
6 c1-pos1-0.snjsca1.home.net (24.7.65.165) 79.257 ms 40.063 ms 27.556
ms
7 bb2-pos1-0.paix.nap.home.net (24.7.74.170) 27.336 ms 26.768 ms 29.030
ms
8 if-5-0-0.bb1.PaloAlto.Teleglobe.net (207.45.200.237) 62.568 ms 49.526
ms 35.604 ms
9 if-4-4.core1.PaloAlto.Teleglobe.net (207.45.223.182) 28.492 ms 36.240
ms 29.668 ms
10 if-10-2.core1.NewYork.Teleglobe.net (207.45.223.113) 94.230 ms 121.230
ms 96.573 ms
11 if-0-2.core2.London.Teleglobe.net (195.219.0.189) 210.640 ms 163.043
ms 221.308 ms
12 if-4-0.core1.London.Teleglobe.net (195.219.96.69) 168.276 ms 166.007
ms 207.687 ms
13 if-10-0.core1.Paris.Teleglobe.net (195.219.96.90) 185.786 ms 187.361
ms 180.246 ms
14 if-0-0.core1.Paris2.Teleglobe.net (195.219.96.98) 186.462 ms 242.369
ms 247.563 ms
15 if-8-0.core1.Frankfurt2.Teleglobe.net (195.219.15.206) 193.642 ms
190.363 ms 193.273 ms
16 if-1-0.core2.Stockholm.Teleglobe.net (195.219.96.18) 204.359 ms
211.927 ms 233.863 ms
17 e-gw.teleglobe.net (195.219.88.194) 199.569 ms 200.483 ms 200.530 ms
18 no-gw.nordu.net (193.10.68.30) 205.564 ms 204.389 ms 203.271 ms
19 oslo-gw1.uninett.no (193.10.68.50) 236.889 ms 234.938 ms 216.129 ms
20 trd-gw.uninett.no (128.39.0.250) 218.793 ms 294.659 ms 212.135 ms
21 ntnu-gw2.ntnu.no (158.38.0.222) 217.712 ms 220.490 ms 215.849 ms
22 sb-gw.ntnu.no (129.241.76.130) 210.867 ms 226.953 ms 223.532 ms
23 fire.pvv.org (129.241.210.221) 213.327 ms 224.817 ms 221.740 ms
----- Original Message -----

> Hello Brian,
>
> Monday, March 05, 2001, 9:24:57 PM, you wrote:
>
> I hope that was a temporary glitch :) If you could rerun it maybe at a
> later time, that would be great. With Sprint Broadband, I get usually
> around 300ms at night. Flaky 500ms during day.
>
> That address is a MUD. This is the thing I wasted much on my youth on
> and where I met my wife and I didn't get around to playing it for like
> 2 yrs, because of bad links...
>
> Thanks for your help and keep em coming! :)
>
> -Armin
>
>
> BC> HOLY CRAP!!! what is that first one??? a satellite connection????
Thats
> BC> the only thing that I have ever seen that gets ping times that bad
> BC> consistently.
>
> BC> Brian Cluff
>
> BC> Here's the results you requested....
>
> BC> [brian@napita brian]$ ping mume.pvv.org
> BC> PING fire.pvv.org (129.241.210.221): 56 data bytes
> BC> 64 bytes from 129.241.210.221: icmp_seq=0 ttl=234 time=1023.3 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=1 ttl=234 time=1004.9 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=2 ttl=234 time=1025.9 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=3 ttl=234 time=1029.0 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=4 ttl=234 time=1028.8 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=5 ttl=234 time=1012.7 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=6 ttl=234 time=986.7 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=7 ttl=234 time=990.2 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=8 ttl=234 time=977.6 ms
> BC> 64 bytes from 129.241.210.221: icmp_seq=9 ttl=234 time=972.1 ms
>
> BC> --- fire.pvv.org ping statistics ---
> BC> 11 packets transmitted, 10 packets received, 9% packet loss
> BC> round-trip min/avg/max = 972.1/1005.1/1029.0 ms