BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
87.227.128.0/17
Announced exactly
- 87.227.128.0/17AS8717A1 Bulgaria EADRPKI Valid87.227.128.0
- Registry
- RIPE NCC · Bulgaria · Jul 12, 2005
- Delegated block
- 87.227.128.0 – 87.227.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 87.227.128.0/24AS29580A1 Bulgaria EADRPKI Valid87.227.128.0
- 87.227.129.0/24AS29580A1 Bulgaria EADRPKI Valid87.227.129.0
- 87.227.130.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.130.0
- 87.227.132.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.132.0
- 87.227.140.0/24AS59484SiS Net 05 EOODRPKI Valid87.227.140.0
- 87.227.141.0/24AS29580A1 Bulgaria EADRPKI Valid87.227.141.0
- 87.227.142.0/24AS29580A1 Bulgaria EADRPKI Valid87.227.142.0
- 87.227.143.0/24AS29580A1 Bulgaria EADRPKI Valid87.227.143.0
- 87.227.160.0/22AS29580A1 Bulgaria EADRPKI Valid87.227.160.0
- 87.227.164.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.164.0
- 87.227.166.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.166.0
- 87.227.168.0/24AS29580A1 Bulgaria EADRPKI Valid87.227.168.0
- 87.227.169.0/24AS29580A1 Bulgaria EADRPKI Valid87.227.169.0
- 87.227.170.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.170.0
- 87.227.172.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.172.0
- 87.227.174.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.174.0
- 87.227.178.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.178.0
- 87.227.180.0/22AS29580A1 Bulgaria EADRPKI Valid87.227.180.0
- 87.227.184.0/21AS29580A1 Bulgaria EADRPKI Valid87.227.184.0
- 87.227.194.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.194.0
- 87.227.196.0/22AS29580A1 Bulgaria EADRPKI Valid87.227.196.0
- 87.227.200.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.200.0
- 87.227.202.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.202.0
- 87.227.206.0/24AS12962First Investment Bank ADRPKI Valid87.227.206.0
- 87.227.208.0/21AS29580A1 Bulgaria EADRPKI Valid87.227.208.0
- 87.227.218.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.218.0
- 87.227.220.0/22AS29580A1 Bulgaria EADRPKI Valid87.227.220.0
- 87.227.224.0/21AS29580A1 Bulgaria EADRPKI Valid87.227.224.0
- 87.227.232.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.232.0
- 87.227.234.0/23AS29580A1 Bulgaria EADRPKI Valid87.227.234.0
- 87.227.236.0/22AS29580A1 Bulgaria EADRPKI Valid87.227.236.0
- 87.227.240.0/20AS29580A1 Bulgaria EADRPKI Valid87.227.240.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.