It's a new year, but most of us are still stuck with the same old DSL and cable monopolies. Though many communities have built their own networks to create competition and numerous other benefits, nearly half of the 50 states have enacted legislation to make it harder for communities to build their own networks. Fortunately, this practice has increasingly come under scrutiny. Unfortunately, we expect to see massive cable and telephone corporations use their unrivaled lobbying power to pass more laws in 2012 like the North Carolina law pushed by Time Warner Cable to essentially stop new community broadband networks. The FCC's National Broadband Plan calls for all local governments to be free of state barriers (created by big cable and phone companies trying to limit competition). Recommendation 8.19: Congress should make clear that Tribal, state, regional and local governments can build broadband networks. But modern day railroad barons like Time Warner Cable, AT&T, etc., have a stranglehold on a Congress that depends on their campaign contributions and a national capital built on the lobbying largesse of dominant industries that want to throttle any threats to their businesses. (Hat tip to the Rootstrikers that are trying to fix that mess.) We occasionally put together a list of notable achievements of these few companies that dominate access to the Internet across the United States. The last one is available here. As you read this, remember that the FCC's National Broadband Plan largely places the future of Internet access in the hands of these corporations.

The net is buzzing about Comcast's data caps after a Seattle resident ran afoul of them. I found it particularly interesting given Seattle's recent decision to use its assets to further Comcast's monopoly following a poorly considered RFP. This story highlights many of the frustrations and injustices that come with companies as massive as Comcast effectively monopolizing an essential utility, with practically no oversight locally or federally. When Comcast enacted is 250GB monthly transfer cap years ago, many thought it was sufficiently high that few would run afoul of it. But the smart folks noted that if it did not increase as natural usage increases, it would hurt legitimate users (as opposed to those who run servers constantly trafficking in file sharing that violates copyright).

I made very clear to the gentleman I spoke with that I thought Comcast’s data cap policy was arbitrary, unfair, and extremely irritating… and that if I had any decent competitive options in the neighborhood I’d dump Comcast in a heartbeat. Since I don’t, I listened to him read his canned warning that if I exceeded their cap again I’d be cut off again.

Bear in mind that when you fill up the fuel tank in your car, you are at a gas station that is regularly inspected by the state to ensure it is correctly measuring the volume of gas dispensed. Comcast is not similarly regulated and we have to take Comcast's word on how much traffic we use. Most of the time I have visited Comcast's meter to see what my household usage is, I have been unable to even access it. But back to the story, our Seattle friend later found that he had unintentionally violated the cap again, despite taking precautions not to:

The Customer Security agent was polite, and after the standard identification questions notified me I was cut off for a year due to exceeding Comcast’s Acceptable Use Policy limits on their bandwidth cap. I asked for details on what had been using bandwidth, and again, Comcast would not share. In a sudden brainstorm, I then asked whether the 250 GB bandwidth cap applied to just downloads (which I had assumed, as the majority of most bandwidth used in households is downstream bandwidth), or download and upload bandwidth. Surprise, surprise!

The net is buzzing about Comcast's data caps after a Seattle resident ran afoul of them. I found it particularly interesting given Seattle's recent decision to use its assets to further Comcast's monopoly following a poorly considered RFP. This story highlights many of the frustrations and injustices that come with companies as massive as Comcast effectively monopolizing an essential utility, with practically no oversight locally or federally. When Comcast enacted is 250GB monthly transfer cap years ago, many thought it was sufficiently high that few would run afoul of it. But the smart folks noted that if it did not increase as natural usage increases, it would hurt legitimate users (as opposed to those who run servers constantly trafficking in file sharing that violates copyright).

I made very clear to the gentleman I spoke with that I thought Comcast’s data cap policy was arbitrary, unfair, and extremely irritating… and that if I had any decent competitive options in the neighborhood I’d dump Comcast in a heartbeat. Since I don’t, I listened to him read his canned warning that if I exceeded their cap again I’d be cut off again.

Bear in mind that when you fill up the fuel tank in your car, you are at a gas station that is regularly inspected by the state to ensure it is correctly measuring the volume of gas dispensed. Comcast is not similarly regulated and we have to take Comcast's word on how much traffic we use. Most of the time I have visited Comcast's meter to see what my household usage is, I have been unable to even access it. But back to the story, our Seattle friend later found that he had unintentionally violated the cap again, despite taking precautions not to:

The Customer Security agent was polite, and after the standard identification questions notified me I was cut off for a year due to exceeding Comcast’s Acceptable Use Policy limits on their bandwidth cap. I asked for details on what had been using bandwidth, and again, Comcast would not share. In a sudden brainstorm, I then asked whether the 250 GB bandwidth cap applied to just downloads (which I had assumed, as the majority of most bandwidth used in households is downstream bandwidth), or download and upload bandwidth. Surprise, surprise!

The net is buzzing about Comcast's data caps after a Seattle resident ran afoul of them. I found it particularly interesting given Seattle's recent decision to use its assets to further Comcast's monopoly following a poorly considered RFP. This story highlights many of the frustrations and injustices that come with companies as massive as Comcast effectively monopolizing an essential utility, with practically no oversight locally or federally. When Comcast enacted is 250GB monthly transfer cap years ago, many thought it was sufficiently high that few would run afoul of it. But the smart folks noted that if it did not increase as natural usage increases, it would hurt legitimate users (as opposed to those who run servers constantly trafficking in file sharing that violates copyright).

I made very clear to the gentleman I spoke with that I thought Comcast’s data cap policy was arbitrary, unfair, and extremely irritating… and that if I had any decent competitive options in the neighborhood I’d dump Comcast in a heartbeat. Since I don’t, I listened to him read his canned warning that if I exceeded their cap again I’d be cut off again.

Bear in mind that when you fill up the fuel tank in your car, you are at a gas station that is regularly inspected by the state to ensure it is correctly measuring the volume of gas dispensed. Comcast is not similarly regulated and we have to take Comcast's word on how much traffic we use. Most of the time I have visited Comcast's meter to see what my household usage is, I have been unable to even access it. But back to the story, our Seattle friend later found that he had unintentionally violated the cap again, despite taking precautions not to:

The Customer Security agent was polite, and after the standard identification questions notified me I was cut off for a year due to exceeding Comcast’s Acceptable Use Policy limits on their bandwidth cap. I asked for details on what had been using bandwidth, and again, Comcast would not share. In a sudden brainstorm, I then asked whether the 250 GB bandwidth cap applied to just downloads (which I had assumed, as the majority of most bandwidth used in households is downstream bandwidth), or download and upload bandwidth. Surprise, surprise!

The net is buzzing about Comcast's data caps after a Seattle resident ran afoul of them. I found it particularly interesting given Seattle's recent decision to use its assets to further Comcast's monopoly following a poorly considered RFP. This story highlights many of the frustrations and injustices that come with companies as massive as Comcast effectively monopolizing an essential utility, with practically no oversight locally or federally. When Comcast enacted is 250GB monthly transfer cap years ago, many thought it was sufficiently high that few would run afoul of it. But the smart folks noted that if it did not increase as natural usage increases, it would hurt legitimate users (as opposed to those who run servers constantly trafficking in file sharing that violates copyright).

I made very clear to the gentleman I spoke with that I thought Comcast’s data cap policy was arbitrary, unfair, and extremely irritating… and that if I had any decent competitive options in the neighborhood I’d dump Comcast in a heartbeat. Since I don’t, I listened to him read his canned warning that if I exceeded their cap again I’d be cut off again.

Bear in mind that when you fill up the fuel tank in your car, you are at a gas station that is regularly inspected by the state to ensure it is correctly measuring the volume of gas dispensed. Comcast is not similarly regulated and we have to take Comcast's word on how much traffic we use. Most of the time I have visited Comcast's meter to see what my household usage is, I have been unable to even access it. But back to the story, our Seattle friend later found that he had unintentionally violated the cap again, despite taking precautions not to:

The Customer Security agent was polite, and after the standard identification questions notified me I was cut off for a year due to exceeding Comcast’s Acceptable Use Policy limits on their bandwidth cap. I asked for details on what had been using bandwidth, and again, Comcast would not share. In a sudden brainstorm, I then asked whether the 250 GB bandwidth cap applied to just downloads (which I had assumed, as the majority of most bandwidth used in households is downstream bandwidth), or download and upload bandwidth. Surprise, surprise!

The net is buzzing about Comcast's data caps after a Seattle resident ran afoul of them. I found it particularly interesting given Seattle's recent decision to use its assets to further Comcast's monopoly following a poorly considered RFP. This story highlights many of the frustrations and injustices that come with companies as massive as Comcast effectively monopolizing an essential utility, with practically no oversight locally or federally. When Comcast enacted is 250GB monthly transfer cap years ago, many thought it was sufficiently high that few would run afoul of it. But the smart folks noted that if it did not increase as natural usage increases, it would hurt legitimate users (as opposed to those who run servers constantly trafficking in file sharing that violates copyright).

I made very clear to the gentleman I spoke with that I thought Comcast’s data cap policy was arbitrary, unfair, and extremely irritating… and that if I had any decent competitive options in the neighborhood I’d dump Comcast in a heartbeat. Since I don’t, I listened to him read his canned warning that if I exceeded their cap again I’d be cut off again.

Bear in mind that when you fill up the fuel tank in your car, you are at a gas station that is regularly inspected by the state to ensure it is correctly measuring the volume of gas dispensed. Comcast is not similarly regulated and we have to take Comcast's word on how much traffic we use. Most of the time I have visited Comcast's meter to see what my household usage is, I have been unable to even access it. But back to the story, our Seattle friend later found that he had unintentionally violated the cap again, despite taking precautions not to:

The Customer Security agent was polite, and after the standard identification questions notified me I was cut off for a year due to exceeding Comcast’s Acceptable Use Policy limits on their bandwidth cap. I asked for details on what had been using bandwidth, and again, Comcast would not share. In a sudden brainstorm, I then asked whether the 250 GB bandwidth cap applied to just downloads (which I had assumed, as the majority of most bandwidth used in households is downstream bandwidth), or download and upload bandwidth. Surprise, surprise!

The net is buzzing about Comcast's data caps after a Seattle resident ran afoul of them. I found it particularly interesting given Seattle's recent decision to use its assets to further Comcast's monopoly following a poorly considered RFP. This story highlights many of the frustrations and injustices that come with companies as massive as Comcast effectively monopolizing an essential utility, with practically no oversight locally or federally. When Comcast enacted is 250GB monthly transfer cap years ago, many thought it was sufficiently high that few would run afoul of it. But the smart folks noted that if it did not increase as natural usage increases, it would hurt legitimate users (as opposed to those who run servers constantly trafficking in file sharing that violates copyright).

I made very clear to the gentleman I spoke with that I thought Comcast’s data cap policy was arbitrary, unfair, and extremely irritating… and that if I had any decent competitive options in the neighborhood I’d dump Comcast in a heartbeat. Since I don’t, I listened to him read his canned warning that if I exceeded their cap again I’d be cut off again.

Bear in mind that when you fill up the fuel tank in your car, you are at a gas station that is regularly inspected by the state to ensure it is correctly measuring the volume of gas dispensed. Comcast is not similarly regulated and we have to take Comcast's word on how much traffic we use. Most of the time I have visited Comcast's meter to see what my household usage is, I have been unable to even access it. But back to the story, our Seattle friend later found that he had unintentionally violated the cap again, despite taking precautions not to:

The Customer Security agent was polite, and after the standard identification questions notified me I was cut off for a year due to exceeding Comcast’s Acceptable Use Policy limits on their bandwidth cap. I asked for details on what had been using bandwidth, and again, Comcast would not share. In a sudden brainstorm, I then asked whether the 250 GB bandwidth cap applied to just downloads (which I had assumed, as the majority of most bandwidth used in households is downstream bandwidth), or download and upload bandwidth. Surprise, surprise!

Lafayette's LUS Fiber network, after recently kicking off its ad campaign, has decided to offer 100Mbps residential connections after a number of requests from subscribers. The network previously offered a 100Mbps business service for $200 -- it seems they are now just allowing anyone to subscribe at that level and price. As John notes at Lafayette Pro Fiber blog, this is the only tier for which residential plans come with the same price as business plans.

The other residential tiers are cheaper than their corresponding business tiers by 45-48%. Nor, according to Huval's remarks in the comments is the monthly usage cap any different—in both the residential and the commercial versions of the 100 meg package is capped at 8 terabits. (Note: that'd be about 1 terabyte of hard disk storage.) The idea behind the higher prices for businesses is that they use much more bandwidth than households—and LUS pays for its connectivity by capacity.

This brings up something I don't think I previously noted in discussions about LUS Fiber - it comes with a monthly transfer cap. I cut the cap chart out of their user agreement [pdf] above. Remember, 8 bits to the byte. Thanks to DSL Reports for the link to the user agreement. This raises an interesting discussion. Private cable companies typically enforce caps because their network cannot physically support many users using a lot of bandwidth simultaneously. When hundreds of users share a single connection (as with cable), a few major users can seriously impact the experiences of others. In a FTTH network like Lafayette's, there is no real danger of one user's activities affecting another's. However, there is a danger of racking up a high bandwidth charge for LUS Fiber if many users are constantly using a lot of bandwidth.

Lafayette's LUS Fiber network, after recently kicking off its ad campaign, has decided to offer 100Mbps residential connections after a number of requests from subscribers. The network previously offered a 100Mbps business service for $200 -- it seems they are now just allowing anyone to subscribe at that level and price. As John notes at Lafayette Pro Fiber blog, this is the only tier for which residential plans come with the same price as business plans.

The other residential tiers are cheaper than their corresponding business tiers by 45-48%. Nor, according to Huval's remarks in the comments is the monthly usage cap any different—in both the residential and the commercial versions of the 100 meg package is capped at 8 terabits. (Note: that'd be about 1 terabyte of hard disk storage.) The idea behind the higher prices for businesses is that they use much more bandwidth than households—and LUS pays for its connectivity by capacity.

This brings up something I don't think I previously noted in discussions about LUS Fiber - it comes with a monthly transfer cap. I cut the cap chart out of their user agreement [pdf] above. Remember, 8 bits to the byte. Thanks to DSL Reports for the link to the user agreement. This raises an interesting discussion. Private cable companies typically enforce caps because their network cannot physically support many users using a lot of bandwidth simultaneously. When hundreds of users share a single connection (as with cable), a few major users can seriously impact the experiences of others. In a FTTH network like Lafayette's, there is no real danger of one user's activities affecting another's. However, there is a danger of racking up a high bandwidth charge for LUS Fiber if many users are constantly using a lot of bandwidth.

Lafayette's LUS Fiber network, after recently kicking off its ad campaign, has decided to offer 100Mbps residential connections after a number of requests from subscribers. The network previously offered a 100Mbps business service for $200 -- it seems they are now just allowing anyone to subscribe at that level and price. As John notes at Lafayette Pro Fiber blog, this is the only tier for which residential plans come with the same price as business plans.

The other residential tiers are cheaper than their corresponding business tiers by 45-48%. Nor, according to Huval's remarks in the comments is the monthly usage cap any different—in both the residential and the commercial versions of the 100 meg package is capped at 8 terabits. (Note: that'd be about 1 terabyte of hard disk storage.) The idea behind the higher prices for businesses is that they use much more bandwidth than households—and LUS pays for its connectivity by capacity.

This brings up something I don't think I previously noted in discussions about LUS Fiber - it comes with a monthly transfer cap. I cut the cap chart out of their user agreement [pdf] above. Remember, 8 bits to the byte. Thanks to DSL Reports for the link to the user agreement. This raises an interesting discussion. Private cable companies typically enforce caps because their network cannot physically support many users using a lot of bandwidth simultaneously. When hundreds of users share a single connection (as with cable), a few major users can seriously impact the experiences of others. In a FTTH network like Lafayette's, there is no real danger of one user's activities affecting another's. However, there is a danger of racking up a high bandwidth charge for LUS Fiber if many users are constantly using a lot of bandwidth.