AT&T: Just like Comcast only worse

It came out last month that Internet service provider Comcast was rate-limiting the bandwidth availability of its customers who were using BitTorrent. Now, it appears, AT&T’s SBC Yahoo! DSL is doing the same.

I am a AT&T customer (more by necessity than by choice), and after attempts to get the newest Fedora Linux ISO image via BitTorrent—completely legal and within the scope of that permitted by Fedora—were painful at best, I decided to download it directly from Fedora Project: placing the entire burden of the upload on one non-profit entity (Fedora) as opposed to a distributed system which would actually help bandwidth utilization for everyone.

What I noticed was that when the Torrent was open, even if it was slow, my entire connection was limited to less than half the level of service that I pay to use. Instead of the 6 Megabit service, I was getting somewhere between 2 and 3 Megabit download rates.

I tried an experiment: I capped the bandwidth on the torrent to 10 Kilobytes per second: an extremely slow speed, barely noticeable when you’re (supposedly) surfing at 6 Megabits per second. Despite that, my direct download from Fedora Project never reached more than 300 Kilobytes (2.4 Megabits) while it was running. When I paused the torrent, the direct download immediately jumped up to over 600 Kilobytes per second: nearly 5 megabits (and the practical throughput limit of the theoretical 6 megabit bandwidth).

There’s nothing neutral about this net. I do not agree with the decision to throttle any traffic, torrent or otherwise, but it would be slightly more understandable if ISPs only throttled the packets determined to contain illegal content. (How that determination would be made is unknown, but it’s slightly more agreeable in theory.)

To throttle all bandwidth, though, to less than half of what the customer has paid to use, for no reason at all—none, as I have said, because my intent was to download a torrent made available legally. Even if I had more questionable motives, however, my ISP has no way of knowing that, nor should they be scanning all the traffic flowing through their pipes.

In fact, when they do scan all the traffic they threaten their own safe harbor status provided under the Communications Decency Act—the only that says that ISPs and web hosting providers are not liable for the content placed there by their customers, which in practice keeps such ISPs and web hosting companies (and YouTube and MySpace and every other web site you know about) from losing their shirts due to copyright infringement, child pornography, hate speech, and other content that has been deemed to be unlawful.

So it’s yet one more double standard in the war of megacorporations versus the common people: SBC gets to steal my bandwidth that I’ve paid for back from me, but I don’t get to do anything about it. In fact, according to their new Terms of Service, they could even disconnect my service for criticizing them. But then, I’m observing, not criticizing.  ⌘ 

  1. 12 Responses to “AT&T: Just like Comcast only worse”

  2. By Ben on Nov 9, 2007 | Reply

    I noticed this yesterday. Not only are they capped, but if I try to download more than 3 torrents at a time, my service completely disconnects. As in, redlight flashing, no service at all.

  3. By Ben on Nov 9, 2007 | Reply

    PROOF

    http://www.youtube.com/watch?v=4PB_h9A5fsM

  4. By Billifer on Nov 10, 2007 | Reply

    Ben » Wow, Ben. I haven’t noticed anything like that. I was able to torrent 4 files simultaneously. One difference is that I’m using Xtorrent instead of Transmission. Still, completely killing the connection goes much further than Comcast (to my knowledge) ever did.

    It’s just not right. It’s like going to the grocery store and the grocery being happy to sell you all the groceries you want, but if you buy generic brands instead of name brands, you have to carry them to the car in Easter baskets, no more than 2 baskets at a time. Everything else, hell, they’re happy to carry it out for you. Second class packets.

  5. By jrmy on Nov 20, 2007 | Reply

    I have been banging my head for two weeks trying to figure out why my torrents were suddenly capping at 10k/sec. This sucks, flat out. Also, if I have more then one or two active torrents then the others are completely dead. {fume}

  6. By Billifer on Nov 21, 2007 | Reply

    jrmy » And now you know. Even with what I’ve observed, 10k/sec is extremely low. I’ve personally seen the cap raise considerably in the last couple of days. I don’t know whether that’s because of AT&T policy changes or because of my own network settings tweaks.

    If you’re on a Mac, Linux, or other *BSD-based system, and you’re comfortable with advanced system tuning, you can set net.inet.tcp.icmp_may_rst to 0 and net.inet.icmp.icmplim to a very low value (mine is at 10; default is 250—don’t set it to 0, though). That might help but not eliminate the problem.

  7. By brian on Nov 26, 2007 | Reply

    i’ve noticed the same problem. seeding at even 10 kb per second causes me to disconnect completely about 2-3 times an hour at least. this is compounded by the utterly moronic behavior of ATT/SBC hardware portals. My 2wire redirects me to an error page and then forces me to restart the browser whenever it disconnects. (apparently the morons can’t simply redirect me to google.com when it’s fixed).

  8. By Billifer on Nov 26, 2007 | Reply

    brian » you bring up a good point… I wonder whether the disconnect that you and Ben are seeing is because of a 2wire issue (maybe a special little bug feature that AT&T knows about and uses) that causes the connection to drop. I’m not using a 2wire modem/router, but instead a Siemens modem and an Apple AirPort router. I haven’t seen the disconnect, but I have seen the crawl, obviously, since I wrote this post.

  9. By Anonymous on Jan 24, 2008 | Reply

    I HATE THEM.

  10. By Billifer on Jan 25, 2008 | Reply

    @Anonymous » ROFLMPO

  11. By Zeph on Apr 21, 2008 | Reply

    I had a problem that after ~100hrs of downloads my connection would go to shit until reinstalling the OS. Now I have the problem that when I start downloading torrents the same thing happens after an hour. Fuck AT&T & comcast! I’m switching to Cavalier after finals are over (they’re joined with google so i have at least something to reference my trust).

  12. By Billifer on Apr 21, 2008 | Reply

    @Zeph: That sounds rather bizarre about the ~100hrs of downloads. Could it possibly be a browser cache issue? As for the torrents… I’ve seen some improvement since I wrote that post, but nothing at all like a return to full bandwidth.

  1. 1 Trackback(s)

  2. Nov 9, 2007: Linux Code and More » Blog Archive » AT&T: Just like Comcast only worse

Post a Comment

Or enter the following information to leave a comment

You may use HTML or Markdown in your comments, although the live preview below will not display Markdown accurately. A Markdown Syntax Reference is available.