We're always working to improve on our services and products, but at this moment I wouldn't be able to offer you a definitive date or timeframe as to when available speeds and capacity in your area will increase. Apologies.
Thanks for your response, Zach.
Of course, it is disappointing to hear that VMO2 can't even put a date to when this fault can be resolved especially since your CEO was making a big point about the speed increases in the area back in November.
Virginmediao2 connects Macclesfield to gigabit broadband
I note the specific references to Bollington in the article
- Bollington and Prestbury all now gigabit ready
As part of today’s gigabit switch-on, Virgin Media O2 has upgraded thousands of homes in Bollington and Prestbury to gigabit speeds.
As you can probably understand, I can't commit to another 18 month tie in without some equivalent commitment from VMO2.
In any case, recent announcements from Openreach would seem to make this a moot point since Bollington has been specifically targeted for FTTP rollout in the next year or so.
Ultrafast Full Fibre broadband Build Programme January 2022
Regarding the speeds, do you have any other devices you can test the speeds on to see if they're also impacted? Can you also confirm any other troubleshooting and diagnostics you've performed thus far in an effort to remedy this?
I have one high powered gaming desktop and two other laptops with gigabit cable ethernet interfaces that all show similar results...
400-600Mb/s during the day
200-400Mb/s during the evening
620-650Mb/s at night.
I have done the usual Hub3 reboots, factory resets, switch to and from modem/router mode but as you probably realise this won't have any impact on the wider issues in the are, which are out of my control.
It's also more that a little disingenuous to suggest that problems with my equipment or test methods are the cause of the M350 restrictions in my area.
Finally, a simple acknowledgment that there is a fault on my local network segment would go someway to make me consider staying with (or even ever returning to) VMO2.