BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.109.0.0/16
Announced exactly
- 210.109.0.0/16AS9848SEJONG NETWORKSRPKI Not found210.109.0.0
- Registry
- APNIC · South Korea · Apr 30, 1997
- Delegated block
- 210.109.0.0 – 210.109.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.109.11.0/24AS23588KAKAO EnterpriseRPKI Not found210.109.11.0
- 210.109.12.0/24AS23588KAKAO EnterpriseRPKI Not found210.109.12.0
- 210.109.14.0/23AS23588KAKAO EnterpriseRPKI Not found210.109.14.0
- 210.109.16.0/24AS9697LG HelloVision Corp.RPKI Not found210.109.16.0
- 210.109.19.0/24AS38676flexnetworksRPKI Not found210.109.19.0
- 210.109.20.0/24AS38676flexnetworksRPKI Not found210.109.20.0
- 210.109.21.0/24AS38676flexnetworksRPKI Not found210.109.21.0
- 210.109.22.0/24AS38676flexnetworksRPKI Not found210.109.22.0
- 210.109.23.0/24AS38676flexnetworksRPKI Not found210.109.23.0
- 210.109.52.0/23AS23588KAKAO EnterpriseRPKI Not found210.109.52.0
- 210.109.54.0/23AS23588KAKAO EnterpriseRPKI Not found210.109.54.0
- 210.109.58.0/23AS23588KAKAO EnterpriseRPKI Not found210.109.58.0
- 210.109.60.0/23AS23588KAKAO EnterpriseRPKI Not found210.109.60.0
- 210.109.76.0/22AS23588KAKAO EnterpriseRPKI Not found210.109.76.0
- 210.109.80.0/22AS23588KAKAO EnterpriseRPKI Not found210.109.80.0
- 210.109.96.0/21AS9952Hostway IDCRPKI Not found210.109.96.0
- 210.109.96.0/24AS9952Hostway IDCRPKI Not found210.109.96.0
- 210.109.97.0/24AS9952Hostway IDCRPKI Not found210.109.97.0
- 210.109.98.0/24AS9952Hostway IDCRPKI Not found210.109.98.0
- 210.109.99.0/24AS9952Hostway IDCRPKI Not found210.109.99.0
- 210.109.100.0/24AS9952Hostway IDCRPKI Not found210.109.100.0
- 210.109.101.0/24AS9952Hostway IDCRPKI Not found210.109.101.0
- 210.109.102.0/24AS9952Hostway IDCRPKI Not found210.109.102.0
- 210.109.103.0/24AS9952Hostway IDCRPKI Not found210.109.103.0
- 210.109.145.0/24AS23588KAKAO EnterpriseRPKI Not found210.109.145.0
- 210.109.152.0/24AS18300KEPCORPKI Not found210.109.152.0
- 210.109.153.0/24AS18300KEPCORPKI Not found210.109.153.0
- 210.109.154.0/24AS18300KEPCORPKI Not found210.109.154.0
- 210.109.155.0/24AS18300KEPCORPKI Not found210.109.155.0
- 210.109.156.0/24AS18300KEPCORPKI Not found210.109.156.0
- 210.109.157.0/24AS18300KEPCORPKI Not found210.109.157.0
- 210.109.158.0/24AS18300KEPCORPKI Not found210.109.158.0
- 210.109.159.0/24AS18300KEPCORPKI Not found210.109.159.0
- 210.109.175.0/24AS18305POSCO DXRPKI Not found210.109.175.0
- 210.109.200.0/21AS9848SEJONG NETWORKSRPKI Not found210.109.200.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.