BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
65.64.0.0/13
Announced exactly
- 65.64.0.0/13AS7018AT&T Enterprises, LLCRPKI Not found65.64.0.0
- Registry
- ARIN · United States · Oct 3, 2000
- Delegated block
- 65.64.0.0 – 65.71.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 65.64.16.0/22AS15026Acxiom LLCRPKI Not found65.64.16.0
- 65.64.216.0/24AS19934Uber Freight US LLCRPKI Not found65.64.216.0
- 65.65.128.0/20AS36105Big Bend Telephone Company, Inc.RPKI Valid65.65.128.0
- 65.65.128.0/21AS36105Big Bend Telephone Company, Inc.RPKI Valid65.65.128.0
- 65.65.136.0/21AS36105Big Bend Telephone Company, Inc.RPKI Valid65.65.136.0
- 65.65.152.0/21AS36105Big Bend Telephone Company, Inc.RPKI Valid65.65.152.0
- 65.66.196.0/23AS26295UNASSIGNEDRPKI Not found65.66.196.0
- 65.67.212.0/23AS400218Cherokee Nation GovernmentRPKI Not found65.67.212.0
- 65.67.214.0/24AS400218Cherokee Nation GovernmentRPKI Not found65.67.214.0
- 65.68.53.0/24AS2386AT&T Enterprises, LLCRPKI Not found65.68.53.0
- 65.69.172.0/23AS2386AT&T Enterprises, LLCRPKI Not found65.69.172.0
- 65.70.69.0/24AS21648SageNetRPKI Not found65.70.69.0
- 65.70.242.0/23AS11492CABLE ONE, INC.RPKI Not found65.70.242.0
- 65.71.30.0/24AS393359Security Service Federal Credit UnionRPKI Not found65.71.30.0
- 65.71.154.0/24AS396977USAble Mutual Insurance CompanyRPKI Not found65.71.154.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.