cancel
Showing results for 
Search instead for 
Did you mean: 

Lag issues which have only recently started happening!

TiPs1
Joining in

Hi, Over the last 1-2 weeks I have noticed I have started getting a lag on my hard wired connection on Xbox on the likes of Call of Duty and kids having issues on Fortnite. I have since ran a BQM for the last few days and noticed I am getting random spikes in latency which roughly matches the time we have issues while gaming and getting lag spikes.

I am not sure if its a network issue or what. I have checked the cable in my house which is only like 1m long as the entry point is right next to the router and the cable is tight. I have even changed ethernet cables just as a precaution but still no change.

Please see below my BQMs for the past few days and my router stats, hopefully its a simple fix (I have rebooted the router etc which hasn't helped. I even disconnected the VM cable and reconnected but nope.

I have also noticed in the Hub 5 log over the last day I have a few entries saying: DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value

Hub 5 with 1gig connection.

25/01/2024

TiPs1_0-1706528173372.png

26/01/2024

TiPs1_1-1706528213102.png

27/01/2024 (Red will be when I disconnected everything and made sure all cables were secure)

TiPs1_4-1706528350072.png

28/01/2024

TiPs1_3-1706528296070.png

29/01/2024 (until 11:40am)

 

TiPs1_6-1706528414401.png

 

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1427000000-1.840QAM 25637
22110000001.841QAM 25610
32190000001.641QAM 25611
42270000001.541QAM 25612
52350000001.341QAM 25613
62430000000.741QAM 25614
72510000000.140QAM 25615
82590000000.240QAM 25616
92670000000.641QAM 25617
102750000000.440QAM 25618
112830000000.441QAM 25619
122910000000.441QAM 25620
132990000000.441QAM 25621
143070000000.341QAM 25622
153150000000.240QAM 25623
163230000000.140QAM 25624
173310000000.240QAM 25625
183390000000.240QAM 25626
193470000000.241QAM 25627
203550000000.341QAM 25628
213630000000.341QAM 25629
22371000000-141QAM 25630
23379000000-1.840QAM 25631
24387000000-240QAM 25632
25395000000-240QAM 25633
26403000000-1.940QAM 25634
27411000000-2.140QAM 25635
28419000000-240QAM 25636
29435000000-240QAM 25638
30443000000-1.940QAM 25639
31451000000-1.640QAM 25640

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4000
2Locked4100
3Locked4100
4Locked4100
5Locked4100
6Locked4100
7Locked4000
8Locked4000
9Locked4100
10Locked4000
11Locked4100
12Locked4100
13Locked4100
14Locked4100
15Locked4000
16Locked4000
17Locked4000
18Locked4000
19Locked4110
20Locked4100
21Locked4110
22Locked4100
23Locked4020
24Locked4010
25Locked4000
26Locked4000
27Locked4010
28Locked4010
29Locked4040
30Locked4030
31Locked4000

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159944K1840QAM 40961108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
159Locked40-3.731204976857152

 

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000051.55120QAM 641
14310000050.85120QAM 642
23660000050.55120QAM 643
330100000505120QAM 644
423600000495120QAM 645

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
61046.02KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA20074000000100
22 REPLIES 22

TiPs1
Joining in

Network Log

Time Priority Description
28-01-2024 19:30:55warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 19:30:55noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 18:21:34noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 18:21:34warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 14:58:45noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 14:58:45warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 13:50:07noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 13:50:07warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:51:53noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:51:53warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:21:20noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:21:20warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:20:55warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:20:55noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:20:31warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:20:04criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:19:54criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:34:02warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:34:02noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:58noticeREGISTRATION COMPLETE - Waiting for Operational status
27-01-2024 13:33:53warningDynamic Range Window violation
27-01-2024 13:33:53warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:53warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:53warningDynamic Range Window violation
27-01-2024 13:33:53warningDynamic Range Window violation
27-01-2024 13:33:53warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:52warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:46noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:39warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:37noticeHonoring MDD; IP provisioning mode = IPv4
27-01-2024 13:33:21criticalCable Modem Reboot because of - HW or Power-On Reset
27-01-2024 13:33:21criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

TiPs1
Joining in

Just to add, I have also checked the service status phone number and online and no faults for broadband have been raised in my area.

I just find it strange that this has only happened within the last 1-2 weeks which is making me think something has been done in the area.

TiPs1
Joining in

Went on the Virgin Media website last night to check again the service status and to check for any faults on my line. It prompted I had to factory reset my hub for some reason which I have done. After the reset the connection was even worse and to the point I just stopped playing online games as no matter what game I played I was getting spikes of lag. Looking at the graph it also shows spikes which I am guessing is what I was experiecing. Can someone from Virgin please take a look at my connection and my area as this has only started happening within the last 1-2 weeks! - Connection was perfect before then and nothing in my home has changed. Always have been hardwired.

Latest Graph for the last 24hrs

TiPs1_0-1706607520143.png

 

TiPs1
Joining in

Disapointed someone from Virgin has still not messaged regarding this issue I am having. Its clear as day its mostly happening at peak times which is making me think its a Utilisation issue as its mostly always happening during peak times. See below my latest BQM results and also my latest router logs and power levels.

Tuesday 30/01/2024

TiPs1_1-1706775200349.png

Wednesday 31/01/2024

TiPs1_2-1706775267070.png

Thursday 01/02/2024  (upto 8am) (Some sort of outage during the night)

TiPs1_3-1706775349168.png

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
12350000001.141QAM 25613
21390000002.340QAM 2561
31470000002.240QAM 2562
41550000002.140QAM 2563
51630000001.740QAM 2564
61710000001.540QAM 2565
71790000001.340QAM 2566
81870000001.440QAM 2567
91950000001.541QAM 2568
102030000001.441QAM 2569
112110000001.541QAM 25610
122190000001.341QAM 25611
132270000001.341QAM 25612
142430000000.541QAM 25614
152510000000.140QAM 25615
162590000000.140QAM 25616
172670000000.341QAM 25617
182750000000.141QAM 25618
192830000000.141QAM 25619
202910000000.141QAM 25620
212990000000.141QAM 25621
22307000000040QAM 25622
233150000000.140QAM 25623
243230000000.340QAM 25624
253310000000.540QAM 25625
263390000000.440QAM 25626
273470000000.441QAM 25627
283550000000.541QAM 25628
293630000000.541QAM 25629
30371000000-1.141QAM 25630
31379000000-2.140QAM 25631
32387000000-2.340QAM 25632

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4110
2Locked4050
3Locked4050
4Locked4098
5Locked4057
6Locked4057
7Locked4086
8Locked40127
9Locked4178
10Locked4148
11Locked4188
12Locked41128
13Locked4167
14Locked4199
15Locked4038
16Locked4080
17Locked4180
18Locked4150
19Locked4130
20Locked4160
21Locked4140
22Locked4030
23Locked4060
24Locked4070
25Locked40120
26Locked4050
27Locked4120
28Locked4120
29Locked4110
30Locked4110
31Locked4020
32Locked4000

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159944K1840QAM 40961108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
159Locked40-3.934647702794307

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000051.35120QAM 641
14310000050.55120QAM 642
23660000050.35120QAM 643
330100000505120QAM 644
42360000048.85120QAM 645

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA01520
1ATDMA01500
2ATDMA01500
3ATDMA01500
4ATDMA01550

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
61046.02KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA2007400000000

 

Network Log

Time Priority Description
01-02-2024 01:55:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:55:22criticalNo Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:55:00warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:55:00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:54:00noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:54:00warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:56criticalNo Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:56noticeREGISTRATION COMPLETE - Waiting for Operational status
01-02-2024 01:53:56warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:47warningDynamic Range Window violation
01-02-2024 01:53:47warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:46warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:46warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:46warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:46warningDynamic Range Window violation
01-02-2024 01:53:46warningDynamic Range Window violation
01-02-2024 01:53:46warningDynamic Range Window violation
01-02-2024 01:53:46warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:41noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:34warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:31noticeHonoring MDD; IP provisioning mode = IPv4
01-02-2024 01:50:46criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:50:45criticalSYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:50criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:49criticalSYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:26criticalSYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:24:15criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:24:11warningToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:24:10criticalReceived 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;
01-02-2024 01:23:50criticalReceived 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;
01-02-2024 01:23:50criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

TiPs1
Joining in

Bufferbloat Test at 11:25am (01/02/2024)

 

TiPs1_0-1706786766046.png

BQM so far for today 01/02/2024 (11:30am)

TiPs1_1-1706786998854.png

 

jpeg1
Alessandro Volta

Apart from the gap at 2am which was probably network switching, your BQM isn't bad. Those spikes probably coincide with something else on your own network. Do a couple of speedtests and you'll see spikes like those. 

- jpeg1
My name is NOT Alessandro. That's just a tag Virginmedia sticks on some contributors. Please ignore it.

The BQM is bad enough to affect my gaming online which I said previously has started with these lag spikes within the last 1-2 weeks. Peak times has become a joke and occassional rubber banding on games. Spikes are showing on the BQM when no one is using the broadband ... especially very late at night and early morning it spikes but everyone is asleep. Something has happened within the last 1-2 weeks in my area which is effecting my network now. No changes have been made in my house

jpeg1
Alessandro Volta

I don't doubt that you are having gaming problems with lagging. I'm only saying that your BQM is not a particularly bad one, and better than many.

- jpeg1
My name is NOT Alessandro. That's just a tag Virginmedia sticks on some contributors. Please ignore it.

legacy1
Alessandro Volta

You think how many packets of coordinated player positioning and firing of a gun happens in just one second that you go from 20mins-40 max ms to 100ms delay and normally more its a problem its the consistency of the connection that the server must depend on some jitter OK the odd spike thats not by much OK but when you push beyond that its a mess.

Like I know I'm doing everything possible to not cause a ping spike by doing BWM or QoS and being on the low speed to not be hit routers upstream from impacting the flow to me or from me but even now I spike high in BQM at times. 

---------------------------------------------------------------