Insurer Refuses To Cover Cox In Massive Piracy Lawsuit (torrentfreak.com)

An anonymous reader writes with news that Cox Communications' insurer, Lloyds Of London underwriter Beazley, is refusing to cover legal costs and any liabilities from the case brought against it by BMG and Round Hill Music. TorrentFreak reports: "Trouble continues for one of the largest Internet providers in the United States, with a Lloyds underwriter now suing Cox Communications over an insurance dispute. The insurer is refusing to cover legal fees and potential piracy damages in Cox's case against BMG Rights Management and Round Hill Music. Following a ruling from a Virginia federal court that Cox is not protected by the safe-harbor provisions of the DMCA, the Internet provider must now deal with another setback. Following a ruling from a Virginia federal court that Cox is not protected by the safe-harbor provisions of the DMCA, the Internet provider must now deal with another setback."

Comments

Re:Uh? How does the DMCA apply to an ISP?

[unrtst]

The assertion (by BMG/RHM) is that Cox has not fulfilled the requirements for safe harbor, which include terminating the accounts of repeat offenders.

Alledged repeat offenders.

How many times a year do we read about big media companies using automated systems that fire off buttloads of false DMCA takedowns?
BMG are not (and should never be) judge,jury and executioner.

FWIW, the previous story made it clear that Cox has called them out on exactly that grounds, as well as a bunch of other claims/country-claims.
One of their main claims is that BMG had spammed them with way too many notices that had lacked proper evidence and such. Cox had notified BMG of that a bunch of times and tried to work with them, and they would not stop sending the automated and often unjustified notices, so Cox stopped listening to any of their reports.

IMO, that's the real story, and makes both sides make more sense. This has almost nothing to do with the end user. Neither Cox nor BMG want to take the time to do the proper paperwork and research to determine if these red flags are detecting actual cases of infringement. BMG is automatically spamming all possible claims; Cox is automatically sending them all to /dev/null; Neither of those are very helpful.

This will likely be settled out of court with some agreement that either BMG will do a little more work, or they'll pay Cox to do it, and then Cox will accept the vast majority of the claims. I'd almost be willing to wager money on that one, if I cared enough to follow this further.

Previous slashdot story: http://yro.slashdot.org/story/...
Cox's response: http://ia801407.us.archive.org...

Their response is actually kinda fun to read.

Looks bad for Cox

[michaelmalak]

FTFA:

In addition Beazley point out that the piracy lawsuit was filed November last year, several days before the December 1, 2014 date the insurance policy began.

Headline misses a key detail.

[Frobnicator]

The Slashdot headline missed a key detail covered in the article:

Beazley point out that the piracy lawsuit was filed November last year, several days before the December 1, 2014 date the insurance policy began.

It is a bit difficult to file an insurance claim against lawsuit costs when the lawsuit was instigated before the insurance took effect.

Since we love automobile analogies so much: It is like buying car insurance in December to insure against a crash that took place the month before. That's not going to help much.

Or buying a life insurance policy for your recently-deceased relative.

The date insurance coverage began is going to be a far bigger problem than details of what the policy covers.