v0.4.17-RC1 fixed the issue for me.

"probably fixed"
https://github.com/BitShares/bitshares_toolkit/issues/809

Quote from: bitder on September 23, 2014, 01:51:56 AM

Quote from: emski on September 23, 2014, 01:45:29 AM
I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

There's definitely something wrong with the networking code with 0.4.16
I left my non-delegate client (CLI) running after upgrading to 0.4.16 and it has stopped syncing multiple times now.
It requires one or more restarts of the client for it to sync again.

I have the same problem with v0.4.17-RC1 !!!

My delegate also mysteriously missed a couple chunks of blocks while I was sleeping last night.  The connection was fine and it started producing on main chain again on it's own so I'm not sure what the problem was exactly.

Quote from: bitder on September 23, 2014, 01:51:56 AM

Quote from: emski on September 23, 2014, 01:45:29 AM
I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

There's definitely something wrong with the networking code with 0.4.16
I left my non-delegate client (CLI) running after upgrading to 0.4.16 and it has stopped syncing multiple times now.
It requires one or more restarts of the client for it to sync again.

Hey bitder, sign up to www.beyondbitcoinx.net to say what your delegate policies are.

Quote from: emski on September 23, 2014, 01:45:29 AM
I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

There's definitely something wrong with the networking code with 0.4.16
I left my non-delegate client (CLI) running after upgrading to 0.4.16 and it has stopped syncing multiple times now.
It requires one or more restarts of the client for it to sync again.

I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

I am experiencing that as well. It seems that the client goes through periods of being a few minutes behind. If one of these lags happens during your slot you miss those blocks.

Check out this thread: https://bitsharestalk.org/index.php?topic=9195.msg118971#msg118971

Both my delegates www.minebitshares-com and www2.minebitshares-com have missed blocks yesterday/today without explanation for the first time.

They both run on Amazon AWS instances (Ireland and Sydney) and nothing has changed apart from upgrading to 0.4.16   :'(

I know delegate.liondani has also had similar issues.

Anyone else experience missing blocks for the first time, or have any troubleshooting tips?