BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
177.48.0.0/14
Announced exactly
- 177.48.0.0/14AS26615TIM S/ARPKI Not found177.48.0.0
- Registry
- LACNIC · Brazil · Apr 5, 2011
- Delegated block
- 177.48.0.0 – 177.51.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 177.50.0.0/23AS26615TIM S/ARPKI Not found177.50.0.0
- 177.50.2.0/23AS26615TIM S/ARPKI Not found177.50.2.0
- 177.50.4.0/23AS26615TIM S/ARPKI Not found177.50.4.0
- 177.50.6.0/23AS26615TIM S/ARPKI Not found177.50.6.0
- 177.50.8.0/23AS26615TIM S/ARPKI Not found177.50.8.0
- 177.50.10.0/23AS26615TIM S/ARPKI Not found177.50.10.0
- 177.50.12.0/23AS26615TIM S/ARPKI Not found177.50.12.0
- 177.50.14.0/23AS26615TIM S/ARPKI Not found177.50.14.0
- 177.50.16.0/23AS26615TIM S/ARPKI Not found177.50.16.0
- 177.50.18.0/23AS26615TIM S/ARPKI Not found177.50.18.0
- 177.50.20.0/23AS26615TIM S/ARPKI Not found177.50.20.0
- 177.50.22.0/23AS26615TIM S/ARPKI Not found177.50.22.0
- 177.50.24.0/23AS26615TIM S/ARPKI Not found177.50.24.0
- 177.50.26.0/23AS26615TIM S/ARPKI Not found177.50.26.0
- 177.50.28.0/23AS26615TIM S/ARPKI Not found177.50.28.0
- 177.50.30.0/23AS26615TIM S/ARPKI Not found177.50.30.0
- 177.50.32.0/23AS26615TIM S/ARPKI Not found177.50.32.0
- 177.50.34.0/23AS26615TIM S/ARPKI Not found177.50.34.0
- 177.50.36.0/23AS26615TIM S/ARPKI Not found177.50.36.0
- 177.50.38.0/23AS26615TIM S/ARPKI Not found177.50.38.0
- 177.50.40.0/23AS26615TIM S/ARPKI Not found177.50.40.0
- 177.50.42.0/23AS26615TIM S/ARPKI Not found177.50.42.0
- 177.50.44.0/23AS26615TIM S/ARPKI Not found177.50.44.0
- 177.50.46.0/23AS26615TIM S/ARPKI Not found177.50.46.0
- 177.50.64.0/23AS26615TIM S/ARPKI Not found177.50.64.0
- 177.50.66.0/23AS26615TIM S/ARPKI Not found177.50.66.0
- 177.50.68.0/23AS26615TIM S/ARPKI Not found177.50.68.0
- 177.50.70.0/23AS26615TIM S/ARPKI Not found177.50.70.0
- 177.50.72.0/23AS26615TIM S/ARPKI Not found177.50.72.0
- 177.50.74.0/23AS26615TIM S/ARPKI Not found177.50.74.0
- 177.50.76.0/23AS26615TIM S/ARPKI Not found177.50.76.0
- 177.50.78.0/23AS26615TIM S/ARPKI Not found177.50.78.0
- 177.50.96.0/23AS26615TIM S/ARPKI Not found177.50.96.0
- 177.50.98.0/23AS26615TIM S/ARPKI Not found177.50.98.0
- 177.50.100.0/23AS26615TIM S/ARPKI Not found177.50.100.0
- 177.50.102.0/23AS26615TIM S/ARPKI Not found177.50.102.0
- 177.50.104.0/23AS26615TIM S/ARPKI Not found177.50.104.0
- 177.50.106.0/23AS26615TIM S/ARPKI Not found177.50.106.0
- 177.50.118.0/23AS26615TIM S/ARPKI Not found177.50.118.0
- 177.50.120.0/22AS26615TIM S/ARPKI Not found177.50.120.0
- 177.50.124.0/22AS26615TIM S/ARPKI Not found177.50.124.0
- 177.50.128.0/20AS26615TIM S/ARPKI Not found177.50.128.0
- 177.50.160.0/19AS26615TIM S/ARPKI Not found177.50.160.0
- 177.50.192.0/19AS26615TIM S/ARPKI Not found177.50.192.0
- 177.50.224.0/19AS26615TIM S/ARPKI Not found177.50.224.0
- 177.51.0.0/22AS26615TIM S/ARPKI Not found177.51.0.0
- 177.51.4.0/22AS26615TIM S/ARPKI Not found177.51.4.0
- 177.51.8.0/22AS26615TIM S/ARPKI Not found177.51.8.0
- 177.51.12.0/22AS26615TIM S/ARPKI Not found177.51.12.0
- 177.51.16.0/22AS26615TIM S/ARPKI Not found177.51.16.0
- 177.51.20.0/22AS26615TIM S/ARPKI Not found177.51.20.0
- 177.51.32.0/23AS26615TIM S/ARPKI Not found177.51.32.0
- 177.51.34.0/23AS26615TIM S/ARPKI Not found177.51.34.0
- 177.51.64.0/23AS26615TIM S/ARPKI Not found177.51.64.0
- 177.51.66.0/23AS26615TIM S/ARPKI Not found177.51.66.0
- 177.51.72.0/23AS26615TIM S/ARPKI Not found177.51.72.0
- 177.51.74.0/23AS26615TIM S/ARPKI Not found177.51.74.0
- 177.51.76.0/22AS26615TIM S/ARPKI Not found177.51.76.0
- 177.51.80.0/22AS26615TIM S/ARPKI Not found177.51.80.0
- 177.51.84.0/22AS26615TIM S/ARPKI Not found177.51.84.0
- 177.51.88.0/22AS26615TIM S/ARPKI Not found177.51.88.0
- 177.51.92.0/22AS26615TIM S/ARPKI Not found177.51.92.0
- 177.51.96.0/22AS26615TIM S/ARPKI Not found177.51.96.0
- 177.51.100.0/22AS26615TIM S/ARPKI Not found177.51.100.0
- 177.51.104.0/22AS26615TIM S/ARPKI Not found177.51.104.0
- 177.51.108.0/22AS26615TIM S/ARPKI Not found177.51.108.0
- 177.51.112.0/22AS26615TIM S/ARPKI Not found177.51.112.0
- 177.51.116.0/22AS26615TIM S/ARPKI Not found177.51.116.0
- 177.51.120.0/22AS26615TIM S/ARPKI Not found177.51.120.0
- 177.51.124.0/22AS26615TIM S/ARPKI Not found177.51.124.0
- 177.51.144.0/20AS26615TIM S/ARPKI Not found177.51.144.0
- 177.51.160.0/20AS26615TIM S/ARPKI Not found177.51.160.0
- 177.51.176.0/23AS26615TIM S/ARPKI Not found177.51.176.0
- 177.51.178.0/23AS26615TIM S/ARPKI Not found177.51.178.0
- 177.51.184.0/24AS26615TIM S/ARPKI Not found177.51.184.0
- 177.51.192.0/22AS26615TIM S/ARPKI Not found177.51.192.0
- 177.51.196.0/22AS26615TIM S/ARPKI Not found177.51.196.0
- 177.51.200.0/22AS26615TIM S/ARPKI Not found177.51.200.0
- 177.51.204.0/22AS26615TIM S/ARPKI Not found177.51.204.0
- 177.51.208.0/22AS26615TIM S/ARPKI Not found177.51.208.0
- 177.51.212.0/22AS26615TIM S/ARPKI Not found177.51.212.0
- 177.51.216.0/22AS26615TIM S/ARPKI Not found177.51.216.0
- 177.51.220.0/22AS26615TIM S/ARPKI Not found177.51.220.0
- 177.51.236.0/22AS26615TIM S/ARPKI Not found177.51.236.0
- 177.51.240.0/22AS26615TIM S/ARPKI Not found177.51.240.0
- 177.51.244.0/22AS26615TIM S/ARPKI Not found177.51.244.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.