BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
70.39.128.0/17
Announced exactly
- 70.39.128.0/17AS3257GTT Communications Inc.RPKI Not found70.39.128.0
- Registry
- ARIN · United States · Nov 24, 2009
- Delegated block
- 70.39.128.0 – 70.39.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 70.39.128.0/24AS2914NTT America, Inc.RPKI Valid70.39.128.0
- 70.39.130.0/24AS2914NTT America, Inc.RPKI Valid70.39.130.0
- 70.39.131.0/24AS2914NTT America, Inc.RPKI Valid70.39.131.0
- 70.39.132.0/24AS2914NTT America, Inc.RPKI Valid70.39.132.0
- 70.39.133.0/24AS2914NTT America, Inc.RPKI Valid70.39.133.0
- 70.39.134.0/24AS2914NTT America, Inc.RPKI Valid70.39.134.0
- 70.39.135.0/24AS2914NTT America, Inc.RPKI Valid70.39.135.0
- 70.39.136.0/24AS2914NTT America, Inc.RPKI Valid70.39.136.0
- 70.39.137.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid70.39.137.0
- 70.39.140.0/24AS2914NTT America, Inc.RPKI Valid70.39.140.0
- 70.39.141.0/24AS2914NTT America, Inc.RPKI Valid70.39.141.0
- 70.39.143.0/24AS2914NTT America, Inc.RPKI Valid70.39.143.0
- 70.39.144.0/21AS54641InMotion Hosting, Inc.RPKI Not found70.39.144.0
- 70.39.154.0/24AS3257GTT Communications Inc.RPKI Invalid70.39.154.0
- 70.39.156.0/24AS3257GTT Communications Inc.RPKI Invalid70.39.156.0
- 70.39.158.0/24AS2914NTT America, Inc.RPKI Valid70.39.158.0
- 70.39.159.0/24AS22616ZSCALER, INC.RPKI Not found70.39.159.0
- 70.39.164.0/24AS2914NTT America, Inc.RPKI Valid70.39.164.0
- 70.39.170.0/24AS3257GTT Communications Inc.RPKI Invalid70.39.170.0
- 70.39.171.0/24AS32043NeoFiber Communications inc.RPKI Valid70.39.171.0
- 70.39.176.0/21AS3257GTT Communications Inc.RPKI Not found70.39.176.0
- 70.39.178.0/24AS979NetLab GlobalRPKI Not found70.39.178.0
- 70.39.180.0/23AS979NetLab GlobalRPKI Not found70.39.180.0
- 70.39.180.0/24AS1014NetLab GlobalRPKI Not found70.39.180.0
- 70.39.181.0/24AS1014NetLab GlobalRPKI Not found70.39.181.0
- 70.39.183.0/24AS979NetLab GlobalRPKI Not found70.39.183.0
- 70.39.184.0/24AS5065Bunny CommunicationsRPKI Valid70.39.184.0
- 70.39.185.0/24AS399073BUNNY TECHNOLOGY LLCRPKI Valid70.39.185.0
- 70.39.186.0/24AS399073BUNNY TECHNOLOGY LLCRPKI Valid70.39.186.0
- 70.39.187.0/24AS399073BUNNY TECHNOLOGY LLCRPKI Valid70.39.187.0
- 70.39.189.0/24AS54994Meteverse Limited.RPKI Not found70.39.189.0
- 70.39.191.0/24AS3257GTT Communications Inc.RPKI Invalid70.39.191.0
- 70.39.192.0/21AS3257GTT Communications Inc.RPKI Not found70.39.192.0
- 70.39.195.0/24AS979NetLab GlobalRPKI Not found70.39.195.0
- 70.39.197.0/24AS979NetLab GlobalRPKI Not found70.39.197.0
- 70.39.198.0/24AS979NetLab GlobalRPKI Not found70.39.198.0
- 70.39.200.0/21AS3257GTT Communications Inc.RPKI Not found70.39.200.0
- 70.39.200.0/22AS979NetLab GlobalRPKI Not found70.39.200.0
- 70.39.200.0/24AS979NetLab GlobalRPKI Not found70.39.200.0
- 70.39.201.0/24AS979NetLab GlobalRPKI Not found70.39.201.0
- 70.39.202.0/24AS1014NetLab GlobalRPKI Not found70.39.202.0
- 70.39.203.0/24AS1014NetLab GlobalRPKI Not found70.39.203.0
- 70.39.204.0/22AS979NetLab GlobalRPKI Not found70.39.204.0
- 70.39.204.0/24AS1014NetLab GlobalRPKI Not found70.39.204.0
- 70.39.205.0/24AS979NetLab GlobalRPKI Not found70.39.205.0
- 70.39.206.0/24AS1014NetLab GlobalRPKI Not found70.39.206.0
- 70.39.207.0/24AS1014NetLab GlobalRPKI Not found70.39.207.0
- 70.39.224.0/22AS3257GTT Communications Inc.RPKI Not found70.39.224.0
- 70.39.228.0/24AS11403NYIRPKI Not found70.39.228.0
- 70.39.230.0/24AS3257GTT Communications Inc.RPKI Valid70.39.230.0
- 70.39.231.0/24AS2914NTT America, Inc.RPKI Valid70.39.231.0
- 70.39.232.0/23AS54641InMotion Hosting, Inc.RPKI Not found70.39.232.0
- 70.39.234.0/23AS54641InMotion Hosting, Inc.RPKI Not found70.39.234.0
- 70.39.236.0/24AS5065Bunny CommunicationsRPKI Valid70.39.236.0
- 70.39.237.0/24AS5065Bunny CommunicationsRPKI Valid70.39.237.0
- 70.39.238.0/24AS7346Springtide CommunicationsRPKI Valid70.39.238.0
- 70.39.239.0/24AS5065Bunny CommunicationsRPKI Valid70.39.239.0
- 70.39.240.0/24AS53483ReSource Pro, LLCRPKI Not found70.39.240.0
- 70.39.241.0/24AS2914NTT America, Inc.RPKI Valid70.39.241.0
- 70.39.242.0/24AS3257GTT Communications Inc.RPKI Invalid70.39.242.0
- 70.39.243.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid70.39.243.0
- 70.39.246.0/23AS30366Rhythmic Technologies, Inc.RPKI Not found70.39.246.0
- 70.39.246.0/24AS30366Rhythmic Technologies, Inc.RPKI Not found70.39.246.0
- 70.39.247.0/24AS30366Rhythmic Technologies, Inc.RPKI Not found70.39.247.0
- 70.39.248.0/23AS54641InMotion Hosting, Inc.RPKI Not found70.39.248.0
- 70.39.250.0/23AS54641InMotion Hosting, Inc.RPKI Not found70.39.250.0
- 70.39.252.0/24AS2914NTT America, Inc.RPKI Valid70.39.252.0
- 70.39.253.0/24AS16647Perimeterwatch Technologies, INCRPKI Valid70.39.253.0
- 70.39.254.0/24AS3257GTT Communications Inc.RPKI Invalid70.39.254.0
- 70.39.255.0/24AS3257GTT Communications Inc.RPKI Invalid70.39.255.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.