Sprint (1239) blackhole ? Or bogus /32 route ?

Thu Sep 26 17:56:43 UTC 2002

Thanks to all who have responding with information from their network 
vantage point.  It does indeed seem to be an IGP or blackholing issue 
inside of Sprint. In the interim I made an advertising change to hopefully 
minimize the impact until I hear from someone at Sprint as to what the 
issue is.

         ---Mike

At 01:35 PM 26/09/2002 -0400, Mike Tancsa wrote:

>At 01:31 PM 26/09/2002 -0400, Vinny Abello wrote:
>>Looks like something isn't right... I see the announcement from Sprint 
>>with an AS path of 1239 852 11647, but it never gets past one of the 
>>routers on Sprint's network. I have no problem going through Cable and 
>>Wireless:
>
>Yes, and the strange thing is that is just one IP address :-( 
>199.212.134.9... If you try 199.212.134.1 I bet you can get to it via sprint.
>
>
>>Type escape sequence to abort.
>>Tracing the route to smtp2.sentex.ca (199.212.134.9)
>>
>>   1 63-121-101-106.focaldata.net (63.121.101.106) [AS 18984] 0 msec 0 
>> msec 0 msec
>>   2 acr2-so-3-3-0.newyork.cw.net (206.24.193.153) [AS 3561] 0 msec 4 
>> msec 0 msec
>>   3 agr4-loopback.newyork.cw.net (206.24.194.104) [AS 3561] 4 msec 0 msec
>>     agr3-loopback.newyork.cw.net (206.24.194.103) [AS 3561] 4 msec
>>   4 dcr1-so-7-2-0.newyork.cw.net (206.24.207.73) [AS 3561] 4 msec
>>     dcr1-so-6-2-0.newyork.cw.net (206.24.207.57) [AS 3561] 0 msec
>>     dcr1-so-7-3-0.newyork.cw.net (206.24.207.77) [AS 3561] 4 msec
>>   5 telus-services-inc.newyork.cw.net (206.24.207.90) [AS 3561] 24 msec 
>> 24 msec 20 msec
>>   6 toroonnlbr00.bb.telus.com (154.11.11.130) [AS 852] 20 msec 24 msec 
>> 20 msec
>>   7 toroonzddr00.bb.telus.com (154.11.6.67) [AS 852] 24 msec 24 msec 20 msec
>>   8 peer.toroonzddr00.bb.telus.com (209.115.141.5) [AS 852] 28 msec 28 
>> msec 32 msec
>>   9 iolite.sentex.ca (209.112.4.3) [AS 15290] 24 msec 24 msec 24 msec
>>  10 smtp2.sentex.ca (199.212.134.9) [AS 11647] 28 msec 24 msec 32 msec
>>
>>I would contact Sprint. Good luck!
>
>Thanks, I did.  Responder robot said they would try to get back to me in 
>72hrs :-(
>
>         ---Mike
>