We've received an e-mail containing the same message. It seems like a problem happened in Apple's side. We hope it will be resolved in a short time.