We have identified the root cause of the issue and working on a fix that we will likely deploy tonight.

Currently we are experiencing high load on the database and we are investigating.