BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
137.145.0.0/16
Announced exactly
- 137.145.0.0/16AS2152CENICRPKI Not found137.145.0.0
- Registry
- ARIN · United States · Nov 30, 1989
- Delegated block
- 137.145.0.0 – 137.145.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 137.145.7.0/24AS2152CENICRPKI Not found137.145.7.0
- 137.145.10.0/24AS2152CENICRPKI Not found137.145.10.0
- 137.145.17.0/24AS2152CENICRPKI Not found137.145.17.0
- 137.145.20.0/24AS2152CENICRPKI Not found137.145.20.0
- 137.145.21.0/24AS2152CENICRPKI Not found137.145.21.0
- 137.145.22.0/24AS2152CENICRPKI Not found137.145.22.0
- 137.145.23.0/24AS2152CENICRPKI Not found137.145.23.0
- 137.145.34.0/24AS2152CENICRPKI Not found137.145.34.0
- 137.145.35.0/24AS2152CENICRPKI Not found137.145.35.0
- 137.145.36.0/24AS2152CENICRPKI Not found137.145.36.0
- 137.145.40.0/24AS2152CENICRPKI Not found137.145.40.0
- 137.145.96.0/22AS2152CENICRPKI Not found137.145.96.0
- 137.145.130.0/24AS2152CENICRPKI Not found137.145.130.0
- 137.145.133.0/24AS2152CENICRPKI Not found137.145.133.0
- 137.145.148.0/24AS2152CENICRPKI Not found137.145.148.0
- 137.145.150.0/24AS2152CENICRPKI Not found137.145.150.0
- 137.145.160.0/24AS2152CENICRPKI Not found137.145.160.0
- 137.145.161.0/24AS2152CENICRPKI Not found137.145.161.0
- 137.145.165.0/24AS2152CENICRPKI Not found137.145.165.0
- 137.145.166.0/23AS2152CENICRPKI Not found137.145.166.0
- 137.145.168.0/23AS2152CENICRPKI Not found137.145.168.0
- 137.145.170.0/24AS2152CENICRPKI Not found137.145.170.0
- 137.145.171.0/24AS2152CENICRPKI Not found137.145.171.0
- 137.145.172.0/24AS2152CENICRPKI Not found137.145.172.0
- 137.145.176.0/22AS2152CENICRPKI Not found137.145.176.0
- 137.145.180.0/22AS2152CENICRPKI Not found137.145.180.0
- 137.145.184.0/24AS2152CENICRPKI Not found137.145.184.0
- 137.145.187.0/24AS2152CENICRPKI Not found137.145.187.0
- 137.145.189.0/24AS2152CENICRPKI Not found137.145.189.0
- 137.145.190.0/23AS2152CENICRPKI Not found137.145.190.0
- 137.145.196.0/23AS2152CENICRPKI Not found137.145.196.0
- 137.145.199.0/24AS2152CENICRPKI Not found137.145.199.0
- 137.145.203.0/24AS2152CENICRPKI Not found137.145.203.0
- 137.145.224.0/24AS2152CENICRPKI Not found137.145.224.0
- 137.145.230.0/23AS2152CENICRPKI Not found137.145.230.0
- 137.145.232.0/23AS2152CENICRPKI Not found137.145.232.0
- 137.145.234.0/23AS2152CENICRPKI Not found137.145.234.0
- 137.145.236.0/23AS2152CENICRPKI Not found137.145.236.0
- 137.145.238.0/23AS2152CENICRPKI Not found137.145.238.0
- 137.145.240.0/23AS2152CENICRPKI Not found137.145.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, 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.