This issue has now been resolved.

We are investigating and working to resolve. We'll post more information soon.