Looks like this particular problem has been resurrected. Engineers are once again fixing this error. Anyone else having this experience this morning?
