BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
152.192.0.0/13
Announced exactly
- 152.192.0.0/13AS701Verizon BusinessRPKI Not found152.192.0.0
- Registry
- ARIN · United States · Apr 1, 1992
- Delegated block
- 152.192.0.0 – 152.199.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 152.194.36.0/24AS62642Bigleaf Networks, Inc.RPKI Not found152.194.36.0
- 152.194.64.0/22AS702Verizon BusinessRPKI Not found152.194.64.0
- 152.196.0.0/22AS1339Verizon BusinessRPKI Not found152.196.0.0
- 152.196.0.0/24AS1339Verizon BusinessRPKI Not found152.196.0.0
- 152.196.4.0/22AS1321Verizon BusinessRPKI Not found152.196.4.0
- 152.196.4.0/24AS1321Verizon BusinessRPKI Not found152.196.4.0
- 152.196.8.0/24AS1321Verizon BusinessRPKI Not found152.196.8.0
- 152.196.10.0/24AS1321Verizon BusinessRPKI Not found152.196.10.0
- 152.196.12.0/24AS1321Verizon BusinessRPKI Not found152.196.12.0
- 152.196.14.0/24AS1321Verizon BusinessRPKI Not found152.196.14.0
- 152.196.16.0/24AS1321Verizon BusinessRPKI Not found152.196.16.0
- 152.196.18.0/24AS1321Verizon BusinessRPKI Not found152.196.18.0
- 152.196.20.0/24AS1321Verizon BusinessRPKI Not found152.196.20.0
- 152.196.22.0/24AS1321Verizon BusinessRPKI Not found152.196.22.0
- 152.196.26.0/24AS1321Verizon BusinessRPKI Not found152.196.26.0
- 152.196.28.0/24AS1321Verizon BusinessRPKI Not found152.196.28.0
- 152.196.68.0/24AS1321Verizon BusinessRPKI Not found152.196.68.0
- 152.196.70.0/24AS1321Verizon BusinessRPKI Not found152.196.70.0
- 152.196.72.0/24AS1321Verizon BusinessRPKI Not found152.196.72.0
- 152.196.74.0/24AS1321Verizon BusinessRPKI Not found152.196.74.0
- 152.196.100.0/24AS1321Verizon BusinessRPKI Not found152.196.100.0
- 152.196.102.0/24AS1321Verizon BusinessRPKI Not found152.196.102.0
- 152.196.104.0/24AS1321Verizon BusinessRPKI Not found152.196.104.0
- 152.196.106.0/24AS1321Verizon BusinessRPKI Not found152.196.106.0
- 152.196.110.0/23AS1339Verizon BusinessRPKI Not found152.196.110.0
- 152.196.112.0/23AS1339Verizon BusinessRPKI Not found152.196.112.0
- 152.196.112.0/24AS1339Verizon BusinessRPKI Not found152.196.112.0
- 152.196.114.0/23AS1339Verizon BusinessRPKI Not found152.196.114.0
- 152.196.116.0/23AS1339Verizon BusinessRPKI Not found152.196.116.0
- 152.196.118.0/23AS1383Verizon BusinessRPKI Not found152.196.118.0
- 152.196.121.0/24AS1321Verizon BusinessRPKI Not found152.196.121.0
- 152.196.123.0/24AS1339Verizon BusinessRPKI Not found152.196.123.0
- 152.196.124.0/24AS1339Verizon BusinessRPKI Not found152.196.124.0
- 152.196.240.0/24AS1339Verizon BusinessRPKI Not found152.196.240.0
- 152.198.0.0/24AS1326Verizon BusinessRPKI Not found152.198.0.0
- 152.198.4.0/24AS1326Verizon BusinessRPKI Not found152.198.4.0
- 152.198.7.0/24AS1326Verizon BusinessRPKI Not found152.198.7.0
- 152.199.157.0/24AS14210Edgecast Inc.RPKI Not found152.199.157.0
- 152.199.158.0/24AS14210Edgecast Inc.RPKI Not found152.199.158.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.