We've pinpointed the cause of this issue and we're working on fixing it right now. Will report back with either an ETA or "Its fixed" (hopefully the latter).