Thanks everyone, yes adding AS works...

Will it be updated to just accept 65000 without the "AS" in the near future?



> Subject: Re: ANNOUNCE: bgptables.merit.edu - understanding visibility of your 
> prefix/AS
> From: mka...@merit.edu
> Date: Mon, 16 Jan 2012 15:44:08 -0500
> CC: nanog@nanog.org
> To: brandon....@brandontek.com
> 
> 
> Please remember to add the "as" before the number for your query.
> so for AS 65000 your search term should be "as65000"
> 
> Thanks.
> -manish
> 
> 
> On Jan 16, 2012, at 3:19 PM, Brandon Kim wrote:
> 
> > I'm getting a database error when I search for an AS....
> > 
> > 
> > 
> > > Subject: Re: ANNOUNCE: bgptables.merit.edu - understanding visibility of 
> > > your prefix/AS
> > > From: arturo.ser...@gmail.com
> > > Date: Mon, 16 Jan 2012 15:53:51 -0200
> > > To: mka...@merit.edu
> > > CC: nanog@nanog.org
> > > 
> > > Manish,
> > > 
> > > Nice tool.
> > > 
> > > Is it possible to see the "history" of a prefix?
> > > 
> > > 
> > > Regards,
> > > ..as
> > > 
> > > 
> > > 
> > > On 13 Jan 2012, at 18:19, Manish Karir wrote:
> > > 
> > > > 
> > > > All,
> > > > 
> > > > We would like to announce the availability of the bgpTables Project at 
> > > > Merit at: http://bgptables.merit.edu
> > > > bgpTables allows users to easily navigate global routing table data 
> > > > collected via routviews.org. bgptables
> > > > essentially processes the data collected at routeviews and makes is 
> > > > available in a somewhat easier
> > > > to use interface. The goal of bgpTables is to represent global prefix 
> > > > and AS visibility information from the
> > > > vantage point of the various bgp table views as seen at routeviews. 
> > > > The data is currently updated nightly (EST) but we hope to improve this 
> > > > over time. 
> > > > Please see the FAQ (http://bgptables.merit.edu/faq.php) for some simple 
> > > > examples of how you can use bgpTables.
> > > > 
> > > > Some examples:
> > > > - You can query for a specific ASN by entering the text 'as' followed 
> > > > by the AS number into the search box. For example to query for 
> > > > information about AS 237 you would enter 'as237' [without quotation 
> > > > marks] into the search box and then click 'search'. You can then use 
> > > > the view navigator map to switch to different routing table views for 
> > > > this ASN
> > > > 
> > > > - You can query for a specific prefix by directly entering the prefix 
> > > > into the search box. For example to query for information about prefix 
> > > > 12.0.0.0/8 you would simply enter '12.0.0.0/8' [without quotation 
> > > > marks] into the search box and then click 'search'. You can then use 
> > > > the view navigator map to switch to different routing table views for 
> > > > the prefix.
> > > > 
> > > > - You can find a particular prefix that you might be interested in by 
> > > > running a 'contained within' query via the search box. For example to 
> > > > quickly browse a list of prefixes contained within 1.0.0.0/8 to find 
> > > > the particular prefix you might be interested in, you can enter the 
> > > > text 'cw1.0.0.0/8' [without quotation marks] into the search box and 
> > > > click 'search'. You can then browse the resulting table to select the 
> > > > particular prefix you might be interested in.
> > > > 
> > > > - You can simply enter the text 'as' followed by the company name into 
> > > > the search box then click search to view a list of possible matches for 
> > > > that text. For example, to view all matching google ASNs you can simply 
> > > > enter 'asgoogle' into the search box and click search. A list of 
> > > > possible matching ASNs that reference Google by name will be returned 
> > > > from which you an then select the particular ASN that is of interest to 
> > > > you.
> > > > 
> > > > 
> > > > Comments, corrections, and suggestions are very welcome. Please send 
> > > > them to mka...@merit.edu. Hopefully folks will find this useful.
> > > > 
> > > > Thanks.
> > > > -The Merit Network Research and Development Team
> > > > 
> > > 
> > > 
> 
                                          

Reply via email to