Virgin Media Community

[whippyice]

So the net where i am has been fine up until just after Christmas, 

But then all of a sudden high and wild ping spikes, call of duty is literally unplayable on pc/xbox/ps4 rainbow six is the same, and basically anything with the need for good ping. 

i work from home as a IT service desk engineer so i have a fairly good understanding of what im looking at but frankly i can't see any issues with my end, i even went and spent silly money on a RX700 with mesh and although it tamed the wildness of the ping a little it's still impossible to play anything, 

i've missed out on the entier  last end of season 2 and all of season 3 of COD MW and i just need this working now, 

Voip calls dropping, for work slow RDP's aswell, 

Hub3 in Modem mode, details below 

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)	723000000	Locked
Ranged Upstream Channel (Hz)	39400000	Locked
Provisioning State	Online

Back

Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	723000000	2.9	38	256 qam	40
2	539000000	2.7	38	256 qam	17
3	547000000	2.4	38	256 qam	18
4	555000000	2.5	38	256 qam	19
5	563000000	2.7	38	256 qam	20
6	571000000	2.7	38	256 qam	21
7	579000000	2.4	38	256 qam	22
8	587000000	2.4	38	256 qam	23
9	595000000	2.5	38	256 qam	24
10	603000000	2.5	38	256 qam	25
11	611000000	2.5	38	256 qam	26
12	619000000	2.2	38	256 qam	27
13	627000000	2.2	38	256 qam	28
14	635000000	2.2	38	256 qam	29
15	643000000	2.2	38	256 qam	30
16	651000000	2.4	38	256 qam	31
17	659000000	2.5	38	256 qam	32
18	667000000	2.7	38	256 qam	33
19	675000000	3.2	38	256 qam	34
20	683000000	3.2	38	256 qam	35
21	691000000	3.2	38	256 qam	36
22	699000000	3.2	38	256 qam	37
23	707000000	3.2	38	256 qam	38
24	715000000	3	38	256 qam	39

Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	38.9	169	0
2	Locked	38.6	105	0
3	Locked	38.6	108	0
4	Locked	38.6	134	0
5	Locked	38.9	136	0
6	Locked	38.6	135	0
7	Locked	38.9	136	0
8	Locked	38.6	124	0
9	Locked	38.6	129	0
10	Locked	38.6	136	0
11	Locked	38.9	108	0
12	Locked	38.9	117	0
13	Locked	38.6	134	0
14	Locked	38.6	157	0
15	Locked	38.9	131	0
16	Locked	38.6	134	0
17	Locked	38.9	142	0
18	Locked	38.9	150	0
19	Locked	38.9	147	0
20	Locked	38.9	162	0
21	Locked	38.9	179	0
22	Locked	38.9	167	0
23	Locked	38.9	202	57
24	Locked	38.9	225	0

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

1	39400000	4.2	5120	64 qam	2
2	25800000	4.2	5120	64 qam	4
3	32600000	4.2	5120	64 qam	3
4	46200000	4.2	5120	64 qam	1

[David_Bn]

Good Afternoon whippyice,

Thanks for your post and a very warm welcome to you!

Sorry to see that you've been having issues with your broadband services. 

Have you been advised that we've been experiencing high utilisation in your local area from 19/02 and until the estimated fix time and date of 03/06 15:00?

Beyond 3pm today, it may be worth resetting your router and coming back to us to see if this has been resolved

Kindest regards,

David_Bn

[whippyice]

ok ill give it a reset and confirm back in a few 

[whippyice]

Unfortunately its the same infact i got an even worse ping in COD but that might be due to the time of day,
145ms ping

[whippyice]

tested again this morning, 

5am to 7am really good, 

after 7am starting to break down, by 9, unplayable, 

i dont know what it is they are trying to do to fix this issue, but their either not doing it right or demand is outpacing their fix, which leaves us in the the same situation. 

it can't continue like this i've already had a letter through the door from CityFiber and frankly at the price they are offering at the speed they are offering its a sure thing right now. 

Pinging www.google.com [216.58.198.164] with 32 bytes of data:
Reply from 216.58.198.164: bytes=32 time=78ms TTL=53
Reply from 216.58.198.164: bytes=32 time=27ms TTL=53
Reply from 216.58.198.164: bytes=32 time=57ms TTL=53
Request timed out.
Reply from 216.58.198.164: bytes=32 time=143ms TTL=53
Reply from 216.58.198.164: bytes=32 time=30ms TTL=53
Reply from 216.58.198.164: bytes=32 time=44ms TTL=53
Reply from 216.58.198.164: bytes=32 time=61ms TTL=53
Reply from 216.58.198.164: bytes=32 time=49ms TTL=53
Reply from 216.58.198.164: bytes=32 time=86ms TTL=53
Reply from 216.58.198.164: bytes=32 time=68ms TTL=53
Reply from 216.58.198.164: bytes=32 time=21ms TTL=53
Reply from 216.58.198.164: bytes=32 time=27ms TTL=53
Reply from 216.58.198.164: bytes=32 time=388ms TTL=53
Reply from 216.58.198.164: bytes=32 time=50ms TTL=53
Reply from 216.58.198.164: bytes=32 time=172ms TTL=53
Reply from 216.58.198.164: bytes=32 time=40ms TTL=53
Reply from 216.58.198.164: bytes=32 time=48ms TTL=53
Reply from 216.58.198.164: bytes=32 time=25ms TTL=53
Reply from 216.58.198.164: bytes=32 time=112ms TTL=53
Reply from 216.58.198.164: bytes=32 time=22ms TTL=53
Reply from 216.58.198.164: bytes=32 time=45ms TTL=53
Reply from 216.58.198.164: bytes=32 time=204ms TTL=53
Reply from 216.58.198.164: bytes=32 time=19ms TTL=53
Reply from 216.58.198.164: bytes=32 time=214ms TTL=53
Reply from 216.58.198.164: bytes=32 time=75ms TTL=53
Reply from 216.58.198.164: bytes=32 time=53ms TTL=53
Reply from 216.58.198.164: bytes=32 time=30ms TTL=53
Reply from 216.58.198.164: bytes=32 time=29ms TTL=53
Reply from 216.58.198.164: bytes=32 time=265ms TTL=53
Reply from 216.58.198.164: bytes=32 time=50ms TTL=53
Reply from 216.58.198.164: bytes=32 time=44ms TTL=53
Reply from 216.58.198.164: bytes=32 time=142ms TTL=53
Reply from 216.58.198.164: bytes=32 time=22ms TTL=53
Reply from 216.58.198.164: bytes=32 time=26ms TTL=53
Reply from 216.58.198.164: bytes=32 time=33ms TTL=53
Reply from 216.58.198.164: bytes=32 time=94ms TTL=53
Reply from 216.58.198.164: bytes=32 time=270ms TTL=53
Reply from 216.58.198.164: bytes=32 time=153ms TTL=53
Reply from 216.58.198.164: bytes=32 time=44ms TTL=53
Reply from 216.58.198.164: bytes=32 time=30ms TTL=53

[hortonj88]

estimated fix time and date of 03/06 15:00?

"estimated".

[whippyice]

related record if anyone wanted to look at it is F007793688 for one of the guys who also live in my area (literally just down my street) 

[Melissa_F]

Thanks whippyice. 

I've had a look and the estimated fix time is now 24/06 at 15:00.

Apologies.

Thanks

Melissa 

[whippyice]

Blimy another 20 days. really ? 

pffffff, it wouldn't be so bad if i could go out and enjoy my evenings, or work from my office and not have these issues when im trying to talk to someone and i miss every 5th word 

can you see about having this improved ? 

[Melissa_F]

I know I can really understand that. 

Our team will do all they can to get this resolved as soon as possible.

Thanks

Melissa