BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.141.0.0/17
Announced exactly
- 64.141.0.0/17AS6327Shaw CommunicationsRPKI Not found64.141.0.0
- Registry
- ARIN · Canada · May 20, 2002
- Delegated block
- 64.141.0.0 – 64.141.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.141.0.0/22AS6327Shaw CommunicationsRPKI Not found64.141.0.0
- 64.141.4.0/22AS6327Shaw CommunicationsRPKI Not found64.141.4.0
- 64.141.5.0/24AS53359CUBE Global Storage Ltd.RPKI Not found64.141.5.0
- 64.141.8.0/22AS6327Shaw CommunicationsRPKI Not found64.141.8.0
- 64.141.12.0/22AS6327Shaw CommunicationsRPKI Not found64.141.12.0
- 64.141.12.0/24AS53342Delco Automation IncRPKI Not found64.141.12.0
- 64.141.16.0/21AS6327Shaw CommunicationsRPKI Not found64.141.16.0
- 64.141.22.0/24AS394006Vincent Communications & Controls Ltd.RPKI Not found64.141.22.0
- 64.141.24.0/24AS6327Shaw CommunicationsRPKI Not found64.141.24.0
- 64.141.25.0/24AS6327Shaw CommunicationsRPKI Not found64.141.25.0
- 64.141.26.0/23AS6327Shaw CommunicationsRPKI Not found64.141.26.0
- 64.141.28.0/22AS6327Shaw CommunicationsRPKI Not found64.141.28.0
- 64.141.32.0/21AS6327Shaw CommunicationsRPKI Not found64.141.32.0
- 64.141.37.0/24AS6327Shaw CommunicationsRPKI Not found64.141.37.0
- 64.141.38.0/23AS6327Shaw CommunicationsRPKI Not found64.141.38.0
- 64.141.40.0/21AS6327Shaw CommunicationsRPKI Not found64.141.40.0
- 64.141.42.0/24AS3963743C Information Solutions Inc.RPKI Not found64.141.42.0
- 64.141.48.0/21AS6327Shaw CommunicationsRPKI Not found64.141.48.0
- 64.141.50.0/24AS399688Hy-Tek Computer Sales and Services LtdRPKI Not found64.141.50.0
- 64.141.52.0/24AS6327Shaw CommunicationsRPKI Not found64.141.52.0
- 64.141.56.0/21AS6327Shaw CommunicationsRPKI Not found64.141.56.0
- 64.141.64.0/24AS6327Shaw CommunicationsRPKI Not found64.141.64.0
- 64.141.65.0/24AS6327Shaw CommunicationsRPKI Not found64.141.65.0
- 64.141.66.0/24AS6327Shaw CommunicationsRPKI Not found64.141.66.0
- 64.141.67.0/24AS6327Shaw CommunicationsRPKI Not found64.141.67.0
- 64.141.68.0/22AS6327Shaw CommunicationsRPKI Not found64.141.68.0
- 64.141.70.0/23AS6327Shaw CommunicationsRPKI Not found64.141.70.0
- 64.141.72.0/22AS6327Shaw CommunicationsRPKI Not found64.141.72.0
- 64.141.72.0/24AS6327Shaw CommunicationsRPKI Not found64.141.72.0
- 64.141.76.0/22AS6327Shaw CommunicationsRPKI Not found64.141.76.0
- 64.141.80.0/21AS6327Shaw CommunicationsRPKI Not found64.141.80.0
- 64.141.88.0/21AS6327Shaw CommunicationsRPKI Not found64.141.88.0
- 64.141.96.0/21AS6327Shaw CommunicationsRPKI Not found64.141.96.0
- 64.141.104.0/22AS21533Corus Entertainment IncRPKI Not found64.141.104.0
- 64.141.108.0/22AS6327Shaw CommunicationsRPKI Not found64.141.108.0
- 64.141.112.0/21AS6327Shaw CommunicationsRPKI Not found64.141.112.0
- 64.141.120.0/21AS6327Shaw CommunicationsRPKI Not found64.141.120.0
- 64.141.120.0/22AS32738Hybrid Wireless IncRPKI Not found64.141.120.0
- 64.141.125.0/24AS6327Shaw CommunicationsRPKI Not found64.141.125.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.