Thanks for reporting this. This looks like an issue with our backend; looking into it now.