It appears berkeley is off the air. These two links show the data rates on
the lines going into them. The first one is for the data server and the
second is the line to the home page. Looks like berkeley fell into the
pacific.

http://cricket.berkeley.edu:8885/inr-668-interfaces.html

http://cricket.berkeley.edu:8885/inr-60-interfaces.html
"Robi" <me@privacy.net> wrote in message
news:bp6qa1$1la51e$1@ID-211961.news.uni-berlin.de...

[crosspost alt.sci.seti, sci.astro.seti]

Am I the only one having trouble accessing the SETI @ Home website
http://setiathome.ssl.berkeley.edu/ [128.32.18.151]?


--- reading URL http://setiathome.ssl.berkeley.edu/
--- contacting host setiathome.ssl.berkeley.edu [128.32.18.151] on port 80

--- error: timed out


$ ping setiathome.ssl.berkeley.edu

Pinging setiathome.ssl.berkeley.edu [128.32.18.151] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 128.32.18.151:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms



--- traceroute to setiathome.ssl.berkeley.edu [128.32.18.151],
    30 hops max, 18 byte packets

[...]
  7  [    12.123.9.85]  ggr2-p390.wswdc.ip.att.net  109 ms
  8  [209.244.219.141]  so-2-0-0.edge1.Washington1.Level3.net  41 ms
  9  [  209.244.11.13]  so-5-0-0.gar2.Washington1.Level3.net  41 ms
 10  [   64.159.1.157]  so-0-0-0.bbr1.LosAngeles1.level3.net  109 ms
 11  [  209.247.9.142]  unknown.Level3.net  96 ms
 12  [ 209.244.10.254]  gigabitethernet4-2.ipcolo1.LosAngeles1.Level3.net

83 ms

 13  [  64.156.191.10]  unknown.Level3.net  83 ms
 14  [ 137.164.24.142]  inet-ucb--lax-isp.cenic.net  96 ms
 15  [   128.32.0.251]  vlan194.inr-202-doecev.Berkeley.EDU  82 ms
 16.  *
[...]
 30.  *

--- host unreachable
--- traceroute statistics for setiathome.ssl.berkeley.edu
    30 packets transmitted, 15 received
    round-trip time (ms) min 41, avg 92, max 178



-- 
Robi
(2.9#@ 2.77 yrs)