BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.125.128.0/17
Announced exactly
- 210.125.128.0/17AS4766Korea TelecomRPKI Not found210.125.128.0
- Registry
- APNIC · South Korea · Jul 18, 1996
- Delegated block
- 210.125.128.0 – 210.125.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.125.128.0/22AS4766Korea TelecomRPKI Not found210.125.128.0
- 210.125.132.0/24AS4766Korea TelecomRPKI Not found210.125.132.0
- 210.125.133.0/24AS4766Korea TelecomRPKI Not found210.125.133.0
- 210.125.134.0/24AS4766Korea TelecomRPKI Not found210.125.134.0
- 210.125.135.0/24AS4766Korea TelecomRPKI Not found210.125.135.0
- 210.125.136.0/22AS18029Daejeon Helath Sciences CollegeRPKI Not found210.125.136.0
- 210.125.140.0/22AS3786LG DACOM CorporationRPKI Not found210.125.140.0
- 210.125.140.0/24AS3786LG DACOM CorporationRPKI Not found210.125.140.0
- 210.125.141.0/24AS3786LG DACOM CorporationRPKI Not found210.125.141.0
- 210.125.142.0/24AS3786LG DACOM CorporationRPKI Not found210.125.142.0
- 210.125.143.0/24AS3786LG DACOM CorporationRPKI Not found210.125.143.0
- 210.125.144.0/20AS18158CHUNGBUK NATIONAL UNIVERSITYRPKI Not found210.125.144.0
- 210.125.158.0/24AS3786LG DACOM CorporationRPKI Not found210.125.158.0
- 210.125.160.0/23AS4766Korea TelecomRPKI Not found210.125.160.0
- 210.125.162.0/24AS4766Korea TelecomRPKI Not found210.125.162.0
- 210.125.163.0/24AS4766Korea TelecomRPKI Not found210.125.163.0
- 210.125.164.0/24AS3786LG DACOM CorporationRPKI Not found210.125.164.0
- 210.125.165.0/24AS3786LG DACOM CorporationRPKI Not found210.125.165.0
- 210.125.166.0/24AS4766Korea TelecomRPKI Not found210.125.166.0
- 210.125.167.0/24AS4766Korea TelecomRPKI Not found210.125.167.0
- 210.125.168.0/24AS4766Korea TelecomRPKI Not found210.125.168.0
- 210.125.169.0/24AS4766Korea TelecomRPKI Not found210.125.169.0
- 210.125.170.0/24AS4766Korea TelecomRPKI Not found210.125.170.0
- 210.125.171.0/24AS4766Korea TelecomRPKI Not found210.125.171.0
- 210.125.172.0/23AS4766Korea TelecomRPKI Not found210.125.172.0
- 210.125.174.0/24AS17858LG POWERCOMMRPKI Not found210.125.174.0
- 210.125.176.0/21AS9978The University of SeoulRPKI Not found210.125.176.0
- 210.125.183.128/25AS9978The University of SeoulRPKI Not found210.125.183.128
- 210.125.185.0/24AS4766Korea TelecomRPKI Not found210.125.185.0
- 210.125.186.0/23AS3786LG DACOM CorporationRPKI Not found210.125.186.0
- 210.125.186.0/24AS4766Korea TelecomRPKI Not found210.125.186.0
- 210.125.187.0/24AS4766Korea TelecomRPKI Not found210.125.187.0
- 210.125.188.0/24AS4766Korea TelecomRPKI Not found210.125.188.0
- 210.125.189.0/24AS4766Korea TelecomRPKI Not found210.125.189.0
- 210.125.190.0/24AS4766Korea TelecomRPKI Not found210.125.190.0
- 210.125.191.0/24AS4766Korea TelecomRPKI Not found210.125.191.0
- 210.125.192.0/24AS9867VISION College of JeonjuRPKI Not found210.125.192.0
- 210.125.193.0/24AS9867VISION College of JeonjuRPKI Not found210.125.193.0
- 210.125.194.0/24AS9867VISION College of JeonjuRPKI Not found210.125.194.0
- 210.125.195.0/24AS9867VISION College of JeonjuRPKI Not found210.125.195.0
- 210.125.196.0/24AS9867VISION College of JeonjuRPKI Not found210.125.196.0
- 210.125.197.0/24AS9867VISION College of JeonjuRPKI Not found210.125.197.0
- 210.125.198.0/24AS9867VISION College of JeonjuRPKI Not found210.125.198.0
- 210.125.199.0/24AS9867VISION College of JeonjuRPKI Not found210.125.199.0
- 210.125.200.0/22AS17858LG POWERCOMMRPKI Not found210.125.200.0
- 210.125.204.0/24AS4766Korea TelecomRPKI Not found210.125.204.0
- 210.125.205.0/24AS4766Korea TelecomRPKI Not found210.125.205.0
- 210.125.206.0/24AS4766Korea TelecomRPKI Not found210.125.206.0
- 210.125.207.0/24AS4766Korea TelecomRPKI Not found210.125.207.0
- 210.125.208.0/22AS3786LG DACOM CorporationRPKI Not found210.125.208.0
- 210.125.208.0/23AS3786LG DACOM CorporationRPKI Not found210.125.208.0
- 210.125.210.0/23AS3786LG DACOM CorporationRPKI Not found210.125.210.0
- 210.125.212.0/22AS3786LG DACOM CorporationRPKI Not found210.125.212.0
- 210.125.212.0/23AS3786LG DACOM CorporationRPKI Not found210.125.212.0
- 210.125.214.0/23AS3786LG DACOM CorporationRPKI Not found210.125.214.0
- 210.125.216.0/22AS3786LG DACOM CorporationRPKI Not found210.125.216.0
- 210.125.216.0/23AS3786LG DACOM CorporationRPKI Not found210.125.216.0
- 210.125.218.0/23AS3786LG DACOM CorporationRPKI Not found210.125.218.0
- 210.125.220.0/22AS18029Daejeon Helath Sciences CollegeRPKI Not found210.125.220.0
- 210.125.224.0/24AS3786LG DACOM CorporationRPKI Not found210.125.224.0
- 210.125.225.0/24AS3786LG DACOM CorporationRPKI Not found210.125.225.0
- 210.125.227.0/24AS3786LG DACOM CorporationRPKI Not found210.125.227.0
- 210.125.228.0/24AS3786LG DACOM CorporationRPKI Not found210.125.228.0
- 210.125.229.0/24AS3786LG DACOM CorporationRPKI Not found210.125.229.0
- 210.125.230.0/24AS4766Korea TelecomRPKI Not found210.125.230.0
- 210.125.231.0/24AS10190Joongbu UniversityRPKI Not found210.125.231.0
- 210.125.232.0/21AS10190Joongbu UniversityRPKI Not found210.125.232.0
- 210.125.240.0/21AS4766Korea TelecomRPKI Not found210.125.240.0
- 210.125.248.0/21AS4766Korea TelecomRPKI Not found210.125.248.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.