BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
14.129.0.0/16
Announced exactly
- 14.129.0.0/16AS46003CONNECTWAVERPKI Not found14.129.0.0
- Registry
- APNIC · South Korea · Aug 12, 2010
- Delegated block
- 14.129.0.0 – 14.129.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 14.129.1.0/24AS9286KINXRPKI Not found14.129.1.0
- 14.129.2.0/24AS9286KINXRPKI Not found14.129.2.0
- 14.129.3.0/24AS9286KINXRPKI Not found14.129.3.0
- 14.129.4.0/24AS9286KINXRPKI Not found14.129.4.0
- 14.129.5.0/24AS9286KINXRPKI Not found14.129.5.0
- 14.129.6.0/24AS9286KINXRPKI Not found14.129.6.0
- 14.129.18.0/24AS9286KINXRPKI Not found14.129.18.0
- 14.129.64.0/24AS46003CONNECTWAVERPKI Not found14.129.64.0
- 14.129.65.0/24AS46003CONNECTWAVERPKI Not found14.129.65.0
- 14.129.66.0/24AS46003CONNECTWAVERPKI Not found14.129.66.0
- 14.129.73.0/24AS9286KINXRPKI Not found14.129.73.0
- 14.129.74.0/24AS9286KINXRPKI Not found14.129.74.0
- 14.129.75.0/24AS9286KINXRPKI Not found14.129.75.0
- 14.129.76.0/24AS9286KINXRPKI Not found14.129.76.0
- 14.129.80.0/20AS9286KINXRPKI Not found14.129.80.0
- 14.129.96.0/24AS9286KINXRPKI Not found14.129.96.0
- 14.129.97.0/24AS9286KINXRPKI Not found14.129.97.0
- 14.129.110.0/24AS9286KINXRPKI Not found14.129.110.0
- 14.129.111.0/24AS9286KINXRPKI Not found14.129.111.0
- 14.129.112.0/24AS9286KINXRPKI Not found14.129.112.0
- 14.129.113.0/24AS9286KINXRPKI Not found14.129.113.0
- 14.129.114.0/24AS9286KINXRPKI Not found14.129.114.0
- 14.129.115.0/24AS9286KINXRPKI Not found14.129.115.0
- 14.129.116.0/24AS9286KINXRPKI Not found14.129.116.0
- 14.129.117.0/24AS9286KINXRPKI Not found14.129.117.0
- 14.129.118.0/24AS9286KINXRPKI Not found14.129.118.0
- 14.129.119.0/24AS9286KINXRPKI Not found14.129.119.0
- 14.129.120.0/24AS9286KINXRPKI Not found14.129.120.0
- 14.129.140.0/24AS9286KINXRPKI Not found14.129.140.0
- 14.129.166.0/24AS9286KINXRPKI Not found14.129.166.0
- 14.129.167.0/24AS9286KINXRPKI Not found14.129.167.0
- 14.129.168.0/24AS9286KINXRPKI Not found14.129.168.0
- 14.129.169.0/24AS9286KINXRPKI Not found14.129.169.0
- 14.129.200.0/24AS9286KINXRPKI Not found14.129.200.0
- 14.129.201.0/24AS9286KINXRPKI Not found14.129.201.0
- 14.129.211.0/24AS9286KINXRPKI Not found14.129.211.0
- 14.129.212.0/24AS9286KINXRPKI Not found14.129.212.0
- 14.129.213.0/24AS9286KINXRPKI Not found14.129.213.0
- 14.129.214.0/24AS9286KINXRPKI Not found14.129.214.0
- 14.129.224.0/24AS38676flexnetworksRPKI Not found14.129.224.0
- 14.129.225.0/24AS38676flexnetworksRPKI Not found14.129.225.0
- 14.129.226.0/24AS38676flexnetworksRPKI Not found14.129.226.0
- 14.129.227.0/24AS38676flexnetworksRPKI Not found14.129.227.0
- 14.129.228.0/24AS38676flexnetworksRPKI Not found14.129.228.0
- 14.129.229.0/24AS38676flexnetworksRPKI Not found14.129.229.0
- 14.129.230.0/24AS38676flexnetworksRPKI Not found14.129.230.0
- 14.129.231.0/24AS38676flexnetworksRPKI Not found14.129.231.0
- 14.129.232.0/24AS38676flexnetworksRPKI Not found14.129.232.0
- 14.129.233.0/24AS38676flexnetworksRPKI Not found14.129.233.0
- 14.129.234.0/24AS38676flexnetworksRPKI Not found14.129.234.0
- 14.129.235.0/24AS38676flexnetworksRPKI Not found14.129.235.0
- 14.129.236.0/24AS38676flexnetworksRPKI Not found14.129.236.0
- 14.129.237.0/24AS38676flexnetworksRPKI Not found14.129.237.0
- 14.129.238.0/24AS38676flexnetworksRPKI Not found14.129.238.0
- 14.129.239.0/24AS38676flexnetworksRPKI Not found14.129.239.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.