Other than invalid complaints (did not meet the requirements for a complaint, was not a copyright complaint, etc) we have never had an abusive DMCA notice -- 100% of our notices (and we usually get a couple per day) have been valid.
We don't have the issue with our host being able to unplug us that easily (we manage our own network) but we do have the issue of liability, which the DMCA solves for providers like us.
Also -- I'd definitely be interested in the cases you're referring to, where false DMCA claims have resulted in major damages.
- We already have the expertise to do so, so the cost to us is much smaller
- We can ensure a much higher level of service by making sure every component along the line is up to par (you'd cry if you heard what some colo providers do)
- We can fix problems in-line with our priorities, since we're the ones that fix them (like keeping published sites up, even if the editor is down, for example)
- We can set up and manage geographically redundant datacenters
- And finally, we're able to do so extremely cheaply
It's definitely something to consider when you reach a certain scale, and especially if you have the know-how to get it done. We've calculated that for every server we purchase, we'd pay that cost every 2-3 months on AWS, for perspective.
and, worst of all, you're at their whim -- if they decide, for whatever reason, to unplug you, that's it. we prefer to eliminate anyone who has the ability to take our service down :)
Believe it or not, we've had botnet attacks that took down $100k Cisco routers. Nasty :(
I'd love to hear more, if you're at liberty to share.
This law makes any noncompliant service a "publisher", liable for all content on the site - unless you follow the DMCA. Upon receiving a takedown notice, the service provider must take down content immediately, and issue a notice to the supposed actual content owner. Content owner has a short period in which he can file a counter claim and keep the content up for a little bit while the two sides argue.
Service provider becomes a publisher, liable for your potentially illegal content (trademark/copyright infringement, slander, libel, child pornography, etc) if they do not comply.
Rackspace is not the problem - the 105th Congress was the problem.
If we get normal trademark disputes they are usually easy to deal with: we simply put the two parties into direct contact and they can figure it out. However, if the requester uses the DMCA method everything changes: We get an ultimatum from our hosting company (Rackspace) to resolve the conflict within 7 days or they will unplug our servers, which would disconnect many thousands of e-commerce stores and millions of sales. Obviously we cannot allow this to happen. Rackspace does this because they need to stay a "safe harbor" under the DMCA and this is how they pass the buck to us.
Luckily there have been precedents where false DMCA claims have lead to hundreds of thousands of dollar in damages to the plaintiffs. Our only recurse is to point this out to the originator of the claim before forwarding it to the affected store. In most cases this leads to them dropping the complaint and/or pursuing the (correct) copyright/trademark avenue instead.