BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
159.0.0.0/16
Announced exactly
- 159.0.0.0/16AS25019Saudi Telecom Company JSCRPKI Valid159.0.0.0
- Registry
- RIPE NCC · Saudi Arabia · Aug 19, 2011
- Delegated block
- 159.0.0.0 – 159.0.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 159.0.0.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.0.0
- 159.0.16.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.16.0
- 159.0.32.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.32.0
- 159.0.48.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.48.0
- 159.0.64.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.64.0
- 159.0.80.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.80.0
- 159.0.96.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.96.0
- 159.0.112.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.112.0
- 159.0.128.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.128.0
- 159.0.129.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.129.0
- 159.0.130.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.130.0
- 159.0.131.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.131.0
- 159.0.132.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.132.0
- 159.0.133.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.133.0
- 159.0.134.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.134.0
- 159.0.135.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.135.0
- 159.0.136.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.136.0
- 159.0.137.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.137.0
- 159.0.138.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.138.0
- 159.0.139.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.139.0
- 159.0.140.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.140.0
- 159.0.141.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.141.0
- 159.0.142.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.142.0
- 159.0.143.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.143.0
- 159.0.144.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.144.0
- 159.0.145.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.145.0
- 159.0.146.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.146.0
- 159.0.147.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.147.0
- 159.0.148.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.148.0
- 159.0.149.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.149.0
- 159.0.150.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.150.0
- 159.0.151.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.151.0
- 159.0.152.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.152.0
- 159.0.153.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.153.0
- 159.0.154.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.154.0
- 159.0.155.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.155.0
- 159.0.156.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.156.0
- 159.0.157.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.157.0
- 159.0.158.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.158.0
- 159.0.159.0/24AS25019Saudi Telecom Company JSCRPKI Valid159.0.159.0
- 159.0.160.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.160.0
- 159.0.184.0/24AS39386Saudi Telecom Company JSCRPKI Valid159.0.184.0
- 159.0.186.0/24AS39891Saudi Telecom Company JSCRPKI Valid159.0.186.0
- 159.0.188.0/22AS39891Saudi Telecom Company JSCRPKI Valid159.0.188.0
- 159.0.192.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.192.0
- 159.0.208.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.208.0
- 159.0.224.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.224.0
- 159.0.240.0/20AS25019Saudi Telecom Company JSCRPKI Valid159.0.240.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.