Skip to main content

How To Cancel ATT Uverse

I was a subscriber to the AT&T Uverse service for a little over 2 years. In that time, we had experienced good service for the first year, and then it sucked. After 12 months, or there in, the service degraded quickly, and would stop working all together at times. At first it would die for a short period of time, usually when we were not home. Then it would get progressively worst, until there was an entire week of no service. We had technicians at the house trying to fix the service, but it would repeat the behavior quite consistently.

On January 15th we finally gave up and switched to a lesser service, COX TV and Internet. In the past we had cable service and it was always reliable, but not as good as the AT&T digital service. COX doesn't have nearly as many HD channels, but that's not enough. We needed internet to be reliable, and AT&T couldn't deliver that.

Cancelling the AT&T service was a nightmare. Try to find anything about such things on their web site only left you with a number to their automated menu system. If you answered "Cancel Service" to the computer, it directed you to a number that was for an office that was always "closed", and then it would hang up.

I had to get on a chat session with tech support, complain about the bad number that she gave me (same as the IVR number for support), and then was transferred to a customer service chat, who responded to my lamentation with:

Sorry to know that. You have to call our disconnection department to cancel your U-verse service. You may reach them at 877-377-0415, between 8am-7pm, Mondays-Fridays.

Note that number because that's the number you call if you want to disconnect your service. The time is CENTRAL TIME in the US (not local time as the AT&T web site claims for other numbers). Once I called that number, I got a no-nonsense CSR who was quick and to the point.

Our house is new construction in an area where the AT&T fibre node was literally just a couple blocks away. The DVR device from AT&T is very slow and would often times just lock up on us while trying to move through the channel line up.

AT&T DVRs can record up to 4 shows at once AND allow you to watch live TV. The COX DVR can only record 2 shows and when at 2 shows, you can not watch live TV. The AT&T technology is superior to COX, but the delivery of the service is horribly inept. The service techs are great and very knowledgeable, but in the end, you just can't polish a tird.

COX by far has been the lowest of the three TV services we've tried (AT&T and Time Warner before). I find myself watching 480p TV now, whereas with AT&T I never watched those channels. The COX DVR is only 1080i, even with HDMI. The AT&T DVR was 1080p.

Popular posts from this blog

Number of Primes

Anderson's Theorem (a) The number of primes in [1,n] is no more than 2+floor(n/2). The probability of n being prime when n is not prime is 1/2 - see Dasgupta,Papadimitriou,Vazirani "Algorithms" page 26. Therefore, the E(pi(n)) is n/2. (b) There does not exist another set of adjacent primes other than {1,2,3} 5: 2 + floor(5/2) = 2 + 2 = 4:=> {1,2,3,5} : 4 <= 4 7: 2 + floor(7/2) = 2 + 3 = 5 => {1,2,3,5,7} : 5 <= 5 11: 2 + floor(11/2) = 2 + 5 = 7 => {1,2,3,5,7,11} 6 <= 7 26: 2 + floor(26/2) = 15 => {1,2,3,5,7,11,13,17,19,23} : 10 <= 15 Lagrange's Theorem is Inaccurate Lagrange's theorem about primes states that pi(x) is the number of primes <= x. The pi(x) is approximately x/ln(x). He postulated that the lim of pi(x)/(x/lnx) as x-> infinity was 1. This is incorrect. if the number of primes is bounded by n/2 then refactoring and reducing Lagrange's Theorem results in the lim of ln(x) as x approaches infinity. This is alwa...

DNS Custom Logs and selinux

If you google "named custom logs selinux" you will find quite a bit of chatter about setting up custom logs outside of /var/log for DNS (named). These posts are interesting, but they tend to be run on posts about learning selinux and becoming an expert on named. What you need to know? If you have setup custom logging locations in your /etc/named.conf file, such as:     channel default_file {         file "/var/log/named/default.log" versions 3 size 5m;         severity dynamic;         print-time yes;     }; Then you will likely see errors like this in /var/log/messages: Oct 26 11:41:13 namedsvr setroubleshoot: SELinux is preventing /usr/sbin/named from write access on the directory /var/named/chroot/var/log/named. For complete SELinux messages. run sealert -l 6eab4aaf-e615-4ade-9e88-4efdc789eaf2 Then you run the sealert command as suggested by the very friendly selinux audit log and yo...