Menu
Reply
aj26
  • 35
  • 0
  • 2
On our wavelength
1,385 Views
Message 1 of 50
Flag for a moderator

Gig1 Latency

Moved to Gig1 last week, was great got over 1Gb download, 50 up with 16ms average Latency and 3ms Jitter with 0 packet loss. This week its been getting v.bad. lower speed I can easily live with its the latency that's destroying gaming. Contacted support to be told everything looks fine, but all he checked was connectivity and escalated the call when I mentioned latency of 368ms and 0.009% packet loss (tested on samknows and recorded on BQM, still waiting for a callback. Anyone else in RG6 having issues?? Is this a common thing on Gig1? still on my cooling off period so may have to cancel if it is 😞

https://www.thinkbroadband.com/broadband/monitoring/quality/share/36ba77a75ab7401c336eabc4ec43d2d96e...

 

samknows1.jpg

0 Kudos
Reply
Chris_W1
  • 4.05K
  • 181
  • 252
Forum Team
Forum Team
1,302 Views
Message 2 of 50
Flag for a moderator

Re: Gig1 Latency

HI aj26, thanks for messaging us and are sorry to see that you are having issues with the service, Can you confirm if you are still having this issue or has this now been resolved? Can you confirm if you had had this call back? When was the call back advised? - Chris 

0 Kudos
Reply
aj26
  • 35
  • 0
  • 2
On our wavelength
1,199 Views
Message 3 of 50
Flag for a moderator

Re: Gig1 Latency

Still having the issue, someone called back to say its an overutilization issue and will be fixed by the 17th. I think that's partially the issue but think there may be issues with the CMTS as the lag spikes are there between midnight and 8 am and that surely can't be down to overutilization?? Pinging the external facing IP's of my CMTS shows issues.

 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/4782ae321da23f89b3a27daaa764171cbae59c61

 

0 Kudos
Reply
aj26
  • 35
  • 0
  • 2
On our wavelength
1,194 Views
Message 4 of 50
Flag for a moderator

Re: Gig1 Latency

Ping to my gateway

Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

Ping to my external IP

ping x.x.x.x

Pinging x.x.x.x with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time=1ms TTL=64
Reply from x.x.x.x: bytes=32 time=1ms TTL=64
Reply from x.x.x.x: bytes=32 time=1ms TTL=64
Reply from x.x.x.x: bytes=32 time<1ms TTL=64

Ping statistics for x.x.x.x:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

Ping to external IP of CMTS

Pinging 62.253.98.2 with 32 bytes of data:
Reply from 62.253.98.2: bytes=32 time=16ms TTL=254
Reply from 62.253.98.2: bytes=32 time=659ms TTL=254
Reply from 62.253.98.2: bytes=32 time=106ms TTL=254
Reply from 62.253.98.2: bytes=32 time=46ms TTL=254

Ping statistics for 62.253.98.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 659ms, Average = 206ms

A quick scan shows 14 external IP addresses for my CMTS all have this latency issue, yes it could be overutilization but this doesn't explain the issues being seen at 3 am. Its got to be a fault or config error in the CMTS.

0 Kudos
Reply
Lisa_CC
  • 3.96K
  • 236
  • 433
Moderator
Moderator
1,181 Views
Message 5 of 50
Flag for a moderator

Re: Gig1 Latency

Hey aj26,

 

Yes I can see the high utilisation ticket still being open and for that date you mentioned and I've had a quick glance at your network stats too. You have high upstream power levels which we'll need to get a tech out to get them back down. Please wait for the high utilisation ticket to close first and then we can have another look and arrange a tech out if required.

 

Regards,

 

Lisa

0 Kudos
Reply
aj26
  • 35
  • 0
  • 2
On our wavelength
1,177 Views
Message 6 of 50
Flag for a moderator

Re: Gig1 Latency

Thanks

0 Kudos
Reply
Andrew-G
  • 6.09K
  • 1.07K
  • 2.57K
Very Insightful Person
Very Insightful Person
1,169 Views
Message 7 of 50
Flag for a moderator

Re: Gig1 Latency

Still having the issue, someone called back to say its an overutilization issue and will be fixed by the 17th. 

Devil's Advocate:  17th of when?  My money's on the thirteenth month, Neveruary.

Secondary thought: Wish I'd tried to grab the forum name of Devil's Advocate.  Or if that was taken, Devil's Advocaat.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
aj26
  • 35
  • 0
  • 2
On our wavelength
1,147 Views
Message 8 of 50
Flag for a moderator

Re: Gig1 Latency

Yes its high, upstream logs also show 8QAM modulation

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

16030000058.7705995120 KSym/sec64QAM1
23940000058.7705995120 KSym/sec8QAM4
34620000058.7705995120 KSym/sec64QAM3
45370000058.7705995120 KSym/sec64QAM2
0 Kudos
Reply
aj26
  • 35
  • 0
  • 2
On our wavelength
1,145 Views
Message 9 of 50
Flag for a moderator

Re: Gig1 Latency

I was told 17th June before 1:50pm 

0 Kudos
Reply
Andrew-G
  • 6.09K
  • 1.07K
  • 2.57K
Very Insightful Person
Very Insightful Person
1,133 Views
Message 10 of 50
Flag for a moderator

Re: Gig1 Latency

Good to hear the over-utilisation was fixed yesterday - and presumably the BQM's looking a lot better?

Your upstream certainly looks dodgy - the power levels are way too high and the modulation is all over the place, so you still need a technician to sort that.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply