BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
199.111.0.0/16
Announced exactly
- 199.111.0.0/16AS225University of VirginiaRPKI Not found199.111.0.0
- Registry
- ARIN · United States · Jan 11, 1994
- Delegated block
- 199.111.0.0 – 199.111.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 199.111.0.0/24AS225University of VirginiaRPKI Not found199.111.0.0
- 199.111.1.0/24AS225University of VirginiaRPKI Not found199.111.1.0
- 199.111.2.0/23AS225University of VirginiaRPKI Not found199.111.2.0
- 199.111.18.0/24AS225University of VirginiaRPKI Not found199.111.18.0
- 199.111.19.0/24AS225University of VirginiaRPKI Not found199.111.19.0
- 199.111.20.0/24AS25680Eastern Mennonite UniversityRPKI Not found199.111.20.0
- 199.111.21.0/24AS7795LUMOS Networks, Inc.RPKI Not found199.111.21.0
- 199.111.40.0/21AS225University of VirginiaRPKI Not found199.111.40.0
- 199.111.48.0/20AS225University of VirginiaRPKI Not found199.111.48.0
- 199.111.64.0/19AS397644University of Mary WashingtonRPKI Not found199.111.64.0
- 199.111.64.0/20AS397644University of Mary WashingtonRPKI Not found199.111.64.0
- 199.111.80.0/20AS397644University of Mary WashingtonRPKI Not found199.111.80.0
- 199.111.96.0/22AS23339Marymount UniversityRPKI Not found199.111.96.0
- 199.111.96.0/23AS23339Marymount UniversityRPKI Not found199.111.96.0
- 199.111.98.0/23AS23339Marymount UniversityRPKI Not found199.111.98.0
- 199.111.112.0/20AS7795LUMOS Networks, Inc.RPKI Not found199.111.112.0
- 199.111.116.0/24AS7795LUMOS Networks, Inc.RPKI Not found199.111.116.0
- 199.111.117.0/24AS7795LUMOS Networks, Inc.RPKI Not found199.111.117.0
- 199.111.118.0/24AS7795LUMOS Networks, Inc.RPKI Not found199.111.118.0
- 199.111.119.0/24AS7795LUMOS Networks, Inc.RPKI Not found199.111.119.0
- 199.111.121.0/24AS7795LUMOS Networks, Inc.RPKI Not found199.111.121.0
- 199.111.128.0/21AS7795LUMOS Networks, Inc.RPKI Not found199.111.128.0
- 199.111.136.0/24AS397644University of Mary WashingtonRPKI Not found199.111.136.0
- 199.111.137.0/24AS397644University of Mary WashingtonRPKI Not found199.111.137.0
- 199.111.138.0/23AS397644University of Mary WashingtonRPKI Not found199.111.138.0
- 199.111.138.0/24AS397644University of Mary WashingtonRPKI Not found199.111.138.0
- 199.111.139.0/24AS397644University of Mary WashingtonRPKI Not found199.111.139.0
- 199.111.140.0/23AS397644University of Mary WashingtonRPKI Not found199.111.140.0
- 199.111.140.0/24AS397644University of Mary WashingtonRPKI Not found199.111.140.0
- 199.111.141.0/24AS397644University of Mary WashingtonRPKI Not found199.111.141.0
- 199.111.144.0/20AS7795LUMOS Networks, Inc.RPKI Not found199.111.144.0
- 199.111.144.0/21AS394533Roanoke CollegeRPKI Not found199.111.144.0
- 199.111.152.0/21AS394533Roanoke CollegeRPKI Not found199.111.152.0
- 199.111.160.0/19AS225University of VirginiaRPKI Not found199.111.160.0
- 199.111.192.0/18AS225University of VirginiaRPKI Not found199.111.192.0
- 199.111.208.0/22AS225University of VirginiaRPKI Not found199.111.208.0
- 199.111.224.0/19AS225University of VirginiaRPKI Not found199.111.224.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.