BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
106.240.0.0/12
Announced exactly
- 106.240.0.0/12AS3786LG DACOM CorporationRPKI Not found106.240.0.0
- Registry
- APNIC · South Korea · Mar 28, 2011
- Delegated block
- 106.240.0.0 – 106.255.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 106.241.38.0/24AS10167HANVIT BANKRPKI Not found106.241.38.0
- 106.241.45.0/24AS23555Shinhan BankRPKI Not found106.241.45.0
- 106.241.47.0/24AS9703Shinhan BankRPKI Not found106.241.47.0
- 106.241.48.0/24AS9703Shinhan BankRPKI Not found106.241.48.0
- 106.241.49.0/24AS9703Shinhan BankRPKI Not found106.241.49.0
- 106.241.74.0/24AS131819Doosan Engineering Construction Co.,LtdRPKI Not found106.241.74.0
- 106.241.79.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found106.241.79.0
- 106.241.135.0/24AS9641Korea Development BankRPKI Not found106.241.135.0
- 106.241.145.0/24AS17583Keumgang Cable NetworkRPKI Not found106.241.145.0
- 106.241.146.0/23AS17583Keumgang Cable NetworkRPKI Not found106.241.146.0
- 106.241.148.0/22AS17583Keumgang Cable NetworkRPKI Not found106.241.148.0
- 106.241.152.0/22AS17583Keumgang Cable NetworkRPKI Not found106.241.152.0
- 106.241.156.0/24AS17583Keumgang Cable NetworkRPKI Not found106.241.156.0
- 106.241.157.0/24AS17834WOORICARDRPKI Not found106.241.157.0
- 106.249.5.0/24AS131093viva republicaRPKI Not found106.249.5.0
- 106.249.18.0/23AS45974NHNCLOUDRPKI Not found106.249.18.0
- 106.249.18.0/24AS45974NHNCLOUDRPKI Not found106.249.18.0
- 106.249.19.0/24AS45974NHNCLOUDRPKI Not found106.249.19.0
- 106.249.20.0/22AS45974NHNCLOUDRPKI Not found106.249.20.0
- 106.249.20.0/24AS45974NHNCLOUDRPKI Not found106.249.20.0
- 106.249.21.0/24AS45974NHNCLOUDRPKI Not found106.249.21.0
- 106.249.22.0/24AS45974NHNCLOUDRPKI Not found106.249.22.0
- 106.249.23.0/24AS45974NHNCLOUDRPKI Not found106.249.23.0
- 106.249.24.0/21AS45974NHNCLOUDRPKI Not found106.249.24.0
- 106.249.24.0/24AS45974NHNCLOUDRPKI Not found106.249.24.0
- 106.249.25.0/24AS45974NHNCLOUDRPKI Not found106.249.25.0
- 106.249.30.0/24AS45974NHNCLOUDRPKI Not found106.249.30.0
- 106.249.31.0/24AS45974NHNCLOUDRPKI Not found106.249.31.0
- 106.249.32.0/23AS45974NHNCLOUDRPKI Not found106.249.32.0
- 106.249.32.0/24AS45974NHNCLOUDRPKI Not found106.249.32.0
- 106.249.33.0/24AS45974NHNCLOUDRPKI Not found106.249.33.0
- 106.249.35.0/24AS9972INTMANAGEMENT Corp.,RPKI Not found106.249.35.0
- 106.249.45.0/24AS9959KOREA STOCK EXCHANGERPKI Not found106.249.45.0
- 106.249.55.0/24AS18317SHINHAN DSRPKI Not found106.249.55.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.