BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
84.252.0.0/18
Announced exactly
- 84.252.0.0/18AS8717A1 Bulgaria EADRPKI Valid84.252.0.0
- Registry
- RIPE NCC · Bulgaria · Sep 8, 2004
- Delegated block
- 84.252.0.0 – 84.252.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 84.252.1.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.1.0
- 84.252.2.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.2.0
- 84.252.3.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.3.0
- 84.252.4.0/22AS13124A1 Bulgaria EADRPKI Valid84.252.4.0
- 84.252.8.0/23AS13124A1 Bulgaria EADRPKI Valid84.252.8.0
- 84.252.10.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.10.0
- 84.252.11.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.11.0
- 84.252.12.0/23AS13124A1 Bulgaria EADRPKI Valid84.252.12.0
- 84.252.14.0/24AS29580A1 Bulgaria EADRPKI Valid84.252.14.0
- 84.252.15.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.15.0
- 84.252.16.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.16.0
- 84.252.17.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.17.0
- 84.252.18.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.18.0
- 84.252.19.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.19.0
- 84.252.20.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.20.0
- 84.252.21.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.21.0
- 84.252.22.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.22.0
- 84.252.23.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.23.0
- 84.252.24.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.24.0
- 84.252.25.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.25.0
- 84.252.26.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.26.0
- 84.252.27.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.27.0
- 84.252.28.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.28.0
- 84.252.29.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.29.0
- 84.252.30.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.30.0
- 84.252.31.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.31.0
- 84.252.32.0/21AS13124A1 Bulgaria EADRPKI Valid84.252.32.0
- 84.252.40.0/23AS12716A1 Bulgaria EADRPKI Valid84.252.40.0
- 84.252.42.0/23AS13124A1 Bulgaria EADRPKI Valid84.252.42.0
- 84.252.44.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.44.0
- 84.252.45.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.45.0
- 84.252.46.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.46.0
- 84.252.47.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.47.0
- 84.252.52.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.52.0
- 84.252.53.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.53.0
- 84.252.54.0/24AS13124A1 Bulgaria EADRPKI Valid84.252.54.0
- 84.252.55.0/24AS202043Bulgarian Industrial Association, Union of Bulgarian businessRPKI Valid84.252.55.0
- 84.252.56.0/22AS13124A1 Bulgaria EADRPKI Valid84.252.56.0
- 84.252.60.0/22AS13124A1 Bulgaria EADRPKI Valid84.252.60.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.