I was hoping that the maintenance today might have resolved this, but the issue persists.