Re: uunet/packbell problems in the bay area

[Nick Feamster <feamster () lcs mit edu>]

Here are the traces we saw on Friday (we heard 3 withdrawals on Friday
afternoon from this prefix) --

||131.106.0.0/16|131.106.0.1|1003524418||
traceroute to 131.106.0.1 (131.106.0.1), 30 hops max, 40 byte packets
 1  18.31.0.1  110 ms  111 ms  33 ms
 2  18.24.10.3  108 ms  108 ms  68 ms
 3  18.201.1.1  300 ms  143 ms  35 ms
 4  18.168.0.18  179 ms  194 ms  116 ms
 5  * * *
 6  * * *
 7  * * *
....

||131.106.0.0/16|131.106.0.1|1003535393||
traceroute to 131.106.0.1 (131.106.0.1), 30 hops max, 40 byte packets
 1  18.31.0.1  12 ms  8 ms  1 ms
 2  18.24.10.3  51 ms  2 ms  8 ms
 3  18.201.1.1  65 ms  50 ms  270 ms
 4  18.168.0.18  8 ms  10 ms  17 ms
 5  * * *
 6  * * *
 7  * * *
....


||131.106.0.0/16|131.106.0.1|1003537252||
traceroute to 131.106.0.1 (131.106.0.1), 30 hops max, 40 byte packets
 1  18.31.0.1  4 ms  141 ms  34 ms
 2  18.24.10.3  41 ms  38 ms  5 ms
 3  18.201.1.1  17 ms  10 ms  14 ms
 4  18.168.0.18  12 ms  12 ms  4 ms
 5  4.1.80.9  6 ms  7 ms  6 ms
 6  4.1.80.6  6 ms  6 ms  7 ms
 7  4.0.6.246  6 ms  10 ms  8 ms
 8  4.24.10.218  6 ms  9 ms  8 ms
 9  4.24.6.50  12 ms  13 ms  13 ms
10  4.24.8.170  12 ms  11 ms  14 ms
11  4.0.6.142  15 ms  17 ms  13 ms
12  152.63.18.222  12 ms  12 ms  13 ms
13  152.63.23.133  14 ms  15 ms  13 ms
14  152.63.146.82  88 ms  88 ms  89 ms
15  152.63.54.9  89 ms  87 ms  87 ms
16  152.63.54.2  90 ms  89 ms  89 ms
17  152.63.50.14  90 ms  89 ms  90 ms
18  146.188.148.165  97 ms  95 ms  89 ms
19  146.188.148.165  95 ms !A *  95 ms !A





On Fri, 19 Oct 2001, Brian Whalen wrote:

> 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