Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

High Ping on Hell Let Loose (PC).

aphex187
On our wavelength

on ‎03-05-2022 12:00

Hi guys,

When joining a UK/EU and the server is around half capacity say 30 players my ping sits around 56. As soon as the server fills up to a 100 my ping shoots up from 88 to 100 and will fluctuate around those and will not drop below. I tried CS Source and my ping was A OK on that with me hitting around 18 but again the player count on those types of servers is real low compared to something like HLL.

I'm running a wired connection from a Hub 4 on a Gig1 connection.

P.S. also seeing dropouts on my wifi soundbar and I'm also seeing streaming lose quality from time to time when watching films.

Cheers for any help on this matter 🙂

0 Kudos
20 REPLIES 20

aphex187
On our wavelength

on ‎03-05-2022 12:02

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

92030000007.30000338.983261QAM2569
81950000007.40000238.983261QAM2568
102110000007.19999738.983261QAM25610
112190000007.30000338.983261QAM25611
122270000007.09999838.983261QAM25612
132350000006.90000238.983261QAM25613
142430000007.00000038.983261QAM25614
152510000007.09999838.983261QAM25615
162590000007.19999740.366287QAM25616
172670000006.90000238.605377QAM25617
182750000006.90000238.983261QAM25618
192830000007.09999838.605377QAM25619
202910000007.30000338.605377QAM25620
212990000007.69999740.366287QAM25621
223070000007.69999740.366287QAM25622
233150000007.40000240.366287QAM25623
243230000007.09999838.983261QAM25624
253310000007.00000038.983261QAM25625
263390000006.59999838.605377QAM25626
273470000006.59999838.983261QAM25627
283550000006.80000338.983261QAM25628
293630000006.80000338.983261QAM25629
303710000006.50000038.983261QAM25630
313790000006.30000338.983261QAM25631
11390000009.69999738.983261QAM2561
21470000009.50000038.983261QAM2562
31550000009.50000038.983261QAM2563
41630000009.00000038.983261QAM2564
51710000008.50000040.366287QAM2565
61790000008.00000040.366287QAM2566
71870000008.09999838.983261QAM2567



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

9Locked38.98326100
8Locked38.98326100
10Locked38.98326100
11Locked38.98326100
12Locked38.98326100
13Locked38.98326100
14Locked38.98326100
15Locked38.98326100
16Locked40.36628700
17Locked38.60537700
18Locked38.98326100
19Locked38.60537700
20Locked38.60537700
21Locked40.36628700
22Locked40.36628700
23Locked40.36628700
24Locked38.98326100
25Locked38.98326100
26Locked38.60537700
27Locked38.98326100
28Locked38.98326100
29Locked38.98326100
30Locked38.98326100
31Locked38.98326100
1Locked38.98326100
2Locked38.98326100
3Locked38.98326100
4Locked38.98326100
5Locked40.36628700
6Locked40.36628700
7Locked38.98326100



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1880QAM4096424


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked426.919878579950
0 Kudos

aphex187
On our wavelength
In response to aphex187

on ‎03-05-2022 12:03

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

13940000032.5205995120 KSym/sec64QAM4
24620000033.0205995120 KSym/sec64QAM3
35370000034.0205995120 KSym/sec64QAM2
46030000034.5205995120 KSym/sec64QAM1



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0010
3US_TYPE_STDMA0010
4US_TYPE_STDMA0000
0 Kudos

aphex187
On our wavelength
In response to aphex187

on ‎03-05-2022 12:03

Time Priority Description

Wed Apr 20 00:46:45 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:46:47 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:47:53 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:47:55 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:50:05 20223DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:50:31 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:51:52 20223DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:52:02 20223Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:52:21 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:53:30 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:53:32 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:55:44 20223DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:55:51 20223Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:56:40 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:56:44 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:57:15 20223SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:57:21 20225Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 00:58:48 20223Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:09:58 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:11:08 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:11:10 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:12:23 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:12:26 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:13:27 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:13:29 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:14:36 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:14:39 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:15:50 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:16:16 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:17:27 20225B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:17:28 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:18:33 20223DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:18:44 20223Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:20:05 20223DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:20:16 20223Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 20 01:20:30 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

carl_pearce
Community elder
In response to aphex187

on ‎03-05-2022 12:05

 

@aphex187 wrote:

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

13940000032.5205995120 KSym/sec64QAM4
24620000033.0205995120 KSym/sec64QAM3
35370000034.0205995120 KSym/sec64QAM2
46030000034.5205995120 KSym/sec64QAM1



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0010
3US_TYPE_STDMA0010
4US_TYPE_STDMA0000

Are you in a FTTP or coax-fibre hybrid area?

The reason I ask is your upstream power levels are quite low, depending on the area you are in.

aphex187
On our wavelength
In response to carl_pearce

on ‎03-05-2022 12:14

Thanks for the quick reply mate!

I'm not sure on that one. How would I find out? I'm in the Teesside area (Stockton-on-tees).

0 Kudos

carl_pearce
Community elder
In response to aphex187

‎03-05-2022 12:23 - edited ‎03-05-2022 12:24

@aphex187 wrote:

Thanks for the quick reply mate!

I'm not sure on that one. How would I find out? I'm in the Teesside area (Stockton-on-tees).

Does your internal wall socket require a powered connection?

aphex187
On our wavelength
In response to carl_pearce

on ‎03-05-2022 14:13

Sorry for the late reply, no it doesn't.

0 Kudos

carl_pearce
Community elder
In response to aphex187

on ‎03-05-2022 19:22

@aphex187 wrote:

Sorry for the late reply, no it doesn't.

In that case your upstream power levels are too low and need to be corrected by an engineer visit.

aphex187
On our wavelength
In response to carl_pearce

on ‎03-05-2022 22:15

Only had a couple of Engineers out not so long ago as well.

Cheers for getting back though Carl, appreciate it 😉

0 Kudos
Top