BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
88.224.0.0/11
Announced exactly
- 88.224.0.0/11AS9121TTNETRPKI Valid88.224.0.0
- Registry
- RIPE NCC · Türkiye · Oct 27, 2005
- Delegated block
- 88.224.0.0 – 88.255.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 88.224.0.0/17AS9121TTNETRPKI Valid88.224.0.0
- 88.224.128.0/17AS9121TTNETRPKI Valid88.224.128.0
- 88.225.0.0/17AS9121TTNETRPKI Valid88.225.0.0
- 88.225.128.0/17AS9121TTNETRPKI Valid88.225.128.0
- 88.226.0.0/17AS9121TTNETRPKI Valid88.226.0.0
- 88.226.128.0/17AS9121TTNETRPKI Valid88.226.128.0
- 88.226.191.0/24AS47331TTNETRPKI Valid88.226.191.0
- 88.227.0.0/17AS9121TTNETRPKI Valid88.227.0.0
- 88.227.128.0/17AS9121TTNETRPKI Valid88.227.128.0
- 88.228.0.0/17AS9121TTNETRPKI Valid88.228.0.0
- 88.228.128.0/17AS9121TTNETRPKI Valid88.228.128.0
- 88.229.0.0/17AS9121TTNETRPKI Valid88.229.0.0
- 88.229.16.0/21AS47331TTNETRPKI Valid88.229.16.0
- 88.229.128.0/17AS9121TTNETRPKI Valid88.229.128.0
- 88.229.208.0/21AS47331TTNETRPKI Valid88.229.208.0
- 88.229.216.0/22AS47331TTNETRPKI Valid88.229.216.0
- 88.229.220.0/22AS9121TTNETRPKI Valid88.229.220.0
- 88.230.0.0/17AS9121TTNETRPKI Valid88.230.0.0
- 88.230.88.0/21AS9121TTNETRPKI Valid88.230.88.0
- 88.230.128.0/17AS9121TTNETRPKI Valid88.230.128.0
- 88.231.0.0/17AS9121TTNETRPKI Valid88.231.0.0
- 88.231.128.0/17AS9121TTNETRPKI Valid88.231.128.0
- 88.232.0.0/17AS9121TTNETRPKI Valid88.232.0.0
- 88.232.128.0/17AS9121TTNETRPKI Valid88.232.128.0
- 88.233.0.0/17AS9121TTNETRPKI Valid88.233.0.0
- 88.233.128.0/17AS9121TTNETRPKI Valid88.233.128.0
- 88.234.0.0/17AS9121TTNETRPKI Valid88.234.0.0
- 88.234.128.0/17AS9121TTNETRPKI Valid88.234.128.0
- 88.234.228.0/22AS9121TTNETRPKI Valid88.234.228.0
- 88.234.232.0/21AS9121TTNETRPKI Valid88.234.232.0
- 88.234.240.0/21AS9121TTNETRPKI Valid88.234.240.0
- 88.234.248.0/21AS9121TTNETRPKI Valid88.234.248.0
- 88.235.0.0/17AS9121TTNETRPKI Valid88.235.0.0
- 88.235.128.0/17AS9121TTNETRPKI Valid88.235.128.0
- 88.235.212.0/22AS9121TTNETRPKI Valid88.235.212.0
- 88.235.224.0/21AS9121TTNETRPKI Valid88.235.224.0
- 88.236.0.0/17AS9121TTNETRPKI Valid88.236.0.0
- 88.236.96.0/21AS47331TTNETRPKI Valid88.236.96.0
- 88.236.104.0/21AS47331TTNETRPKI Valid88.236.104.0
- 88.236.112.0/21AS47331TTNETRPKI Valid88.236.112.0
- 88.236.128.0/17AS9121TTNETRPKI Valid88.236.128.0
- 88.237.0.0/17AS9121TTNETRPKI Valid88.237.0.0
- 88.237.128.0/17AS9121TTNETRPKI Valid88.237.128.0
- 88.238.0.0/17AS9121TTNETRPKI Valid88.238.0.0
- 88.238.128.0/17AS9121TTNETRPKI Valid88.238.128.0
- 88.238.128.0/18AS47331TTNETRPKI Valid88.238.128.0
- 88.239.0.0/17AS9121TTNETRPKI Valid88.239.0.0
- 88.239.128.0/17AS9121TTNETRPKI Valid88.239.128.0
- 88.240.0.0/17AS9121TTNETRPKI Valid88.240.0.0
- 88.240.96.0/21AS47331TTNETRPKI Valid88.240.96.0
- 88.240.128.0/17AS9121TTNETRPKI Valid88.240.128.0
- 88.240.136.0/21AS47331TTNETRPKI Valid88.240.136.0
- 88.241.0.0/17AS9121TTNETRPKI Valid88.241.0.0
- 88.241.128.0/17AS9121TTNETRPKI Valid88.241.128.0
- 88.241.192.0/18AS47331TTNETRPKI Valid88.241.192.0
- 88.242.0.0/17AS9121TTNETRPKI Valid88.242.0.0
- 88.242.128.0/17AS9121TTNETRPKI Valid88.242.128.0
- 88.243.0.0/17AS9121TTNETRPKI Valid88.243.0.0
- 88.243.128.0/17AS9121TTNETRPKI Valid88.243.128.0
- 88.244.0.0/17AS9121TTNETRPKI Valid88.244.0.0
- 88.244.128.0/17AS9121TTNETRPKI Valid88.244.128.0
- 88.245.0.0/17AS9121TTNETRPKI Valid88.245.0.0
- 88.245.128.0/17AS9121TTNETRPKI Valid88.245.128.0
- 88.246.0.0/17AS9121TTNETRPKI Valid88.246.0.0
- 88.246.128.0/17AS9121TTNETRPKI Valid88.246.128.0
- 88.247.0.0/17AS9121TTNETRPKI Valid88.247.0.0
- 88.247.128.0/17AS9121TTNETRPKI Valid88.247.128.0
- 88.248.0.0/17AS9121TTNETRPKI Valid88.248.0.0
- 88.248.128.0/17AS9121TTNETRPKI Valid88.248.128.0
- 88.249.0.0/17AS9121TTNETRPKI Valid88.249.0.0
- 88.249.128.0/17AS9121TTNETRPKI Valid88.249.128.0
- 88.250.0.0/17AS9121TTNETRPKI Valid88.250.0.0
- 88.250.128.0/17AS9121TTNETRPKI Valid88.250.128.0
- 88.251.0.0/17AS9121TTNETRPKI Valid88.251.0.0
- 88.251.128.0/17AS9121TTNETRPKI Valid88.251.128.0
- 88.252.0.0/17AS9121TTNETRPKI Valid88.252.0.0
- 88.252.128.0/17AS9121TTNETRPKI Valid88.252.128.0
- 88.253.0.0/17AS9121TTNETRPKI Valid88.253.0.0
- 88.253.128.0/17AS9121TTNETRPKI Valid88.253.128.0
- 88.254.0.0/17AS9121TTNETRPKI Valid88.254.0.0
- 88.254.128.0/17AS9121TTNETRPKI Valid88.254.128.0
- 88.254.196.0/22AS47331TTNETRPKI Valid88.254.196.0
- 88.255.0.0/17AS9121TTNETRPKI Valid88.255.0.0
- 88.255.48.0/24AS9121TTNETRPKI Valid88.255.48.0
- 88.255.83.0/24AS9121TTNETRPKI Valid88.255.83.0
- 88.255.109.0/24AS9121TTNETRPKI Valid88.255.109.0
- 88.255.128.0/17AS9121TTNETRPKI Valid88.255.128.0
- 88.255.158.0/24AS9121TTNETRPKI Valid88.255.158.0
- 88.255.190.0/24AS9121TTNETRPKI Valid88.255.190.0
- 88.255.220.0/22AS9121TTNETRPKI Valid88.255.220.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.