BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
121.78.192.0/18
Announced exactly
- 121.78.192.0/18AS9286KINXRPKI Not found121.78.192.0
- Registry
- APNIC · South Korea · Jun 20, 2006
- Delegated block
- 121.78.0.0 – 121.78.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 121.78.192.0/24AS17589GABIA Inc.RPKI Not found121.78.192.0
- 121.78.193.0/24AS17589GABIA Inc.RPKI Not found121.78.193.0
- 121.78.194.0/24AS17589GABIA Inc.RPKI Not found121.78.194.0
- 121.78.195.0/24AS17589GABIA Inc.RPKI Not found121.78.195.0
- 121.78.196.0/24AS17589GABIA Inc.RPKI Not found121.78.196.0
- 121.78.197.0/24AS17589GABIA Inc.RPKI Not found121.78.197.0
- 121.78.199.0/24AS9957KINXRPKI Not found121.78.199.0
- 121.78.216.0/24AS9286KINXRPKI Not found121.78.216.0
- 121.78.221.0/24AS9286KINXRPKI Not found121.78.221.0
- 121.78.223.0/24AS9286KINXRPKI Not found121.78.223.0
- 121.78.224.0/19AS9286KINXRPKI Not found121.78.224.0
- 121.78.224.0/24AS9957KINXRPKI Not found121.78.224.0
- 121.78.225.0/24AS9286KINXRPKI Not found121.78.225.0
- 121.78.226.0/24AS9286KINXRPKI Not found121.78.226.0
- 121.78.227.0/25AS9957KINXRPKI Not found121.78.227.0
- 121.78.227.128/25AS9286KINXRPKI Not found121.78.227.128
- 121.78.228.0/24AS9286KINXRPKI Not found121.78.228.0
- 121.78.229.0/24AS9286KINXRPKI Not found121.78.229.0
- 121.78.230.0/24AS9286KINXRPKI Not found121.78.230.0
- 121.78.231.0/24AS9957KINXRPKI Not found121.78.231.0
- 121.78.233.0/24AS9286KINXRPKI Not found121.78.233.0
- 121.78.234.0/25AS9286KINXRPKI Not found121.78.234.0
- 121.78.236.0/24AS9286KINXRPKI Not found121.78.236.0
- 121.78.237.0/24AS9286KINXRPKI Not found121.78.237.0
- 121.78.240.0/24AS9286KINXRPKI Not found121.78.240.0
- 121.78.242.0/24AS9286KINXRPKI Not found121.78.242.0
- 121.78.243.0/24AS9286KINXRPKI Not found121.78.243.0
- 121.78.244.0/24AS9286KINXRPKI Not found121.78.244.0
- 121.78.246.0/24AS9286KINXRPKI Not found121.78.246.0
- 121.78.252.0/24AS9286KINXRPKI Not found121.78.252.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.