BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
177.16.0.0/14
Announced exactly
- 177.16.0.0/14AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.0.0
- Registry
- LACNIC · Brazil · Dec 7, 2010
- Delegated block
- 177.16.0.0 – 177.19.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 177.16.0.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.0.0
- 177.16.40.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.40.0
- 177.16.48.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.48.0
- 177.16.48.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.48.0
- 177.16.64.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.64.0
- 177.16.80.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.80.0
- 177.16.104.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.104.0
- 177.16.112.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.112.0
- 177.16.128.0/22AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.128.0
- 177.16.132.0/22AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.132.0
- 177.16.136.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.136.0
- 177.16.144.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.144.0
- 177.16.152.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.152.0
- 177.16.160.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.160.0
- 177.16.192.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.192.0
- 177.16.192.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.192.0
- 177.16.208.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.208.0
- 177.16.224.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.224.0
- 177.16.224.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.16.224.0
- 177.17.0.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.0.0
- 177.17.32.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.32.0
- 177.17.48.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.48.0
- 177.17.64.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.64.0
- 177.17.80.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.80.0
- 177.17.112.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.112.0
- 177.17.128.0/17AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.128.0
- 177.17.160.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.17.160.0
- 177.18.0.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.0.0
- 177.18.0.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.0.0
- 177.18.32.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.32.0
- 177.18.56.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.56.0
- 177.18.56.0/22AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.56.0
- 177.18.64.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.64.0
- 177.18.64.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.64.0
- 177.18.96.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.96.0
- 177.18.112.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.112.0
- 177.18.120.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.120.0
- 177.18.128.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.128.0
- 177.18.136.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.136.0
- 177.18.144.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.144.0
- 177.18.160.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.160.0
- 177.18.176.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.176.0
- 177.18.192.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.192.0
- 177.18.208.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.208.0
- 177.18.224.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.18.224.0
- 177.19.0.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.0.0
- 177.19.16.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.16.0
- 177.19.32.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.32.0
- 177.19.64.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.64.0
- 177.19.96.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.96.0
- 177.19.112.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.112.0
- 177.19.128.0/19AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.128.0
- 177.19.152.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.152.0
- 177.19.160.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.160.0
- 177.19.192.0/20AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.192.0
- 177.19.208.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.208.0
- 177.19.216.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.216.0
- 177.19.240.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.240.0
- 177.19.248.0/21AS18881TELEFONICA BRASIL S.ARPKI Not found177.19.248.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 128.139.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.