Try emailing Matt at uversecare@att.com, give your account #, good phone # and time to call and give him this thread link and explain the problem. They should have used cat5e for the homerun, they've found too many freeze/pixelization problems w/coax homeruns. Good luck Bob. 
Chris
__________________________________________________
Please NO SD stretch-o-vision or 480 SD HD Channels
1-866-465-1496 for direct TS to avoid Mr. Voice recognition
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more
ScottMac wrote:
perritterd wrote:
ScottMac wrote:Coax in good condition is an acceptable alternative to UTP/Cat5e for the "Home Run" between the NID and the RG.
Even if you are getting freezing/pixelization? How can you rule out that the lack of Cat5e wiring into the RG is not a possible cause? I believe that in one of the above posts, it is stated that Cat5e is supposed to be run into the house from the phone box outside to the RG, especially here in S. Fla. (per the Installation Mgr. in Jax, Fla. also).
Bob
Because the signal from the NID to the RG is still VDSL2; it'll travel well on barbed wire if it's strung right.
It's much more likely that the issue is between the RG and your STB(s) and / or your DVR.Try removing all non-Uverse stuff (as a diagnostic) and make sure the STB(s) and DVR are directly connected to the RG and see if you still have the issue.
Also try running SomeJoe's realtime diagnostic and see what your stats look like (and optionally post the screenshots so we can see 'em too).
Here you go ScottMac, the screenshot of my Stats page:
I have been in contact w/ Matt, Tier II tech. support and he has stated that it is not just my system but the whole neighbor hood that is being affected and sending out service call tomorrow and for me to request a lineman to check the lines.
Bob.
perritterd wrote:
ScottMac wrote:
perritterd wrote:
ScottMac wrote:Coax in good condition is an acceptable alternative to UTP/Cat5e for the "Home Run" between the NID and the RG.
Even if you are getting freezing/pixelization? How can you rule out that the lack of Cat5e wiring into the RG is not a possible cause? I believe that in one of the above posts, it is stated that Cat5e is supposed to be run into the house from the phone box outside to the RG, especially here in S. Fla. (per the Installation Mgr. in Jax, Fla. also).
Bob
Because the signal from the NID to the RG is still VDSL2; it'll travel well on barbed wire if it's strung right.
It's much more likely that the issue is between the RG and your STB(s) and / or your DVR.Try removing all non-Uverse stuff (as a diagnostic) and make sure the STB(s) and DVR are directly connected to the RG and see if you still have the issue.
Also try running SomeJoe's realtime diagnostic and see what your stats look like (and optionally post the screenshots so we can see 'em too).
Here you go ScottMac, the screenshot of my Stats page:
I have been in contact w/ Matt, Tier II tech. support and he has stated that it is not just my system but the whole neighbor hood that is being affected and sending out service call tomorrow and for me to request a lineman to check the lines.
Bob.
Those number are lookin' pretty good. With the information provided, IMO, the problems you describe are either happening after the RG (somewhere in your LAN) or are coming in as valid data (i.e., created / produced at the headend and sent as the video stream).
I'm not ruling out an occasional WAN/network hit, but not at the rate and level you described earlier. Events of that scope and magnatude would show up more in your stats.
Have you notice the occurrances in the context of other events in your home, possibly outside your home, and (really happens) something in a neighbor's house?
A neighbor with a new kilowatt linear for his Ham or CB radio?
Maybe a blinky streetlight?
Any electrically-operated workout gear in your home (or neighbor's)?
Aquariums?
Heating Pads?
Light Dimmers?
Touch-control lamps?
Dusk/Dawn sensors on the porch?
Any new CFL bulbs (OK to be green, as long as you don't watch TV or listen to AM radio ... j/k ...)
The root cause of the issue you presented is essentially packet-drop. The packet drop can be caused by noise, which interferes with the data in transit and causes it to be too corrupt to use, so it's dropped or, congestion, which delays the packet until it's too late, or has been in-queue long enough to cause its expiration before it can be used at the destination.
So, try to look at your system in the house from the perspective of "what can cause electrical noise?" (the examples above are the top hitters for home noise) and "what parts of my LAN can cause data corruption and / or delays?"
Give it some thought and let us know ...
