BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
27.102.0.0/16
Announced exactly
- 27.102.0.0/16AS45996DAOU TECHNOLOGYRPKI Not found27.102.0.0
- Registry
- APNIC · South Korea · May 27, 2010
- Delegated block
- 27.102.0.0 – 27.102.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 27.102.50.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.50.0
- 27.102.51.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.51.0
- 27.102.52.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.52.0
- 27.102.54.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.54.0
- 27.102.55.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.55.0
- 27.102.64.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.64.0
- 27.102.65.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.65.0
- 27.102.66.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.66.0
- 27.102.85.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.85.0
- 27.102.94.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.94.0
- 27.102.102.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.102.0
- 27.102.106.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.106.0
- 27.102.107.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.107.0
- 27.102.111.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.111.0
- 27.102.112.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.112.0
- 27.102.113.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.113.0
- 27.102.114.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.114.0
- 27.102.115.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.115.0
- 27.102.118.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.118.0
- 27.102.119.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.119.0
- 27.102.120.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.120.0
- 27.102.121.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.121.0
- 27.102.122.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.122.0
- 27.102.127.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.127.0
- 27.102.128.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.128.0
- 27.102.129.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.129.0
- 27.102.130.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.130.0
- 27.102.132.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.132.0
- 27.102.134.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.134.0
- 27.102.165.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.165.0
- 27.102.166.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.166.0
- 27.102.167.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.167.0
- 27.102.168.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.168.0
- 27.102.169.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.169.0
- 27.102.204.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.204.0
- 27.102.205.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.205.0
- 27.102.206.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.206.0
- 27.102.207.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.207.0
- 27.102.220.0/24AS45996DAOU TECHNOLOGYRPKI Not found27.102.220.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.