BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
220.120.0.0/13
Announced exactly
- 220.120.0.0/13AS4766Korea TelecomRPKI Not found220.120.0.0
- Registry
- APNIC · South Korea · Dec 31, 2002
- Delegated block
- 220.120.0.0 – 220.127.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 220.120.10.0/24AS131095HanwhalifeFinancialServiceRPKI Not found220.120.10.0
- 220.120.86.0/24AS131095HanwhalifeFinancialServiceRPKI Not found220.120.86.0
- 220.120.122.0/24AS4766Korea TelecomRPKI Not found220.120.122.0
- 220.120.127.0/24AS38401Gyeonggi Provincial Anseong Office of EducationRPKI Not found220.120.127.0
- 220.120.129.0/24AS38400Gyeonggi-do Pyongtaek Office EducationRPKI Not found220.120.129.0
- 220.120.182.0/23AS9572Hankuk University of Foreign Studies Computer CenterRPKI Not found220.120.182.0
- 220.120.228.0/23AS4766Korea TelecomRPKI Not found220.120.228.0
- 220.120.253.0/24AS131819Doosan Engineering Construction Co.,LtdRPKI Not found220.120.253.0
- 220.121.131.128/25AS4766Korea TelecomRPKI Not found220.121.131.128
- 220.122.214.0/25AS18305POSCO DXRPKI Not found220.122.214.0
- 220.123.79.0/24AS17856Konyang UniversityRPKI Not found220.123.79.0
- 220.123.80.0/22AS23552Korea Nazarene UniversityRPKI Not found220.123.80.0
- 220.123.126.0/23AS17856Konyang UniversityRPKI Not found220.123.126.0
- 220.123.193.0/24AS4766Korea TelecomRPKI Not found220.123.193.0
- 220.125.109.0/24AS4766Korea TelecomRPKI Not found220.125.109.0
- 220.125.139.0/24AS4766Korea TelecomRPKI Not found220.125.139.0
- 220.125.143.0/24AS4766Korea TelecomRPKI Not found220.125.143.0
- 220.125.170.0/24AS4766Korea TelecomRPKI Not found220.125.170.0
- 220.126.26.0/24AS10185Hana Bank Co.RPKI Not found220.126.26.0
- 220.126.45.0/24AS9578Cheiljedang.Co.Inc.RPKI Not found220.126.45.0
- 220.126.159.0/24AS9578Cheiljedang.Co.Inc.RPKI Not found220.126.159.0
- 220.127.5.0/24AS38707TosspaymentsRPKI Not found220.127.5.0
- 220.127.13.0/24AS4766Korea TelecomRPKI Not found220.127.13.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.