BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.146.128.0/17
Announced exactly
- 64.146.128.0/17AS16713Northwest Open Access NetworkRPKI Valid64.146.128.0
- Registry
- ARIN · United States · Sep 13, 2001
- Delegated block
- 64.146.128.0 – 64.146.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.146.132.0/23AS27373Douglas County PUDRPKI Valid64.146.132.0
- 64.146.142.0/23AS16713Northwest Open Access NetworkRPKI Valid64.146.142.0
- 64.146.144.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.144.0
- 64.146.146.0/24AS20224Columbia Energy L.L.CRPKI Valid64.146.146.0
- 64.146.147.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.147.0
- 64.146.148.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.148.0
- 64.146.150.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.150.0
- 64.146.163.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.163.0
- 64.146.164.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.164.0
- 64.146.165.0/24AS396098U.S. Department of Energy - HanfordRPKI Valid64.146.165.0
- 64.146.166.0/24AS400686WAHKIAKUM WEST TELEVISION, INC.RPKI Valid64.146.166.0
- 64.146.170.0/23AS20224Columbia Energy L.L.CRPKI Valid64.146.170.0
- 64.146.172.0/24AS27373Douglas County PUDRPKI Valid64.146.172.0
- 64.146.176.0/22AS20224Columbia Energy L.L.CRPKI Valid64.146.176.0
- 64.146.184.0/24AS32312Telecommunication Systems, Inc.RPKI Valid64.146.184.0
- 64.146.185.0/24AS32312Telecommunication Systems, Inc.RPKI Valid64.146.185.0
- 64.146.186.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.186.0
- 64.146.188.0/24AS401706Valley Smart HomesRPKI Valid64.146.188.0
- 64.146.208.0/22AS16713Northwest Open Access NetworkRPKI Valid64.146.208.0
- 64.146.212.0/23AS16713Northwest Open Access NetworkRPKI Valid64.146.212.0
- 64.146.212.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.212.0
- 64.146.216.0/21AS7799Olypen, Inc.RPKI Valid64.146.216.0
- 64.146.230.0/24AS20224Columbia Energy L.L.CRPKI Valid64.146.230.0
- 64.146.233.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.233.0
- 64.146.234.0/23AS16713Northwest Open Access NetworkRPKI Valid64.146.234.0
- 64.146.240.0/21AS7799Olypen, Inc.RPKI Valid64.146.240.0
- 64.146.250.0/23AS16713Northwest Open Access NetworkRPKI Valid64.146.250.0
- 64.146.253.0/24AS16713Northwest Open Access NetworkRPKI Valid64.146.253.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.