BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
152.176.0.0/12
Announced exactly
- 152.176.0.0/12AS701Verizon BusinessRPKI Not found152.176.0.0
- Registry
- ARIN · United States · Apr 1, 1992
- Delegated block
- 152.176.0.0 – 152.191.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 152.178.24.0/21AS1699Verizon BusinessRPKI Not found152.178.24.0
- 152.178.32.0/21AS1699Verizon BusinessRPKI Not found152.178.32.0
- 152.178.40.0/21AS1699Verizon BusinessRPKI Not found152.178.40.0
- 152.178.48.0/21AS1699Verizon BusinessRPKI Not found152.178.48.0
- 152.178.64.0/24AS1689Verizon BusinessRPKI Not found152.178.64.0
- 152.178.68.0/24AS1689Verizon BusinessRPKI Not found152.178.68.0
- 152.178.72.0/24AS1689Verizon BusinessRPKI Not found152.178.72.0
- 152.178.130.0/24AS1699Verizon BusinessRPKI Not found152.178.130.0
- 152.178.131.0/24AS1699Verizon BusinessRPKI Not found152.178.131.0
- 152.178.132.0/24AS1699Verizon BusinessRPKI Not found152.178.132.0
- 152.180.10.0/24AS398033U.S. Department of Labor - OASAMDIRMRPKI Valid152.180.10.0
- 152.180.11.0/24AS398033U.S. Department of Labor - OASAMDIRMRPKI Valid152.180.11.0
- 152.180.20.0/23AS398033U.S. Department of Labor - OASAMDIRMRPKI Not found152.180.20.0
- 152.180.28.0/24AS15572CYBERTRUST former CybertrustRPKI Not found152.180.28.0
- 152.180.73.0/24AS17242UNIPAC Service CorporationRPKI Not found152.180.73.0
- 152.182.67.0/24AS6256Verizon BusinessRPKI Not found152.182.67.0
- 152.184.128.0/17AS701Verizon BusinessRPKI Not found152.184.128.0
- 152.186.46.0/24AS399222NEWCOM, INCRPKI Not found152.186.46.0
- 152.186.80.0/24AS1689Verizon BusinessRPKI Not found152.186.80.0
- 152.186.84.0/24AS1689Verizon BusinessRPKI Not found152.186.84.0
- 152.186.88.0/24AS1689Verizon BusinessRPKI Not found152.186.88.0
- 152.186.89.0/24AS1689Verizon BusinessRPKI Not found152.186.89.0
- 152.186.90.0/24AS702Verizon BusinessRPKI Not found152.186.90.0
- 152.186.92.0/24AS1689Verizon BusinessRPKI Not found152.186.92.0
- 152.186.93.0/24AS1689Verizon BusinessRPKI Not found152.186.93.0
- 152.186.94.0/24AS703Verizon BusinessRPKI Not found152.186.94.0
- 152.186.96.0/24AS1689Verizon BusinessRPKI Not found152.186.96.0
- 152.186.97.0/24AS1689Verizon BusinessRPKI Not found152.186.97.0
- 152.186.98.0/24AS702Verizon BusinessRPKI Not found152.186.98.0
- 152.189.92.0/24AS1661Verizon BusinessRPKI Not found152.189.92.0
- 152.189.93.0/24AS1661Verizon BusinessRPKI Not found152.189.93.0
- 152.189.95.0/24AS1661Verizon BusinessRPKI Not found152.189.95.0
- 152.189.96.0/24AS1661Verizon BusinessRPKI Not found152.189.96.0
- 152.189.114.0/24AS1661Verizon BusinessRPKI Not found152.189.114.0
- 152.189.115.0/24AS1661Verizon BusinessRPKI Not found152.189.115.0
- 152.189.117.0/24AS1661Verizon BusinessRPKI Not found152.189.117.0
- 152.189.118.0/24AS1661Verizon BusinessRPKI Not found152.189.118.0
- 152.190.160.0/24AS1699Verizon BusinessRPKI Not found152.190.160.0
- 152.190.161.0/24AS6984Verizon BusinessRPKI Not found152.190.161.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.