BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
65.86.0.0/16
Announced exactly
- 65.86.0.0/16AS3257GTT Communications Inc.RPKI Not found65.86.0.0
- Registry
- ARIN · United States · Dec 8, 2000
- Delegated block
- 65.86.0.0 – 65.86.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 65.86.32.0/24AS394380Leaseweb USA, Inc.RPKI Valid65.86.32.0
- 65.86.33.0/24AS8447A1 Telekom Austria AGRPKI Valid65.86.33.0
- 65.86.34.0/24AS8447A1 Telekom Austria AGRPKI Valid65.86.34.0
- 65.86.35.0/24AS8447A1 Telekom Austria AGRPKI Valid65.86.35.0
- 65.86.40.0/22AS5650Frontier Communications of America, Inc.RPKI Valid65.86.40.0
- 65.86.48.0/22AS5650Frontier Communications of America, Inc.RPKI Valid65.86.48.0
- 65.86.56.0/22AS3257GTT Communications Inc.RPKI Not found65.86.56.0
- 65.86.80.0/22AS20115Charter Communications LLCRPKI Valid65.86.80.0
- 65.86.88.0/24AS3257GTT Communications Inc.RPKI Not found65.86.88.0
- 65.86.89.0/24AS3257GTT Communications Inc.RPKI Not found65.86.89.0
- 65.86.90.0/24AS3257GTT Communications Inc.RPKI Not found65.86.90.0
- 65.86.91.0/24AS3257GTT Communications Inc.RPKI Not found65.86.91.0
- 65.86.92.0/23AS3257GTT Communications Inc.RPKI Not found65.86.92.0
- 65.86.94.0/24AS3257GTT Communications Inc.RPKI Not found65.86.94.0
- 65.86.95.0/24AS3257GTT Communications Inc.RPKI Not found65.86.95.0
- 65.86.104.0/21AS12271Charter Communications IncRPKI Valid65.86.104.0
- 65.86.136.0/22AS20115Charter Communications LLCRPKI Valid65.86.136.0
- 65.86.140.0/22AS399989ULTRA ONERPKI Valid65.86.140.0
- 65.86.146.0/23AS5650Frontier Communications of America, Inc.RPKI Valid65.86.146.0
- 65.86.150.0/23AS5650Frontier Communications of America, Inc.RPKI Valid65.86.150.0
- 65.86.150.0/24AS7029Windstream Communications LLCRPKI Valid65.86.150.0
- 65.86.151.0/24AS7029Windstream Communications LLCRPKI Valid65.86.151.0
- 65.86.160.0/24AS6079RCNRPKI Valid65.86.160.0
- 65.86.161.0/24AS6079RCNRPKI Valid65.86.161.0
- 65.86.162.0/24AS6079RCNRPKI Valid65.86.162.0
- 65.86.163.0/24AS6079RCNRPKI Valid65.86.163.0
- 65.86.164.0/24AS6079RCNRPKI Valid65.86.164.0
- 65.86.165.0/24AS6079RCNRPKI Valid65.86.165.0
- 65.86.166.0/24AS6079RCNRPKI Valid65.86.166.0
- 65.86.167.0/24AS6079RCNRPKI Valid65.86.167.0
- 65.86.168.0/24AS6079RCNRPKI Valid65.86.168.0
- 65.86.169.0/24AS6079RCNRPKI Valid65.86.169.0
- 65.86.170.0/24AS6079RCNRPKI Valid65.86.170.0
- 65.86.171.0/24AS6079RCNRPKI Valid65.86.171.0
- 65.86.172.0/24AS6079RCNRPKI Valid65.86.172.0
- 65.86.173.0/24AS6079RCNRPKI Valid65.86.173.0
- 65.86.174.0/24AS6079RCNRPKI Valid65.86.174.0
- 65.86.175.0/24AS6079RCNRPKI Valid65.86.175.0
- 65.86.176.0/22AS25369Hydra Communications LtdRPKI Valid65.86.176.0
- 65.86.180.0/22AS199959GWY IT PTY LTDRPKI Valid65.86.180.0
- 65.86.184.0/22AS25369Hydra Communications LtdRPKI Valid65.86.184.0
- 65.86.188.0/22AS199959GWY IT PTY LTDRPKI Valid65.86.188.0
- 65.86.192.0/22AS16509Amazon.com, Inc.RPKI Valid65.86.192.0
- 65.86.197.0/24AS212238Datacamp LimitedRPKI Valid65.86.197.0
- 65.86.200.0/24AS137410MiM Digital Marketing Solution Ltd.RPKI Valid65.86.200.0
- 65.86.204.0/24AS212238Datacamp LimitedRPKI Valid65.86.204.0
- 65.86.206.0/24AS6079RCNRPKI Valid65.86.206.0
- 65.86.208.0/21AS22773Cox Communications Inc.RPKI Valid65.86.208.0
- 65.86.216.0/24AS219075VSEEK LIMITEDRPKI Valid65.86.216.0
- 65.86.218.0/24AS219075VSEEK LIMITEDRPKI Valid65.86.218.0
- 65.86.220.0/24AS218911ORION LIMITEDRPKI Valid65.86.220.0
- 65.86.222.0/24AS212477RoyaleHosting BVRPKI Valid65.86.222.0
- 65.86.223.0/24AS212477RoyaleHosting BVRPKI Valid65.86.223.0
- 65.86.224.0/20AS6079RCNRPKI Valid65.86.224.0
- 65.86.240.0/20AS6079RCNRPKI Valid65.86.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, 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.