BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.105.0.0/16
Announced exactly
- 210.105.0.0/16AS4766Korea TelecomRPKI Not found210.105.0.0
- Registry
- APNIC · South Korea · Aug 29, 1997
- Delegated block
- 210.104.0.0 – 210.105.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.105.0.0/24AS152214Korean Air LinesRPKI Not found210.105.0.0
- 210.105.2.0/24AS152214Korean Air LinesRPKI Not found210.105.2.0
- 210.105.3.0/24AS152214Korean Air LinesRPKI Not found210.105.3.0
- 210.105.4.0/24AS152214Korean Air LinesRPKI Not found210.105.4.0
- 210.105.5.0/24AS152214Korean Air LinesRPKI Not found210.105.5.0
- 210.105.6.0/24AS152214Korean Air LinesRPKI Not found210.105.6.0
- 210.105.7.0/24AS152214Korean Air LinesRPKI Not found210.105.7.0
- 210.105.8.0/24AS152214Korean Air LinesRPKI Not found210.105.8.0
- 210.105.10.0/24AS152214Korean Air LinesRPKI Not found210.105.10.0
- 210.105.11.0/24AS152214Korean Air LinesRPKI Not found210.105.11.0
- 210.105.12.0/24AS152214Korean Air LinesRPKI Not found210.105.12.0
- 210.105.16.0/22AS4766Korea TelecomRPKI Not found210.105.16.0
- 210.105.20.0/24AS4766Korea TelecomRPKI Not found210.105.20.0
- 210.105.69.0/24AS23556ININextRPKI Not found210.105.69.0
- 210.105.108.0/24AS4766Korea TelecomRPKI Not found210.105.108.0
- 210.105.118.0/23AS18324Masan CollegeRPKI Not found210.105.118.0
- 210.105.154.0/24AS18305POSCO DXRPKI Not found210.105.154.0
- 210.105.181.128/25AS4766Korea TelecomRPKI Not found210.105.181.128
- 210.105.216.0/24AS38695bucheon universityRPKI Not found210.105.216.0
- 210.105.217.0/24AS38695bucheon universityRPKI Not found210.105.217.0
- 210.105.218.0/24AS38695bucheon universityRPKI Not found210.105.218.0
- 210.105.219.0/24AS38695bucheon universityRPKI Not found210.105.219.0
- 210.105.220.0/24AS38695bucheon universityRPKI Not found210.105.220.0
- 210.105.221.0/24AS38695bucheon universityRPKI Not found210.105.221.0
- 210.105.222.0/24AS38695bucheon universityRPKI Not found210.105.222.0
- 210.105.223.0/24AS38695bucheon universityRPKI Not found210.105.223.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.