Well - for starters, if you get a prefix that was announced by ASN xxxx from [timestamp] to [timestamp], went to ASN yyyy on [timestamp] etc.
Quite useful if you want to tie this into route leak, prefix hijack, malicious ASN etc tracking tools. --srs On Wed, Jan 18, 2012 at 3:22 AM, Manish Karir <mka...@merit.edu> wrote: > > Hi Arturo, > > We could easily archive older copies of the database when we update the data, > but I think our issue right now > is that we dont fully understand how to add the notion of time to the user > interface and we dont understand how > folks might want to use it. Do you have a simple use case description of an > example which might help us > figure out how the notion of time can help answer a question.? What would be > an example of a query > that uses time? > > Thanks. > -manish > > > On Jan 16, 2012, at 12:53 PM, Arturo Servin wrote: > >> 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 >>> >> > > -- Suresh Ramasubramanian (ops.li...@gmail.com)
