BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
51.36.0.0/18
Announced exactly
- 51.36.0.0/18AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.0.0
- Registry
- RIPE NCC · Saudi Arabia · Sep 1, 1993
- Delegated block
- 51.36.0.0 – 51.36.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 51.36.0.0/19AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.0.0
- 51.36.0.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.0.0
- 51.36.0.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.0.0
- 51.36.1.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.1.0
- 51.36.10.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.10.0
- 51.36.12.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.12.0
- 51.36.14.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.14.0
- 51.36.16.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.16.0
- 51.36.18.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.18.0
- 51.36.2.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.2.0
- 51.36.20.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.20.0
- 51.36.20.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.20.0
- 51.36.21.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.21.0
- 51.36.22.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.22.0
- 51.36.22.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.22.0
- 51.36.24.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.24.0
- 51.36.26.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.26.0
- 51.36.28.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.28.0
- 51.36.30.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.30.0
- 51.36.30.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.30.0
- 51.36.31.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.31.0
- 51.36.32.0/19AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.32.0
- 51.36.32.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.32.0
- 51.36.34.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.34.0
- 51.36.36.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.36.0
- 51.36.38.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.38.0
- 51.36.4.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.4.0
- 51.36.40.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.40.0
- 51.36.40.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.40.0
- 51.36.41.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.41.0
- 51.36.42.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.42.0
- 51.36.44.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.44.0
- 51.36.46.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.46.0
- 51.36.48.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.48.0
- 51.36.48.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.48.0
- 51.36.49.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.49.0
- 51.36.50.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.50.0
- 51.36.50.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.50.0
- 51.36.51.0/24AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.51.0
- 51.36.52.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.52.0
- 51.36.54.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.54.0
- 51.36.56.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.56.0
- 51.36.58.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.58.0
- 51.36.6.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.6.0
- 51.36.60.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.60.0
- 51.36.62.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.62.0
- 51.36.8.0/22AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.8.0
- 51.36.8.0/23AS43766Mobile Telecommunication Company Saudi Arabia Joint-Stock companyRPKI Valid51.36.8.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 90.190.0.0/15 (Telia Eesti, AS3249). 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.