BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
211.249.0.0/16
Announced exactly
- 211.249.0.0/16AS9457DREAMLINE CO.RPKI Not found211.249.0.0
- Registry
- APNIC · South Korea · Sep 8, 2000
- Delegated block
- 211.249.0.0 – 211.249.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 211.249.21.0/24AS17878DREAMMARK1RPKI Not found211.249.21.0
- 211.249.22.0/24AS17878DREAMMARK1RPKI Not found211.249.22.0
- 211.249.40.0/21AS23576NAVER Cloud Corp.RPKI Not found211.249.40.0
- 211.249.40.0/22AS23576NAVER Cloud Corp.RPKI Not found211.249.40.0
- 211.249.44.0/22AS23576NAVER Cloud Corp.RPKI Not found211.249.44.0
- 211.249.48.0/20AS23576NAVER Cloud Corp.RPKI Not found211.249.48.0
- 211.249.48.0/21AS23576NAVER Cloud Corp.RPKI Not found211.249.48.0
- 211.249.56.0/21AS23576NAVER Cloud Corp.RPKI Not found211.249.56.0
- 211.249.64.0/23AS23576NAVER Cloud Corp.RPKI Not found211.249.64.0
- 211.249.64.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.64.0
- 211.249.65.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.65.0
- 211.249.66.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.66.0
- 211.249.67.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.67.0
- 211.249.68.0/23AS23576NAVER Cloud Corp.RPKI Not found211.249.68.0
- 211.249.68.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.68.0
- 211.249.69.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.69.0
- 211.249.70.0/23AS23576NAVER Cloud Corp.RPKI Not found211.249.70.0
- 211.249.70.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.70.0
- 211.249.71.0/24AS23576NAVER Cloud Corp.RPKI Not found211.249.71.0
- 211.249.118.0/24AS17867KOREA BANKING INSTITUTERPKI Not found211.249.118.0
- 211.249.118.128/25AS17867KOREA BANKING INSTITUTERPKI Not found211.249.118.128
- 211.249.200.0/24AS38099Kakao CorpRPKI Not found211.249.200.0
- 211.249.201.0/24AS38099Kakao CorpRPKI Not found211.249.201.0
- 211.249.202.0/24AS38099Kakao CorpRPKI Not found211.249.202.0
- 211.249.203.0/24AS38099Kakao CorpRPKI Not found211.249.203.0
- 211.249.204.0/24AS38099Kakao CorpRPKI Not found211.249.204.0
- 211.249.205.0/24AS38099Kakao CorpRPKI Not found211.249.205.0
- 211.249.206.0/24AS10178Kakaopay CorpRPKI Not found211.249.206.0
- 211.249.207.0/24AS38099Kakao CorpRPKI Not found211.249.207.0
- 211.249.216.0/21AS7625Kakao CorpRPKI Not found211.249.216.0
- 211.249.240.0/24AS7625Kakao CorpRPKI Not found211.249.240.0
- 211.249.241.0/24AS7625Kakao CorpRPKI Not found211.249.241.0
- 211.249.242.0/24AS7625Kakao CorpRPKI Not found211.249.242.0
- 211.249.243.0/24AS7625Kakao CorpRPKI Not found211.249.243.0
- 211.249.244.0/24AS7625Kakao CorpRPKI Not found211.249.244.0
- 211.249.245.0/24AS7625Kakao CorpRPKI Not found211.249.245.0
- 211.249.246.0/24AS7625Kakao CorpRPKI Not found211.249.246.0
- 211.249.247.0/24AS7625Kakao CorpRPKI Not found211.249.247.0
- 211.249.248.0/24AS7625Kakao CorpRPKI Not found211.249.248.0
- 211.249.249.0/24AS7625Kakao CorpRPKI Not found211.249.249.0
- 211.249.250.0/24AS7625Kakao CorpRPKI Not found211.249.250.0
- 211.249.251.0/24AS7625Kakao CorpRPKI Not found211.249.251.0
- 211.249.252.0/22AS38099Kakao CorpRPKI Not found211.249.252.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.