Might have been a transient error as we were deploying some auth provider fixes. Should be good to go now! :) - Billy