BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
109.62.0.0/17
Announced exactly
- 109.62.0.0/17AS20776Outremer Telecom SASRPKI Valid109.62.0.0
- Registry
- RIPE NCC · Martinique · Dec 23, 2009
- Delegated block
- 109.62.0.0 – 109.62.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 109.62.0.0/19AS20776Outremer Telecom SASRPKI Valid109.62.0.0
- 109.62.0.0/21AS20776Outremer Telecom SASRPKI Valid109.62.0.0
- 109.62.4.0/22AS20776Outremer Telecom SASRPKI Valid109.62.4.0
- 109.62.8.0/24AS20776Outremer Telecom SASRPKI Valid109.62.8.0
- 109.62.9.0/24AS20776Outremer Telecom SASRPKI Valid109.62.9.0
- 109.62.10.0/23AS20776Outremer Telecom SASRPKI Valid109.62.10.0
- 109.62.12.0/23AS20776Outremer Telecom SASRPKI Valid109.62.12.0
- 109.62.14.0/24AS20776Outremer Telecom SASRPKI Valid109.62.14.0
- 109.62.15.0/24AS20776Outremer Telecom SASRPKI Valid109.62.15.0
- 109.62.16.0/21AS20776Outremer Telecom SASRPKI Valid109.62.16.0
- 109.62.24.0/23AS20776Outremer Telecom SASRPKI Valid109.62.24.0
- 109.62.26.0/24AS20776Outremer Telecom SASRPKI Valid109.62.26.0
- 109.62.27.0/24AS20776Outremer Telecom SASRPKI Valid109.62.27.0
- 109.62.28.0/22AS20776Outremer Telecom SASRPKI Valid109.62.28.0
- 109.62.32.0/20AS20776Outremer Telecom SASRPKI Valid109.62.32.0
- 109.62.48.0/20AS20776Outremer Telecom SASRPKI Valid109.62.48.0
- 109.62.48.0/21AS20776Outremer Telecom SASRPKI Valid109.62.48.0
- 109.62.56.0/22AS20776Outremer Telecom SASRPKI Valid109.62.56.0
- 109.62.60.0/22AS20776Outremer Telecom SASRPKI Valid109.62.60.0
- 109.62.64.0/23AS20776Outremer Telecom SASRPKI Valid109.62.64.0
- 109.62.64.0/24AS20776Outremer Telecom SASRPKI Valid109.62.64.0
- 109.62.65.0/24AS20776Outremer Telecom SASRPKI Valid109.62.65.0
- 109.62.66.0/23AS20776Outremer Telecom SASRPKI Valid109.62.66.0
- 109.62.66.0/24AS20776Outremer Telecom SASRPKI Valid109.62.66.0
- 109.62.67.0/24AS20776Outremer Telecom SASRPKI Valid109.62.67.0
- 109.62.68.0/22AS20776Outremer Telecom SASRPKI Valid109.62.68.0
- 109.62.68.0/23AS20776Outremer Telecom SASRPKI Valid109.62.68.0
- 109.62.70.0/23AS20776Outremer Telecom SASRPKI Valid109.62.70.0
- 109.62.72.0/21AS20776Outremer Telecom SASRPKI Valid109.62.72.0
- 109.62.72.0/22AS20776Outremer Telecom SASRPKI Valid109.62.72.0
- 109.62.76.0/22AS20776Outremer Telecom SASRPKI Valid109.62.76.0
- 109.62.80.0/20AS20776Outremer Telecom SASRPKI Valid109.62.80.0
- 109.62.80.0/21AS20776Outremer Telecom SASRPKI Valid109.62.80.0
- 109.62.88.0/21AS20776Outremer Telecom SASRPKI Valid109.62.88.0
- 109.62.96.0/20AS20776Outremer Telecom SASRPKI Valid109.62.96.0
- 109.62.96.0/21AS20776Outremer Telecom SASRPKI Valid109.62.96.0
- 109.62.104.0/21AS20776Outremer Telecom SASRPKI Valid109.62.104.0
- 109.62.112.0/21AS20776Outremer Telecom SASRPKI Valid109.62.112.0
- 109.62.120.0/21AS20776Outremer Telecom SASRPKI Valid109.62.120.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.