BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
175.192.0.0/13
Announced exactly
- 175.192.0.0/13AS4766Korea TelecomRPKI Not found175.192.0.0
- Registry
- APNIC · South Korea · Jan 27, 2010
- Delegated block
- 175.192.0.0 – 175.255.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 175.192.181.0/24AS4790Chosun ilbo Inc.RPKI Not found175.192.181.0
- 175.192.182.0/24AS4790Chosun ilbo Inc.RPKI Not found175.192.182.0
- 175.192.230.0/24AS4766Korea TelecomRPKI Not found175.192.230.0
- 175.193.201.0/24AS17574Seoul Metropolitan Government Computer CenterRPKI Not found175.193.201.0
- 175.193.202.0/24AS17574Seoul Metropolitan Government Computer CenterRPKI Not found175.193.202.0
- 175.193.240.0/24AS55585CAPE Investment Securitie Co., Ltd.RPKI Not found175.193.240.0
- 175.194.168.0/24AS23554Shinhan BankRPKI Not found175.194.168.0
- 175.195.74.0/24AS131816IBK InsuranceRPKI Not found175.195.74.0
- 175.195.75.0/24AS131816IBK InsuranceRPKI Not found175.195.75.0
- 175.195.138.0/24AS9684HANWHA Corp. Information Service div.RPKI Not found175.195.138.0
- 175.195.175.0/24AS10179Daehan Investment Trust SecuritiesRPKI Not found175.195.175.0
- 175.196.1.0/24AS9696Oscar EnterpriseRPKI Not found175.196.1.0
- 175.196.12.0/24AS9696Oscar EnterpriseRPKI Not found175.196.12.0
- 175.196.99.0/24AS9696Oscar EnterpriseRPKI Not found175.196.99.0
- 175.196.160.0/24AS131844Nonghyup Property and Casualty Insurance Co.,LtdRPKI Not found175.196.160.0
- 175.196.208.0/22AS46009YABESKRPKI Not found175.196.208.0
- 175.196.227.0/25AS9524Hyundai Autoever Corp.RPKI Not found175.196.227.0
- 175.196.227.128/25AS9524Hyundai Autoever Corp.RPKI Not found175.196.227.128
- 175.196.239.0/24AS131822Korea National University of TransportationRPKI Not found175.196.239.0
- 175.196.240.0/24AS131822Korea National University of TransportationRPKI Not found175.196.240.0
- 175.197.49.128/25AS9701viawebRPKI Not found175.197.49.128
- 175.197.50.0/24AS55592Korea Data Telecommunication Co., Ltd.RPKI Not found175.197.50.0
- 175.197.53.0/24AS9318SK Broadband Co LtdRPKI Not found175.197.53.0
- 175.197.89.0/24AS55592Korea Data Telecommunication Co., Ltd.RPKI Not found175.197.89.0
- 175.197.102.0/23AS17837NHN KCP Corp.RPKI Not found175.197.102.0
- 175.197.102.0/24AS17837NHN KCP Corp.RPKI Not found175.197.102.0
- 175.197.103.0/24AS17837NHN KCP Corp.RPKI Not found175.197.103.0
- 175.197.107.0/24AS38676flexnetworksRPKI Not found175.197.107.0
- 175.197.165.0/24AS9526KOSCOMRPKI Not found175.197.165.0
- 175.197.198.0/24AS152214Korean Air LinesRPKI Not found175.197.198.0
- 175.197.199.0/24AS152214Korean Air LinesRPKI Not found175.197.199.0
- 175.197.200.0/24AS152287HANWHALIFERPKI Not found175.197.200.0
- 175.198.61.0/24AS4766Korea TelecomRPKI Not found175.198.61.0
- 175.198.65.0/24AS55592Korea Data Telecommunication Co., Ltd.RPKI Not found175.198.65.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.