Menu
Reply
  • 8
  • 0
  • 0
Richard--
Joining in
205 Views
Message 1 of 8
Flag for a moderator

Superhub 2ac performance poor since around 11th or 12th of December

Not sure what has happened recently, but it's had an impact on me. I looked and there does seem to be a fault in my area F004931459 but it doesn't look like it is what is affecting me as it says its to do with the win10 update? My ping 'jitter' is way too high now to allow me to play online games, whereas I was playing them a week ago on Saturday 10th with no problem. Here is my net performance for the last half hour: http://testmy.net/stats/?&t=u&d=12172016&x=1&l=25&q=dreaming11

Allow me to post my router log as there are a lot of T3 errors:

Information

Cable ModemEuroDOCSIS 3.0 Compliant
Serial Number483152WG12C52
Boot Code VersionPSPU-Boot 1.0.20.1391
Software VersionV1.01.11
Hardware Version1.03
CA KeyInstalled

Cable Modem Status Item Status Comments

Acquired Downstream Channel (Hz)267000000Locked
Ranged Upstream Channel (Hz)31000000Success
Provisioning StateOKOperational

 

Downstream   DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)267000000275000000283000000291000000299000000307000000315000000323000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID910111213141516
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)3.003.092.862.902.792.952.832.26
RxMER (dB)37.9438.2637.9437.9437.6437.9437.9437.94

 

Pre RS Errors

68843510661300914896106211894311255

 

Post RS Errors

2982899639539731044319953

 

Upstream   US-1 US-2 US-3 US-4

Channel Type2.0N/AN/A2.0
Channel ID6N/AN/A7
Frequency (Hz)31000000N/AN/A24400000
Ranging StatusSuccessOtherOtherSuccess
Modulation64QAMN/AN/A64QAM
Symbol Rate (Sym/sec)5120000N/AN/A5120000
Mini-Slot Size4N/AN/A4
Power Level (dBmV)43.50N/AN/A43.25
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts3899000
T4 Timeouts0000

 

Upstream Burst   Req
(1) Init Maint
(3) Per Maint
(4) Adv Short
(9) Adv Long
(10) Adv UGS
(11)

Modulation TypeQPSKQPSKQPSK64QAM64QAM64QAM
Differential EncodingOFFOFFOFFOFFOFFOFF
Preamble Length56640384104104104
Preamble Value Offset65200716716716
FEC Error Correction (T)055121612
FEC Codeword Information Bytes (K)1634348122381
Maximum Burst Size00011193219
Guard Time Size84848888
Last Codeword LengthFixedFixedFixedShortenedShortenedShortened
Scrambler On/OffONONONONONON

 

General Configuration

Network AccessAllowed
Maximum Number of CPEs1
Baseline PrivacyEnabled
DOCSIS ModeEuroDOCSIS 3.0
Config File 

Primary Downstream Service Flow

SFID417730
Max Traffic Rate172500000 bps
Max Traffic Burst42600 bytes
Min Traffic Rate0 bps

Primary Upstream Service Flow

SFID417729
Max Traffic Rate10500000 bps
Max Traffic Burst16320 bytes
Min Traffic Rate0 bps
Max Concatenated Burst16320 bytes
Scheduling TypeBest Effort

 

Network Log

First TimeLast TimePriorityError NumberDescription
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
17/12/2016 16:55:24 GMT17/12/2016 16:55:24 GMTCritical (3)82000200No Ranging Response received - T3 time-out
0 Kudos
Reply

Helpful Answers
  • 9.02K
  • 760
  • 1.88K
Superuser
Superuser
308 Views
Message 2 of 8
Flag for a moderator
Helpful Answer

Re: Superhub 2ac performance poor since around 11th or 12th of December

There are a huge amount of T3 errors showing on the counters, this is probably why your log table is full and the last entry is repeating itself. It would be worth clearing tour kogs.

It looks like you have a upstream problem. VM will need to confirm this.

You will need to contact VM for resolution, either by waiting here about a week until a VM Forum Team Member picks up the thread, or give them a call on 150 from a VM line or 0345 454 1111 for a quicker response.

0 Kudos
Reply
  • 7.37K
  • 316
  • 524
Forum Team
Forum Team
247 Views
Message 3 of 8
Flag for a moderator
Helpful Answer

Re: Superhub 2ac performance poor since around 11th or 12th of December

Hi Richard--,

 

Thanks for posting!

 

Sorry to hear you're having trouble with your connection.

 

I've run a diagnostic on your equipment and I can see an issue with your levels that will need to be adjusted by a technician. I've sent you a private message (purple envelope at the top right of your screen) so I can arrange an appointment.

 

Look forward to hearing from you! Smiley Very Happy

 

Josh


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply

All Replies
  • 9.02K
  • 760
  • 1.88K
Superuser
Superuser
309 Views
Message 2 of 8
Flag for a moderator
Helpful Answer

Re: Superhub 2ac performance poor since around 11th or 12th of December

There are a huge amount of T3 errors showing on the counters, this is probably why your log table is full and the last entry is repeating itself. It would be worth clearing tour kogs.

It looks like you have a upstream problem. VM will need to confirm this.

You will need to contact VM for resolution, either by waiting here about a week until a VM Forum Team Member picks up the thread, or give them a call on 150 from a VM line or 0345 454 1111 for a quicker response.

0 Kudos
Reply
  • 7.37K
  • 316
  • 524
Forum Team
Forum Team
248 Views
Message 3 of 8
Flag for a moderator
Helpful Answer

Re: Superhub 2ac performance poor since around 11th or 12th of December

Hi Richard--,

 

Thanks for posting!

 

Sorry to hear you're having trouble with your connection.

 

I've run a diagnostic on your equipment and I can see an issue with your levels that will need to be adjusted by a technician. I've sent you a private message (purple envelope at the top right of your screen) so I can arrange an appointment.

 

Look forward to hearing from you! Smiley Very Happy

 

Josh


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply
  • 8
  • 0
  • 0
Richard--
Joining in
88 Views
Message 4 of 8
Flag for a moderator

Re: Superhub 2ac performance poor since around 11th or 12th of December

Hello,

Engineer has come and gone. He did a couple of speedtests and said sometimes it was 30mbs sometimes it was 150mbps, so he replaced all of my wiring internally and externally and also at the box as he said it was ancient, and said hopefully that should resolve the issue. Unfortunately it appears I'm still getting a lot of issues and timeouts at times.

My logs attached to post.

DownstreamDownstreamNetwork LogNetwork LogUpstreamUpstream

 

0 Kudos
Reply
  • 8
  • 0
  • 0
Richard--
Joining in
77 Views
Message 5 of 8
Flag for a moderator

Re: Superhub 2ac performance poor since around 11th or 12th of December

pingtest.netpingtest.net

0 Kudos
Reply
  • 9.02K
  • 760
  • 1.88K
Superuser
Superuser
80 Views
Message 6 of 8
Flag for a moderator

Re: Superhub 2ac performance poor since around 11th or 12th of December

It looks like the T3 errors are still occuring. aybe the tech missed something or there is noise further up the line, however,  do need to revisit.

0 Kudos
Reply
  • 5.98K
  • 160
  • 417
Forum Team
Forum Team
68 Views
Message 7 of 8
Flag for a moderator

Re: Superhub 2ac performance poor since around 11th or 12th of December

Thanks for updating the thread Richard--,

 

As mentioned by griffin, there are still some high timeouts present and SNR still isn't looking too great at the moment.

 

I've sent you a private message so that we can get another appointment arranged for you.

 

Speak to you soon,

 

Nat_J


Who's who? Find out more about our community members. Good folk to know


0 Kudos
Reply
  • 5.98K
  • 160
  • 417
Forum Team
Forum Team
63 Views
Message 8 of 8
Flag for a moderator

Re: Superhub 2ac performance poor since around 11th or 12th of December

Thanks for updating the thread Richard--,

 

I've sent you a private message so that we can get another engineer appointment arranged for you.

 

Speak soon,

 

Nat_J


Who's who? Find out more about our community members. Good folk to know


0 Kudos
Reply