BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
171.104.0.0/14
Announced exactly
- 171.104.0.0/14AS4134No.31,Jin-rong StreetRPKI Valid171.104.0.0
- Registry
- APNIC · China · Mar 3, 2011
- Delegated block
- 171.104.0.0 – 171.111.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 171.104.136.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.136.0
- 171.104.137.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.137.0
- 171.104.138.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.138.0
- 171.104.139.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.139.0
- 171.104.140.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.140.0
- 171.104.141.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.141.0
- 171.104.142.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.142.0
- 171.104.143.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.143.0
- 171.104.232.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.232.0
- 171.104.233.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.233.0
- 171.104.234.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.234.0
- 171.104.235.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.104.235.0
- 171.105.16.0/20AS138169China TelecomRPKI Valid171.105.16.0
- 171.105.56.0/21AS138169China TelecomRPKI Valid171.105.56.0
- 171.105.184.0/21AS138169China TelecomRPKI Valid171.105.184.0
- 171.105.192.0/21AS138169China TelecomRPKI Valid171.105.192.0
- 171.105.216.0/21AS138169China TelecomRPKI Valid171.105.216.0
- 171.105.224.0/20AS138169China TelecomRPKI Valid171.105.224.0
- 171.107.76.0/23AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.107.76.0
- 171.107.78.0/24AS138169China TelecomRPKI Valid171.107.78.0
- 171.107.79.0/24AS137693CHINATELECOM Guangxi Nanning IDC networkdescr: Nanning , Guangxi Province, P.R.China.RPKI Valid171.107.79.0
- 171.107.80.0/24AS138169China TelecomRPKI Valid171.107.80.0
- 171.107.81.0/24AS138169China TelecomRPKI Valid171.107.81.0
- 171.107.82.0/24AS138169China TelecomRPKI Valid171.107.82.0
- 171.107.83.0/24AS138169China TelecomRPKI Valid171.107.83.0
- 171.107.84.0/22AS138169China TelecomRPKI Valid171.107.84.0
- 171.107.184.0/22AS138169China TelecomRPKI Valid171.107.184.0
- 171.107.188.0/22AS138169China TelecomRPKI Valid171.107.188.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.