BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
106.224.0.0/14
Announced exactly
- 106.224.0.0/14AS4134No.31,Jin-rong StreetRPKI Not found106.224.0.0
- Registry
- APNIC · China · Mar 21, 2011
- Delegated block
- 106.224.0.0 – 106.239.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 106.225.128.0/19AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.128.0
- 106.225.128.0/22AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.128.0
- 106.225.128.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.128.0
- 106.225.129.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.129.0
- 106.225.132.0/22AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.132.0
- 106.225.134.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.134.0
- 106.225.136.0/21AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.136.0
- 106.225.144.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.144.0
- 106.225.145.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.145.0
- 106.225.146.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.146.0
- 106.225.147.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.147.0
- 106.225.148.0/22AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.148.0
- 106.225.152.0/21AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.152.0
- 106.225.157.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.157.0
- 106.225.160.0/21AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.160.0
- 106.225.163.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.163.0
- 106.225.168.0/21AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.168.0
- 106.225.176.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.176.0
- 106.225.177.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.177.0
- 106.225.178.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.178.0
- 106.225.180.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.180.0
- 106.225.184.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.184.0
- 106.225.188.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.225.188.0
- 106.225.192.0/18AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.192.0
- 106.225.192.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.192.0
- 106.225.193.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.193.0
- 106.225.196.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.196.0
- 106.225.197.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.197.0
- 106.225.198.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.198.0
- 106.225.198.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.198.0
- 106.225.204.0/23AS134238CHINANET Jiangx province IDC networkRPKI Invalid106.225.204.0
- 106.225.204.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.204.0
- 106.225.208.0/21AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.208.0
- 106.225.212.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.212.0
- 106.225.215.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.225.215.0
- 106.226.240.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.226.240.0
- 106.226.244.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid106.226.244.0
- 106.227.0.0/21AS134238CHINANET Jiangx province IDC networkRPKI Valid106.227.0.0
- 106.227.5.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.227.5.0
- 106.227.8.0/22AS134238CHINANET Jiangx province IDC networkRPKI Valid106.227.8.0
- 106.227.12.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.227.12.0
- 106.227.16.0/20AS148969China TelecomRPKI Valid106.227.16.0
- 106.227.28.0/24AS148969China TelecomRPKI Valid106.227.28.0
- 106.227.32.0/21AS134238CHINANET Jiangx province IDC networkRPKI Valid106.227.32.0
- 106.227.32.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.227.32.0
- 106.227.33.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.227.33.0
- 106.227.35.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid106.227.35.0
- 106.227.40.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.227.40.0
- 106.227.42.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid106.227.42.0
- 106.227.44.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.227.44.0
- 106.227.48.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.227.48.0
- 106.227.52.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.227.52.0
- 106.227.56.0/21AS148969China TelecomRPKI Valid106.227.56.0
- 106.227.64.0/19AS149837China TelecomRPKI Valid106.227.64.0
- 106.227.68.0/24AS149837China TelecomRPKI Valid106.227.68.0
- 106.227.74.0/24AS149837China TelecomRPKI Valid106.227.74.0
- 106.227.96.0/21AS148969China TelecomRPKI Valid106.227.96.0
- 106.227.200.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid106.227.200.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.