RIPE database query for a route object, or why my network is not advertised


via BGP to the world wordpress_id: 2027 category: Cisco tags: Cisco, Linux


Once it was a nice-to-have configuration that most ISPs in the world ignored anyway, but today it is a must if you are planning to advertise your networks via BGP through your uplink provider - your route object in the AS whois database of the uplink provider. If not - you will happily advertise your networks, the uplink provider will duly advertise them to its uplink peers, which will check AS registry database of your provider and not finding this route object will silently drop the advertising.
Of course it is duty of your transit ISP provider to update their records with your network, but after all, you are the one most interested - so as they say in Russian " Доверяй но проверяй " , and here is how to do it:
whois -h whois.ripe.net -- '-a -r -i or -T route AS1680' | grep route
In this example I assume your uplink provider is Netvision with AS1680 , replace AS number with the correct one. Output will look like:

route:          109.186.0.0/16
route:          109.253.0.0/16
route:          117.121.245.0/24
route:          138.134.0.0/16
route:          147.161.0.0/16
...

If you don't find in such listing your network - Houston, you have a problem here.