BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
46.238.0.0/18
Announced exactly
- 46.238.0.0/18AS8717A1 Bulgaria EADRPKI Valid46.238.0.0
- Registry
- RIPE NCC · Bulgaria · Jan 31, 2011
- Delegated block
- 46.238.0.0 – 46.238.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 46.238.0.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.0.0
- 46.238.1.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.1.0
- 46.238.2.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.2.0
- 46.238.3.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.3.0
- 46.238.4.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.4.0
- 46.238.5.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.5.0
- 46.238.6.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.6.0
- 46.238.7.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.7.0
- 46.238.9.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.9.0
- 46.238.10.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.10.0
- 46.238.11.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.11.0
- 46.238.12.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.12.0
- 46.238.13.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.13.0
- 46.238.14.0/24AS8717A1 Bulgaria EADRPKI Valid46.238.14.0
- 46.238.15.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.15.0
- 46.238.16.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.16.0
- 46.238.17.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.17.0
- 46.238.18.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.18.0
- 46.238.19.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.19.0
- 46.238.20.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.20.0
- 46.238.21.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.21.0
- 46.238.22.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.22.0
- 46.238.23.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.23.0
- 46.238.24.0/23AS29580A1 Bulgaria EADRPKI Valid46.238.24.0
- 46.238.26.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.26.0
- 46.238.27.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.27.0
- 46.238.28.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.28.0
- 46.238.29.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.29.0
- 46.238.30.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.30.0
- 46.238.31.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.31.0
- 46.238.32.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.32.0
- 46.238.33.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.33.0
- 46.238.34.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.34.0
- 46.238.35.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.35.0
- 46.238.37.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.37.0
- 46.238.38.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.38.0
- 46.238.39.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.39.0
- 46.238.40.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.40.0
- 46.238.41.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.41.0
- 46.238.42.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.42.0
- 46.238.43.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.43.0
- 46.238.44.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.44.0
- 46.238.45.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.45.0
- 46.238.46.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.46.0
- 46.238.48.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.48.0
- 46.238.49.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.49.0
- 46.238.50.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.50.0
- 46.238.51.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.51.0
- 46.238.52.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.52.0
- 46.238.53.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.53.0
- 46.238.54.0/24AS29580A1 Bulgaria EADRPKI Valid46.238.54.0
- 46.238.55.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.55.0
- 46.238.56.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.56.0
- 46.238.57.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.57.0
- 46.238.58.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.58.0
- 46.238.59.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.59.0
- 46.238.60.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.60.0
- 46.238.61.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.61.0
- 46.238.62.0/24AS35141A1 Bulgaria EADRPKI Valid46.238.62.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.