BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
36.103.0.0/16
Announced exactly
- 36.103.0.0/16AS4134CHINANET-BACKBONE No.31,Jin-rong StreetRPKI Valid36.103.0.0
- Registry
- APNIC · China · Jan 17, 2011
- Delegated block
- 36.96.0.0 – 36.127.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 36.103.120.0/21AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.120.0
- 36.103.128.0/19AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.128.0
- 36.103.157.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.157.0
- 36.103.158.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.158.0
- 36.103.159.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.159.0
- 36.103.160.0/20AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.160.0
- 36.103.160.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.160.0
- 36.103.161.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.161.0
- 36.103.162.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.162.0
- 36.103.163.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.163.0
- 36.103.166.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.166.0
- 36.103.167.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.167.0
- 36.103.168.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.168.0
- 36.103.176.0/20AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.176.0
- 36.103.176.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.176.0
- 36.103.178.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.178.0
- 36.103.180.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.180.0
- 36.103.182.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.182.0
- 36.103.183.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.183.0
- 36.103.184.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.184.0
- 36.103.192.0/20AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.192.0
- 36.103.192.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.192.0
- 36.103.197.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.197.0
- 36.103.198.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.198.0
- 36.103.199.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.199.0
- 36.103.200.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.200.0
- 36.103.204.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.204.0
- 36.103.206.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.206.0
- 36.103.208.0/21AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.208.0
- 36.103.208.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.208.0
- 36.103.209.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.209.0
- 36.103.211.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.211.0
- 36.103.212.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.212.0
- 36.103.214.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.214.0
- 36.103.216.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.216.0
- 36.103.216.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.216.0
- 36.103.219.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.219.0
- 36.103.220.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.220.0
- 36.103.220.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.220.0
- 36.103.222.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.222.0
- 36.103.224.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.224.0
- 36.103.228.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.228.0
- 36.103.232.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.232.0
- 36.103.233.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.233.0
- 36.103.236.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.236.0
- 36.103.239.0/24AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.239.0
- 36.103.240.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.240.0
- 36.103.244.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.244.0
- 36.103.244.0/23AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.244.0
- 36.103.248.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.248.0
- 36.103.252.0/22AS134761CHINANET-NINGXIA-ZHONGWEI-IDC CHINANET NINGXIA province ZHONGWEI IDC networkRPKI Valid36.103.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, 193.166.0.0/15. 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.