Thanks for the bug report! This seems to have happened due to an outage in our database service. I will investigate this.