Same issue here. I sent them a message on Twitter too -- will report back here if I get any additional information on when they are fixing this.
