BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
121.53.0.0/16
Announced exactly
- 121.53.0.0/16AS9457DREAMLINE CO.RPKI Not found121.53.0.0
- Registry
- APNIC · South Korea · Jun 19, 2006
- Delegated block
- 121.53.0.0 – 121.53.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 121.53.22.0/24AS9845LG HelloVision Corp.RPKI Not found121.53.22.0
- 121.53.80.0/21AS7625Kakao CorpRPKI Not found121.53.80.0
- 121.53.88.0/24AS7625Kakao CorpRPKI Not found121.53.88.0
- 121.53.89.0/24AS7625Kakao CorpRPKI Not found121.53.89.0
- 121.53.90.0/24AS18160Kakao CorpRPKI Not found121.53.90.0
- 121.53.91.0/24AS18160Kakao CorpRPKI Not found121.53.91.0
- 121.53.92.0/24AS18160Kakao CorpRPKI Not found121.53.92.0
- 121.53.93.0/24AS18160Kakao CorpRPKI Not found121.53.93.0
- 121.53.94.0/24AS18160Kakao CorpRPKI Not found121.53.94.0
- 121.53.95.0/24AS18160Kakao CorpRPKI Not found121.53.95.0
- 121.53.104.0/23AS38099Kakao CorpRPKI Not found121.53.104.0
- 121.53.106.0/23AS38099Kakao CorpRPKI Not found121.53.106.0
- 121.53.108.0/24AS38099Kakao CorpRPKI Not found121.53.108.0
- 121.53.109.0/24AS38099Kakao CorpRPKI Not found121.53.109.0
- 121.53.110.0/24AS38099Kakao CorpRPKI Not found121.53.110.0
- 121.53.111.0/24AS38099Kakao CorpRPKI Not found121.53.111.0
- 121.53.176.0/23AS38099Kakao CorpRPKI Not found121.53.176.0
- 121.53.178.0/23AS10178Kakaopay CorpRPKI Not found121.53.178.0
- 121.53.180.0/24AS38099Kakao CorpRPKI Not found121.53.180.0
- 121.53.181.0/24AS38099Kakao CorpRPKI Not found121.53.181.0
- 121.53.200.0/24AS38099Kakao CorpRPKI Not found121.53.200.0
- 121.53.201.0/24AS38099Kakao CorpRPKI Not found121.53.201.0
- 121.53.202.0/24AS38099Kakao CorpRPKI Not found121.53.202.0
- 121.53.203.0/24AS38099Kakao CorpRPKI Not found121.53.203.0
- 121.53.204.0/24AS38099Kakao CorpRPKI Not found121.53.204.0
- 121.53.205.0/24AS38099Kakao CorpRPKI Not found121.53.205.0
- 121.53.206.0/24AS38099Kakao CorpRPKI Not found121.53.206.0
- 121.53.207.0/24AS38099Kakao CorpRPKI Not found121.53.207.0
- 121.53.216.0/22AS7625Kakao CorpRPKI Not found121.53.216.0
- 121.53.220.0/24AS18160Kakao CorpRPKI Not found121.53.220.0
- 121.53.221.0/24AS18160Kakao CorpRPKI Not found121.53.221.0
- 121.53.222.0/24AS18160Kakao CorpRPKI Not found121.53.222.0
- 121.53.223.0/24AS18160Kakao CorpRPKI Not found121.53.223.0
- 121.53.230.0/24AS152199Kakao CorpRPKI Not found121.53.230.0
- 121.53.231.0/24AS152199Kakao CorpRPKI Not found121.53.231.0
- 121.53.234.0/24AS7625Kakao CorpRPKI Not found121.53.234.0
- 121.53.235.0/24AS7625Kakao CorpRPKI Not found121.53.235.0
- 121.53.236.0/24AS7625Kakao CorpRPKI Not found121.53.236.0
- 121.53.237.0/24AS7625Kakao CorpRPKI Not found121.53.237.0
- 121.53.238.0/23AS7625Kakao CorpRPKI Not found121.53.238.0
- 121.53.238.0/24AS7625Kakao CorpRPKI Not found121.53.238.0
- 121.53.239.0/24AS7625Kakao CorpRPKI Not found121.53.239.0
- 121.53.240.0/22AS7625Kakao CorpRPKI Not found121.53.240.0
- 121.53.244.0/22AS38099Kakao CorpRPKI Not found121.53.244.0
- 121.53.248.0/24AS17878DREAMMARK1RPKI Not found121.53.248.0
- 121.53.255.0/24AS38101Yulchon LLCRPKI Not found121.53.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.