I just spent a lot of time talking to the folks at both, and things look good; in brief, the problem involves a genuine bug, but was made much worse by lack of communication. It was not deliberate, just communication issues that are pretty human. Here's the short version of the story.
Authentium folks told me that it was their bug, and that they did have a tentative fix months ago, but that the message didn't make it reliably to their customers or us. A better fix is in the pipeline for August. (They've offered me a steak dinner, in appreciation, which I'll take unless my nutritionist finds out and scolds me.)
The whole thing was exacerbated by folks talking about 'net neutrality, mostly, an effort to preserve the level playing field that the 'net represents, which is just fairness. The message from some is that blocking sites is something that big telecoms might do and in all the confusion, that message turned into an incorrect message that an ISP actually did. To repeat, none of this was deliberate. However, it does illustrate a downside of journalism via blogs; stuff is published, then maybe fact-checked.
One good outcome of this is that we flushed out a swiftboater (in the generic sense), and this helps me understand the way disinformation gangs operate. Unfortunately, in some blogs, a good guy has been linked with the swiftboater, which isn't fair, and hopefully, we can do something about that.
Finally, I'm personally curious about the tech problem, but customer service trumps curiousity, and I'm part of a team dealing with a lot of spamvertisers and a few real-estate guys who need to aspire to more ethical behavior, and lots more.
I'm getting too old for this.