BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
95.24.0.0/13
Announced exactly
- 95.24.0.0/13AS8402PJSC "Vimpelcom"RPKI Not found95.24.0.0
- Registry
- RIPE NCC · Russia · Oct 10, 2008
- Delegated block
- 95.24.0.0 – 95.31.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 95.24.0.0/15AS8402PJSC "Vimpelcom"RPKI Not found95.24.0.0
- 95.24.0.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.0.0
- 95.24.4.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.4.0
- 95.24.8.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.8.0
- 95.24.12.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.12.0
- 95.24.16.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.16.0
- 95.24.20.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.20.0
- 95.24.24.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.24.0
- 95.24.28.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.28.0
- 95.24.32.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.32.0
- 95.24.36.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.36.0
- 95.24.40.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.40.0
- 95.24.44.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.44.0
- 95.24.48.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.48.0
- 95.24.52.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.52.0
- 95.24.56.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.56.0
- 95.24.60.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.60.0
- 95.24.64.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.64.0
- 95.24.68.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.68.0
- 95.24.72.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.72.0
- 95.24.76.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.76.0
- 95.24.80.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.80.0
- 95.24.84.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.84.0
- 95.24.88.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.88.0
- 95.24.92.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.92.0
- 95.24.96.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.96.0
- 95.24.100.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.100.0
- 95.24.104.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.104.0
- 95.24.108.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.108.0
- 95.24.112.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.112.0
- 95.24.116.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.116.0
- 95.24.120.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.120.0
- 95.24.124.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.124.0
- 95.24.128.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.128.0
- 95.24.136.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.136.0
- 95.24.140.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.140.0
- 95.24.144.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.144.0
- 95.24.148.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.148.0
- 95.24.152.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.152.0
- 95.24.156.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.156.0
- 95.24.160.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.160.0
- 95.24.164.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.164.0
- 95.24.168.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.168.0
- 95.24.172.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.172.0
- 95.24.176.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.176.0
- 95.24.180.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.180.0
- 95.24.184.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.184.0
- 95.24.188.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.188.0
- 95.24.192.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.192.0
- 95.24.196.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.196.0
- 95.24.200.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.200.0
- 95.24.204.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.204.0
- 95.24.208.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.208.0
- 95.24.212.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.24.212.0
- 95.25.0.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.0.0
- 95.25.2.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.2.0
- 95.25.4.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.4.0
- 95.25.6.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.6.0
- 95.25.8.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.8.0
- 95.25.10.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.10.0
- 95.25.12.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.12.0
- 95.25.16.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.16.0
- 95.25.20.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.20.0
- 95.25.24.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.24.0
- 95.25.28.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.28.0
- 95.25.32.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.32.0
- 95.25.36.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.36.0
- 95.25.38.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.38.0
- 95.25.40.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.40.0
- 95.25.42.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.42.0
- 95.25.44.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.44.0
- 95.25.46.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.46.0
- 95.25.48.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.48.0
- 95.25.52.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.52.0
- 95.25.56.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.56.0
- 95.25.60.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.60.0
- 95.25.64.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.64.0
- 95.25.68.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.68.0
- 95.25.72.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.72.0
- 95.25.74.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.74.0
- 95.25.76.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.76.0
- 95.25.78.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.78.0
- 95.25.80.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.80.0
- 95.25.82.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.82.0
- 95.25.84.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.84.0
- 95.25.86.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.86.0
- 95.25.88.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.88.0
- 95.25.90.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.90.0
- 95.25.92.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.92.0
- 95.25.94.0/23AS8402PJSC "Vimpelcom"RPKI Not found95.25.94.0
- 95.25.96.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.96.0
- 95.25.100.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.100.0
- 95.25.104.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.104.0
- 95.25.108.0/22AS8402PJSC "Vimpelcom"RPKI Not found95.25.108.0
- 95.25.112.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.112.0
- 95.25.114.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.114.0
- 95.25.116.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.116.0
- 95.25.118.0/23AS42110PJSC "Vimpelcom"RPKI Not found95.25.118.0
- 95.25.120.0/22AS3216PJSC "Vimpelcom"RPKI Not found95.25.120.0
- 95.25.124.0/22AS3216PJSC "Vimpelcom"RPKI Not found95.25.124.0
Showing the first 100.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.