Yeah, the error that's being linked to seems to have returned. I've experienced it back in November, around the same time BrowserUK posted about it, then it was fine, until it started happening again earlier this week. Encountered it half a dozen times or so this week, at different times.