BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.122.0.0/16
Announced exactly
- 210.122.0.0/16AS9848SEJONGTELECOM-AS-KR SEJONG NETWORKSRPKI Not found210.122.0.0
- Registry
- APNIC · South Korea · Nov 26, 1996
- Delegated block
- 210.122.0.0 – 210.122.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.122.0.0/24AS9952HOSTWAY-AS-KR Hostway IDCRPKI Not found210.122.0.0
- 210.122.1.0/24AS9952HOSTWAY-AS-KR Hostway IDCRPKI Not found210.122.1.0
- 210.122.6.0/24AS9952HOSTWAY-AS-KR Hostway IDCRPKI Not found210.122.6.0
- 210.122.9.0/24AS9952HOSTWAY-AS-KR Hostway IDCRPKI Not found210.122.9.0
- 210.122.16.0/20AS4961DISC-AS-KR Daewoo Information SystemsRPKI Not found210.122.16.0
- 210.122.40.0/24AS9952HOSTWAY-AS-KR Hostway IDCRPKI Not found210.122.40.0
- 210.122.69.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.69.0
- 210.122.72.0/22AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.72.0
- 210.122.72.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.72.0
- 210.122.73.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.73.0
- 210.122.74.0/23AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.74.0
- 210.122.76.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.76.0
- 210.122.77.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.77.0
- 210.122.78.0/23AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.78.0
- 210.122.80.0/23AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.80.0
- 210.122.80.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.80.0
- 210.122.81.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.81.0
- 210.122.81.0/25AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.81.0
- 210.122.81.128/25AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.81.128
- 210.122.96.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.96.0
- 210.122.97.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.97.0
- 210.122.98.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.98.0
- 210.122.99.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.99.0
- 210.122.100.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.100.0
- 210.122.101.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.101.0
- 210.122.102.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.102.0
- 210.122.103.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.103.0
- 210.122.104.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.104.0
- 210.122.105.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.105.0
- 210.122.106.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.106.0
- 210.122.107.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.107.0
- 210.122.108.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.108.0
- 210.122.109.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.109.0
- 210.122.110.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.110.0
- 210.122.111.0/24AS9578CJNET-AS Cheiljedang.Co.Inc.RPKI Not found210.122.111.0
- 210.122.123.0/24AS18317SHINHANSYS2-AS-KR SHINHAN DSRPKI Not found210.122.123.0
- 210.122.128.0/20AS131826HY-AS-KR hyRPKI Not found210.122.128.0
- 210.122.128.0/21AS131826HY-AS-KR hyRPKI Not found210.122.128.0
- 210.122.128.0/24AS131826HY-AS-KR hyRPKI Not found210.122.128.0
- 210.122.136.0/24AS131826HY-AS-KR hyRPKI Not found210.122.136.0
- 210.122.137.0/24AS131826HY-AS-KR hyRPKI Not found210.122.137.0
- 210.122.138.0/24AS131826HY-AS-KR hyRPKI Not found210.122.138.0
- 210.122.139.0/24AS131826HY-AS-KR hyRPKI Not found210.122.139.0
- 210.122.140.0/22AS131826HY-AS-KR hyRPKI Not found210.122.140.0
- 210.122.160.0/21AS9848SEJONGTELECOM-AS-KR SEJONG NETWORKSRPKI Not found210.122.160.0
- 210.122.170.0/24AS38123AMCSEOUL-AS-KR asan medical centerRPKI Not found210.122.170.0
- 210.122.171.0/24AS38123AMCSEOUL-AS-KR asan medical centerRPKI Not found210.122.171.0
- 210.122.172.0/24AS38123AMCSEOUL-AS-KR asan medical centerRPKI Not found210.122.172.0
- 210.122.173.0/24AS38123AMCSEOUL-AS-KR asan medical centerRPKI Not found210.122.173.0
- 210.122.176.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.176.0
- 210.122.177.0/24AS17837KCP-AS-KR NHN KCP Corp.RPKI Not found210.122.177.0
- 210.122.230.0/23AS9848SEJONGTELECOM-AS-KR SEJONG NETWORKSRPKI Not found210.122.230.0
- 210.122.248.0/21AS9848SEJONGTELECOM-AS-KR SEJONG NETWORKSRPKI Not found210.122.248.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.