BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
65.49.0.0/17
Announced exactly
- 65.49.0.0/17AS6939Hurricane Electric LLCRPKI Valid65.49.0.0
- Registry
- ARIN · United States · Oct 4, 2007
- Delegated block
- 65.49.0.0 – 65.49.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 65.49.2.0/24AS6939Hurricane Electric LLCRPKI Valid65.49.2.0
- 65.49.5.0/24AS54288SolidTools Technology, Inc.RPKI Valid65.49.5.0
- 65.49.6.0/23AS36103Central Utah Telephone, Inc.RPKI Valid65.49.6.0
- 65.49.11.0/24AS16468AirFiber WISP LLCRPKI Valid65.49.11.0
- 65.49.14.0/24AS6939Hurricane Electric LLCRPKI Valid65.49.14.0
- 65.49.15.0/24AS36707System Admin, LLCRPKI Valid65.49.15.0
- 65.49.23.0/24AS398885Aerwave, Inc.RPKI Valid65.49.23.0
- 65.49.26.0/24AS60154CONNECTRIA-ASN-1RPKI Valid65.49.26.0
- 65.49.31.0/24AS40604N2N Technologies, Inc.RPKI Valid65.49.31.0
- 65.49.41.0/24AS54288SolidTools Technology, Inc.RPKI Valid65.49.41.0
- 65.49.45.0/24AS54288SolidTools Technology, Inc.RPKI Valid65.49.45.0
- 65.49.46.0/24AS36111Brinks, IncorporatedRPKI Valid65.49.46.0
- 65.49.54.0/24AS39499647-2339071RPKI Valid65.49.54.0
- 65.49.55.0/24AS53268EIS Group, INCRPKI Valid65.49.55.0
- 65.49.57.0/24AS54288SolidTools Technology, Inc.RPKI Valid65.49.57.0
- 65.49.58.0/23AS36103Central Utah Telephone, Inc.RPKI Valid65.49.58.0
- 65.49.60.0/24AS401742ServerOptimaRPKI Valid65.49.60.0
- 65.49.65.0/24AS401742ServerOptimaRPKI Valid65.49.65.0
- 65.49.68.0/24AS6939Hurricane Electric LLCRPKI Valid65.49.68.0
- 65.49.74.0/23AS36103Central Utah Telephone, Inc.RPKI Valid65.49.74.0
- 65.49.78.0/24AS39499647-2339071RPKI Valid65.49.78.0
- 65.49.81.0/24AS39499647-2339071RPKI Valid65.49.81.0
- 65.49.84.0/22AS36103Central Utah Telephone, Inc.RPKI Valid65.49.84.0
- 65.49.85.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.85.0
- 65.49.86.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.86.0
- 65.49.87.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.87.0
- 65.49.90.0/23AS36103Central Utah Telephone, Inc.RPKI Valid65.49.90.0
- 65.49.92.0/24AS54288SolidTools Technology, Inc.RPKI Valid65.49.92.0
- 65.49.93.0/24AS18779EGIHostingRPKI Valid65.49.93.0
- 65.49.94.0/23AS36103Central Utah Telephone, Inc.RPKI Valid65.49.94.0
- 65.49.96.0/22AS36103Central Utah Telephone, Inc.RPKI Valid65.49.96.0
- 65.49.100.0/22AS393552Longmont Power & CommunicationsRPKI Valid65.49.100.0
- 65.49.104.0/22AS6939Hurricane Electric LLCRPKI Valid65.49.104.0
- 65.49.108.0/22AS6939Hurricane Electric LLCRPKI Valid65.49.108.0
- 65.49.110.0/23AS133929TWOWINCOLIMITED-AS-AP TWOWIN CO., LIMITEDRPKI Valid65.49.110.0
- 65.49.110.0/24AS133929TWOWINCOLIMITED-AS-AP TWOWIN CO., LIMITEDRPKI Valid65.49.110.0
- 65.49.111.0/24AS133929TWOWINCOLIMITED-AS-AP TWOWIN CO., LIMITEDRPKI Valid65.49.111.0
- 65.49.112.0/25AS398885Aerwave, Inc.RPKI Invalid65.49.112.0
- 65.49.112.128/25AS398885Aerwave, Inc.RPKI Invalid65.49.112.128
- 65.49.116.0/22AS36103Central Utah Telephone, Inc.RPKI Valid65.49.116.0
- 65.49.116.0/23AS36103Central Utah Telephone, Inc.RPKI Valid65.49.116.0
- 65.49.118.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.118.0
- 65.49.120.0/22AS36103Central Utah Telephone, Inc.RPKI Valid65.49.120.0
- 65.49.120.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.120.0
- 65.49.121.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.121.0
- 65.49.122.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.122.0
- 65.49.123.0/24AS36103Central Utah Telephone, Inc.RPKI Valid65.49.123.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.