BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
87.97.128.0/17
Announced exactly
- 87.97.128.0/17AS8717A1 Bulgaria EADRPKI Valid87.97.128.0
- Registry
- RIPE NCC · Bulgaria · Aug 8, 2005
- Delegated block
- 87.97.128.0 – 87.97.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 87.97.128.0/21AS13124A1 Bulgaria EADRPKI Valid87.97.128.0
- 87.97.128.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.128.0
- 87.97.129.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.129.0
- 87.97.130.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.130.0
- 87.97.131.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.131.0
- 87.97.132.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.132.0
- 87.97.133.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.133.0
- 87.97.134.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.134.0
- 87.97.135.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.135.0
- 87.97.136.0/21AS13124A1 Bulgaria EADRPKI Valid87.97.136.0
- 87.97.144.0/20AS13124A1 Bulgaria EADRPKI Valid87.97.144.0
- 87.97.160.0/22AS8717A1 Bulgaria EADRPKI Valid87.97.160.0
- 87.97.160.0/24AS29580A1 Bulgaria EADRPKI Valid87.97.160.0
- 87.97.161.0/24AS29580A1 Bulgaria EADRPKI Valid87.97.161.0
- 87.97.162.0/24AS29580A1 Bulgaria EADRPKI Valid87.97.162.0
- 87.97.163.0/24AS29580A1 Bulgaria EADRPKI Valid87.97.163.0
- 87.97.164.0/22AS13124A1 Bulgaria EADRPKI Valid87.97.164.0
- 87.97.164.0/23AS13124A1 Bulgaria EADRPKI Valid87.97.164.0
- 87.97.166.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.166.0
- 87.97.168.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.168.0
- 87.97.169.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.169.0
- 87.97.170.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.170.0
- 87.97.171.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.171.0
- 87.97.172.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.172.0
- 87.97.173.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.173.0
- 87.97.174.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.174.0
- 87.97.175.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.175.0
- 87.97.176.0/23AS13124A1 Bulgaria EADRPKI Valid87.97.176.0
- 87.97.178.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.178.0
- 87.97.179.0/24AS29580A1 Bulgaria EADRPKI Valid87.97.179.0
- 87.97.180.0/23AS13124A1 Bulgaria EADRPKI Valid87.97.180.0
- 87.97.182.0/23AS13124A1 Bulgaria EADRPKI Valid87.97.182.0
- 87.97.184.0/22AS13124A1 Bulgaria EADRPKI Valid87.97.184.0
- 87.97.188.0/23AS13124A1 Bulgaria EADRPKI Valid87.97.188.0
- 87.97.190.0/23AS13124A1 Bulgaria EADRPKI Valid87.97.190.0
- 87.97.192.0/18AS13124A1 Bulgaria EADRPKI Valid87.97.192.0
- 87.97.192.0/19AS13124A1 Bulgaria EADRPKI Valid87.97.192.0
- 87.97.192.0/20AS13124A1 Bulgaria EADRPKI Valid87.97.192.0
- 87.97.208.0/21AS13124A1 Bulgaria EADRPKI Valid87.97.208.0
- 87.97.216.0/21AS13124A1 Bulgaria EADRPKI Valid87.97.216.0
- 87.97.224.0/19AS13124A1 Bulgaria EADRPKI Valid87.97.224.0
- 87.97.224.0/21AS13124A1 Bulgaria EADRPKI Valid87.97.224.0
- 87.97.232.0/21AS13124A1 Bulgaria EADRPKI Valid87.97.232.0
- 87.97.240.0/23AS29580A1 Bulgaria EADRPKI Valid87.97.240.0
- 87.97.242.0/23AS29580A1 Bulgaria EADRPKI Valid87.97.242.0
- 87.97.244.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.244.0
- 87.97.245.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.245.0
- 87.97.246.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.246.0
- 87.97.247.0/24AS13124A1 Bulgaria EADRPKI Valid87.97.247.0
- 87.97.248.0/22AS13124A1 Bulgaria EADRPKI Valid87.97.248.0
- 87.97.252.0/22AS13124A1 Bulgaria EADRPKI Valid87.97.252.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.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.