Appears to be the same issue as yesterday. It looked like it was fixed for a short while early this morning (or late last night), but I'm guessing WK had to go to work and will finish fixing things later.