This was a database issue that was resolved yesterday. Please let us know if you still encounter the issue.