BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
Examples:
64.81.0.0/16
One collector's view (APNIC). A route filtered before it reaches that collector is not listed.
Announced exactly
- 64.81.0.0/16AS3257GTT-BACKBONE GTTRPKI Not found64.81.0.0
- Registry
- ARIN · United States · Apr 28, 2000
- Delegated block
- 64.81.0.0 – 64.81.255.255
Covering routes
0
No less-specific route covers it.
More-specific routes
61 more-specifics from 22 origin AS(es)
- 64.81.16.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.81.16.0
- 64.81.20.0/24AS3257GTT-BACKBONE GTTRPKI Not found64.81.20.0
- 64.81.24.0/21AS3257GTT-BACKBONE GTTRPKI Not found64.81.24.0
- 64.81.26.0/23AS979NetLab GlobalRPKI Not found64.81.26.0
- 64.81.30.0/24AS979NetLab GlobalRPKI Not found64.81.30.0
- 64.81.32.0/21AS3257GTT-BACKBONE GTTRPKI Not found64.81.32.0
- 64.81.40.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.81.40.0
- 64.81.44.0/24AS12259EBOCOM LLCRPKI Valid64.81.44.0
- 64.81.45.0/24AS11696Fusion, LLCRPKI Not found64.81.45.0
- 64.81.46.0/23AS3257GTT-BACKBONE GTTRPKI Valid64.81.46.0
- 64.81.64.0/21AS3257GTT-BACKBONE GTTRPKI Valid64.81.64.0
- 64.81.72.0/22AS50118CARITELE-ASRPKI Valid64.81.72.0
- 64.81.76.0/23AS3257GTT-BACKBONE GTTRPKI Valid64.81.76.0
- 64.81.78.0/24AS3257GTT-BACKBONE GTTRPKI Not found64.81.78.0
- 64.81.79.0/24AS11696Fusion, LLCRPKI Not found64.81.79.0
- 64.81.112.0/21AS3257GTT-BACKBONE GTTRPKI Not found64.81.112.0
- 64.81.112.0/22AS979NetLab GlobalRPKI Not found64.81.112.0
- 64.81.112.0/24AS979NetLab GlobalRPKI Not found64.81.112.0
- 64.81.113.0/24AS979NetLab GlobalRPKI Not found64.81.113.0
- 64.81.114.0/24AS979NetLab GlobalRPKI Not found64.81.114.0
- 64.81.115.0/24AS979NetLab GlobalRPKI Not found64.81.115.0
- 64.81.116.0/23AS979NetLab GlobalRPKI Not found64.81.116.0
- 64.81.120.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.81.120.0
- 64.81.124.0/23AS3257GTT-BACKBONE GTTRPKI Valid64.81.124.0
- 64.81.126.0/24AS3257GTT-BACKBONE GTTRPKI Not found64.81.126.0
- 64.81.127.0/24AS11696Fusion, LLCRPKI Not found64.81.127.0
- 64.81.128.0/20AS3257GTT-BACKBONE GTTRPKI Valid64.81.128.0
- 64.81.144.0/21AS3257GTT-BACKBONE GTTRPKI Valid64.81.144.0
- 64.81.152.0/22AS3257GTT-BACKBONE GTTRPKI Valid64.81.152.0
- 64.81.156.0/23AS3257GTT-BACKBONE GTTRPKI Valid64.81.156.0
- 64.81.158.0/24AS3257GTT-BACKBONE GTTRPKI Not found64.81.158.0
- 64.81.159.0/24AS11696Fusion, LLCRPKI Not found64.81.159.0
- 64.81.160.0/24AS398184Highscore, IncRPKI Valid64.81.160.0
- 64.81.161.0/24AS3257GTT-BACKBONE GTTRPKI Valid64.81.161.0
- 64.81.162.0/24AS197537WISDOM-CLOUDRPKI Valid64.81.162.0
- 64.81.163.0/24AS3257GTT-BACKBONE GTTRPKI Valid64.81.163.0
- 64.81.164.0/24AS27176DataWagon LLCRPKI Valid64.81.164.0
- 64.81.165.0/24AS3257GTT-BACKBONE GTTRPKI Valid64.81.165.0
- 64.81.166.0/23AS3257GTT-BACKBONE GTTRPKI Valid64.81.166.0
- 64.81.168.0/24AS13537Mega Colocation, Inc.RPKI Valid64.81.168.0
- 64.81.169.0/24AS3257GTT-BACKBONE GTTRPKI Valid64.81.169.0
- 64.81.170.0/24AS6079RCNRPKI Valid64.81.170.0
- 64.81.171.0/24AS402394VuedgeRPKI Valid64.81.171.0
- 64.81.172.0/23AS4766KIXS-AS-KR Korea TelecomRPKI Valid64.81.172.0
- 64.81.174.0/24AS273034COMPANIA DE TELECOMUNICACIONES LEON & RODAS LR-COMPTEL S.A.RPKI Valid64.81.174.0
- 64.81.175.0/24AS273034COMPANIA DE TELECOMUNICACIONES LEON & RODAS LR-COMPTEL S.A.RPKI Valid64.81.175.0
- 64.81.176.0/24AS6079RCNRPKI Valid64.81.176.0
- 64.81.177.0/24AS5650Frontier Communications of America, Inc.RPKI Valid64.81.177.0
- 64.81.179.0/24AS46370Grand Web Solutions, Inc.RPKI Valid64.81.179.0
- 64.81.180.0/24AS402394VuedgeRPKI Valid64.81.180.0
- 64.81.181.0/24AS14927TeraTeams IncRPKI Valid64.81.181.0
- 64.81.182.0/24AS2914NTT America, Inc.RPKI Valid64.81.182.0
- 64.81.183.0/24AS26666Interserver, IncRPKI Valid64.81.183.0
- 64.81.184.0/24AS152726DREAMENGINEERING-AS-AP Dream EngineeringRPKI Valid64.81.184.0
- 64.81.185.0/24AS6079RCNRPKI Valid64.81.185.0
- 64.81.186.0/24AS3257GTT-BACKBONE GTTRPKI Valid64.81.186.0
- 64.81.187.0/24AS135402US-FXCAPITALRPKI Valid64.81.187.0
- 64.81.188.0/24AS21859Zenlayer IncRPKI Valid64.81.188.0
- 64.81.189.0/24AS395092Shock Hosting LLCRPKI Valid64.81.189.0
- 64.81.191.0/24AS6079RCNRPKI Valid64.81.191.0
- 64.81.192.0/18AS6079RCNRPKI Valid64.81.192.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.