This was a glitch on our end. We have corrected the problem.
Sorry for the inconvenience and thanks for bringing that to our attention!
