BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
78.160.0.0/11
Announced exactly
- 78.160.0.0/11AS9121TTNETRPKI Valid78.160.0.0
- Registry
- RIPE NCC · Türkiye · May 1, 2007
- Delegated block
- 78.160.0.0 – 78.191.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 78.160.0.0/17AS9121TTNETRPKI Valid78.160.0.0
- 78.160.128.0/17AS9121TTNETRPKI Valid78.160.128.0
- 78.161.0.0/17AS9121TTNETRPKI Valid78.161.0.0
- 78.161.128.0/17AS9121TTNETRPKI Valid78.161.128.0
- 78.161.209.0/24AS47331TTNETRPKI Valid78.161.209.0
- 78.162.0.0/17AS9121TTNETRPKI Valid78.162.0.0
- 78.162.128.0/17AS9121TTNETRPKI Valid78.162.128.0
- 78.162.192.0/18AS47331TTNETRPKI Valid78.162.192.0
- 78.163.0.0/17AS9121TTNETRPKI Valid78.163.0.0
- 78.163.128.0/17AS9121TTNETRPKI Valid78.163.128.0
- 78.164.0.0/17AS9121TTNETRPKI Valid78.164.0.0
- 78.164.128.0/17AS9121TTNETRPKI Valid78.164.128.0
- 78.165.0.0/17AS9121TTNETRPKI Valid78.165.0.0
- 78.165.128.0/17AS9121TTNETRPKI Valid78.165.128.0
- 78.166.0.0/17AS9121TTNETRPKI Valid78.166.0.0
- 78.166.128.0/17AS9121TTNETRPKI Valid78.166.128.0
- 78.167.0.0/17AS9121TTNETRPKI Valid78.167.0.0
- 78.167.128.0/17AS9121TTNETRPKI Valid78.167.128.0
- 78.168.0.0/17AS9121TTNETRPKI Valid78.168.0.0
- 78.168.128.0/17AS9121TTNETRPKI Valid78.168.128.0
- 78.169.0.0/17AS9121TTNETRPKI Valid78.169.0.0
- 78.169.128.0/17AS9121TTNETRPKI Valid78.169.128.0
- 78.169.189.0/24AS47331TTNETRPKI Valid78.169.189.0
- 78.169.190.0/24AS47331TTNETRPKI Valid78.169.190.0
- 78.170.0.0/17AS9121TTNETRPKI Valid78.170.0.0
- 78.170.128.0/17AS9121TTNETRPKI Valid78.170.128.0
- 78.171.0.0/17AS9121TTNETRPKI Valid78.171.0.0
- 78.171.16.0/21AS47331TTNETRPKI Valid78.171.16.0
- 78.171.72.0/21AS47331TTNETRPKI Valid78.171.72.0
- 78.171.88.0/21AS47331TTNETRPKI Valid78.171.88.0
- 78.171.128.0/17AS9121TTNETRPKI Valid78.171.128.0
- 78.172.0.0/17AS9121TTNETRPKI Valid78.172.0.0
- 78.172.128.0/17AS9121TTNETRPKI Valid78.172.128.0
- 78.172.140.0/24AS47331TTNETRPKI Valid78.172.140.0
- 78.172.153.0/24AS47331TTNETRPKI Valid78.172.153.0
- 78.173.0.0/17AS9121TTNETRPKI Valid78.173.0.0
- 78.173.72.0/21AS9121TTNETRPKI Valid78.173.72.0
- 78.173.128.0/17AS9121TTNETRPKI Valid78.173.128.0
- 78.173.208.0/21AS47331TTNETRPKI Valid78.173.208.0
- 78.174.0.0/17AS9121TTNETRPKI Valid78.174.0.0
- 78.174.128.0/17AS9121TTNETRPKI Valid78.174.128.0
- 78.175.0.0/17AS9121TTNETRPKI Valid78.175.0.0
- 78.175.128.0/17AS9121TTNETRPKI Valid78.175.128.0
- 78.176.0.0/17AS9121TTNETRPKI Valid78.176.0.0
- 78.176.128.0/17AS9121TTNETRPKI Valid78.176.128.0
- 78.177.0.0/17AS9121TTNETRPKI Valid78.177.0.0
- 78.177.128.0/17AS9121TTNETRPKI Valid78.177.128.0
- 78.177.184.0/22AS47331TTNETRPKI Valid78.177.184.0
- 78.178.0.0/17AS9121TTNETRPKI Valid78.178.0.0
- 78.178.128.0/17AS9121TTNETRPKI Valid78.178.128.0
- 78.178.192.0/23AS9121TTNETRPKI Valid78.178.192.0
- 78.179.0.0/17AS9121TTNETRPKI Valid78.179.0.0
- 78.179.128.0/17AS9121TTNETRPKI Valid78.179.128.0
- 78.180.0.0/17AS9121TTNETRPKI Valid78.180.0.0
- 78.180.128.0/17AS9121TTNETRPKI Valid78.180.128.0
- 78.181.0.0/17AS9121TTNETRPKI Valid78.181.0.0
- 78.181.128.0/17AS9121TTNETRPKI Valid78.181.128.0
- 78.181.190.0/24AS47331TTNETRPKI Valid78.181.190.0
- 78.182.0.0/17AS9121TTNETRPKI Valid78.182.0.0
- 78.182.128.0/17AS9121TTNETRPKI Valid78.182.128.0
- 78.183.0.0/17AS9121TTNETRPKI Valid78.183.0.0
- 78.183.128.0/17AS9121TTNETRPKI Valid78.183.128.0
- 78.184.0.0/17AS9121TTNETRPKI Valid78.184.0.0
- 78.184.64.0/18AS47331TTNETRPKI Valid78.184.64.0
- 78.184.128.0/17AS9121TTNETRPKI Valid78.184.128.0
- 78.185.0.0/17AS9121TTNETRPKI Valid78.185.0.0
- 78.185.128.0/17AS9121TTNETRPKI Valid78.185.128.0
- 78.186.0.0/17AS9121TTNETRPKI Valid78.186.0.0
- 78.186.128.0/17AS9121TTNETRPKI Valid78.186.128.0
- 78.187.0.0/17AS9121TTNETRPKI Valid78.187.0.0
- 78.187.128.0/17AS9121TTNETRPKI Valid78.187.128.0
- 78.188.0.0/17AS9121TTNETRPKI Valid78.188.0.0
- 78.188.128.0/17AS9121TTNETRPKI Valid78.188.128.0
- 78.189.0.0/17AS9121TTNETRPKI Valid78.189.0.0
- 78.189.128.0/17AS9121TTNETRPKI Valid78.189.128.0
- 78.190.0.0/17AS9121TTNETRPKI Valid78.190.0.0
- 78.190.128.0/17AS9121TTNETRPKI Valid78.190.128.0
- 78.191.0.0/17AS9121TTNETRPKI Valid78.191.0.0
- 78.191.128.0/17AS9121TTNETRPKI Valid78.191.128.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.