Thanks for reporting. We're aware of the issue and are currently looking into it. Will hopefully work again later this week...