how-to block ads
|
|
Uniqs:
320 |
Share Topic
 |
 |
|
|
|
1 edit | 70 million corrected blocks in last few hours
First | 
30 minutes later |
Background: I have had a series of retrains, and many service calls. First episode was last June. Changing my RG helped then but the problem is back, and now I am on my 3rd RG. Latest thing done, was a homerun cat 5 wiring done by AT&T two days ago. Yesterday, when I checked, I had like 500 corrected blocks over 24 hours (down from 10 to 100K a day), so I thought that homerun wiring fixed the problem. Uversecare, which I initially contacted through AT&T Direct here, has been monitoring my line and have found a fault on the outside wiring but AT&T field teams have outright refused to make changes UverseCare ordered.
Tonight, as I saw these corrected blocks, I called 800-288-2020 asking the Tier 2 tech that answered to check my line, hoping he would see the errors in the act and therefore possibly be able to pinpoint the source. He did a Quality Check and said he saw many errors and the line showed "line failure" (he could not understand how my service was staying up.) He cut and pasted what his test showed and put it into my account notes.
Anyone ever seen corrected blocks balloon like this? Any advice on how I can get this fixed (again I have contacted AT&T Direct/UverseCare through this site, and that group sees a fought in my line, but the field group literally refuses to address it, telling me that the things Uversecare requested them to do are not warranted in their opinions.) | |
4 edits | The UverseCare tech replied to my email about the shots above and the 800-288-2020 tech's notes. He wrote, that as far as fixing my problem, this is great news because an independent agent (the one on phone) saw the same problem and agrees it should bring my service down and the problem (if out in the field) could have far reaching problems for others in my area, so they need to fix it now before it hits many more customers. He said he had just found a field manager, in my area, who has already agreed to take ownership and see that the problem is fixed, so this episode will make that commitment even stronger he thinks.
AT&T's field group's reaction reminds me of a problem I had with DSL many years ago, that could have prevented a major outage for like half of Houston had it been addressed sooner. I was getting horrible latency all the time all of a sudden. From tracroute test I saw it was likely happening on the 3rd or 4th or so hop (owned by SW Bell) that I always went through so it was part of their cirucit. I called SW Bell/AT&T about it but they did not seem to care about latency slowdowns since I was getting decent throughput still and they failed to ackowledge that the problem was on their infrastructure a few hops from me (they kept having me turn off my modem and restart it and all that kind of stuff.) The high latency stayed that way for a week or two and then it got worse and my throughput started falling too. At that point, I contacted AT&T Direct here.
During my correspondence with AT&T Direct, which took place over a day or two, I completely lost my DSL. When I got back up I saw tha the same AT&T guy had puhlicly posted in my region's DSL forum that a major gateway and/or backbone in Houston came down, and service for some parts of Houston would be down until further notice (lasted a few hours.) In my AT&T Direct message, he wrote that what I had experienced were early signs of that failing gateway, and he wished people would have been on it earlier. So lesson: if AT&T would properly troubleshoot these type of things, instead of telling is to restart our modems and hoping we go away, they could perhaps limit major fire drills. | | |
|
| reply to nine9s2
I know this isn't really providing any help, but it never hurts to know other subs are listening and do feel your pain. Based on your prior thread on this issue and the symptoms plus what the techs are telling you, my money is on dirty power/halogen street light. Between your RG and the VRAD (it's not network backbone or in the VRAD because then other subs near you would also have trouble tickets, raising the red flags) is a source of interference that ATT might not have authority to remove, like a poorly installed streetlight. In some cases it can be in the home, improperly shielded treadmill motor or a compressor that kicks in randomly.
Hats off for being patient and helpful with all the techs assisting you. I hope that I'm wrong and some tech does correct a network issue that fixes it, wouldn't be the first. | |
2 edits | said by Forosnai:I know this isn't really providing any help, but it never hurts to know other subs are listening and do feel your pain. Based on your prior thread on this issue and the symptoms plus what the techs are telling you, my money is on dirty power/halogen street light. Between your RG and the VRAD (it's not network backbone or in the VRAD because then other subs near you would also have trouble tickets, raising the red flags) is a source of interference that ATT might not have authority to remove, like a poorly installed streetlight. In some cases it can be in the home, improperly shielded treadmill motor or a compressor that kicks in randomly.
Thanks for the insight. It only happens in evenings, so it might be something like that. Although, while it is dark in evenings now, during June, when the problem first started, it would happen around 6 to 7 pm usually, and it was bright daylight then, so it was not a street light then .
Might not be able to eliminate the VRAD because I am in a neighborhood with only about 40 houses, and from talking with many of my neighbors, I have found no one with Uverse (they have DSL but no Uverse), and I ask them about it all the time, hoping to get some of the referral rewards but everyone is happy with the DSL and Directv. So I very well might be the only customer off my VRAD.
I cannot think of anything in my house (and I thought about it a lot last June, when I tried to pinpoint a possible problem) that would run only during evening hours. I cannot think of anything and I unplug most electronics when not in use, even when I will use them in a few days.
The UverseCare guy seems to think it something on the field line (a stray circuit), that only gets amplified intermittently. In fact he thinks it might develop into a case study for R&D for semi-rural deployment. For example, he keeps writing that my readings are very strange and unique (for example, he saw billions of errors on my line last night, something he has never seen in close comparison anywhere - how the service stayed up is a complete mystery.) The last thing he wrote was " This situation falls clearly in line with a theoretical scenario that I was speaking with a Chief Principal Architect about earlier in the day. I definitely want to get the manager out to test all of the service pairs in your serving terminal. Not only will we be able to bring this that much closer to conclusion but this will likely yield most excellent data to bring to R&D Labs." | |
|
