BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.201.160.0/19
Announced exactly
- 64.201.160.0/19AS20161TeraGo Networks Inc.RPKI Not found64.201.160.0
- Registry
- ARIN · Canada · Oct 11, 2002
- Delegated block
- 64.201.160.0 – 64.201.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.201.160.0/21AS20161TeraGo Networks Inc.RPKI Not found64.201.160.0
- 64.201.168.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.168.0
- 64.201.169.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.169.0
- 64.201.170.0/23AS20161TeraGo Networks Inc.RPKI Not found64.201.170.0
- 64.201.170.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.170.0
- 64.201.171.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.171.0
- 64.201.172.0/23AS20161TeraGo Networks Inc.RPKI Not found64.201.172.0
- 64.201.174.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.174.0
- 64.201.175.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.175.0
- 64.201.177.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.177.0
- 64.201.178.0/24AS16543Gate West Communications Inc.RPKI Not found64.201.178.0
- 64.201.179.0/24AS16543Gate West Communications Inc.RPKI Not found64.201.179.0
- 64.201.180.0/23AS20161TeraGo Networks Inc.RPKI Not found64.201.180.0
- 64.201.180.0/24AS16543Gate West Communications Inc.RPKI Not found64.201.180.0
- 64.201.181.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.181.0
- 64.201.182.0/23AS20161TeraGo Networks Inc.RPKI Not found64.201.182.0
- 64.201.184.0/23AS20161TeraGo Networks Inc.RPKI Not found64.201.184.0
- 64.201.187.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.187.0
- 64.201.188.0/24AS20161TeraGo Networks Inc.RPKI Not found64.201.188.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.