|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: CW....also CNN
We saw these same problems this morning, on some addresses that are multihomed to CW and UUNet. UUNet recommended we announce our addresses with longer prefixes for a few minutes, then withdraw the announcements. Don't know why it worked, but it did... Anyways, might be worth a try if you're getting hosed by this. -------Scott. >> Traffic from me to best.com looks like: >> >> traceroute to shell4.ba.best.com (206.184.139.135), 30 hops max, 40 byte packets >> 1 eth-0.cisco-1.intur.net (206.97.151.1) 2.106 ms 2.073 ms 2.088 ms >> 2 border1-serial3-0.Dallas.cw.net (204.70.115.41) 72.321 ms 16.649 ms 203.451 ms >> 3 core1-fddi-0.Dallas.cw.net (204.70.114.17) 4.789 ms 5.113 ms 10.839 ms >> 4 bordercore1.SanFrancisco.cw.net (166.48.12.1) 72.705 ms 42.307 ms 41.859 ms >> 5 best-internet.SanFrancisco.cw.net (166.48.13.250) 1001.36 ms 1052.2 ms 1010.41 ms >> 6 core1-hssi8-0-0.mv.best.net (206.86.228.89) 979.218 ms 1007.01 ms 1000.45 ms >> 7 shell4.ba.best.com (206.184.139.135) 1013.52 ms * 1018.15 ms > > This is still quest yes, the routes are getting from qwest to sprint >then going on to uu.net.. it looks like its only happening in la tho.. maybe >a bad filter? > > At this time I'm not seeing anyone leaking routes to me, including >sprint. > >-- >Steven O. Noble -- Sr. Backbone Engineer, Exodus Communications (EXDS) > -- Work:408.346.2333 -- > All my love to the Canadian Mooing Frog. >
|