BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
65.168.0.0/14
Announced exactly
- 65.168.0.0/14AS174Cogent Communications, LLCRPKI Not found65.168.0.0
- Registry
- ARIN · United States · Sep 19, 2000
- Delegated block
- 65.168.0.0 – 65.171.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 65.168.33.0/24AS6103The Manitowoc Company IncRPKI Not found65.168.33.0
- 65.168.58.0/24AS174Cogent Communications, LLCRPKI Not found65.168.58.0
- 65.168.64.0/21AS18435The Junction Internet, LLCRPKI Not found65.168.64.0
- 65.168.64.0/22AS18435The Junction Internet, LLCRPKI Not found65.168.64.0
- 65.168.68.0/22AS18435The Junction Internet, LLCRPKI Not found65.168.68.0
- 65.168.228.0/23AS14861ISC GroupRPKI Not found65.168.228.0
- 65.168.234.0/24AS40489ALMO CorporationRPKI Not found65.168.234.0
- 65.169.6.0/23AS62802Macys Systems and Technology, Inc.RPKI Valid65.169.6.0
- 65.169.15.0/24AS20282Broadridge Trading and Connectivity Solutions Inc.RPKI Not found65.169.15.0
- 65.169.76.0/24AS22083Memorial Health Care SystemRPKI Not found65.169.76.0
- 65.169.144.0/24AS23005SWITCH, LTDRPKI Not found65.169.144.0
- 65.169.156.0/24AS33198Qualcomm, Inc.RPKI Not found65.169.156.0
- 65.169.250.0/24AS22106Samsung SDS America, Inc.RPKI Not found65.169.250.0
- 65.170.4.0/23AS12044Willamette Valley InternetRPKI Not found65.170.4.0
- 65.170.40.0/24AS174Cogent Communications, LLCRPKI Not found65.170.40.0
- 65.170.41.0/24AS36488Southwest Airlines Co.RPKI Not found65.170.41.0
- 65.170.63.0/24AS174Cogent Communications, LLCRPKI Not found65.170.63.0
- 65.170.86.0/23AS13866Computer CountryRPKI Not found65.170.86.0
- 65.170.122.0/24AS46140CAMP SYSTEMS INTERNATIONALRPKI Not found65.170.122.0
- 65.170.175.0/24AS29756RPE OutsourcingRPKI Not found65.170.175.0
- 65.170.202.0/24AS62802Macys Systems and Technology, Inc.RPKI Valid65.170.202.0
- 65.170.218.0/24AS396411MicroPact Global, IncRPKI Not found65.170.218.0
- 65.170.224.0/19AS4637ASN-TELSTRA-GLOBAL Telstra GlobalRPKI Not found65.170.224.0
- 65.171.32.0/19AS4637ASN-TELSTRA-GLOBAL Telstra GlobalRPKI Not found65.171.32.0
- 65.171.98.0/24AS36549WestTel Ltd.RPKI Not found65.171.98.0
- 65.171.146.0/24AS19257SUBRIGO CORPORATIONRPKI Not found65.171.146.0
- 65.171.147.0/24AS19257SUBRIGO CORPORATIONRPKI Not found65.171.147.0
- 65.171.192.0/19AS4637ASN-TELSTRA-GLOBAL Telstra GlobalRPKI Not found65.171.192.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.