The issue has been identified; we expect to have it corrected by the end of the day on Friday (1/12).
