BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
223.220.0.0/15
Announced exactly
- 223.220.0.0/15AS4134No.31,Jin-rong StreetRPKI Valid223.220.0.0
- Registry
- APNIC · China · Jul 23, 2010
- Delegated block
- 223.220.0.0 – 223.221.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 223.220.0.0/17AS140061Qinghai TelecomRPKI Valid223.220.0.0
- 223.220.0.0/21AS140061Qinghai TelecomRPKI Valid223.220.0.0
- 223.220.8.0/21AS140061Qinghai TelecomRPKI Valid223.220.8.0
- 223.220.16.0/20AS140061Qinghai TelecomRPKI Valid223.220.16.0
- 223.220.32.0/23AS140061Qinghai TelecomRPKI Valid223.220.32.0
- 223.220.34.0/24AS140061Qinghai TelecomRPKI Valid223.220.34.0
- 223.220.35.0/24AS140061Qinghai TelecomRPKI Valid223.220.35.0
- 223.220.36.0/23AS140061Qinghai TelecomRPKI Valid223.220.36.0
- 223.220.38.0/24AS140061Qinghai TelecomRPKI Valid223.220.38.0
- 223.220.39.0/24AS140061Qinghai TelecomRPKI Valid223.220.39.0
- 223.220.44.0/23AS140061Qinghai TelecomRPKI Valid223.220.44.0
- 223.220.46.0/23AS140061Qinghai TelecomRPKI Valid223.220.46.0
- 223.220.48.0/24AS140061Qinghai TelecomRPKI Valid223.220.48.0
- 223.220.49.0/24AS140061Qinghai TelecomRPKI Valid223.220.49.0
- 223.220.50.0/24AS140061Qinghai TelecomRPKI Valid223.220.50.0
- 223.220.51.0/24AS140061Qinghai TelecomRPKI Valid223.220.51.0
- 223.220.52.0/24AS140061Qinghai TelecomRPKI Valid223.220.52.0
- 223.220.53.0/24AS140061Qinghai TelecomRPKI Valid223.220.53.0
- 223.220.54.0/24AS140061Qinghai TelecomRPKI Valid223.220.54.0
- 223.220.55.0/24AS140061Qinghai TelecomRPKI Valid223.220.55.0
- 223.220.58.0/24AS140061Qinghai TelecomRPKI Valid223.220.58.0
- 223.220.59.0/24AS140061Qinghai TelecomRPKI Valid223.220.59.0
- 223.220.64.0/20AS140061Qinghai TelecomRPKI Valid223.220.64.0
- 223.220.80.0/24AS140061Qinghai TelecomRPKI Valid223.220.80.0
- 223.220.82.0/24AS140061Qinghai TelecomRPKI Valid223.220.82.0
- 223.220.83.0/24AS140061Qinghai TelecomRPKI Valid223.220.83.0
- 223.220.84.0/22AS140061Qinghai TelecomRPKI Valid223.220.84.0
- 223.220.88.0/22AS140061Qinghai TelecomRPKI Valid223.220.88.0
- 223.220.92.0/22AS140061Qinghai TelecomRPKI Valid223.220.92.0
- 223.220.104.0/24AS140061Qinghai TelecomRPKI Valid223.220.104.0
- 223.220.105.0/24AS140061Qinghai TelecomRPKI Valid223.220.105.0
- 223.220.106.0/24AS140061Qinghai TelecomRPKI Valid223.220.106.0
- 223.220.107.0/24AS140061Qinghai TelecomRPKI Valid223.220.107.0
- 223.220.108.0/22AS140061Qinghai TelecomRPKI Valid223.220.108.0
- 223.220.114.0/24AS140061Qinghai TelecomRPKI Valid223.220.114.0
- 223.220.115.0/24AS140061Qinghai TelecomRPKI Valid223.220.115.0
- 223.220.116.0/24AS140061Qinghai TelecomRPKI Valid223.220.116.0
- 223.220.117.0/24AS140061Qinghai TelecomRPKI Valid223.220.117.0
- 223.220.118.0/24AS140061Qinghai TelecomRPKI Invalid223.220.118.0
- 223.220.119.0/24AS140061Qinghai TelecomRPKI Valid223.220.119.0
- 223.220.120.0/22AS140061Qinghai TelecomRPKI Valid223.220.120.0
- 223.220.124.0/22AS140061Qinghai TelecomRPKI Valid223.220.124.0
- 223.220.128.0/17AS140061Qinghai TelecomRPKI Valid223.220.128.0
- 223.220.128.0/22AS140061Qinghai TelecomRPKI Valid223.220.128.0
- 223.220.132.0/23AS140061Qinghai TelecomRPKI Valid223.220.132.0
- 223.220.134.0/24AS140061Qinghai TelecomRPKI Valid223.220.134.0
- 223.220.135.0/24AS140061Qinghai TelecomRPKI Valid223.220.135.0
- 223.220.136.0/24AS140061Qinghai TelecomRPKI Valid223.220.136.0
- 223.220.137.0/24AS140061Qinghai TelecomRPKI Valid223.220.137.0
- 223.220.138.0/24AS140061Qinghai TelecomRPKI Valid223.220.138.0
- 223.220.139.0/24AS140061Qinghai TelecomRPKI Valid223.220.139.0
- 223.220.140.0/24AS140061Qinghai TelecomRPKI Valid223.220.140.0
- 223.220.141.0/24AS140061Qinghai TelecomRPKI Valid223.220.141.0
- 223.220.142.0/24AS140061Qinghai TelecomRPKI Valid223.220.142.0
- 223.220.143.0/24AS140061Qinghai TelecomRPKI Valid223.220.143.0
- 223.220.144.0/22AS140061Qinghai TelecomRPKI Valid223.220.144.0
- 223.220.148.0/24AS140061Qinghai TelecomRPKI Valid223.220.148.0
- 223.220.149.0/24AS140061Qinghai TelecomRPKI Valid223.220.149.0
- 223.220.152.0/24AS140061Qinghai TelecomRPKI Valid223.220.152.0
- 223.220.154.0/24AS140061Qinghai TelecomRPKI Valid223.220.154.0
- 223.220.155.0/24AS140061Qinghai TelecomRPKI Valid223.220.155.0
- 223.220.156.0/23AS140061Qinghai TelecomRPKI Valid223.220.156.0
- 223.220.158.0/24AS140061Qinghai TelecomRPKI Valid223.220.158.0
- 223.220.159.0/24AS140061Qinghai TelecomRPKI Valid223.220.159.0
- 223.220.162.0/24AS140061Qinghai TelecomRPKI Valid223.220.162.0
- 223.220.163.0/24AS140061Qinghai TelecomRPKI Valid223.220.163.0
- 223.220.164.0/24AS140061Qinghai TelecomRPKI Valid223.220.164.0
- 223.220.165.0/24AS140061Qinghai TelecomRPKI Valid223.220.165.0
- 223.220.166.0/24AS140061Qinghai TelecomRPKI Valid223.220.166.0
- 223.220.167.0/24AS140061Qinghai TelecomRPKI Valid223.220.167.0
- 223.220.168.0/24AS140061Qinghai TelecomRPKI Valid223.220.168.0
- 223.220.169.0/24AS140061Qinghai TelecomRPKI Valid223.220.169.0
- 223.220.170.0/24AS140061Qinghai TelecomRPKI Valid223.220.170.0
- 223.220.171.0/24AS140061Qinghai TelecomRPKI Valid223.220.171.0
- 223.220.172.0/24AS140061Qinghai TelecomRPKI Valid223.220.172.0
- 223.220.173.0/24AS140061Qinghai TelecomRPKI Valid223.220.173.0
- 223.220.174.0/24AS140061Qinghai TelecomRPKI Valid223.220.174.0
- 223.220.176.0/21AS140061Qinghai TelecomRPKI Valid223.220.176.0
- 223.220.184.0/21AS132225China TelecomRPKI Valid223.220.184.0
- 223.220.249.0/24AS140061Qinghai TelecomRPKI Valid223.220.249.0
- 223.220.250.0/24AS140061Qinghai TelecomRPKI Valid223.220.250.0
- 223.220.254.0/24AS140061Qinghai TelecomRPKI Valid223.220.254.0
- 223.220.255.0/24AS140061Qinghai TelecomRPKI Valid223.220.255.0
- 223.221.0.0/17AS140061Qinghai TelecomRPKI Valid223.221.0.0
- 223.221.7.0/24AS140061Qinghai TelecomRPKI Valid223.221.7.0
- 223.221.8.0/24AS140061Qinghai TelecomRPKI Valid223.221.8.0
- 223.221.9.0/24AS140061Qinghai TelecomRPKI Valid223.221.9.0
- 223.221.10.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid223.221.10.0
- 223.221.12.0/24AS140061Qinghai TelecomRPKI Valid223.221.12.0
- 223.221.13.0/24AS140061Qinghai TelecomRPKI Valid223.221.13.0
- 223.221.14.0/24AS140061Qinghai TelecomRPKI Valid223.221.14.0
- 223.221.16.0/21AS140061Qinghai TelecomRPKI Valid223.221.16.0
- 223.221.24.0/24AS140061Qinghai TelecomRPKI Valid223.221.24.0
- 223.221.28.0/24AS140061Qinghai TelecomRPKI Valid223.221.28.0
- 223.221.29.0/24AS140061Qinghai TelecomRPKI Valid223.221.29.0
- 223.221.30.0/24AS140061Qinghai TelecomRPKI Valid223.221.30.0
- 223.221.31.0/24AS140061Qinghai TelecomRPKI Valid223.221.31.0
- 223.221.34.0/24AS140061Qinghai TelecomRPKI Valid223.221.34.0
- 223.221.35.0/24AS140061Qinghai TelecomRPKI Valid223.221.35.0
- 223.221.36.0/24AS140061Qinghai TelecomRPKI Valid223.221.36.0
Showing the first 100.
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.