Done Refresh page.
Sweet, I always like to see when i have a heft % of the pools hashrate..
It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
PING miningrigrentals.com(2606:4700:20::681a:3d (2606:4700:20::681a:3d)) 56 data bytes
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=1 ttl=57 time=1.38 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=2 ttl=57 time=1.25 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=3 ttl=57 time=1.16 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=4 ttl=57 time=1.27 ms
64 bytes from 2606:4700:20::681a:3d (2606:4700:20::681a:3d): icmp_seq=5 ttl=57 time=1.44 ms
PING miningrigrentals.com (104.26.0.61) 56(84) bytes of data.
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=1 ttl=57 time=1.44 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=2 ttl=57 time=1.27 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=3 ttl=57 time=1.34 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=4 ttl=57 time=1.30 ms
64 bytes from 104.26.0.61 (104.26.0.61): icmp_seq=5 ttl=57 time=1.32 ms
ping -4 nicehash.com
PING nicehash.com (104.17.254.46) 56(84) bytes of data.
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=1 ttl=57 time=1.40 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=2 ttl=57 time=1.53 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=3 ttl=57 time=1.44 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=4 ttl=57 time=1.42 ms
64 bytes from 104.17.254.46 (104.17.254.46): icmp_seq=5 ttl=57 time=1.52 ms
ping -6 nicehash.com
PING nicehash.com(2606:4700::6811:ff2e (2606:4700::6811:ff2e)) 56 data bytes
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=1 ttl=56 time=19.6 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=2 ttl=56 time=19.7 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=3 ttl=56 time=19.5 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=4 ttl=56 time=19.5 ms
64 bytes from 2606:4700::6811:ff2e (2606:4700::6811:ff2e): icmp_seq=5 ttl=56 time=18.6 ms
Note that solo.ckpool.org supports both IPV4 and IPV6 transparently.
You may wish to find which is lower latency for you and specify one or the other directly.
IPV4 is solo4.ckpool.org
IPV6 is solo6.ckpool.org