Thursday, March 05, 2015

AT&T update: out of the frying pan, into the fire

An update on our on-going nightmare with AT&T: after two weeks, four technician visits to our house, and I don't know how many phone calls to CSRs and supervisors, they were finally able to get our internet connection back up and running today.

That's the good news.

The bad news is that somehow they managed to break our phone line in the process.  It was working this morning, but just as the internet tech was leaving we noticed that we didn't have a dial tone on our main phone line any more.  We've been down for a few hours now and they have not been able to figure out what the problem is, except that as far as anyone can tell, the problem is far upstream of our house, and the fact that it happened at the same time that we were fiddling with the internet connection is just a coincidence.

But it's a damned odd coincidence.  Damned annoying too.

[UPDATE:] They fixed it.  Whew!

[UPDATE March 12:] The nightmare is not over.  They are still billing me for my now-discontinued DSL service.  On hold with AT&T billing for 30 minutes and counting while they (supposedly) fix it... arrggghhh!!!

1 comment:

XO said...

Apologies for commenting on an old post Ron. I just wrote an article referencing a similiar pain I had (roughly around the same year) with the old att DSL service. I totally sympathize with this. I spent 2 weeks trying to get them to understand a route was deleted and my Internet was down because of it. Despite evidence, they insisted on sending a tech out to my house and charge me for it. I told them not to waste their time. Two weeks later, they confessed - a route was deleted in California (I was living in MO at the time). I saved all the case notes because I knew they wouldn't (despite me asking them to). I figured, perhaps it would save me time - should this occur again. A year later, the issue returns. My notes had no bearing on time-to-fix. Two weeks later, they confess, a route was deleted in California (as part of yearly maintenance). Now back to looking for any posts you've written concerning Biblical errors :).