Hi all,
we've just released some new tools for RIS, which may also benefit
you :)
The most notable change is the introduction of the AS dashboard and
prefix dashboard. These dashboards show an overview of most
information RIS has about an AS or prefix. For ASes, think prefixes,
age of prefixes, transits, old bogon filters. For prefixes, think
visibility and stability.
Besides this, we have made improvements to the search, prefixinuse
and asinuse tools.
- The search can now summarise updates for a clearer view of events
- Prefixinuse now also displays prefixes from a block that are 'free'
and shows what
percentage of space is still unannounced
- ASinuse should run faster
Focus with these improvements is to improve the presentation of the
data, making more data available in a clearer and more attractive way.
For example, see the prefix dashboard of the RIPE meeting network
prefix, which had some reachability problems:
http://www.ris.ripe.net/dashboard/193.0.8.0/22
The prefix graph for 3333, our office network, nicely shows the build-
up of our prefixes: http://www.ris.ripe.net/dashboard/3333
It also shows our transits, although this is difficult to estimate
and wrong in some cases.
The k-root dashboard shows an /28 in the prefix list - seen by two
peers. The prefix graph is also quite nice: http://www.ris.ripe.net/
dashboard/25152
If you check/uncheck the "strip prepending" box on the AS path
lengths tab, you can clearly see the prepending done by k-root.
The dashboards for the k-root anycast prefixes also show something
interesting:
http://www.ris.ripe.net/dashboard/193.0.14.0/24http://www.ris.ripe.net/dashboard/193.0.14.0/23
If you look at the "list of peers not seeing the prefix" below the
map, you can see 20932 doesn't send the /24, and 26943 doesn't send
either.
Note that there still is a small bug in the AS dashboard - it shows a
prefix has stopped being announced in some cases when it is not.
These tools are public now, so feel free to tell others. However, we
are not doing an external announcement until the RIPE meeting, to
prevent everyone from already knowing most things we'll say in the
RIS update. So, don't shout around on lists/websites/etc. yet.
Obviously, if you have any ideas, let us know.
cheers,
--
Erik Romijn RIPE NCC software engineer
http://www.ripe.net/ Information Services dept.
