BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
Examples:
124.104.0.0/14
One collector's view (APNIC). A route filtered before it reaches that collector is not listed.
Announced exactly
- 124.104.0.0/14AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.0.0
- Registry
- APNIC · Philippines · Feb 13, 2006
- Delegated block
- 124.104.0.0 – 124.107.255.255
Covering routes
0
No less-specific route covers it.
More-specific routes
51 more-specifics from 4 origin AS(es)
- 124.104.0.0/16AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.0.0
- 124.104.0.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.0.0
- 124.104.64.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.64.0
- 124.104.64.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.64.0
- 124.104.80.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.80.0
- 124.104.96.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.96.0
- 124.104.128.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.128.0
- 124.104.160.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.160.0
- 124.104.192.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.192.0
- 124.104.224.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.104.224.0
- 124.105.0.0/16AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.0.0
- 124.105.0.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.0.0
- 124.105.32.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.32.0
- 124.105.64.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.64.0
- 124.105.96.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.96.0
- 124.105.128.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.128.0
- 124.105.146.0/23AS23689Makati Shangri-LaRPKI Invalid124.105.146.0
- 124.105.160.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.160.0
- 124.105.192.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.192.0
- 124.105.224.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.105.224.0
- 124.106.0.0/16AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.0.0
- 124.106.0.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.0.0
- 124.106.8.0/24AS20940Akamai International B.V.RPKI Valid124.106.8.0
- 124.106.32.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.32.0
- 124.106.64.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.64.0
- 124.106.96.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.96.0
- 124.106.96.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.96.0
- 124.106.128.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.128.0
- 124.106.128.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.128.0
- 124.106.160.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.160.0
- 124.106.160.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.160.0
- 124.106.174.0/24AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.174.0
- 124.106.175.0/24AS20940Akamai International B.V.RPKI Valid124.106.175.0
- 124.106.176.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.176.0
- 124.106.192.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.192.0
- 124.106.192.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.192.0
- 124.106.208.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.208.0
- 124.106.216.0/24AS15347IBEX Global SolutionsRPKI Valid124.106.216.0
- 124.106.224.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.224.0
- 124.106.240.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.106.240.0
- 124.107.0.0/16AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.0.0
- 124.107.0.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.0.0
- 124.107.32.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.32.0
- 124.107.64.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.64.0
- 124.107.96.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.96.0
- 124.107.128.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.128.0
- 124.107.128.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.128.0
- 124.107.144.0/20AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.144.0
- 124.107.160.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.160.0
- 124.107.192.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.192.0
- 124.107.224.0/19AS9299Philippine Long Distance Telephone CompanyRPKI Valid124.107.224.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.