We're looking into it right now, as a matter of fact. There's another report of it, and we're trying to figure out what could be going on. No clue on an estimated fix timeline, as we don't know the actual cause yet.. but hopefully 'soon'.
Thanks for your patience,
Alex