BMG v Cox - when does an ISP lose its safe harbour protection?

On 1 February last, the Court of Appeals for the Fourth Circuit decided a case closely watched by both internet service providers (ISPs) and content owners. The ruling is a partial win for both sides, since the court affirmed in part, reversed in part and remanded the case for a new trial.

The case deals with two difficult and very interesting questions, the first being whether an ISP can be held liable for infringing activities of its subscribers, more precisely the up- and down-loading of copyright-protected musical works in the BitTorrent-Network. The second question was what mental state is required to establish the requisite intent for contributory copyright infringements: actual knowledge, wilful blindness or negligence?

Facts of the case

BMG Rights Management, which controls rights to a vast amount of popular works, had Rightscorp, Inc. monitor the internet for copyright infringements in the BitTorrent-Network. Rightscorp, Inc. - over the course of about three years - found subscribers of Cox to share BMG’s works almost two million times. For each instance, Rightscorp sent an infringement notice to Cox, which included a settlement offer along other data such as the IP address of the subscriber and the title of the copyright work.

Cox did not react to any of these notices. In fact, the ISP decided to “blacklist” Rightscorp, Inc. and ignore all of its notices entirely, apparently because Rightscorp declined to remove the ‘settlement language’ from its notices. Dissatisfied with this practice, BMG initiated a lawsuit against Cox, alleging that the ISP was vicariously and contributorily liable for acts of copyright infringement by its subscribers.

BMG asserted that Cox had failed to establish a policy entitling it to the safe harbour defence contained in the DMCA (17 U.S.C. § 512(a)). To qualify for that safe harbour, an ISP must have “adopted and reasonably implemented (…) a policy that provides for the termination in appropriate circumstances of subscribers (…) who are repeat infringers”.

Cat is in a safe harbour
The District Court agreed with BMG, stating that “Cox knew accounts were being used repeatedly for infringing activity yet failed to terminate” those accounts and that Cox did “not come forward with any evidence” to the contrary. It thus denied Cox the § 512(a) DMCA safe harbour defence. At the end of the jury trial, the District Court instructed the jury that, to prove contributory infringement, BMG had to show “direct infringement of BMG’s copyrighted works” by Cox subscribers, that “Cox knew or should have known of such infringing activity,” and that “Cox induced, caused, or materially contributed to such infringing activity”. The jury found Cox liable for wilful contributory infringement and awarded BMG USD 25 million in statutory damages.

The Fourth Circuit’s decision

The Court of Appeals first looked at Cox’s argument that it was entitled to the § 512(a) DMCA safe harbour defence. It was undisputed in the first instance that Cox did adopt some sort of repeat infringer policy. However, both the lower court and the Court of Appeals came to the conclusion that Cox did not ‘reasonably implement’ this policy to provide for the termination of repeat infringers in appropriate circumstances.

Indeed, Cox’s policy looks somewhat bizarre: it was a “thirteen-strike process” that never led to the real termination of subscribers. The Court of Appeals described the policy as follows:

“The first notice alleging a subscriber’s infringement produces no action from Cox. The second through seventh notices result in warning emails from Cox to the subscriber. After the eighth and ninth notices, Cox limits the subscriber’s Internet access to a single webpage that contains a warning, but the subscriber can reactivate complete service by clicking an acknowledgement. After the tenth and eleventh notices, Cox suspends services, requiring the subscriber to call a technician, who, after explaining the reason for suspension and advising removal of infringing content, reactivates service. After the twelfth notice, the subscriber is suspended and directed to a specialized technician, who, after another warning to cease infringing conduct, reactivates service. After the thirteenth notice, the subscriber is again suspended, and, for the first time, considered for termination. Cox never automatically terminates a subscriber.”

There were additional limitations to the effectiveness of Cox’s policy, e.g. every six months the subscriber’s thirteen-strike counter would be reset.

Understandably, the Court of Appeals was not impressed by this repeat infringer policy and found that Cox was “very clearly determined not to terminate subscribers who in fact repeatedly violated the policy”. To emphasize this result, Judge Motz cited an email from Cox that summarized Cox’s practice as “DMCA = reactivate”.

Cox asserted its policy was sufficient to grant it the safe harbor defence, irrespective of the above, asserting that none of its subscribers qualified as ‘repeat infringers’. The DMCA does not define the term ‘repeat infringers’, so Cox argued that only adjudicated repeat infringers would fall under the term.

The Court of Appeals disagreed. Looking at other provisions of the Copyright Act and the legislative history of the repeat infringer provision, it found that someone who actually infringes copyright more than once can be considered a repeat infringer. If only adjudicated repeat infringers fell under the provision, there would not be a “realistic threat of losing Internet access”, something the legislators had in mind when drafting the provision.

Summarizing the first part of its judgment, the Court of Appeals held that Cox was not entitled to the safe harbor defense, since the ISP “failed to implement its
[repeat infringer] policy in any consistent or meaningful way — leaving it essentially with no policy”.

Instruction of the Jury

Judge Motz then looked at the question whether the District Court had erred in instructing the cury as to contributory infringement. Cox argued that erroneous jury instructions entitled it to a new trial. The argument has two aspects: first, that an ISP could not be held liable for contributory copyright infringement because its technology was “capable of substantial noninfringing use”.  The second aspect is that negligence would not be sufficient to prove contributory infringement.

With regards to the first aspect, the court was quite clear and stated that this argument is meritless. Citing the Grokster case, Judge Motz states that substantial lawful use of a product does not exempt its producer from contributory infringement. Cox was more successful with its second argument, resulting in the Court reversing the lower court’s decision and remanding for a new trial.

Again citing Grokster, the Court stated that “[o]ne infringes contributorily by intentionally inducing or encouraging direct infringement”. The District Court had instructed the jury that the necessary intent could be presumed if Cox “knew or should have known of such infringing activity” a state that is also described as negligence.

Judge Motz found that negligence does not suffice to prove contributory infringement, rather demanding at least wilful blindness, which is recognized as equivalent to actual knowledge. Mere negligence - meaning the absence of knowledge of infringement - would be difficult to reconcile with the necessary intent to infringe. The court also looked at case law in patent law, especially Global-Tech, which held that wilful blindness satisfies the knowledge requirement, but recklessness or negligence do not.

As a result, the case will see a new trial in which, very likely, the jury will have to evaluate whether Cox knew of specific instances of infringement or was wilfully blind to such instances.

This Kat believes it is quite likely that the Jury will answer this question in the affirmative, due to the fact that Cox prevented itself from receiving any of the nearly two million notices that Rightscorp, Inc. sent on BMG’s behalf.
BMG v Cox - when does an ISP lose its safe harbour protection? BMG v Cox - when does an ISP lose its safe harbour protection? Reviewed by Mirko Brüß on Saturday, February 03, 2018 Rating: 5


  1. Was there any discussion of the "settlement language" in this case? We saw a major uptick in "speculative invoicing" in Canada after a notice requirement became part of our law. I wonder if this also seen in the 'States, and what the courts' views were.

  2. The court only briefly described the "settlement language", since it did not play a significant legal role in this case. Here is the part you are looking for:

    "Rightscorp also asks the ISP to forward the notice to the allegedly infringing subscriber, since only the ISP can match the IP address to the subscriber’s identity. For that purpose, the notice contains a settlement offer, allowing the alleged infringer to pay twenty or thirty dollars for a release from liability for the instance of infringement allegedin the notice. Cox has determined to refuse to forward or process notices that contain such settlement language. When Cox began receiving Rightscorp notices in the spring of 2011 (before Rightscorp had signed BMG as a client), Cox notified Rightscorp that it would process the notices only if Rightscorp removed the settlement language. Rightscorp did not do so."


All comments must be moderated by a member of the IPKat team before they appear on the blog. Comments will not be allowed if the contravene the IPKat policy that readers' comments should not be obscene or defamatory; they should not consist of ad hominem attacks on members of the blog team or other comment-posters and they should make a constructive contribution to the discussion of the post on which they purport to comment.

It is also the IPKat policy that comments should not be made completely anonymously, and users should use a consistent name or pseudonym (which should not itself be defamatory or obscene, or that of another real person), either in the "identity" field, or at the beginning of the comment. Current practice is to, however, allow a limited number of comments that contravene this policy, provided that the comment has a high degree of relevance and the comment chain does not become too difficult to follow.

Learn more here:

Powered by Blogger.