BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
221.160.0.0/13
Announced exactly
- 221.160.0.0/13AS4766Korea TelecomRPKI Not found221.160.0.0
- Registry
- APNIC · South Korea · Apr 17, 2003
- Delegated block
- 221.160.0.0 – 221.167.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 221.160.30.0/24AS4766Korea TelecomRPKI Not found221.160.30.0
- 221.160.143.0/24AS4766Korea TelecomRPKI Not found221.160.143.0
- 221.160.151.0/24AS38422Seowon UniversityRPKI Not found221.160.151.0
- 221.160.178.0/24AS4766Korea TelecomRPKI Not found221.160.178.0
- 221.160.179.0/25AS4766Korea TelecomRPKI Not found221.160.179.0
- 221.160.183.0/24AS38422Seowon UniversityRPKI Not found221.160.183.0
- 221.160.197.0/24AS4766Korea TelecomRPKI Not found221.160.197.0
- 221.161.97.0/25AS23562BUSAN CITY ENVIRONMENTAL INSTALLATIONS CORPRPKI Not found221.161.97.0
- 221.161.97.128/25AS23562BUSAN CITY ENVIRONMENTAL INSTALLATIONS CORPRPKI Not found221.161.97.128
- 221.162.24.0/24AS45377Jeju Special Self Governing Provincial office of EducationRPKI Not found221.162.24.0
- 221.162.86.0/24AS4766Korea TelecomRPKI Not found221.162.86.0
- 221.163.32.0/24AS18323Seoul National University Bundang HospitalRPKI Not found221.163.32.0
- 221.164.0.0/24AS9631youngsan universityRPKI Not found221.164.0.0
- 221.164.1.0/24AS9631youngsan universityRPKI Not found221.164.1.0
- 221.164.2.0/24AS9631youngsan universityRPKI Not found221.164.2.0
- 221.164.3.0/24AS9631youngsan universityRPKI Not found221.164.3.0
- 221.164.5.0/24AS9631youngsan universityRPKI Not found221.164.5.0
- 221.164.9.0/24AS131101BNK SYSTEMRPKI Not found221.164.9.0
- 221.164.68.0/24AS9631youngsan universityRPKI Not found221.164.68.0
- 221.164.69.0/24AS9631youngsan universityRPKI Not found221.164.69.0
- 221.164.70.0/24AS9631youngsan universityRPKI Not found221.164.70.0
- 221.164.71.0/24AS9631youngsan universityRPKI Not found221.164.71.0
- 221.165.26.0/24AS4766Korea TelecomRPKI Not found221.165.26.0
- 221.165.31.0/24AS9862GORayNetRPKI Not found221.165.31.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.