Was not able to reproduce. But forwarded to the engineering so that they can take a look at the server logs and see what the cause of the problem might have been. Expect to get an answer in the next 12 hours.
Update: We are aware of this problem. It is caused by a database connection lead. The engineering team is tracking it down. So there might be a few more hick ups in the next 6-24 hours. We will update this thread when the issue is resolved. Sorry for the inconvenience.