BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
176.14.0.0/15
Announced exactly
- 176.14.0.0/15AS8402PJSC "Vimpelcom"RPKI Not found176.14.0.0
- Registry
- RIPE NCC · Russia · May 18, 2011
- Delegated block
- 176.14.0.0 – 176.15.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 176.14.0.0/16AS16345PJSC "Vimpelcom"RPKI Not found176.14.0.0
- 176.15.0.0/17AS16345PJSC "Vimpelcom"RPKI Not found176.15.0.0
- 176.15.128.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.128.0
- 176.15.129.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.129.0
- 176.15.130.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.130.0
- 176.15.131.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.131.0
- 176.15.132.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.132.0
- 176.15.133.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.133.0
- 176.15.134.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.134.0
- 176.15.135.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.135.0
- 176.15.136.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.136.0
- 176.15.137.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.137.0
- 176.15.140.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.140.0
- 176.15.141.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.141.0
- 176.15.142.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.142.0
- 176.15.143.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.143.0
- 176.15.144.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.144.0
- 176.15.150.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.150.0
- 176.15.151.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.151.0
- 176.15.161.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.161.0
- 176.15.162.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.162.0
- 176.15.163.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.163.0
- 176.15.164.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.164.0
- 176.15.166.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.166.0
- 176.15.168.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.168.0
- 176.15.169.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.169.0
- 176.15.170.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.170.0
- 176.15.171.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.171.0
- 176.15.172.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.172.0
- 176.15.173.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.173.0
- 176.15.174.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.174.0
- 176.15.175.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.175.0
- 176.15.176.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.176.0
- 176.15.178.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.178.0
- 176.15.179.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.179.0
- 176.15.180.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.180.0
- 176.15.181.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.181.0
- 176.15.182.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.182.0
- 176.15.183.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.183.0
- 176.15.185.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.185.0
- 176.15.186.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.186.0
- 176.15.187.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.187.0
- 176.15.188.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.188.0
- 176.15.189.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.189.0
- 176.15.190.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.190.0
- 176.15.191.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.191.0
- 176.15.192.0/21AS16345PJSC "Vimpelcom"RPKI Not found176.15.192.0
- 176.15.200.0/21AS16345PJSC "Vimpelcom"RPKI Not found176.15.200.0
- 176.15.208.0/21AS16345PJSC "Vimpelcom"RPKI Not found176.15.208.0
- 176.15.216.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.216.0
- 176.15.217.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.217.0
- 176.15.218.0/23AS42842PJSC "Vimpelcom"RPKI Not found176.15.218.0
- 176.15.218.0/24AS42842PJSC "Vimpelcom"RPKI Not found176.15.218.0
- 176.15.219.0/24AS42842PJSC "Vimpelcom"RPKI Not found176.15.219.0
- 176.15.220.0/22AS16345PJSC "Vimpelcom"RPKI Not found176.15.220.0
- 176.15.240.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.240.0
- 176.15.242.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.242.0
- 176.15.244.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.244.0
- 176.15.246.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.246.0
- 176.15.248.0/22AS16345PJSC "Vimpelcom"RPKI Not found176.15.248.0
- 176.15.252.0/23AS16345PJSC "Vimpelcom"RPKI Not found176.15.252.0
- 176.15.254.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.254.0
- 176.15.255.0/24AS16345PJSC "Vimpelcom"RPKI Not found176.15.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.