Can you be more specific? Firefox directed me to a Debian Security information page.
Shambhala:~$ ping 130.89.175.54 PING 130.89.175.54 (130.89.175.54): 56 data bytes 64 bytes from 130.89.175.54: icmp_seq=0 ttl=50 time=185.875 ms 64 bytes from 130.89.175.54: icmp_seq=1 ttl=50 time=186.113 ms 64 bytes from 130.89.175.54: icmp_seq=2 ttl=50 time=188.160 ms 64 bytes from 130.89.175.54: icmp_seq=3 ttl=50 time=184.258 ms 64 bytes from 130.89.175.54: icmp_seq=4 ttl=50 time=187.370 ms 64 bytes from 130.89.175.54: icmp_seq=5 ttl=50 time=187.952 ms 64 bytes from 130.89.175.54: icmp_seq=6 ttl=50 time=200.035 ms 64 bytes from 130.89.175.54: icmp_seq=7 ttl=50 time=186.768 ms 64 bytes from 130.89.175.54: icmp_seq=8 ttl=50 time=189.537 ms ^C --- 130.89.175.54 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max/stddev = 184.258/188.452/200.035/4.338 ms Shambhala:~$ traceroute 130.89.175.54 traceroute to 130.89.175.54 (130.89.175.54), 64 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 5.108 ms 2.272 ms 3.337 ms 2 * * * 3 ge-3-8-ur01.bellevue.wa.seattle.comcast.net (68.85.241.97) 167.503 ms 13.891 ms 47.210 ms 4 te-9-3-ur02.bellevue.wa.seattle.comcast.net (68.86.96.70) 11.095 ms 11.783 ms 13.350 ms 5 te-8-3-ar02.seattle.wa.seattle.comcast.net (68.86.96.73) 15.524 ms 22.418 ms 13.693 ms 6 * te-9-1-ar02.seattle.wa.seattle.comcast.net (68.86.90.210) 18.534 ms * 7 * * * 8 TenGigabitethernet1-4.ar5.SEA1.gblx.net (64.209.111.93) 14.211 ms 23.079 ms 22.895 ms 9 64.209.105.158 (64.209.105.158) 185.252 ms 183.511 ms 187.024 ms 10 AF-500.XSR01.Amsterdam1A.surf.net (145.145.80.9) 198.528 ms 182.712 ms 195.694 ms 11 UTwente-router.Customer.surf.net (145.145.4.2) 192.900 ms 796.140 ms 200.269 ms 12 kassia.snt.utwente.nl (130.89.175.54) 185.290 ms 183.573 ms 184.676 ms http://samspade.org/whois/130.89.175.54 I'm on the West Coast (Seattle WA area) and am having no problems, however, a more specific description would help. my remote shell (somewhere in the US?) has no problems. [EMAIL PROTECTED]:~$ ping 130.89.175.54 PING 130.89.175.54 (130.89.175.54): 56 data bytes 64 bytes from 130.89.175.54: icmp_seq=0 ttl=56 time=128.403 ms 64 bytes from 130.89.175.54: icmp_seq=1 ttl=56 time=128.358 ms 64 bytes from 130.89.175.54: icmp_seq=2 ttl=56 time=128.259 ms 64 bytes from 130.89.175.54: icmp_seq=3 ttl=56 time=128.257 ms 64 bytes from 130.89.175.54: icmp_seq=4 ttl=56 time=128.537 ms --- 130.89.175.54 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 128.257/128.362/128.537/0.464 ms [EMAIL PROTECTED]:~$ traceroute 130.89.175.54 traceroute to 130.89.175.54 (130.89.175.54), 64 hops max, 40 byte packets 1 fa-0-24.ucg-as29.tpa.sagonet.net (66.111.62.1) 1.97 ms 0.897 ms 0.807 ms 2 ve20.core01a.tpa.sagonet.net (65.110.32.65) 0.579 ms 6.351 ms 0.651 ms 3 ge-2-1-0.403.ar2.TPA1.gblx.net (64.213.33.49) 1.48 ms 1.51 ms ge-2-1-0.402.ar2.TPA1.gblx.net (64.208.17.93) 1.113 ms 4 ge1-4-10G.ar2.AMS1.gblx.net (67.17.110.17) 128.144 ms 127.972 ms 128.116 ms 5 64.209.105.158 (64.209.105.158) 126.513 ms 126.900 ms 127.126 ms 6 AF-500.XSR01.Amsterdam1A.surf.net (145.145.80.9) 126.635 ms 126.824 ms 126.952 ms 7 UTwente-router.Customer.surf.net (145.145.4.2) 124.643 ms 123.743 ms 124.203 ms 8 kassia.snt.utwente.nl (130.89.175.54) 128.779 ms 128.382 ms 128.241 ms I'd wager the problem is localized to you unless you're having some sort of serious security related issue with the mirror that we need to all be worried about. Good luck :D -rb On Tue, Jun 17, 2008 at 1:38 PM, Bob Tanner <[EMAIL PROTECTED]> wrote: > Last several days I'm having problems accessing 130.89.175.54, a server in > the security.debian.org rotation. > > This is from systems across the midwest of America. > > Is there a known problem with this host? > > Just my network and systems? > > -- > Bob Tanner <[EMAIL PROTECTED]> | Phone : (952)943-8700 > http://www.real-time.com, Debian Linux, OSX | Fax : (952)943-8500 > Key fingerprint = F785 DDFC CF94 7CE8 AA87 3A9D 3895 26F1 0DDB E378 > > > > > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
