Today I had the same problem again, but it took less a minute until its gone. Local time for the server was approx. 2am. At that time the server load should be low. Thus, I believe, that it is a synchronization problem between multiple databases and the secondary database catches up more quick with low load.
I don't know the architecture of the system, but the effect is quite clear.