Does not mark H / s.

It's same with ETN dashboard, user hr is zero! What happened?!?

same with XVG, hr is 0,0

https://coinfoundry.org/pool/xvg2

AND

Pool Wallet... does not exist, can we know what is happening?

https://verge-blockchain.info/address/DFrNGpjQr1MmJoYtimCayWBTt9ubbuEknp

Hmmmm.... Looks like Coinfoundry is doing hashrate skimming!!! I'll notify the community on Bitcointalk.

No, we don't. I'm sorry that I'm working my ass of for improving the user experience for our miners. Before making wild accusations you might read my last post here: https://feedback.coinfoundry.org/communities/1/topics/677-clarification-on-shares-not-updating

Maybe the API is not working? 

Does your dashboard at least list your workers? 

Dashboard was working fine when I started 11 hours ago.

Now, my Dashboard shows 0 Hash, 0 workers, and my shares are not going up anymore.

Dashboard hasn't updated for the last 2 hours.

My miners are all still hashing and shares are being accepted.

XVG lyra pool

Same here,mate.

Same problem on Monero pool.

Please read my last post here: https://feedback.coinfoundry.org/communities/1/topics/677-clarification-on-shares-not-updating

Sorry for the inconvenience.

Alright, I understand that shares were not updated for awhile, being a UI problem, but they are vanishing is this time? I ask this because the shares submitted during "blackout" does not increased the counter.

I was wondering this too.   Once my shares started updating again...  they continued rising from the point where they were previously, they didn't increase by a large amount.   My share number was frozen for a long period of time where my miners were still going, the share number should have increased by a large amount when the UI started updating again.

So you're pretty sure that some of your shares went missing during the update blackout?

Shares were stuck at 429.03 K.     When Shares started updating again, shares started counting upward from that same point.   Shares number did not spike first.

Thanks. I'll try to figure out how that happened.

Somehow the "missed" shares are back in the counter... Thank you!

However, if there is a problem at the database access level I might help with that....