BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
150.133.0.0/16
Announced exactly
- 150.133.0.0/16AS1649Headquarters, USAISCRPKI Not found150.133.0.0
- Registry
- ARIN · United States · May 14, 1991
- Delegated block
- 150.133.0.0 – 150.133.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 150.133.11.0/24AS1649Headquarters, USAISCRPKI Not found150.133.11.0
- 150.133.12.0/24AS1649Headquarters, USAISCRPKI Not found150.133.12.0
- 150.133.17.0/24AS1649Headquarters, USAISCRPKI Not found150.133.17.0
- 150.133.18.0/24AS1649Headquarters, USAISCRPKI Not found150.133.18.0
- 150.133.20.0/24AS1649Headquarters, USAISCRPKI Not found150.133.20.0
- 150.133.32.0/24AS1649Headquarters, USAISCRPKI Not found150.133.32.0
- 150.133.33.0/24AS1649Headquarters, USAISCRPKI Not found150.133.33.0
- 150.133.46.0/24AS1649Headquarters, USAISCRPKI Not found150.133.46.0
- 150.133.50.0/24AS1649Headquarters, USAISCRPKI Not found150.133.50.0
- 150.133.56.0/22AS1540Headquarters, USAISCRPKI Not found150.133.56.0
- 150.133.100.0/24AS1649Headquarters, USAISCRPKI Not found150.133.100.0
- 150.133.101.0/24AS1649Headquarters, USAISCRPKI Not found150.133.101.0
- 150.133.104.0/22AS1649Headquarters, USAISCRPKI Not found150.133.104.0
- 150.133.112.0/22AS1649Headquarters, USAISCRPKI Not found150.133.112.0
- 150.133.128.0/24AS1649Headquarters, USAISCRPKI Not found150.133.128.0
- 150.133.129.0/24AS1649Headquarters, USAISCRPKI Not found150.133.129.0
- 150.133.130.0/24AS1649Headquarters, USAISCRPKI Not found150.133.130.0
- 150.133.170.0/24AS1649Headquarters, USAISCRPKI Not found150.133.170.0
- 150.133.171.0/24AS1649Headquarters, USAISCRPKI Not found150.133.171.0
- 150.133.184.0/24AS1649Headquarters, USAISCRPKI Not found150.133.184.0
- 150.133.216.0/24AS1649Headquarters, USAISCRPKI Not found150.133.216.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.