BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
220.167.128.0/17
Announced exactly
- 220.167.128.0/17AS4134No.31,Jin-rong StreetRPKI Valid220.167.128.0
- Registry
- APNIC · China · Oct 30, 2002
- Delegated block
- 220.160.0.0 – 220.191.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 220.167.128.0/18AS140061Qinghai TelecomRPKI Valid220.167.128.0
- 220.167.140.0/24AS140061Qinghai TelecomRPKI Valid220.167.140.0
- 220.167.141.0/24AS140061Qinghai TelecomRPKI Valid220.167.141.0
- 220.167.142.0/23AS59223CHINANET Qinghai province IDC networkRPKI Valid220.167.142.0
- 220.167.146.0/24AS140061Qinghai TelecomRPKI Valid220.167.146.0
- 220.167.148.0/22AS140061Qinghai TelecomRPKI Valid220.167.148.0
- 220.167.156.0/22AS140061Qinghai TelecomRPKI Valid220.167.156.0
- 220.167.160.0/24AS140061Qinghai TelecomRPKI Valid220.167.160.0
- 220.167.161.0/24AS140061Qinghai TelecomRPKI Valid220.167.161.0
- 220.167.162.0/24AS140061Qinghai TelecomRPKI Valid220.167.162.0
- 220.167.166.0/24AS140061Qinghai TelecomRPKI Valid220.167.166.0
- 220.167.169.0/24AS140061Qinghai TelecomRPKI Valid220.167.169.0
- 220.167.170.0/24AS140061Qinghai TelecomRPKI Valid220.167.170.0
- 220.167.171.0/24AS140061Qinghai TelecomRPKI Valid220.167.171.0
- 220.167.172.0/22AS140061Qinghai TelecomRPKI Valid220.167.172.0
- 220.167.176.0/24AS140061Qinghai TelecomRPKI Valid220.167.176.0
- 220.167.177.0/24AS140061Qinghai TelecomRPKI Valid220.167.177.0
- 220.167.178.0/24AS140061Qinghai TelecomRPKI Valid220.167.178.0
- 220.167.179.0/24AS140061Qinghai TelecomRPKI Valid220.167.179.0
- 220.167.180.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid220.167.180.0
- 220.167.181.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid220.167.181.0
- 220.167.182.0/24AS59223CHINANET Qinghai province IDC networkRPKI Valid220.167.182.0
- 220.167.183.0/24AS140061Qinghai TelecomRPKI Valid220.167.183.0
- 220.167.184.0/24AS140061Qinghai TelecomRPKI Valid220.167.184.0
- 220.167.185.0/24AS140061Qinghai TelecomRPKI Valid220.167.185.0
- 220.167.186.0/24AS140061Qinghai TelecomRPKI Valid220.167.186.0
- 220.167.187.0/24AS140061Qinghai TelecomRPKI Valid220.167.187.0
- 220.167.188.0/23AS140061Qinghai TelecomRPKI Valid220.167.188.0
- 220.167.190.0/23AS140061Qinghai TelecomRPKI Valid220.167.190.0
- 220.167.192.0/18AS140061Qinghai TelecomRPKI Valid220.167.192.0
- 220.167.196.0/22AS140061Qinghai TelecomRPKI Valid220.167.196.0
- 220.167.200.0/24AS140061Qinghai TelecomRPKI Valid220.167.200.0
- 220.167.201.0/24AS140061Qinghai TelecomRPKI Valid220.167.201.0
- 220.167.202.0/23AS140061Qinghai TelecomRPKI Valid220.167.202.0
- 220.167.204.0/24AS140061Qinghai TelecomRPKI Valid220.167.204.0
- 220.167.206.0/24AS140061Qinghai TelecomRPKI Valid220.167.206.0
- 220.167.207.0/24AS140061Qinghai TelecomRPKI Valid220.167.207.0
- 220.167.208.0/23AS140061Qinghai TelecomRPKI Valid220.167.208.0
- 220.167.210.0/24AS140061Qinghai TelecomRPKI Valid220.167.210.0
- 220.167.211.0/24AS140061Qinghai TelecomRPKI Valid220.167.211.0
- 220.167.212.0/22AS140061Qinghai TelecomRPKI Valid220.167.212.0
- 220.167.221.0/24AS140061Qinghai TelecomRPKI Valid220.167.221.0
- 220.167.222.0/24AS140061Qinghai TelecomRPKI Valid220.167.222.0
- 220.167.223.0/24AS140061Qinghai TelecomRPKI Valid220.167.223.0
- 220.167.226.0/23AS140061Qinghai TelecomRPKI Valid220.167.226.0
- 220.167.230.0/24AS140061Qinghai TelecomRPKI Valid220.167.230.0
- 220.167.231.0/24AS140061Qinghai TelecomRPKI Valid220.167.231.0
- 220.167.232.0/23AS140061Qinghai TelecomRPKI Valid220.167.232.0
- 220.167.234.0/24AS140061Qinghai TelecomRPKI Valid220.167.234.0
- 220.167.235.0/24AS140061Qinghai TelecomRPKI Valid220.167.235.0
- 220.167.244.0/22AS140061Qinghai TelecomRPKI Valid220.167.244.0
- 220.167.252.0/24AS140061Qinghai TelecomRPKI Valid220.167.252.0
- 220.167.253.0/24AS140061Qinghai TelecomRPKI Valid220.167.253.0
- 220.167.254.0/24AS140061Qinghai TelecomRPKI Valid220.167.254.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 90.190.0.0/15 (Telia Eesti, AS3249). 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.