s=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Ping statistics for 167.88.15.87:
Packets: Sent = 45, Received = 45, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 27ms, Average = 26ms
hmmmm, looks good to me.
Status as of Monday, October 16, 2017
Forum rules
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.
While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
The Development forum is for discussion of development releases of Prohashing and for feedback on the site, requests for features, etc.
While we can't promise we will be able to implement every feature request, we will give them each due consideration and do our best with the resources and staffing we have available.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Re: Status as of Monday, October 16, 2017
Well, it would appear that the ICMP ping is working. Unfortunately, it's still having trouble with TCP, which means miners will still have trouble connecting.dog1965 wrote:s=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=27ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=25ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Reply from 167.88.15.87: bytes=32 time=26ms TTL=57
Ping statistics for 167.88.15.87:
Packets: Sent = 45, Received = 45, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 27ms, Average = 26ms
hmmmm, looks good to me.
- CryptoDamon
- Posts: 16
- Joined: Mon Aug 28, 2017 3:45 am
Re: Status as of Monday, October 16, 2017
Whats the opposite of Progress? Congress! We were hoping to make a go of getting more miners in, but if PH doesn't expand, so much for my plans.Steve Sokolowski wrote:
We haven't heard from the lawyer today, and we need to hear from him before we can proceed any further. Until then, we're going to close registrations again.
We want to hire people as much as you do, but there are lots of rumors of representatives and senators wanting to introduce regulations that might make the business unprofitable. Once we get more certainty, then we may decide to move forward.