Traces there make it at least far enough to see what is up, pings to www.xinet.com are administratively blocked.. 7 ATM1-0.BR4.SAC1.ALTER.NET (204.255.168.9) 31.416 ms 56.005 ms 80.195 ms 8 0.so-2-2-0.XL1.SAC1.ALTER.NET (152.63.52.210) 43.215 ms 75.250 ms 29.105 ms 9 0.so-3-0-0.XR1.SAC1.ALTER.NET (152.63.53.238) 39.172 ms 41.411 ms 39.079 ms 10 285.ATM7-0.XR1.SFO1.ALTER.NET (152.63.50.6) 65.046 ms 76.507 ms 41.810 ms 11 187.ATM11-0-0.GW1.SFO1.ALTER.NET (146.188.148.169) 31.300 ms 80.824 ms 83.971 ms 12 berkeley.ca.alter.NET (131.106.1.252) 47.926 ms 60.922 ms 66.810 ms 13 131.106.1.42 (131.106.1.42) 73.529 ms !X * 145.362 ms !X ping www.xinet.com PING www.xinet.com (131.106.11.219): 56 data bytes 36 bytes from 131.106.1.42: Communication prohibited by filter Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 9d70 0 0000 f3 01 2cc2 myiphere 131.106.11.219 Brian "Sonic" Whalen Success = Preparation + Opportunity On Fri, 19 Oct 2001, Barb Dijker wrote:
Does anyone know the real story about a major outage in the bay area? For example, 131.106/16 is off the map and has been since Wed. ETR?
...Barb