This was an issue for a day or two erlier this week. Cisco appears to have fixed something on the back end and people who were seeing the same issue earlier are no longer having the issue.
If it is persisting for you, please open a TAC case for further investigation.
