Amazing! great work CK and great work to the community showing Con the support.
CK could you ping MRR to see what the ping is like from there I'm more of a MRR fan than Nicehash would be interesting to know where there ping to the server.
Mine on everyone! Good Luck!
Sure thing. Looks like I picked a VERY popular datacentre lol.
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
Both are insanely fast, and seem to be in the same datacentre again! So just use the solo.ckpool.org address and let the routing choose automatically what to use if it supports IPV6 (most default to 6 and drop to 4 if they can't route through IPV6).