BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
121.204.0.0/14
Announced exactly
- 121.204.0.0/14AS4134No.31,Jin-rong StreetRPKI Valid121.204.0.0
- Registry
- APNIC · China · Aug 31, 2006
- Delegated block
- 121.204.0.0 – 121.207.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 121.204.128.0/18AS133774FuzhouRPKI Valid121.204.128.0
- 121.204.128.0/19AS133774FuzhouRPKI Valid121.204.128.0
- 121.204.160.0/21AS133774FuzhouRPKI Valid121.204.160.0
- 121.204.168.0/22AS133774FuzhouRPKI Valid121.204.168.0
- 121.204.172.0/23AS133774FuzhouRPKI Valid121.204.172.0
- 121.204.176.0/20AS133774FuzhouRPKI Valid121.204.176.0
- 121.204.182.0/24AS133774FuzhouRPKI Valid121.204.182.0
- 121.204.192.0/21AS133774FuzhouRPKI Valid121.204.192.0
- 121.204.200.0/21AS133774FuzhouRPKI Valid121.204.200.0
- 121.204.208.0/21AS133774FuzhouRPKI Valid121.204.208.0
- 121.204.216.0/22AS133774FuzhouRPKI Valid121.204.216.0
- 121.204.220.0/23AS133774FuzhouRPKI Valid121.204.220.0
- 121.204.224.0/21AS133774FuzhouRPKI Valid121.204.224.0
- 121.204.232.0/23AS133774FuzhouRPKI Valid121.204.232.0
- 121.204.234.0/23AS133775XiamenRPKI Valid121.204.234.0
- 121.204.236.0/22AS133775XiamenRPKI Valid121.204.236.0
- 121.204.240.0/22AS133775XiamenRPKI Valid121.204.240.0
- 121.204.244.0/22AS133776QuanzhouRPKI Valid121.204.244.0
- 121.204.248.0/22AS133776QuanzhouRPKI Valid121.204.248.0
- 121.204.252.0/23AS133776QuanzhouRPKI Valid121.204.252.0
- 121.205.6.0/23AS133776QuanzhouRPKI Valid121.205.6.0
- 121.205.88.0/23AS133776QuanzhouRPKI Valid121.205.88.0
- 121.205.90.0/24AS133776QuanzhouRPKI Valid121.205.90.0
- 121.207.224.0/24AS133774FuzhouRPKI Valid121.207.224.0
- 121.207.225.0/24AS133774FuzhouRPKI Valid121.207.225.0
- 121.207.226.0/24AS133774FuzhouRPKI Valid121.207.226.0
- 121.207.227.0/24AS133774FuzhouRPKI Valid121.207.227.0
- 121.207.228.0/24AS133774FuzhouRPKI Valid121.207.228.0
- 121.207.229.0/24AS133774FuzhouRPKI Valid121.207.229.0
- 121.207.230.0/24AS133774FuzhouRPKI Valid121.207.230.0
- 121.207.231.0/24AS133774FuzhouRPKI Valid121.207.231.0
- 121.207.232.0/24AS133774FuzhouRPKI Valid121.207.232.0
- 121.207.233.0/24AS133774FuzhouRPKI Valid121.207.233.0
- 121.207.234.0/24AS133774FuzhouRPKI Valid121.207.234.0
- 121.207.235.0/24AS133774FuzhouRPKI Valid121.207.235.0
- 121.207.236.0/24AS133774FuzhouRPKI Valid121.207.236.0
- 121.207.237.0/24AS133774FuzhouRPKI Valid121.207.237.0
- 121.207.238.0/24AS133774FuzhouRPKI Valid121.207.238.0
- 121.207.239.0/24AS133774FuzhouRPKI Valid121.207.239.0
- 121.207.240.0/24AS133774FuzhouRPKI Valid121.207.240.0
- 121.207.241.0/24AS133774FuzhouRPKI Valid121.207.241.0
- 121.207.242.0/24AS133774FuzhouRPKI Valid121.207.242.0
- 121.207.243.0/24AS133774FuzhouRPKI Valid121.207.243.0
- 121.207.244.0/24AS133774FuzhouRPKI Valid121.207.244.0
- 121.207.245.0/24AS133774FuzhouRPKI Valid121.207.245.0
- 121.207.246.0/24AS133774FuzhouRPKI Valid121.207.246.0
- 121.207.247.0/24AS133774FuzhouRPKI Valid121.207.247.0
- 121.207.248.0/24AS133774FuzhouRPKI Valid121.207.248.0
- 121.207.249.0/24AS133774FuzhouRPKI Valid121.207.249.0
- 121.207.250.0/24AS133774FuzhouRPKI Valid121.207.250.0
- 121.207.251.0/24AS133774FuzhouRPKI Valid121.207.251.0
- 121.207.252.0/24AS133774FuzhouRPKI Valid121.207.252.0
- 121.207.253.0/24AS133774FuzhouRPKI Valid121.207.253.0
- 121.207.254.0/24AS133774FuzhouRPKI Valid121.207.254.0
- 121.207.255.0/24AS133774FuzhouRPKI Valid121.207.255.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.