BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
117.21.0.0/16
Announced exactly
- 117.21.0.0/16AS4134No.31,Jin-rong StreetRPKI Valid117.21.0.0
- Registry
- APNIC · China · Jun 15, 2007
- Delegated block
- 117.21.0.0 – 117.21.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 117.21.56.0/21AS149837China TelecomRPKI Valid117.21.56.0
- 117.21.75.0/24AS4134No.31,Jin-rong StreetRPKI Valid117.21.75.0
- 117.21.178.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.178.0
- 117.21.178.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.178.0
- 117.21.180.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.180.0
- 117.21.182.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.182.0
- 117.21.184.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.184.0
- 117.21.185.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.185.0
- 117.21.186.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.186.0
- 117.21.187.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.187.0
- 117.21.188.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.188.0
- 117.21.189.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.189.0
- 117.21.216.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.216.0
- 117.21.217.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.217.0
- 117.21.218.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.218.0
- 117.21.219.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.219.0
- 117.21.232.0/22AS139201Jiangxi Jiujiang IDCRPKI Valid117.21.232.0
- 117.21.238.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid117.21.238.0
- 117.21.243.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid117.21.243.0
- 117.21.246.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid117.21.246.0
- 117.21.248.0/22AS134238CHINANET Jiangx province IDC networkRPKI Valid117.21.248.0
- 117.21.252.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid117.21.252.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.