BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
111.172.0.0/14
Announced exactly
- 111.172.0.0/14AS4134No.31,Jin-rong StreetRPKI Valid111.172.0.0
- Registry
- APNIC · China · May 22, 2009
- Delegated block
- 111.172.0.0 – 111.175.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 111.172.0.0/16AS137266CHINATELECOM Hubei province Wuhan 5G networkRPKI Valid111.172.0.0
- 111.172.0.0/24AS58563CHINANET Hubei province networkRPKI Valid111.172.0.0
- 111.172.122.0/24AS137266CHINATELECOM Hubei province Wuhan 5G networkRPKI Valid111.172.122.0
- 111.172.134.0/24AS137266CHINATELECOM Hubei province Wuhan 5G networkRPKI Valid111.172.134.0
- 111.172.192.0/22AS138982Hubei Jiangxia IDCRPKI Valid111.172.192.0
- 111.172.195.0/24AS138982Hubei Jiangxia IDCRPKI Valid111.172.195.0
- 111.172.196.0/22AS138982Hubei Jiangxia IDCRPKI Valid111.172.196.0
- 111.172.204.0/24AS138982Hubei Jiangxia IDCRPKI Valid111.172.204.0
- 111.172.208.0/22AS58563CHINANET Hubei province networkRPKI Valid111.172.208.0
- 111.172.216.0/22AS138982Hubei Jiangxia IDCRPKI Valid111.172.216.0
- 111.172.224.0/21AS138982Hubei Jiangxia IDCRPKI Valid111.172.224.0
- 111.172.232.0/22AS138982Hubei Jiangxia IDCRPKI Valid111.172.232.0
- 111.172.236.0/22AS138982Hubei Jiangxia IDCRPKI Valid111.172.236.0
- 111.172.240.0/20AS138982Hubei Jiangxia IDCRPKI Valid111.172.240.0
- 111.173.80.0/22AS148981China TelecomRPKI Valid111.173.80.0
- 111.173.89.0/24AS148981China TelecomRPKI Valid111.173.89.0
- 111.173.104.0/22AS148981China TelecomRPKI Valid111.173.104.0
- 111.173.116.0/22AS148981China TelecomRPKI Valid111.173.116.0
- 111.174.0.0/20AS136194Huangshi, Hubei Province, P.R.China.RPKI Valid111.174.0.0
- 111.174.60.0/22AS136194Huangshi, Hubei Province, P.R.China.RPKI Valid111.174.60.0
- 111.175.0.0/16AS137266CHINATELECOM Hubei province Wuhan 5G networkRPKI Valid111.175.0.0
- 111.175.40.0/22AS137266CHINATELECOM Hubei province Wuhan 5G networkRPKI Valid111.175.40.0
- 111.175.60.0/22AS137266CHINATELECOM Hubei province Wuhan 5G networkRPKI Valid111.175.60.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 128.139.0.0/16. 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.