Menu
Reply
  • 242
  • 2
  • 47
LokiDog
Superfast
838 Views
Message 1 of 106
Flag for a moderator

Wigan WN6, getting annoying

Connection is not good tonight, not good at all.

5157136102

It's not been great for a while.

1d74c73e08db8616c7a9b4377167f775-10-03-2016

 

If I max my connection out with the current <=3mb I'm getting using speedtest.net web pages crawl in.

Have a gander at this ping to bbc, started just before a speed test of 3.47 Mbps down and 1.90 Mbps up

C:\>ping bbc.co.uk -n 40 -l 64

Pinging bbc.co.uk [212.58.244.23] with 64 bytes of data&colon;
Reply from 212.58.244.23: bytes=64 time=25ms TTL=53
Reply from 212.58.244.23: bytes=64 time=27ms TTL=53
Reply from 212.58.244.23: bytes=64 time=26ms TTL=53
Reply from 212.58.244.23: bytes=64 time=159ms TTL=53
Reply from 212.58.244.23: bytes=64 time=23ms TTL=53
Reply from 212.58.244.23: bytes=64 time=22ms TTL=53
Reply from 212.58.244.23: bytes=64 time=240ms TTL=53
Reply from 212.58.244.23: bytes=64 time=254ms TTL=53
Reply from 212.58.244.23: bytes=64 time=297ms TTL=53
Reply from 212.58.244.23: bytes=64 time=696ms TTL=53
Reply from 212.58.244.23: bytes=64 time=752ms TTL=53
Reply from 212.58.244.23: bytes=64 time=723ms TTL=53
Reply from 212.58.244.23: bytes=64 time=929ms TTL=53
Reply from 212.58.244.23: bytes=64 time=852ms TTL=53
Reply from 212.58.244.23: bytes=64 time=749ms TTL=53
Reply from 212.58.244.23: bytes=64 time=742ms TTL=53
Reply from 212.58.244.23: bytes=64 time=893ms TTL=53
Reply from 212.58.244.23: bytes=64 time=841ms TTL=53
Reply from 212.58.244.23: bytes=64 time=869ms TTL=53
Reply from 212.58.244.23: bytes=64 time=819ms TTL=53
Reply from 212.58.244.23: bytes=64 time=839ms TTL=53
Reply from 212.58.244.23: bytes=64 time=910ms TTL=53
Reply from 212.58.244.23: bytes=64 time=572ms TTL=53
Reply from 212.58.244.23: bytes=64 time=424ms TTL=53
Reply from 212.58.244.23: bytes=64 time=130ms TTL=53
Reply from 212.58.244.23: bytes=64 time=25ms TTL=53
Reply from 212.58.244.23: bytes=64 time=24ms TTL=53
Reply from 212.58.244.23: bytes=64 time=26ms TTL=53
Reply from 212.58.244.23: bytes=64 time=319ms TTL=53
Reply from 212.58.244.23: bytes=64 time=256ms TTL=53
Reply from 212.58.244.23: bytes=64 time=749ms TTL=53
Reply from 212.58.244.23: bytes=64 time=697ms TTL=53
Reply from 212.58.244.23: bytes=64 time=463ms TTL=53
Reply from 212.58.244.23: bytes=64 time=637ms TTL=53
Request timed out.
Reply from 212.58.244.23: bytes=64 time=111ms TTL=53
Reply from 212.58.244.23: bytes=64 time=255ms TTL=53
Reply from 212.58.244.23: bytes=64 time=89ms TTL=53
Reply from 212.58.244.23: bytes=64 time=166ms TTL=53
Reply from 212.58.244.23: bytes=64 time=266ms TTL=53

Ping statistics for 212.58.244.23:
Packets: Sent = 40, Received = 39, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 929ms, Average = 433ms

 A ping when no one is using this vast amount of bandwidth is as so:

Ping statistics for 212.58.244.23:
Packets: Sent = 40, Received = 39, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 765ms, Average = 57ms

 

If the green box was open outside my house I would be tempted to unplug everyone for having the cheek to use all the width of bands. Surely there is enough to go around and it is just the odd one using it all for themselves ............ or maybe as there is only 3Mbps left for me of the 50 I should have it's purely that there are 100 people too many on it. Bloody subcribers, coming here taking my Mbps.

And will you please, please, please tell the techs that come out to stop swapping people on bad feeds for people on good feeds, they are just passing the problem along.

I know they do this, last one that came to me put me on a good one under a hoard of cables in the far corner that was trciky to get at, saying it 'may' stay there as they change the ones that are easiest to get at.

It's not right that I have to rush to the pc and check power levels and speed if I happen to see them messing in the box.

  • 242
  • 2
  • 47
LokiDog
Superfast
831 Views
Message 2 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

Joy of Joys, it took a while to post that.

Current ping to bbc.

C:\>ping bbc.co.uk -n 40 -l 64

Pinging bbc.co.uk [212.58.246.79] with 64 bytes of data&colon;
Reply from 212.58.246.79: bytes=64 time=391ms TTL=54
Reply from 212.58.246.79: bytes=64 time=452ms TTL=54
Reply from 212.58.246.79: bytes=64 time=608ms TTL=54
Reply from 212.58.246.79: bytes=64 time=517ms TTL=54
Reply from 212.58.246.79: bytes=64 time=396ms TTL=54
Reply from 212.58.246.79: bytes=64 time=403ms TTL=54
Reply from 212.58.246.79: bytes=64 time=558ms TTL=54
Reply from 212.58.246.79: bytes=64 time=725ms TTL=54
Reply from 212.58.246.79: bytes=64 time=514ms TTL=54
Reply from 212.58.246.79: bytes=64 time=343ms TTL=54
Reply from 212.58.246.79: bytes=64 time=406ms TTL=54
Reply from 212.58.246.79: bytes=64 time=603ms TTL=54
Reply from 212.58.246.79: bytes=64 time=619ms TTL=54
Reply from 212.58.246.79: bytes=64 time=640ms TTL=54
Reply from 212.58.246.79: bytes=64 time=763ms TTL=54
Reply from 212.58.246.79: bytes=64 time=611ms TTL=54
Reply from 212.58.246.79: bytes=64 time=478ms TTL=54
Reply from 212.58.246.79: bytes=64 time=706ms TTL=54
Reply from 212.58.246.79: bytes=64 time=586ms TTL=54
Reply from 212.58.246.79: bytes=64 time=562ms TTL=54
Reply from 212.58.246.79: bytes=64 time=689ms TTL=54
Reply from 212.58.246.79: bytes=64 time=569ms TTL=54
Reply from 212.58.246.79: bytes=64 time=531ms TTL=54
Reply from 212.58.246.79: bytes=64 time=608ms TTL=54
Reply from 212.58.246.79: bytes=64 time=544ms TTL=54
Reply from 212.58.246.79: bytes=64 time=517ms TTL=54
Reply from 212.58.246.79: bytes=64 time=493ms TTL=54
Reply from 212.58.246.79: bytes=64 time=699ms TTL=54
Reply from 212.58.246.79: bytes=64 time=570ms TTL=54
Reply from 212.58.246.79: bytes=64 time=904ms TTL=54
Reply from 212.58.246.79: bytes=64 time=737ms TTL=54
Reply from 212.58.246.79: bytes=64 time=599ms TTL=54
Reply from 212.58.246.79: bytes=64 time=627ms TTL=54
Reply from 212.58.246.79: bytes=64 time=609ms TTL=54
Reply from 212.58.246.79: bytes=64 time=540ms TTL=54
Reply from 212.58.246.79: bytes=64 time=587ms TTL=54
Reply from 212.58.246.79: bytes=64 time=623ms TTL=54
Reply from 212.58.246.79: bytes=64 time=605ms TTL=54
Reply from 212.58.246.79: bytes=64 time=476ms TTL=54
Reply from 212.58.246.79: bytes=64 time=512ms TTL=54

Ping statistics for 212.58.246.79:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 343ms, Maximum = 904ms, Average = 573ms

 

and speed test just after

5157261844

 

 

 

0 Kudos
Reply
  • 5.32K
  • 169
  • 353
Moderator
Moderator
813 Views
Message 3 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

Hi LokiDog,

 

I'm sorry to see your connection was so poor last night, I'd like to see what's caused that, the ping graph in particular doesn't look too clever.

 

I've run some initial diagnostics on the hub and network segment, the hub looks OK, although there is an issue during peak times on the local cable.  I'm not sure whether or not you knew about this already, but our engineers are planning to undertake some broadband upgrades to support an increased demand for our services in your area.  Once this issue is resolved, you'll find that any slow speeds you suffer (especially during peak times) will be resolved.  The reference for this ongoing work is F003478328 and the current review date is 30/03/2016.

 

Your ping graph does show the problem extending beyond peak times, is that a common occurrence, or was it just yesterday?  Do you find rebooting the hub ever helps the situation?  I'm going to send you a PM (purple envelope, top right) with some further info about the peak time issue, including details of how to claim a credit for loss of service.

Kev

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply
  • 242
  • 2
  • 47
LokiDog
Superfast
798 Views
Message 4 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

The graph has been the norm for quite a while.

It did get better after a reboot of the modem, it normally doesn't make any difference.

This is tonights, very slow again

 

e8cce730ca356b8db93f101863efdb0a-11-03-2016

 

0 Kudos
Reply
  • 553
  • 16
  • 190
Parki79
Rising star
774 Views
Message 5 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

That is exactly like mine in Golborne. I know quite a few people in Goose Green who as having those kinds of speeds.

 

Have you had some money refunded yet as you are not receiving the money you are paying for. It could take years for them to get around to fixing it because you are not in a new area so you do not matter.




I am in a Virgin Over Utilised Area - F003476231 - Never Ending Fault.
0 Kudos
Reply
  • 242
  • 2
  • 47
LokiDog
Superfast
742 Views
Message 6 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

 

There is a credit that has been placed on my bill for £7.50, it's suppposed to be a rolling credit until the review date.

The review date so far is 30/3/16, so at the moment it's not going to roll so far....unless the review date gets pushed back.

What do you reckon are the chances of that happening on a scale of 1 to 5:

1. Not a chance in hell, Virgin Media always stick to dead lines and are true to their word.

2. There is a chance it will be pushed back due to the Great Crested Tree Warbler building a nest in a cabinet, but unlikely.

3. Planning permission takes time to get, they've only had a year, give them a chance.

4. Schrödinger's review date, the review date is simultaneously true and untrue. Once the review date is met reality splits into two with one reality getting the fix and the other an extended review date.

5 . The review date is a McGuffin, it's simply there to keep you interested and means nothing, after all, they didn't say they was going to fix it, just take another look at it.

  • 553
  • 16
  • 190
Parki79
Rising star
721 Views
Message 7 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

Planning permission excuse is nonsense. I work in planning in Telecoms and even with road closures it isnt a big process these days.

Untill Virgin actually tell us we will never know why they are so reluctant. The only thing I have been told is due to the staff being tied up as part of the project of connecting new areas and such. This doesnt make sense when they use subbies though.

Seems unlikely that you will be done by the 30/3/16 with the bank holiday weekend. If they can push a date back 4 or 5 times with little explanation there is nothing to stop them from doing it another 4 or 5 times.

 

 




I am in a Virgin Over Utilised Area - F003476231 - Never Ending Fault.
  • 242
  • 2
  • 47
LokiDog
Superfast
699 Views
Message 8 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

As the review date has now passed I was wondering if by any chance there is an update???

0 Kudos
Reply
  • 5.32K
  • 169
  • 353
Moderator
Moderator
685 Views
Message 9 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

Hi LokiDog,

 

Thanks for bumping the thread, I've checked the latest on F003478328, it does look like work is ongoing.  The review date has now been set to 03/08/2016 to allow more work to take place.

 

I'm sorry for the ongoing issues, I've also sent you a PM with a bit of info about this, we'll keep an eye on things and let you know once we receive a further update.

Kev

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


  • 553
  • 16
  • 190
Parki79
Rising star
681 Views
Message 10 of 106
Flag for a moderator

Re: Wigan WN6, getting annoying

With that review date getting pushed so far back I can't imagine there are many reasons for people to stay. It will only get worse for you guys each week as it becomes more and more over utilized. Probably time to call it a day as VM obviously do not care.

Hope you guys find something better as you deserve better.




I am in a Virgin Over Utilised Area - F003476231 - Never Ending Fault.
0 Kudos
Reply