BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
165.26.0.0/16
Announced exactly
- 165.26.0.0/16AS14381Caterpillar, Inc.RPKI Not found165.26.0.0
- Registry
- ARIN · United States · Apr 2, 1993
- Delegated block
- 165.26.0.0 – 165.26.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 165.26.0.0/19AS14381Caterpillar, Inc.RPKI Not found165.26.0.0
- 165.26.32.0/20AS14381Caterpillar, Inc.RPKI Not found165.26.32.0
- 165.26.40.0/21AS14381Caterpillar, Inc.RPKI Not found165.26.40.0
- 165.26.42.0/23AS14381Caterpillar, Inc.RPKI Not found165.26.42.0
- 165.26.44.0/22AS14381Caterpillar, Inc.RPKI Not found165.26.44.0
- 165.26.48.0/20AS14381Caterpillar, Inc.RPKI Not found165.26.48.0
- 165.26.64.0/18AS14381Caterpillar, Inc.RPKI Not found165.26.64.0
- 165.26.128.0/18AS14381Caterpillar, Inc.RPKI Not found165.26.128.0
- 165.26.188.0/22AS14381Caterpillar, Inc.RPKI Not found165.26.188.0
- 165.26.192.0/21AS14381Caterpillar, Inc.RPKI Not found165.26.192.0
- 165.26.192.0/22AS14381Caterpillar, Inc.RPKI Not found165.26.192.0
- 165.26.200.0/22AS14381Caterpillar, Inc.RPKI Not found165.26.200.0
- 165.26.204.0/22AS14381Caterpillar, Inc.RPKI Not found165.26.204.0
- 165.26.208.0/21AS14381Caterpillar, Inc.RPKI Not found165.26.208.0
- 165.26.224.0/21AS14381Caterpillar, Inc.RPKI Not found165.26.224.0
- 165.26.232.0/22AS14381Caterpillar, Inc.RPKI Not found165.26.232.0
- 165.26.236.0/24AS14381Caterpillar, Inc.RPKI Not found165.26.236.0
- 165.26.237.0/24AS14381Caterpillar, Inc.RPKI Not found165.26.237.0
- 165.26.238.0/24AS14381Caterpillar, Inc.RPKI Not found165.26.238.0
- 165.26.240.0/20AS14381Caterpillar, Inc.RPKI Not found165.26.240.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.