In addition to earnings not being reinvested, my entire balance (while not nearly as large as yours) has completely disappeared. Truly a shame that cloudhashing.com cannot be upfront about the details of their current operational status.

My balance has zero'd out now, with no explanation.

To my great dismay, cloudhashing.com has gone "off the air" with communications. The vaunted Reinvestment service they have is non-operative, and no explanation has been given publicly or privately to me regarding the RRP features of my existing contracts.  We are now 17 days into contracts that should have been enabled as of Dec 1, and I am not receiving the mining benefits per my contract. I urge new users to hold off on buying new contracts.

Aside from looking at a dashboard (mine, and I assume yours), how do you know that RRP has been discontinued? I don't doubt it, I'm just looking for more info, perhaps an announcement or newsletter.

Disgruntled, especially since I just re-upped with a new 500GHS contract on Dec 1.

Just now waking up to the cloudhashing problems.

Thoughts on why the hashing rate plummeted to 1.7 P?

cloudhashing.com seems quite wonky at the moment.

The Revinvestment features on my dashboard has disappeared.

My expected Reinvestment contract for Dec 1, 14, has not materialized.

Two messages to the Support tab have not been responded to.

Nice detail Aaron. I can sympathize with you. I first started noticing things were wonky when the Reinvestment contract did not come in on Dec 1st.

I too am trying to get some kind of response from as to what's going on.  But no answers after two Support messages sent.

cloudhashing.com seems to have gone a bit dark in that it has not put up a new reinvestment contract on my dashboard that it should have put up for Dec 1, for earnings reinvested prior.

I've sent two emails, using the web support tab, but no response from them yet.

Anyone else seen this problem?

Indeed, the web site not responding. Below is the WHOIS DNS registry data for the domain.  Of course, it's a private.

   Domain Name: TIMETOBIT.COM
   Registrar: ENOM, INC.
   Whois Server: whois.enom.com
   Referral URL: http://www.enom.com
   Name Server: NS1.TIMETOBIT.COM
   Name Server: NS2.TIMETOBIT.COM
   Status: ok
   Updated Date: 20-jun-2014
   Creation Date: 20-jun-2014
   Expiration Date: 20-jun-2015

Domain Name: TIMETOBIT.COM
Registry Domain ID: 1863693159_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: www.enom.com
Updated Date: 2014-06-20 15:05:55Z
Creation Date: 2014-06-20 22:05:00Z
Registrar Registration Expiration Date: 2015-06-20 22:05:00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Registrar Abuse Contact Email: abuse@enom.com
Registrar Abuse Contact Phone: +1.4252744500
Reseller: NAMECHEAP.COM
Domain Status: ok
Registry Registrant ID:
Registrant Name: WHOISGUARD PROTECTED
Registrant Organization: WHOISGUARD, INC.
Registrant Street: P.O. BOX 0823-03411
Registrant City: PANAMA
Registrant State/Province: PANAMA
Registrant Postal Code: 00000
Registrant Country: PA
Registrant Phone: +507.8365503
Registrant Phone Ext:
Registrant Fax: +51.17057182
Registrant Fax Ext:
Registrant Email: 5E4C19DA260C486B955F398E601C7807.PROTECT@WHOISGUARD.COM
Registry Admin ID:
Admin Name: WHOISGUARD PROTECTED
Admin Organization: WHOISGUARD, INC.
Admin Street: P.O. BOX 0823-03411
Admin City: PANAMA
Admin State/Province: PANAMA
Admin Postal Code: 00000
Admin Country: PA
Admin Phone: +507.8365503
Admin Phone Ext:
Admin Fax: +51.17057182
Admin Fax Ext:
Admin Email: 5E4C19DA260C486B955F398E601C7807.PROTECT@WHOISGUARD.COM
Registry Tech ID:
Tech Name: WHOISGUARD PROTECTED
Tech Organization: WHOISGUARD, INC.
Tech Street: P.O. BOX 0823-03411
Tech City: PANAMA
Tech State/Province: PANAMA
Tech Postal Code: 00000
Tech Country: PA
Tech Phone: +507.8365503
Tech Phone Ext:
Tech Fax: +51.17057182
Tech Fax Ext:
Tech Email: 5E4C19DA260C486B955F398E601C7807.PROTECT@WHOISGUARD.COM
Name Server: NS1.TIMETOBIT.COM
Name Server: NS2.TIMETOBIT.COM
DNSSEC: unSigned

Yep, looks down to me. I signed up based on an article in cryptocoinnews (http://www.cryptocoinsnews.com/).  Of course, the article seems to have been pulled by the site.