Menu
Reply
Highlighted
  • 21
  • 0
  • 0
Joining in
552 Views
Message 1 of 11
Flag for a moderator

Random high pings causing connection issues

Hi,

Please forgive the forthcoming wall of text; I want to provide you guys with as much info as possible.

For about a month now, I've occasionally had a random pocket of high network latency which has caused me to drop out of game servers, and cause video playback issues.  I have recorded a few examples:

1:
Reply from 8.8.8.8: bytes=32 time=12ms TTL=55
Reply from 8.8.8.8: bytes=32 time=17ms TTL=55
Reply from 8.8.8.8: bytes=32 time=16ms TTL=55
Reply from 8.8.8.8: bytes=32 time=15ms TTL=55
Reply from 8.8.8.8: bytes=32 time=14ms TTL=55
Request timed out.
Reply from 8.8.8.8: bytes=32 time=335ms TTL=55
Reply from 8.8.8.8: bytes=32 time=402ms TTL=55
Reply from 8.8.8.8: bytes=32 time=514ms TTL=55
Reply from 8.8.8.8: bytes=32 time=544ms TTL=55
Reply from 8.8.8.8: bytes=32 time=318ms TTL=55
Reply from 8.8.8.8: bytes=32 time=398ms TTL=55
Reply from 8.8.8.8: bytes=32 time=303ms TTL=55
Reply from 8.8.8.8: bytes=32 time=196ms TTL=55
Reply from 8.8.8.8: bytes=32 time=114ms TTL=55
Reply from 8.8.8.8: bytes=32 time=20ms TTL=55
Reply from 8.8.8.8: bytes=32 time=19ms TTL=55
Reply from 8.8.8.8: bytes=32 time=19ms TTL=55
Reply from 8.8.8.8: bytes=32 time=18ms TTL=55

2:
Reply from 8.8.8.8: bytes=32 time=15ms TTL=55
Reply from 8.8.8.8: bytes=32 time=10ms TTL=55
Reply from 8.8.8.8: bytes=32 time=13ms TTL=55
Reply from 8.8.8.8: bytes=32 time=10ms TTL=55
Reply from 8.8.8.8: bytes=32 time=11ms TTL=55
Reply from 8.8.8.8: bytes=32 time=529ms TTL=55
Reply from 8.8.8.8: bytes=32 time=422ms TTL=55
Reply from 8.8.8.8: bytes=32 time=490ms TTL=55
Reply from 8.8.8.8: bytes=32 time=614ms TTL=55
Reply from 8.8.8.8: bytes=32 time=519ms TTL=55
Reply from 8.8.8.8: bytes=32 time=474ms TTL=55
Reply from 8.8.8.8: bytes=32 time=504ms TTL=55
Reply from 8.8.8.8: bytes=32 time=434ms TTL=55
Reply from 8.8.8.8: bytes=32 time=289ms TTL=55
Reply from 8.8.8.8: bytes=32 time=413ms TTL=55
Reply from 8.8.8.8: bytes=32 time=419ms TTL=55
Reply from 8.8.8.8: bytes=32 time=443ms TTL=55
Reply from 8.8.8.8: bytes=32 time=467ms TTL=55
Reply from 8.8.8.8: bytes=32 time=441ms TTL=55
Reply from 8.8.8.8: bytes=32 time=490ms TTL=55
Reply from 8.8.8.8: bytes=32 time=558ms TTL=55
Reply from 8.8.8.8: bytes=32 time=569ms TTL=55
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=591ms TTL=55
Reply from 8.8.8.8: bytes=32 time=409ms TTL=55
Reply from 8.8.8.8: bytes=32 time=295ms TTL=55
Reply from 8.8.8.8: bytes=32 time=83ms TTL=55
Reply from 8.8.8.8: bytes=32 time=280ms TTL=55
Reply from 8.8.8.8: bytes=32 time=529ms TTL=55
Reply from 8.8.8.8: bytes=32 time=572ms TTL=55
Reply from 8.8.8.8: bytes=32 time=283ms TTL=55
Reply from 8.8.8.8: bytes=32 time=389ms TTL=55
Reply from 8.8.8.8: bytes=32 time=345ms TTL=55
Reply from 8.8.8.8: bytes=32 time=350ms TTL=55
Reply from 8.8.8.8: bytes=32 time=487ms TTL=55
Reply from 8.8.8.8: bytes=32 time=468ms TTL=55
Reply from 8.8.8.8: bytes=32 time=499ms TTL=55
Reply from 8.8.8.8: bytes=32 time=398ms TTL=55
Reply from 8.8.8.8: bytes=32 time=535ms TTL=55
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=635ms TTL=55
Reply from 8.8.8.8: bytes=32 time=403ms TTL=55
Reply from 8.8.8.8: bytes=32 time=55ms TTL=55
Reply from 8.8.8.8: bytes=32 time=13ms TTL=55
Reply from 8.8.8.8: bytes=32 time=11ms TTL=55
Reply from 8.8.8.8: bytes=32 time=10ms TTL=55
Reply from 8.8.8.8: bytes=32 time=11ms TTL=55

3:
Reply from 8.8.8.8: bytes=32 time=29ms TTL=57
Reply from 8.8.8.8: bytes=32 time=25ms TTL=57
Reply from 8.8.8.8: bytes=32 time=39ms TTL=57
Reply from 8.8.8.8: bytes=32 time=38ms TTL=57
Reply from 8.8.8.8: bytes=32 time=469ms TTL=57
Reply from 8.8.8.8: bytes=32 time=537ms TTL=57
Reply from 8.8.8.8: bytes=32 time=561ms TTL=57
Reply from 8.8.8.8: bytes=32 time=410ms TTL=57
Reply from 8.8.8.8: bytes=32 time=578ms TTL=57
Request timed out.
Reply from 8.8.8.8: bytes=32 time=571ms TTL=57
Reply from 8.8.8.8: bytes=32 time=427ms TTL=57
Reply from 8.8.8.8: bytes=32 time=507ms TTL=57
Reply from 8.8.8.8: bytes=32 time=588ms TTL=57
Request timed out.
Reply from 8.8.8.8: bytes=32 time=536ms TTL=57
Reply from 8.8.8.8: bytes=32 time=548ms TTL=57
Request timed out.
Reply from 8.8.8.8: bytes=32 time=425ms TTL=57
Request timed out.
Reply from 8.8.8.8: bytes=32 time=476ms TTL=57
Reply from 8.8.8.8: bytes=32 time=475ms TTL=57
Reply from 8.8.8.8: bytes=32 time=468ms TTL=57
Reply from 8.8.8.8: bytes=32 time=398ms TTL=57
Reply from 8.8.8.8: bytes=32 time=478ms TTL=57
Reply from 8.8.8.8: bytes=32 time=527ms TTL=57
Reply from 8.8.8.8: bytes=32 time=389ms TTL=57
Request timed out.
Reply from 8.8.8.8: bytes=32 time=603ms TTL=57
Reply from 8.8.8.8: bytes=32 time=577ms TTL=57
Reply from 8.8.8.8: bytes=32 time=626ms TTL=57
Reply from 8.8.8.8: bytes=32 time=244ms TTL=57
Request timed out.
Reply from 8.8.8.8: bytes=32 time=28ms TTL=57
Reply from 8.8.8.8: bytes=32 time=25ms TTL=57
Reply from 8.8.8.8: bytes=32 time=26ms TTL=57
Reply from 8.8.8.8: bytes=32 time=25ms TTL=57
Reply from 8.8.8.8: bytes=32 time=24ms TTL=57

These instances last anywhere from 20 to 50 seconds, but that's enough to kick me from servers (and as someone who does a fair bit of league simracing on my downtime, this has caused me no end of issues as of late).

0 Kudos
Reply
Highlighted
  • 21
  • 0
  • 0
Joining in
551 Views
Message 2 of 11
Flag for a moderator

Re: Random high pings causing connection issues


Here's the status from the Superhub:

Item

Status

Comments

Acquired Downstream Channel (Hz)

595000000

Locked

Ranged Upstream Channel (Hz)

46200000

Locked

Provisioning State

Online

 

 

Downstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

SNR (dB)

Modulation

Channel ID

1

595000000

5.1

40

256 qam

24

2

411000000

5

38

256 qam

1

3

419000000

5

38

256 qam

2

4

427000000

5

38

256 qam

3

5

435000000

4.9

38

256 qam

4

6

443000000

5

38

256 qam

5

7

451000000

5.4

38

256 qam

6

8

459000000

5.6

38

256 qam

7

9

467000000

5.5

38

256 qam

8

10

475000000

5.3

40

256 qam

9

11

483000000

5.5

40

256 qam

10

12

491000000

5.5

40

256 qam

11

13

499000000

5.3

38

256 qam

12

14

507000000

4.8

38

256 qam

13

15

515000000

4.6

38

256 qam

14

16

523000000

5

38

256 qam

15

17

531000000

5.4

40

256 qam

16

18

539000000

5

38

256 qam

17

19

547000000

4.8

38

256 qam

18

20

555000000

5

38

256 qam

19

21

563000000

5.4

40

256 qam

20

22

571000000

5

38

256 qam

21

23

579000000

4.4

38

256 qam

22

24

587000000

4.5

38

256 qam

23




Downstream bonded channels

Channel

Locked Status

RxMER (dB)

Pre RS Errors

Post RS Errors

1

Locked

40.3

210

0

2

Locked

38.9

185

0

3

Locked

38.9

110

0

4

Locked

38.9

152

0

5

Locked

38.9

243

0

6

Locked

38.9

265

0

7

Locked

38.9

246

0

8

Locked

38.6

157

29

9

Locked

38.9

139

58

10

Locked

40.3

97

0

11

Locked

40.3

95

0

12

Locked

40.3

185

0

13

Locked

38.6

194

0

14

Locked

38.9

155

0

15

Locked

38.6

144

0

16

Locked

38.9

145

0

17

Locked

40.3

121

0

18

Locked

38.9

252

0

19

Locked

38.9

291

29

20

Locked

38.6

274

0

21

Locked

40.3

136

0

22

Locked

38.9

130

0

23

Locked

38.9

130

0

24

Locked

38.9

148

0

Upstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

Symbol Rate (ksps)

Modulation

Channel ID

1

46200000

3.75

5120

64 qam

1

2

25800000

3.7

5120

64 qam

4

3

32600000

3.75

5120

64 qam

3

4

39400000

3.7

5120

64 qam

2




Upstream bonded channels

Channel

Channel Type

T1 Timeouts

T2 Timeouts

T3 Timeouts

T4 Timeouts

1

ATDMA

0

0

0

0

2

ATDMA

0

0

0

0

3

ATDMA

0

0

0

0

4

ATDMA

0

0

0

0

 

0 Kudos
Reply
Highlighted
  • 21
  • 0
  • 0
Joining in
549 Views
Message 3 of 11
Flag for a moderator

Re: Random high pings causing connection issues

 

 

General Configuration

Network access

Allowed

Maximum Number of CPEs

1

Baseline Privacy

Enabled

DOCSIS Mode

Docsis30

Config file

;fg87dsfd;kfoA,.iyewrkldJKDHSUB




Primary Downstream Service Flow

SFID

242

Max Traffic Rate

402500089

Max Traffic Burst

42600

Min Traffic Rate

0




Primary Upstream Service Flow

SFID

241

Max Traffic Rate

38500089

Max Traffic Burst

42600

Min Traffic Rate

0

Max Concatenated Burst

42600

Scheduling Type

BestEffort

 

 

Network Log

Time

Priority

Description

13/03/2020 21:58:39

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

11/03/2020 00:27:53

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

10/03/2020 20:32:38

notice

DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

10/03/2020 20:32:38

Error

DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

10/03/2020 15:37:16

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

10/03/2020 12:34:21

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

10/03/2020 00:51:20

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/03/2020 08:06:20

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/03/2020 00:40:10

notice

DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/03/2020 00:40:10

Error

DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

05/03/2020 17:10:6

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

02/03/2020 09:28:40

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 21:40:8

notice

DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 21:40:8

Error

DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 21:21:49

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 20:14:50

notice

DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 20:14:50

Error

DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 20:03:33

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 19:22:20

notice

DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

29/02/2020 19:22:20

Error

DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;



Please advise what my next step is.  I look forward to hearing from you.

0 Kudos
Reply
Highlighted
  • 2.75K
  • 164
  • 350
Trouble shooter
547 Views
Message 4 of 11
Flag for a moderator

Re: Random high pings causing connection issues

Set up a Broadband Quality Monitor (BQM) at thinkbroadband.com - this will give you an insight into what is happening with the signal at the Hub, it will take a few hours to get any kind of trend showing.

Post a link to your BQM on here.

Instructions for posting BQM Link

Under your BQM graph are two links in red.

Click the lower link (Share Live Graph) then click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see.

On here click the Link icon (2 link chain)

 In the URL box paste the link you copied and then click OK

***********************************************************************************************************************************

Mike Robinson


Ex UK Armed Forces
Computer Based Training and Learning Designer for many of the world's Military Arms.
0 Kudos
Reply
Highlighted
  • 21
  • 0
  • 0
Joining in
519 Views
Message 5 of 11
Flag for a moderator

Re: Random high pings causing connection issues

0 Kudos
Reply
Highlighted
  • 905
  • 64
  • 84
Forum Team
Forum Team
400 Views
Message 6 of 11
Flag for a moderator

Re: Random high pings causing connection issues

Hi RyanR,

 

Thanks for posting on our community page. Sorry to hear that you're having issues with drops out and latency problems. We know how frustrating this can be.

 

We appreciate you showing us your network logs, and upon checking our systems from our back office here and everything is showing as normal, we have no reported issues or area faults either.

 

Can you let us know if anything has changed your end since you last post?

 

Kind regards Jodi

 

0 Kudos
Reply
Highlighted
  • 21
  • 0
  • 0
Joining in
393 Views
Message 7 of 11
Flag for a moderator

Re: Random high pings causing connection issues

No, still having problems.

0 Kudos
Reply
Highlighted
  • 905
  • 64
  • 84
Forum Team
Forum Team
384 Views
Message 8 of 11
Flag for a moderator

Re: Random high pings causing connection issues

Thanks for coming back to us RyanR,

 

Can we ask how your gaming station is connected? Also are you using a 3rd party router at all? If so are you able to remove this and run a speed test using our equipment only?

 

We also would like to know if you are using a VPN?

 

Kind regards Jodi

 

 

0 Kudos
Reply
Highlighted
  • 21
  • 0
  • 0
Joining in
376 Views
Message 9 of 11
Flag for a moderator

Re: Random high pings causing connection issues

Yes, there is a third party router (draytek), and yes this is a problem regardless.  This is not a speed issue.  99% of the time, the link is spot on and running a random speed check will prove nothing.  As you can see even from the ping logs on post 1, the link will be perfect and then I'll hit a random pocket of high and non-responsive pings.  I have moved back onto your superhub and will monitor the BQM for a bit and see what happens.

And I have VPN, but it's only ever used when I need to access my work network which isn't often (it's not a product like PIA for example, it's a private one).

0 Kudos
Reply
Highlighted
  • 21
  • 0
  • 0
Joining in
375 Views
Message 10 of 11
Flag for a moderator

Re: Random high pings causing connection issues

0 Kudos
Reply