BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
140.249.0.0/16
Announced exactly
- 140.249.0.0/16AS4134No.31,Jin-rong StreetRPKI Valid140.249.0.0
- Registry
- APNIC · China · Mar 29, 2011
- Delegated block
- 140.249.0.0 – 140.249.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 140.249.0.0/20AS58541Qingdao,266000RPKI Valid140.249.0.0
- 140.249.3.0/24AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.3.0
- 140.249.7.0/24AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.7.0
- 140.249.16.0/21AS58541Qingdao,266000RPKI Valid140.249.16.0
- 140.249.17.0/24AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.17.0
- 140.249.18.0/23AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.18.0
- 140.249.18.0/24AS58541Qingdao,266000RPKI Valid140.249.18.0
- 140.249.19.0/24AS58541Qingdao,266000RPKI Valid140.249.19.0
- 140.249.20.0/22AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.20.0
- 140.249.20.0/24AS58541Qingdao,266000RPKI Valid140.249.20.0
- 140.249.21.0/24AS58541Qingdao,266000RPKI Valid140.249.21.0
- 140.249.22.0/24AS58541Qingdao,266000RPKI Valid140.249.22.0
- 140.249.23.0/24AS58541Qingdao,266000RPKI Valid140.249.23.0
- 140.249.24.0/22AS58541Qingdao,266000RPKI Valid140.249.24.0
- 140.249.24.0/24AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.24.0
- 140.249.28.0/24AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.28.0
- 140.249.29.0/24AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.29.0
- 140.249.30.0/23AS58541Qingdao,266000RPKI Valid140.249.30.0
- 140.249.32.0/19AS58541Qingdao,266000RPKI Valid140.249.32.0
- 140.249.48.0/21AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.48.0
- 140.249.48.0/22AS58541Qingdao,266000RPKI Valid140.249.48.0
- 140.249.52.0/22AS58541Qingdao,266000RPKI Valid140.249.52.0
- 140.249.62.0/23AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.62.0
- 140.249.64.0/19AS58540Jinan,250000RPKI Valid140.249.64.0
- 140.249.96.0/19AS58540Jinan,250000RPKI Valid140.249.96.0
- 140.249.108.0/24AS58540Jinan,250000RPKI Valid140.249.108.0
- 140.249.111.0/24AS58540Jinan,250000RPKI Valid140.249.111.0
- 140.249.128.0/19AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.128.0
- 140.249.128.0/22AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.128.0
- 140.249.132.0/22AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.132.0
- 140.249.136.0/24AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.136.0
- 140.249.160.0/19AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.160.0
- 140.249.160.0/20AS58541Qingdao,266000RPKI Valid140.249.160.0
- 140.249.176.0/20AS58541Qingdao,266000RPKI Valid140.249.176.0
- 140.249.192.0/20AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.192.0
- 140.249.192.0/21AS58541Qingdao,266000RPKI Valid140.249.192.0
- 140.249.200.0/21AS58541Qingdao,266000RPKI Valid140.249.200.0
- 140.249.208.0/21AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.208.0
- 140.249.208.0/22AS58541Qingdao,266000RPKI Valid140.249.208.0
- 140.249.212.0/22AS58541Qingdao,266000RPKI Valid140.249.212.0
- 140.249.216.0/21AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.216.0
- 140.249.216.0/22AS58541Qingdao,266000RPKI Valid140.249.216.0
- 140.249.220.0/22AS58541Qingdao,266000RPKI Valid140.249.220.0
- 140.249.224.0/20AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.224.0
- 140.249.240.0/20AS136195Qingdao, Shandong Province, P.R.China.RPKI Valid140.249.240.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.