mapping

Content tagged with "mapping"

Related Topics
Displaying 1381 - 1390 of 1449

Yet Another Homeowner Led Astray By Giant ISP; Responds with Muni Fiber Initiative

Last month, we highlighted the story of Seth, a Washington state homeowner forced to put his home up for sale due to a perfect storm of sloppy customer service, corporate bureaucracy, and terrible Internet policy. Now meet Dave Mortimer from Michigan.

Dave is another person in a similar situation, reports Ars Technica. In 2013 incumbent AT&T told Dave three separate times that the house he had his eye on in rural Lowell had U-verse fiber network capabilities. Their website verified what customer service represenatives told him. Dave is an IT professional and wanted the opportunity to work from home. He must be on call while not in the office and so requires a fast residential Internet connection. 

After buying the home and moving in, AT&T backpedaled. Actually his best option was DSL offering 768 Kbps. Oops!

Working from home was a struggle. After Dave complained to AT&T, the FCC, the FTC, and the state Public Service Commission, the provider eventually updated their website but that didn't help Dave. He limped along but seldom worked from home as he had planned to do from the start. His office is 30 minutes away.

Finally, AT&T billed him for a phone line he never requested leading to an auto-payment error and a shut-off of his Internet service. That was enough for Dave. He approached a local wireless provider Vergenness Broadband and, working with the installer, attached the receiver to a tree some distance from his house and buried the extra long cable in cracks in his driveway to his house. Dave now pays $60 per month and gets the 3 Mbps download / 1 Mbps upload he was promised.

Dave is no where near the 45 Mbps he had hoped to obtain from the phantom U-verse, but he has this to say about his local provider:

“This is a night and day difference since switching from AT&T," he said. "Everything that AT&T did wrong, this small local company is doing right.”

Dave was fortunate to have a local company able to bring him service, even though it is not broadband as defined by the FCC. Nevertheless, he considers this a temporary fix and the best he can get for the time being.

Yet Another Homeowner Led Astray By Giant ISP; Responds with Muni Fiber Initiative

Last month, we highlighted the story of Seth, a Washington state homeowner forced to put his home up for sale due to a perfect storm of sloppy customer service, corporate bureaucracy, and terrible Internet policy. Now meet Dave Mortimer from Michigan.

Dave is another person in a similar situation, reports Ars Technica. In 2013 incumbent AT&T told Dave three separate times that the house he had his eye on in rural Lowell had U-verse fiber network capabilities. Their website verified what customer service represenatives told him. Dave is an IT professional and wanted the opportunity to work from home. He must be on call while not in the office and so requires a fast residential Internet connection. 

After buying the home and moving in, AT&T backpedaled. Actually his best option was DSL offering 768 Kbps. Oops!

Working from home was a struggle. After Dave complained to AT&T, the FCC, the FTC, and the state Public Service Commission, the provider eventually updated their website but that didn't help Dave. He limped along but seldom worked from home as he had planned to do from the start. His office is 30 minutes away.

Finally, AT&T billed him for a phone line he never requested leading to an auto-payment error and a shut-off of his Internet service. That was enough for Dave. He approached a local wireless provider Vergenness Broadband and, working with the installer, attached the receiver to a tree some distance from his house and buried the extra long cable in cracks in his driveway to his house. Dave now pays $60 per month and gets the 3 Mbps download / 1 Mbps upload he was promised.

Dave is no where near the 45 Mbps he had hoped to obtain from the phantom U-verse, but he has this to say about his local provider:

“This is a night and day difference since switching from AT&T," he said. "Everything that AT&T did wrong, this small local company is doing right.”

Dave was fortunate to have a local company able to bring him service, even though it is not broadband as defined by the FCC. Nevertheless, he considers this a temporary fix and the best he can get for the time being.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.

Seth's Tale of Comcast Woe Perfectly Illustrates Many Internet Policy Problems

Ideally, working from home allows one to choose the environment where he or she can be most productive. In the case of Seth that was Kitsap County in Washington State. Unfortunately, incompetence on the part of Comcast, CenturyLink, and official broadband maps led Seth down a road of frustration that will ultimately require him to sell his house in order to work from home.

The Consumerist recently reported on Seth's story, the details of which ring true to many readers who have ever dealt with the cable behemoth. This incident is another example of how the cable giant has managed to retain its spotless record as one of the most hated companies in America

Seth, a software developer, provides a detailed timeline of his experience on his blog. In his intro:

Late last year we bought a house in Kitsap County, Washington — the first house I’ve ever owned, actually. I work remotely full time as a software developer, so my core concern was having good, solid, fast broadband available. In Kitsap County, that’s pretty much limited to Comcast, so finding a place with Comcast already installed was number one on our priority list.

We found just such a place. It met all of our criteria, and more. It had a lovely secluded view of trees, a nice kitchen, and a great home office with a separate entrance. After we called (twice!) to verify that Comcast was available, we made an offer.

The Consumerist correctly describes the next three months as "Kafkaesque." Comcast Technicians appear with no notice, do not appear for scheduled appointments, and file mysteriously misplaced "tickets" and "requests." When technicians did appear as scheduled, they are always surprised by what they saw: no connection to the house, no Comcast box on the dwelling, a home too far away from Comcast infrastructure to be hooked up. Every technician sent to work on the problem appeared with no notes or no prior knowledge of the situation.