Yeah, noticed the same. But it should still work. Database seems to be under heavy load today. We shouldn't show these error messages though.