The blog was down for a bit and falling through to the generic Stack Exchange network handler, which is what you saw. It should be working now.