BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
172.247.0.0/16
Announced exactly
- 172.247.0.0/16AS40065CNSERVERS LLCRPKI Not found172.247.0.0
- Registry
- ARIN · United States · Jun 6, 2013
- Delegated block
- 172.247.0.0 – 172.247.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 172.247.0.0/24AS40065CNSERVERS LLCRPKI Not found172.247.0.0
- 172.247.4.0/24AS40065CNSERVERS LLCRPKI Not found172.247.4.0
- 172.247.6.0/24AS40065CNSERVERS LLCRPKI Not found172.247.6.0
- 172.247.18.0/24AS40065CNSERVERS LLCRPKI Not found172.247.18.0
- 172.247.22.0/24AS40065CNSERVERS LLCRPKI Not found172.247.22.0
- 172.247.27.0/24AS40065CNSERVERS LLCRPKI Not found172.247.27.0
- 172.247.31.0/24AS40065CNSERVERS LLCRPKI Not found172.247.31.0
- 172.247.32.0/24AS21859Zenlayer IncRPKI Valid172.247.32.0
- 172.247.34.0/24AS21859Zenlayer IncRPKI Valid172.247.34.0
- 172.247.35.0/24AS21859Zenlayer IncRPKI Valid172.247.35.0
- 172.247.36.0/24AS134176Cloudie LimitedRPKI Not found172.247.36.0
- 172.247.37.0/24AS134176Cloudie LimitedRPKI Not found172.247.37.0
- 172.247.38.0/24AS21859Zenlayer IncRPKI Valid172.247.38.0
- 172.247.39.0/24AS21859Zenlayer IncRPKI Valid172.247.39.0
- 172.247.44.0/24AS40065CNSERVERS LLCRPKI Not found172.247.44.0
- 172.247.45.0/24AS40065CNSERVERS LLCRPKI Not found172.247.45.0
- 172.247.49.0/24AS40065CNSERVERS LLCRPKI Not found172.247.49.0
- 172.247.51.0/24AS40065CNSERVERS LLCRPKI Not found172.247.51.0
- 172.247.52.0/24AS40065CNSERVERS LLCRPKI Not found172.247.52.0
- 172.247.55.0/24AS40065CNSERVERS LLCRPKI Not found172.247.55.0
- 172.247.58.0/24AS40065CNSERVERS LLCRPKI Not found172.247.58.0
- 172.247.69.0/24AS40065CNSERVERS LLCRPKI Not found172.247.69.0
- 172.247.70.0/24AS40065CNSERVERS LLCRPKI Not found172.247.70.0
- 172.247.71.0/24AS40065CNSERVERS LLCRPKI Not found172.247.71.0
- 172.247.72.0/24AS40065CNSERVERS LLCRPKI Not found172.247.72.0
- 172.247.76.0/24AS40065CNSERVERS LLCRPKI Not found172.247.76.0
- 172.247.77.0/24AS40065CNSERVERS LLCRPKI Not found172.247.77.0
- 172.247.78.0/24AS40065CNSERVERS LLCRPKI Not found172.247.78.0
- 172.247.80.0/24AS40065CNSERVERS LLCRPKI Not found172.247.80.0
- 172.247.81.0/24AS40065CNSERVERS LLCRPKI Not found172.247.81.0
- 172.247.90.0/24AS40065CNSERVERS LLCRPKI Not found172.247.90.0
- 172.247.92.0/24AS40065CNSERVERS LLCRPKI Valid172.247.92.0
- 172.247.93.0/24AS40065CNSERVERS LLCRPKI Valid172.247.93.0
- 172.247.96.0/24AS141391BIDA FiberRPKI Not found172.247.96.0
- 172.247.99.0/24AS40065CNSERVERS LLCRPKI Not found172.247.99.0
- 172.247.104.0/24AS40065CNSERVERS LLCRPKI Not found172.247.104.0
- 172.247.107.0/24AS40065CNSERVERS LLCRPKI Not found172.247.107.0
- 172.247.109.0/24AS40065CNSERVERS LLCRPKI Not found172.247.109.0
- 172.247.112.0/24AS40065CNSERVERS LLCRPKI Not found172.247.112.0
- 172.247.116.0/24AS40065CNSERVERS LLCRPKI Not found172.247.116.0
- 172.247.118.0/24AS40065CNSERVERS LLCRPKI Not found172.247.118.0
- 172.247.127.0/24AS40065CNSERVERS LLCRPKI Not found172.247.127.0
- 172.247.134.0/23AS132839POWER LINE DATACENTERRPKI Not found172.247.134.0
- 172.247.136.0/22AS132839POWER LINE DATACENTERRPKI Not found172.247.136.0
- 172.247.140.0/23AS132839POWER LINE DATACENTERRPKI Not found172.247.140.0
- 172.247.143.0/24AS40065CNSERVERS LLCRPKI Not found172.247.143.0
- 172.247.150.0/23AS132839POWER LINE DATACENTERRPKI Not found172.247.150.0
- 172.247.152.0/21AS132839POWER LINE DATACENTERRPKI Not found172.247.152.0
- 172.247.160.0/22AS132839POWER LINE DATACENTERRPKI Not found172.247.160.0
- 172.247.164.0/23AS132839POWER LINE DATACENTERRPKI Not found172.247.164.0
- 172.247.168.0/24AS40065CNSERVERS LLCRPKI Not found172.247.168.0
- 172.247.172.0/24AS40065CNSERVERS LLCRPKI Not found172.247.172.0
- 172.247.174.0/23AS40065CNSERVERS LLCRPKI Not found172.247.174.0
- 172.247.176.0/23AS40065CNSERVERS LLCRPKI Not found172.247.176.0
- 172.247.177.0/24AS40065CNSERVERS LLCRPKI Not found172.247.177.0
- 172.247.178.0/24AS40065CNSERVERS LLCRPKI Not found172.247.178.0
- 172.247.179.0/24AS40065CNSERVERS LLCRPKI Not found172.247.179.0
- 172.247.181.0/24AS40065CNSERVERS LLCRPKI Not found172.247.181.0
- 172.247.185.0/24AS40065CNSERVERS LLCRPKI Not found172.247.185.0
- 172.247.189.0/24AS40065CNSERVERS LLCRPKI Not found172.247.189.0
- 172.247.192.0/24AS40065CNSERVERS LLCRPKI Not found172.247.192.0
- 172.247.193.0/24AS40065CNSERVERS LLCRPKI Not found172.247.193.0
- 172.247.194.0/24AS40065CNSERVERS LLCRPKI Not found172.247.194.0
- 172.247.195.0/24AS40065CNSERVERS LLCRPKI Not found172.247.195.0
- 172.247.196.0/24AS40065CNSERVERS LLCRPKI Not found172.247.196.0
- 172.247.197.0/24AS40065CNSERVERS LLCRPKI Not found172.247.197.0
- 172.247.198.0/24AS40065CNSERVERS LLCRPKI Not found172.247.198.0
- 172.247.199.0/24AS40065CNSERVERS LLCRPKI Not found172.247.199.0
- 172.247.206.0/24AS40065CNSERVERS LLCRPKI Not found172.247.206.0
- 172.247.207.0/24AS40065CNSERVERS LLCRPKI Not found172.247.207.0
- 172.247.222.0/24AS40065CNSERVERS LLCRPKI Not found172.247.222.0
- 172.247.227.0/24AS40065CNSERVERS LLCRPKI Not found172.247.227.0
- 172.247.228.0/24AS40065CNSERVERS LLCRPKI Not found172.247.228.0
- 172.247.230.0/24AS40065CNSERVERS LLCRPKI Not found172.247.230.0
- 172.247.238.0/24AS40065CNSERVERS LLCRPKI Not found172.247.238.0
- 172.247.242.0/24AS40065CNSERVERS LLCRPKI Not found172.247.242.0
- 172.247.244.0/24AS40065CNSERVERS LLCRPKI Not found172.247.244.0
- 172.247.246.0/24AS40065CNSERVERS LLCRPKI Not found172.247.246.0
- 172.247.247.0/24AS40065CNSERVERS LLCRPKI Not found172.247.247.0
- 172.247.248.0/24AS40065CNSERVERS LLCRPKI Not found172.247.248.0
- 172.247.249.0/24AS40065CNSERVERS LLCRPKI Not found172.247.249.0
- 172.247.250.0/24AS40065CNSERVERS LLCRPKI Not found172.247.250.0
- 172.247.251.0/24AS40065CNSERVERS LLCRPKI Not found172.247.251.0
- 172.247.252.0/24AS40065CNSERVERS LLCRPKI Not found172.247.252.0
- 172.247.253.0/24AS40065CNSERVERS LLCRPKI Not found172.247.253.0
- 172.247.254.0/24AS40065CNSERVERS LLCRPKI Not found172.247.254.0
- 172.247.255.0/24AS40065CNSERVERS LLCRPKI Not found172.247.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.