Understanding reason for fork

[wackou]

Thanks, I guess I'll settle for the network propagation explanation for now... I guess it's time for me to get started on implementing / organizing a backbone structure as I described here:

http://digitalgaia.io/backbone.html

[bytemaster]

It could just be a network propagation issue between you and the next delegate.    I would check a pattern for the delegate after you.  If there is no pattern then it was a fluke.

[wackou]

I just saw that the last fork in the blockchain was caused by my delegate (sorry ), but I really am at a loss as to why... My delegate has been running since 0.4.24 uninterrupted and did not miss a single beat, I am properly synchronized to ntp, have a healthy number of connections, etc.

I did look at some delegates that recently missed isolated blocks, and tried to look at the next and previous producing delegate to try to see a pattern (eg: a delegate not properly synchronized to ntp might produce its block early and ignore the one from the delegate just before him), but couldn't find any...

Any help understanding what happened?

Actually, is there a (general) method to do post-mortem analysis of why a block was missed, or a fork created? Best practices, etc?

Thanks for any tip/suggestion too.