yes, seems like there was a bit of forking recently, got 4 missed blocks last night (got alerts), only to wake up with my delegate with no missed block since at least a couple of days, so somehow it got back on the correct branch (with the blocks properly produced ??? how is that even possible?...). I imagine bitmeat is still stuck on its fork...

http://blockchain.bitsuperlab.com/delegate.html

I am using this link to see the delegates performance. Everything is fine.

All good here:




ID    NAME (* next in line)           APPROVAL       PRODUCED MISSED   RELIABILITY   PAY RATE PAY BALANCE         LAST BLOCK
============================================================================================================================
6939  riverhead-del-server-1          10.1698471980 %2597     20       99.24 %       5 %      44.52271 BTSX       276606


Quote from: puppies on August 21, 2014, 12:40:43 AM
I'm pretty sure x.bitmeat.com is on a fork.

It has the correct number of blocks I missed because the client stopped connecting and would not sync. I missed 15 in a row while I was at work. But I've been back on producing for the past couple hours.

I'm pretty sure x.bitmeat.com is on a fork.

I wonder what is going on..

http://x.bitmeat.com/

My delegate node missed a few, but is working again.