BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
220.72.0.0/13
Announced exactly
- 220.72.0.0/13AS4766Korea TelecomRPKI Not found220.72.0.0
- Registry
- APNIC · South Korea · Aug 29, 2002
- Delegated block
- 220.72.0.0 – 220.79.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 220.72.24.0/24AS9492Maeil Business NewspaperRPKI Not found220.72.24.0
- 220.73.10.0/24AS4668LG CNSRPKI Not found220.73.10.0
- 220.73.180.0/22AS4766Korea TelecomRPKI Not found220.73.180.0
- 220.73.184.0/22AS4766Korea TelecomRPKI Not found220.73.184.0
- 220.73.188.0/22AS4766Korea TelecomRPKI Not found220.73.188.0
- 220.73.192.0/20AS4766Korea TelecomRPKI Not found220.73.192.0
- 220.73.208.0/22AS4766Korea TelecomRPKI Not found220.73.208.0
- 220.73.218.0/24AS55593netmarbleRPKI Not found220.73.218.0
- 220.73.221.0/24AS55593netmarbleRPKI Not found220.73.221.0
- 220.73.230.0/23AS9870DONG-EUI UNIVERSITYRPKI Not found220.73.230.0
- 220.73.230.0/24AS9870DONG-EUI UNIVERSITYRPKI Not found220.73.230.0
- 220.73.231.0/24AS9870DONG-EUI UNIVERSITYRPKI Not found220.73.231.0
- 220.73.232.0/24AS9870DONG-EUI UNIVERSITYRPKI Not found220.73.232.0
- 220.73.233.0/24AS9870DONG-EUI UNIVERSITYRPKI Not found220.73.233.0
- 220.73.234.0/24AS4766Korea TelecomRPKI Not found220.73.234.0
- 220.73.235.0/24AS4766Korea TelecomRPKI Not found220.73.235.0
- 220.73.236.0/24AS4766Korea TelecomRPKI Not found220.73.236.0
- 220.74.39.0/24AS131860Nonghyup Property and Casualty Insurance Co.,LtdRPKI Not found220.74.39.0
- 220.75.200.0/24AS131096Master Motors ManagementRPKI Not found220.75.200.0
- 220.75.210.0/24AS17859NICEINFOMATIONSERVICERPKI Not found220.75.210.0
- 220.75.238.128/25AS4671KTOARPKI Not found220.75.238.128
- 220.76.17.0/24AS131093viva republicaRPKI Not found220.76.17.0
- 220.76.115.0/24AS10185Hana Bank Co.RPKI Not found220.76.115.0
- 220.76.177.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found220.76.177.0
- 220.76.194.0/24AS152290JejuairRPKI Not found220.76.194.0
- 220.76.222.0/24AS9855Korean Federation of Community Credit CooperativesRPKI Not found220.76.222.0
- 220.76.239.0/24AS9526KOSCOMRPKI Not found220.76.239.0
- 220.77.21.0/24AS17611Korea Housing Finance CorporationRPKI Not found220.77.21.0
- 220.77.43.0/24AS17611Korea Housing Finance CorporationRPKI Not found220.77.43.0
- 220.77.176.0/24AS9631youngsan universityRPKI Not found220.77.176.0
- 220.77.177.0/24AS9631youngsan universityRPKI Not found220.77.177.0
- 220.78.55.0/24AS4766Korea TelecomRPKI Not found220.78.55.0
- 220.78.56.0/24AS4766Korea TelecomRPKI Not found220.78.56.0
- 220.78.57.0/24AS4766Korea TelecomRPKI Not found220.78.57.0
- 220.78.113.0/24AS38705KOREA DATARPKI Not found220.78.113.0
- 220.78.134.0/24AS9577KYOBO SECURITIESRPKI Not found220.78.134.0
- 220.78.173.0/25AS38402Gyeonggi Provincial Suwon Office of EducationRPKI Not found220.78.173.0
- 220.79.220.0/24AS38431KB InsuranceRPKI Not found220.79.220.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.