X-no-Archive:yes
I guess the subject says it all. But after a disruption of Internet access
(courtesy of a well-known upstream provider), I'm wondering what else might
be disrupted. It looks like the problem is there, not here. Perhaps another
rolling blackout?

My client cannot transmit, and in fact has not been able to for more than a
day (but some of that was local trouble). I also cannot view their web page.
So...

C:\>tracert setiathome.ssl.berkeley.edu

Tracing route to milkyway.ssl.berkeley.edu [128.32.18.165]
over a maximum of 30 hops:

  1   <10 ms    10 ms   <10 ms  172.17.136.7
  2   <10 ms   <10 ms   <10 ms  172.17.130.1
  3   <10 ms     *      <10 ms  10.24.0.2
  4   <10 ms   <10 ms    10 ms  12.30.57.193
  5    20 ms    20 ms    10 ms  12.126.98.165
  6   <10 ms    30 ms    11 ms  gbr2-a31s3.cb1ma.ip.att.net [12.127.5.42]
  7    60 ms    40 ms    40 ms  gbr3-p80.cb1ma.ip.att.net [12.122.5.61]
  8    10 ms    10 ms    30 ms  gbr4-p10.n54ny.ip.att.net [12.122.2.13]
  9    10 ms    10 ms    10 ms  gbr3-p60.n54ny.ip.att.net [12.122.1.121]
 10    20 ms    10 ms    20 ms  gbr3-p10.wswdc.ip.att.net [12.122.3.54]
 11    10 ms    20 ms    30 ms  ggr1-p360.wswdc.ip.att.net [12.123.9.49]
 12    30 ms    20 ms    30 ms  acr1-serial2-0-0-0.Washingtondck.cw.net
[206.24.
227.201]
 13   140 ms   141 ms    90 ms  acr1-loopback.SanFranciscosfd.cw.net
[206.24.210
.61]
 14   140 ms   120 ms   101 ms  cenic.SanFranciscosfd.cw.net
[206.24.211.134]
 15   100 ms   130 ms   130 ms  BERK-7507--BERK.POS.calren2.net
[198.32.249.69]

 16  pos1-0.inr-000-eva.Berkeley.EDU [128.32.0.89]  reports: Destination
host un
reachable.

Trace complete.

C:\>ping -n 1 setiathome.ssl.berkeley.edu

Pinging milkyway.ssl.berkeley.edu [128.32.18.165] with 32 bytes of data:

Reply from 128.32.0.89: Destination host unreachable.

C:\>ping -a -n 1 128.32.0.89

Pinging pos1-0.inr-000-eva.berkeley.edu [128.32.0.89] with 32 bytes of data:

Greg Stigers
http://www.cgiusa.com
some email clients remove an OT: on replies.