Ask a question
Search in U-verse Forums

U-verse Forums

Reply
Posted Feb 21, 2014
9:28:40 AM
View profile
FEC Errors

Hello,

I just checked out my broadband status for the first time a couple days ago. Im concerned about the high FEC count. It was like 48,000 at night in the morning it was over 80k. I cleared the count about 17 hours ago and this is what I have now

 

 

 

My speedtests come out good, however my online experience seems kind of slow and my wifes facebook games she says are slower at home then at work. Maybe its the other servers or traffic.

 

Your opinions and guidance is appreciated. Also I have the NVG589 RG triple play 2 phone lines. I have been told I am 2800' from vrad and I have been told 2000' how can I find out. Thanks.

Ken

Hello,

I just checked out my broadband status for the first time a couple days ago. Im concerned about the high FEC count. It was like 48,000 at night in the morning it was over 80k. I cleared the count about 17 hours ago and this is what I have now

 

 

 

My speedtests come out good, however my online experience seems kind of slow and my wifes facebook games she says are slower at home then at work. Maybe its the other servers or traffic.

 

Your opinions and guidance is appreciated. Also I have the NVG589 RG triple play 2 phone lines. I have been told I am 2800' from vrad and I have been told 2000' how can I find out. Thanks.

Ken

0
(0)
  • Rate this reply
View profile
Solved
Feb 21, 2014 1:38:58 PM
0
(0)
Employee
Line distance is estimating, actual loop length is knowing type of cable used , for how long as often cables types can change.
Cable gauge could be 22, 24 or 26, or a combination of those...a uverse tech meter assigns a wire type and calculation loop length, generally accurate but not precise measurement.

Based on max signal strength, k or n card, and SN margin, plus bonded pair (2800 feet would not qualify)
Closer to 2000 feet, with line attenuation around 26, and SN round 24, much closer than 2000 feet, guess 1600.

Fec errors are corrected, allowed up to 100 per minute, 6000 per hour, 102,000 for 17 hours.
Your current level suggests average less than 25 errors per minute (25,500 for 17 hours), I personally would not be concerned.

Different ISPs, different speed tiers, different routing paths can all explain wife observation, does not mean an issue exists.
Your speed tests are where they should be, with low ping.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.
Accepted Solution

FEC Errors

4,476 views
2 replies
(0) Me too
(0) Me too
Reply
View all replies
(2)
Highlighted
0
(0)
  • Rate this reply
View profile
Solved
Feb 21, 2014 1:38:58 PM
0
(0)
Employee
Line distance is estimating, actual loop length is knowing type of cable used , for how long as often cables types can change.
Cable gauge could be 22, 24 or 26, or a combination of those...a uverse tech meter assigns a wire type and calculation loop length, generally accurate but not precise measurement.

Based on max signal strength, k or n card, and SN margin, plus bonded pair (2800 feet would not qualify)
Closer to 2000 feet, with line attenuation around 26, and SN round 24, much closer than 2000 feet, guess 1600.

Fec errors are corrected, allowed up to 100 per minute, 6000 per hour, 102,000 for 17 hours.
Your current level suggests average less than 25 errors per minute (25,500 for 17 hours), I personally would not be concerned.

Different ISPs, different speed tiers, different routing paths can all explain wife observation, does not mean an issue exists.
Your speed tests are where they should be, with low ping.
Line distance is estimating, actual loop length is knowing type of cable used , for how long as often cables types can change.
Cable gauge could be 22, 24 or 26, or a combination of those...a uverse tech meter assigns a wire type and calculation loop length, generally accurate but not precise measurement.

Based on max signal strength, k or n card, and SN margin, plus bonded pair (2800 feet would not qualify)
Closer to 2000 feet, with line attenuation around 26, and SN round 24, much closer than 2000 feet, guess 1600.

Fec errors are corrected, allowed up to 100 per minute, 6000 per hour, 102,000 for 17 hours.
Your current level suggests average less than 25 errors per minute (25,500 for 17 hours), I personally would not be concerned.

Different ISPs, different speed tiers, different routing paths can all explain wife observation, does not mean an issue exists.
Your speed tests are where they should be, with low ping.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: FEC Errors

2 of 3 (4,443 Views)
Solution
0
(0)
  • Rate this reply
View profile
Feb 21, 2014 6:12:07 PM
0
(0)
Teacher
I appreciate it. Thank You.
I appreciate it. Thank You.

Re: FEC Errors

3 of 3 (4,425 Views)
Share this post
Share this post