High ping Vodafone Gigafast

[pauliuslt8]

Hi. vodafone gigafast 500mbps plan, upload & download speeds are okay 531mbps.  Ping never go lover then 12ms usually 15ms. Whit old copper broadband ping was 8ms. Way ping its so high? 

[flilot]

Pings to where exactly?  Have you any examples? 
Remember the Gigafast network is mostly CityFibre up until they hand off to Vodafone's network so latency could be on the CityFibre side of things.

If you do some traceroutes/pings and post the results here, being on a GigaFast connection myself I can do the same ones and look for any disparities. 

[pauliuslt8]

sorry forgot attach screenshot 12ms at the moment. probably best results in past 2 weeks  https://ibb.co/3ycX0tZ

[clint_flick]

Hi

My GoTo pings are

C:\>ping 13.107.4.52

Minimum = 17ms, Maximum = 20ms, Average = 18ms

C:\>ping bbc.co.uk

Minimum = 18ms, Maximum = 28ms, Average = 22ms

Now the BBC is 60/80 miles away?  ms.edge is Redmond US of A some 4700 miles away.

But you wouldn't know from the ping times.

tracert is 8 hops to the BBC and 9 hops to Redmond.

So I try to use those 2 as my benchmark pingTO places.

[flilot]

My pings to the same places on a Gigafast connection:

PING bbc.co.uk (151.101.0.81): 56 data bytes

64 bytes from 151.101.0.81: icmp_seq=0 ttl=58 time=8.842 ms

64 bytes from 151.101.0.81: icmp_seq=1 ttl=58 time=8.276 ms

64 bytes from 151.101.0.81: icmp_seq=2 ttl=58 time=8.163 ms

64 bytes from 151.101.0.81: icmp_seq=3 ttl=58 time=9.091 ms

64 bytes from 151.101.0.81: icmp_seq=4 ttl=58 time=8.903 ms

64 bytes from 151.101.0.81: icmp_seq=5 ttl=58 time=9.817 ms

64 bytes from 151.101.0.81: icmp_seq=6 ttl=58 time=9.163 ms

64 bytes from 151.101.0.81: icmp_seq=7 ttl=58 time=9.129 ms

64 bytes from 151.101.0.81: icmp_seq=8 ttl=58 time=7.986 ms

64 bytes from 151.101.0.81: icmp_seq=9 ttl=58 time=8.710 ms

PING reddit.com (151.101.1.140): 56 data bytes

64 bytes from 151.101.1.140: icmp_seq=0 ttl=58 time=11.323 ms

64 bytes from 151.101.1.140: icmp_seq=1 ttl=58 time=9.808 ms

64 bytes from 151.101.1.140: icmp_seq=2 ttl=58 time=8.923 ms

64 bytes from 151.101.1.140: icmp_seq=3 ttl=58 time=8.236 ms

64 bytes from 151.101.1.140: icmp_seq=4 ttl=58 time=9.622 ms

64 bytes from 151.101.1.140: icmp_seq=5 ttl=58 time=9.419 ms

64 bytes from 151.101.1.140: icmp_seq=6 ttl=58 time=10.389 ms

64 bytes from 151.101.1.140: icmp_seq=7 ttl=58 time=8.166 ms

64 bytes from 151.101.1.140: icmp_seq=8 ttl=58 time=9.423 ms

64 bytes from 151.101.1.140: icmp_seq=9 ttl=58 time=8.542 ms

PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: icmp_seq=0 ttl=119 time=10.429 ms

64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=9.631 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=9.678 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=9.676 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=9.473 ms

64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=9.045 ms

64 bytes from 8.8.8.8: icmp_seq=6 ttl=119 time=10.896 ms

64 bytes from 8.8.8.8: icmp_seq=7 ttl=119 time=9.121 ms

64 bytes from 8.8.8.8: icmp_seq=8 ttl=119 time=9.743 ms

64 bytes from 8.8.8.8: icmp_seq=9 ttl=119 time=10.068 ms

They all vary from 7-11ms.  Your area of the network may just be busier causing more latency, or your connection may be taking a longer route than mine. For example if you're in Scotland, and you're pinging down to London, the latency will be higher than me pinging London from the Midlands in England. 

[pauliuslt8]

i am from Peterborough, testing local server or located in Cambridge still give me 12ms-14ms ping. 

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=13ms TTL=118
Reply from 8.8.8.8: bytes=32 time=13ms TTL=118
Reply from 8.8.8.8: bytes=32 time=13ms TTL=118
Reply from 8.8.8.8: bytes=32 time=13ms TTL=118

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 13ms, Average = 13ms          

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=12ms TTL=58
Reply from 151.101.0.81: bytes=32 time=12ms TTL=58
Reply from 151.101.0.81: bytes=32 time=12ms TTL=58
Reply from 151.101.0.81: bytes=32 time=14ms TTL=58

Ping statistics for 151.101.0.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 14ms, Average = 12ms

Tracing route to bbc.co.uk [151.101.128.81]
over a maximum of 30 hops:

1 1 ms   1 ms   <1 ms 192.168.1.1
2 12 ms 12 ms 12 ms 84.65.64.1    mine default getaway
3 12 ms 12 ms 12 ms 63.130.104.198
4 13 ms 12 ms 13 ms ae11-100-xcr1.hex.cw.net [195.89.96.1]
5 22 ms 12 ms 12 ms ae17-xcr1.ltw.cw.net [195.2.28.150]
6 * * * Request timed out.
7 12 ms 12 ms 12 ms 151.101.128.81

Trace complete.

[Evie]

Hey @pauliuslt8, thank you for the screenshots and all of the info.

If you find your Ping is higher than expected, I would advised speaking with our Gigafast team on 191 or 0333 304 0191 as they will be able to run through some tests with your broadband 😊

[cowabunga]

The server that you are pinging is based in the USA. Not the UK, (151.101.64.81) BBC = US Based server

You should ping a UK server to get a more accurate speed time

[purrbox]

Look at the 2nd hop on your traceroutes. Notice how it's around 10ms (it should be much less at this stage), that is the latency that is added before it's handed over from Cityfibre to Vodafone. That might not seem like a high number on it's own, but when you add that onto where you're actually pinging it is. 

If you compare your gigafast (city fibre) line to a standard vodafone VDSL line you will always see this extra 10ms on your pings. Ping any server and this can easily be proven. Vodafone host their own speedtest.net server so the pings should be 2 - 3 ms but because of the CityFibre issue they are always > 10ms 

I've spoken with an engineer at City Fibre and  he agreed there is clearly an issue, the problem is they can't work on it until Vodafone 2nd line support issue City Fibre with a ticket.

As the issue is within City Fibre's network (before it gets handed off to the Vodafone gateway), there's nothing Vodafone can really do apart from send support tickets to City Fibre. Therefore, we need to do something to get this resolved.

Encourage everyone to get this escalated. Judging by the traceroutes posted, it would appear you all have this issue.

[purrbox]

Bumping this thread for more exposure.