Yes, we encountered this issue some time ago (see my comment above).
The problem was actually residing outsied, we are using a Virtual hosted environment, which is being maintained at 4am each day.
And as we figured out - this error was always occuring exactly at that time each day.
What exactly happens on this virtual server - we are still investigating - but for sure this issue is caused from outside.