Looks like its working now (on FIOS anyway) Curious to know why the major networks stopped seeing it yesterday as well.
On Thu, Nov 27, 2014 at 12:45 AM, Courtney Smith <[email protected]> wrote: > > > No problem here in Los Angeles either, but seeing a lone route through > Atrato only. > > > > flags destination gateway lpref med aspath origin > > *> 194.71.107.0/24 <> 100 0 3491 5580 39138 22351 2.207 > 51040 i > > * 194.71.107.0/24 <> 100 0 174 5580 39138 22351 > 2.207 51040 i > > > > > > On 11/27/2014 午前 11:24, Tony Wicks wrote: > >> > >> No problem here in New Zealand > >> > >> tonyw@vrhost1-w> show route 194.71.107.0/24 > >> > >> icore1-w.inet.0: 519451 destinations, 525214 routes (519437 active, 14 > >> holddown, 0 hidden) > >> + = Active Route, - = Last Active, * = Both > >> > >> 194.71.107.0/24 *[BGP/170] 10:25:44, MED 0, localpref 90 > >> AS path: 4826 5580 39138 22351 131279 51040 I, > >> validation-state: unverified > >> > to 175.45.102.9 via ae1.526 > >> > > Hopefully the body cones thru this time. The issue isn't city or country > based. In my last post I pointed out the do not announce to peers > community AS5580 was sending to Cogent, Level3 and who knows who else. So > any ASN that is not a customer of Cogent or Level3 wont learn the 5580 path > from them. > > When I checked a few hours ago, Comcast, Centurylink, AT&T, TATA, and > possibly Sprint were not seeing the /24 based on their public looking > glasses or route servers. Have not had time to run bgplay to see if > routeviews data shows how they previously saw the /24 in past 30 days. > Finding the ASN(s) they used to see from would shed light on why they > stopped seeing. Checking bgplay and contacting AS51040 to reach out to > their upstreams is my suggestion.
