cancel
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

High latency - new full fibre 910

superleeds
4: Newbie

Hello,

I'm suffering from really high pings and it's making online gaming difficult. I'm new to this service and voda so if anyone could advise what is happening that would be appreciated please.

Here's my trace route to bbc and it looks like I am connected to my local DC (Leeds) but the pings to it are really high. 

Tracing route to gtm-live.pri.bbc.co.uk [212.58.236.1]
over a maximum of 30 hops:

Tracing route to gtm-live.pri.bbc.co.uk [212.58.235.1]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms  [192.168.1.1]
2 121 ms 99 ms 107 ms 90.246.0.1
3 112 ms 112 ms 121 ms 63.130.172.37
4 * * * Request timed out.
5 * * * Request timed out.
6 114 ms 122 ms 121 ms 132.185.254.217
7 137 ms 128 ms 134 ms 132.185.254.14
8 143 ms 141 ms 133 ms ae1.pr01.eqsl.bbc.co.uk [132.185.249.13]
9 133 ms 134 ms 136 ms 132.185.249.71
10 168 ms 121 ms 114 ms 212.58.235.1

Thanks (in advance) for taking a look.

1 ACCEPTED SOLUTION

I think I'll be cancelling tomorrow and either trying another provider on City Fibre or seeing if Virgin want to make me an offer to stay with them.
Having looked into it, as was said in this thread, a lot of people having the same experience as us - weeks and weeks of it being great and then this. Support are of no use. Even in the bad days of Virgin Media, you could always escalate things and speak to a really expert but it seems Voda aren't bothered.

View solution in original position

54 REPLIES 54

DoctorHeadlock
4: Newbie

Join the club. I'm experiencing the exact same thing and even though I too am Leeds based, I'm connected to the London node for some reason. Ping spikes up from around 4pm and doesn't abate until gone 11. Support won't help because their tests only see if you have a connection at all rather than its latency. It's driving me insane as up until a few days ago it was completely fine.

That's not great to hear, and as if like clockwork, the pings to the Leeds DC are down to less than 10ms!
I'm still in my 14 day cooling period so may have to have a word with them.

Are you using your own router or theirs per chance? I'm using my own as it's frankly a million times better than theirs, but the staff really hate when you do that. They act like any problems are your fault rather than even entertain the possibility that the issue might be with them. I have a family member who actually works for Vodafone, not in the broadband area but still, one thing they have said for years is the two things Vodafone cares about least in the world is 1. Their staff and 2. Their customers.

My own, been using it years - an ASUS one. It's solid. Plus, nothing has changed at my end and the pings have visibility gone down as you say around 11pm. Is this every day or just the weekends? Reminds of issues with every company when broadband became a thing and they couldn't handle the volume of users at peak times but that was 20 years ago!

From what you say,  I suppose I may have been enticed by the low prices.

It literally only started on the 20th, it was completely rock solid with no issues up until then. I've never used an Asus router before, I'm personally on a Unifi Dream Machine Pro. Pure speculation but perhaps there is a degree of throttling happening to us for not using their equipment? Sounds conspiratorial but stranger things have happened.

I'm not sure, they do make it easy to use your own and even have the details on their website on how to go about getting the info you need. Never know though, maybe.

Ah, you see, 20th was when I was connected 😄 I must have done it.

Ah so it was you! You had to come along and ruin everything didn't you? 🤣🤣

How is yours right now? Looks like mine is starting to get bad again according to my BQM

1000037172.png

it's shocking!
Pinging gtm-live.pri.bbc.co.uk [212.58.235.1] with 32 bytes of data:
Reply from 212.58.235.1: bytes=32 time=142ms TTL=59
Reply from 212.58.235.1: bytes=32 time=196ms TTL=59
Reply from 212.58.235.1: bytes=32 time=127ms TTL=59
Reply from 212.58.235.1: bytes=32 time=172ms TTL=59

I was averaging around 11ms through the day.