BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
37.63.0.0/17
Announced exactly
- 37.63.0.0/17AS8717A1 Bulgaria EADRPKI Valid37.63.0.0
- Registry
- RIPE NCC · Bulgaria · Jan 23, 2012
- Delegated block
- 37.63.0.0 – 37.63.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 37.63.0.0/20AS12716A1 Bulgaria EADRPKI Valid37.63.0.0
- 37.63.16.0/22AS12716A1 Bulgaria EADRPKI Valid37.63.16.0
- 37.63.20.0/22AS12716A1 Bulgaria EADRPKI Valid37.63.20.0
- 37.63.24.0/22AS12716A1 Bulgaria EADRPKI Valid37.63.24.0
- 37.63.28.0/22AS12716A1 Bulgaria EADRPKI Valid37.63.28.0
- 37.63.32.0/22AS12716A1 Bulgaria EADRPKI Valid37.63.32.0
- 37.63.36.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.36.0
- 37.63.37.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.37.0
- 37.63.38.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.38.0
- 37.63.39.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.39.0
- 37.63.40.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.40.0
- 37.63.41.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.41.0
- 37.63.42.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.42.0
- 37.63.43.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.43.0
- 37.63.44.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.44.0
- 37.63.45.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.45.0
- 37.63.46.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.46.0
- 37.63.47.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.47.0
- 37.63.48.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.48.0
- 37.63.49.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.49.0
- 37.63.50.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.50.0
- 37.63.51.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.51.0
- 37.63.52.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.52.0
- 37.63.53.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.53.0
- 37.63.54.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.54.0
- 37.63.55.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.55.0
- 37.63.56.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.56.0
- 37.63.57.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.57.0
- 37.63.58.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.58.0
- 37.63.59.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.59.0
- 37.63.60.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.60.0
- 37.63.61.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.61.0
- 37.63.62.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.62.0
- 37.63.63.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.63.0
- 37.63.64.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.64.0
- 37.63.65.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.65.0
- 37.63.66.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.66.0
- 37.63.67.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.67.0
- 37.63.68.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.68.0
- 37.63.69.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.69.0
- 37.63.70.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.70.0
- 37.63.71.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.71.0
- 37.63.72.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.72.0
- 37.63.73.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.73.0
- 37.63.74.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.74.0
- 37.63.75.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.75.0
- 37.63.76.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.76.0
- 37.63.77.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.77.0
- 37.63.78.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.78.0
- 37.63.79.0/24AS200723South-West University "Neofit Rilski"RPKI Valid37.63.79.0
- 37.63.80.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.80.0
- 37.63.81.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.81.0
- 37.63.82.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.82.0
- 37.63.83.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.83.0
- 37.63.84.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.84.0
- 37.63.85.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.85.0
- 37.63.86.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.86.0
- 37.63.87.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.87.0
- 37.63.88.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.88.0
- 37.63.89.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.89.0
- 37.63.90.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.90.0
- 37.63.91.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.91.0
- 37.63.92.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.92.0
- 37.63.93.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.93.0
- 37.63.94.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.94.0
- 37.63.95.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.95.0
- 37.63.96.0/22AS12716A1 Bulgaria EADRPKI Valid37.63.96.0
- 37.63.100.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.100.0
- 37.63.101.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.101.0
- 37.63.102.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.102.0
- 37.63.103.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.103.0
- 37.63.104.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.104.0
- 37.63.105.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.105.0
- 37.63.106.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.106.0
- 37.63.107.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.107.0
- 37.63.108.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.108.0
- 37.63.109.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.109.0
- 37.63.110.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.110.0
- 37.63.111.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.111.0
- 37.63.112.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.112.0
- 37.63.113.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.113.0
- 37.63.114.0/23AS29580A1 Bulgaria EADRPKI Valid37.63.114.0
- 37.63.116.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.116.0
- 37.63.117.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.117.0
- 37.63.118.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.118.0
- 37.63.119.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.119.0
- 37.63.120.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.120.0
- 37.63.121.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.121.0
- 37.63.122.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.122.0
- 37.63.123.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.123.0
- 37.63.124.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.124.0
- 37.63.125.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.125.0
- 37.63.126.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.126.0
- 37.63.127.0/24AS29580A1 Bulgaria EADRPKI Valid37.63.127.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.