BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
220.80.0.0/13
Announced exactly
- 220.80.0.0/13AS4766Korea TelecomRPKI Not found220.80.0.0
- Registry
- APNIC · South Korea · Aug 29, 2002
- Delegated block
- 220.80.0.0 – 220.87.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 220.80.112.0/22AS4766Korea TelecomRPKI Not found220.80.112.0
- 220.81.64.0/24AS4766Korea TelecomRPKI Not found220.81.64.0
- 220.81.65.0/24AS4766Korea TelecomRPKI Not found220.81.65.0
- 220.81.66.0/24AS4766Korea TelecomRPKI Not found220.81.66.0
- 220.81.92.0/22AS4766Korea TelecomRPKI Not found220.81.92.0
- 220.81.195.0/24AS9523Mokwon UniversityRPKI Not found220.81.195.0
- 220.81.196.0/22AS9523Mokwon UniversityRPKI Not found220.81.196.0
- 220.82.0.0/21AS18035HANSEO UNIVERSITYRPKI Not found220.82.0.0
- 220.83.15.0/24AS38422Seowon UniversityRPKI Not found220.83.15.0
- 220.83.16.0/24AS38422Seowon UniversityRPKI Not found220.83.16.0
- 220.83.32.0/24AS4766Korea TelecomRPKI Not found220.83.32.0
- 220.83.33.0/24AS4766Korea TelecomRPKI Not found220.83.33.0
- 220.83.34.0/24AS4766Korea TelecomRPKI Not found220.83.34.0
- 220.83.35.0/24AS4766Korea TelecomRPKI Not found220.83.35.0
- 220.83.46.0/24AS4766Korea TelecomRPKI Not found220.83.46.0
- 220.83.47.0/24AS4766Korea TelecomRPKI Not found220.83.47.0
- 220.83.92.0/24AS4766Korea TelecomRPKI Not found220.83.92.0
- 220.83.125.128/25AS4766Korea TelecomRPKI Not found220.83.125.128
- 220.83.156.0/24AS55615DOUZONEBIZONRPKI Not found220.83.156.0
- 220.83.157.0/24AS55615DOUZONEBIZONRPKI Not found220.83.157.0
- 220.83.237.0/24AS17856Konyang UniversityRPKI Not found220.83.237.0
- 220.85.44.0/24AS45409KBCAPITALRPKI Not found220.85.44.0
- 220.85.223.0/24AS9778DAEJIN UNIVERSITYRPKI Not found220.85.223.0
- 220.86.242.0/24AS4766Korea TelecomRPKI Not found220.86.242.0
- 220.86.243.0/24AS4766Korea TelecomRPKI Not found220.86.243.0
- 220.86.244.0/24AS4766Korea TelecomRPKI Not found220.86.244.0
- 220.86.245.0/24AS4766Korea TelecomRPKI Not found220.86.245.0
- 220.87.44.0/24AS9840INSPIRE Integrated ResortRPKI Not found220.87.44.0
- 220.87.124.0/24AS4766Korea TelecomRPKI Not found220.87.124.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.