BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
61.80.0.0/14
Announced exactly
- 61.80.0.0/14AS4766Korea TelecomRPKI Not found61.80.0.0
- Registry
- APNIC · South Korea · May 11, 2001
- Delegated block
- 61.80.0.0 – 61.83.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 61.80.34.0/24AS4766Korea TelecomRPKI Not found61.80.34.0
- 61.80.45.0/24AS4766Korea TelecomRPKI Not found61.80.45.0
- 61.80.49.0/24AS4766Korea TelecomRPKI Not found61.80.49.0
- 61.80.132.0/24AS4766Korea TelecomRPKI Not found61.80.132.0
- 61.80.133.0/24AS4766Korea TelecomRPKI Not found61.80.133.0
- 61.80.206.0/23AS18341Gumi CollegeRPKI Not found61.80.206.0
- 61.80.208.0/20AS18341Gumi CollegeRPKI Not found61.80.208.0
- 61.81.105.0/24AS10190Joongbu UniversityRPKI Not found61.81.105.0
- 61.81.106.0/23AS10190Joongbu UniversityRPKI Not found61.81.106.0
- 61.81.108.0/22AS10190Joongbu UniversityRPKI Not found61.81.108.0
- 61.81.224.0/19AS4766Korea TelecomRPKI Not found61.81.224.0
- 61.81.242.0/25AS4766Korea TelecomRPKI Not found61.81.242.0
- 61.82.74.0/24AS9318SK Broadband Co LtdRPKI Not found61.82.74.0
- 61.82.75.0/24AS9318SK Broadband Co LtdRPKI Not found61.82.75.0
- 61.82.76.0/24AS9318SK Broadband Co LtdRPKI Not found61.82.76.0
- 61.82.91.0/24AS4766Korea TelecomRPKI Not found61.82.91.0
- 61.82.102.0/24AS9318SK Broadband Co LtdRPKI Not found61.82.102.0
- 61.82.148.0/24AS55592Korea Data Telecommunication Co., Ltd.RPKI Not found61.82.148.0
- 61.82.252.0/22AS18023Korea Maritime and Ocean UniversityRPKI Not found61.82.252.0
- 61.82.252.0/23AS18023Korea Maritime and Ocean UniversityRPKI Not found61.82.252.0
- 61.82.254.0/23AS18023Korea Maritime and Ocean UniversityRPKI Not found61.82.254.0
- 61.83.84.0/23AS4793Hyundai Heavy IndustriesRPKI Not found61.83.84.0
- 61.83.84.0/24AS4793Hyundai Heavy IndustriesRPKI Not found61.83.84.0
- 61.83.85.0/24AS4793Hyundai Heavy IndustriesRPKI Not found61.83.85.0
- 61.83.124.0/24AS4793Hyundai Heavy IndustriesRPKI Not found61.83.124.0
- 61.83.128.0/24AS4766Korea TelecomRPKI Not found61.83.128.0
- 61.83.129.0/24AS4766Korea TelecomRPKI Not found61.83.129.0
- 61.83.130.0/24AS4766Korea TelecomRPKI Not found61.83.130.0
- 61.83.131.0/24AS4766Korea TelecomRPKI Not found61.83.131.0
- 61.83.192.0/24AS131805NHSAVINGSBANKRPKI Not found61.83.192.0
- 61.83.221.0/24AS38408GYEONGGI PROVINCIAL ANYANG OFFICE OF EDUCATIONRPKI Not found61.83.221.0
- 61.83.223.0/24AS4766Korea TelecomRPKI Not found61.83.223.0
- 61.83.233.0/24AS4766Korea TelecomRPKI Not found61.83.233.0
- 61.83.234.0/23AS55624DAELIMRPKI Not found61.83.234.0
- 61.83.236.0/22AS55624DAELIMRPKI Not found61.83.236.0
- 61.83.247.0/25AS45400Korea TelecomRPKI Not found61.83.247.0
- 61.83.247.128/25AS45400Korea TelecomRPKI Not found61.83.247.128
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.