BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.103.128.0/17
Announced exactly
- 210.103.128.0/17AS9848SEJONG NETWORKSRPKI Not found210.103.128.0
- Registry
- APNIC · South Korea · Dec 6, 1997
- Delegated block
- 210.103.128.0 – 210.103.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.103.137.0/24AS131866Digital Edge KoreaRPKI Not found210.103.137.0
- 210.103.138.0/24AS131866Digital Edge KoreaRPKI Not found210.103.138.0
- 210.103.142.0/24AS131866Digital Edge KoreaRPKI Not found210.103.142.0
- 210.103.143.0/24AS131866Digital Edge KoreaRPKI Not found210.103.143.0
- 210.103.152.0/24AS38676flexnetworksRPKI Not found210.103.152.0
- 210.103.153.0/24AS38676flexnetworksRPKI Not found210.103.153.0
- 210.103.154.0/24AS38676flexnetworksRPKI Not found210.103.154.0
- 210.103.155.0/24AS38676flexnetworksRPKI Not found210.103.155.0
- 210.103.176.0/24AS38676flexnetworksRPKI Not found210.103.176.0
- 210.103.187.0/24AS131866Digital Edge KoreaRPKI Not found210.103.187.0
- 210.103.188.0/24AS131866Digital Edge KoreaRPKI Not found210.103.188.0
- 210.103.189.0/24AS131866Digital Edge KoreaRPKI Not found210.103.189.0
- 210.103.190.0/24AS131866Digital Edge KoreaRPKI Not found210.103.190.0
- 210.103.191.0/24AS131866Digital Edge KoreaRPKI Not found210.103.191.0
- 210.103.203.0/24AS23593bkl LLCRPKI Not found210.103.203.0
- 210.103.240.0/24AS10158Kakao CorpRPKI Not found210.103.240.0
- 210.103.241.0/24AS10158Kakao CorpRPKI Not found210.103.241.0
- 210.103.242.0/24AS10158Kakao CorpRPKI Not found210.103.242.0
- 210.103.243.0/24AS10158Kakao CorpRPKI Not found210.103.243.0
- 210.103.244.0/24AS10158Kakao CorpRPKI Not found210.103.244.0
- 210.103.245.0/24AS10158Kakao CorpRPKI Not found210.103.245.0
- 210.103.246.0/24AS10158Kakao CorpRPKI Not found210.103.246.0
- 210.103.247.0/24AS10158Kakao CorpRPKI Not found210.103.247.0
- 210.103.253.0/24AS10178Kakaopay CorpRPKI Not found210.103.253.0
- 210.103.254.0/24AS10178Kakaopay CorpRPKI Not found210.103.254.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.