BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
61.109.128.0/17
Announced exactly
- 61.109.128.0/17AS9848SEJONG NETWORKSRPKI Not found61.109.128.0
- Registry
- APNIC · South Korea · Mar 21, 2001
- Delegated block
- 61.109.128.0 – 61.109.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 61.109.150.0/24AS9845LG HelloVision Corp.RPKI Not found61.109.150.0
- 61.109.158.0/24AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Not found61.109.158.0
- 61.109.159.0/24AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Not found61.109.159.0
- 61.109.160.0/22AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Not found61.109.160.0
- 61.109.160.0/24AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Not found61.109.160.0
- 61.109.164.0/24AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Not found61.109.164.0
- 61.109.192.0/24AS38676flexnetworksRPKI Not found61.109.192.0
- 61.109.193.0/24AS38676flexnetworksRPKI Not found61.109.193.0
- 61.109.194.0/24AS38676flexnetworksRPKI Not found61.109.194.0
- 61.109.195.0/24AS38676flexnetworksRPKI Not found61.109.195.0
- 61.109.196.0/24AS38676flexnetworksRPKI Not found61.109.196.0
- 61.109.213.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.213.0
- 61.109.214.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.214.0
- 61.109.215.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.215.0
- 61.109.216.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.216.0
- 61.109.217.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.217.0
- 61.109.218.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.218.0
- 61.109.220.0/22AS131828KAKAO EnterpriseRPKI Not found61.109.220.0
- 61.109.232.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.232.0
- 61.109.233.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.233.0
- 61.109.235.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.235.0
- 61.109.236.0/22AS23588KAKAO EnterpriseRPKI Not found61.109.236.0
- 61.109.240.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.240.0
- 61.109.241.0/24AS23588KAKAO EnterpriseRPKI Not found61.109.241.0
- 61.109.244.0/22AS9952Hostway IDCRPKI Not found61.109.244.0
- 61.109.244.0/24AS9952Hostway IDCRPKI Not found61.109.244.0
- 61.109.245.0/24AS9952Hostway IDCRPKI Not found61.109.245.0
- 61.109.246.0/24AS9952Hostway IDCRPKI Not found61.109.246.0
- 61.109.247.0/24AS9952Hostway IDCRPKI Not found61.109.247.0
- 61.109.250.0/24AS9952Hostway IDCRPKI Not found61.109.250.0
- 61.109.252.0/22AS9952Hostway IDCRPKI Not found61.109.252.0
- 61.109.252.0/24AS9952Hostway IDCRPKI Not found61.109.252.0
- 61.109.253.0/24AS9952Hostway IDCRPKI Not found61.109.253.0
- 61.109.254.0/24AS9952Hostway IDCRPKI Not found61.109.254.0
- 61.109.255.0/24AS9952Hostway IDCRPKI Not found61.109.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.