The more specific objects are more cosmetic issue. The main problem is the missing object for your /22. As well as your AS23034 does not seem to be listed in AS-ROGERS:AS-CUSTOMERS http://bgp.he.net/AS812#_irr
Karsten 2014-09-18 23:54 GMT+02:00 Brock Massel <[email protected]>: > Karsten, > Thank you I am not sure why those 702 and 19294 old entries would still be > there. > > We have engaged 812 for help. > > Shall I assume cleaning up the old entries will solve the problems? > > > > -----Original Message----- > From: Karsten Elfenbein [mailto:[email protected]] > Sent: Thursday, September 18, 2014 5:46 PM > To: Brock Massel > Cc: [email protected] > Subject: Re: 192.250.24.0/22 (as 23034) not reachable from Verizon, tinet, > global crossing, XO > > Hi, > > looks like you mainly use one transit provider (AS812) or your other transit > providers correctly filter that prefix. > > According to > https://stat.ripe.net/data/prefix-routing-consistency/data.json?preferred_version=0.7&resource=192.250.24.0%2F22 > there is no route object for the 192.250.24.0/22. > As a result the AS6453(TATA COMMUNICATIONS (AMERICA) INC) seemed to have > started filtering the prefix from AS812. Which reduced the visibility of that > prefix. Check the BGplay from the last days: > https://stat.ripe.net/192.250.24.0%2F22#tabId=routing > > so create the correct route object and the prefix should come up over the > next day(s) > > Also get the more specific route objects removed which point to other AS. > > 192.250.24.0/23 AS702 > 192.250.24.0/24 AS19294 > > > > Karsten > > 2014-09-18 22:42 GMT+02:00 Brock Massel <[email protected]>: >> Hi folks, >> I'm hoping someone can shed some light on the situation. >> >> The 192.250.24 addresses have been reachable for several months in the >> current configuration with no reported issues. Since the 16th we have been >> hearing reports that destinations in that block are unavailable for some. >> >> Several looking glass' report network not in table. >> >> Can someone lend a hand? What is the best way to improve this situation? How >> do we find where the problem is? >> >> B >
