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

Ask

2

Reply

3

Solution

Gigafast Slow Speeds

jasperb182
3: Seeker
3: Seeker

Hello All

I have had the vodafone Gigafast 900mb service in Milton Keynes now for about 3 months and am getting only 500-600mb download speed on my PCs. My router is detecting the speed at 1000mb. 

 

I have had a vodafone tech out but they have said that it is a known windows 10 issue.

I have updated all of the LAN drivers on all 3 of my PCs and replaced all of the network cables with Cat6, I have even upgraded the rubbish vodafone router with a Top of the Line Netgear XR500 but am still getting the slow speeds.

On the plus side my upload is around 1600mb

Has anyone else had this issue or any ideas on how to rectify this please.

I really dont need that much speed but as im paying for it it would be nice to get it working

Thanks Marc

 

30 REPLIES 30

Blair
Moderator (Retired)
Moderator (Retired)

Hey @jasperb182 did you contact our dedicated Gigafast team about this at all?

They've got the tools to test your service to see what's causing the bottleneck with your speed.

 

Blair

Blair
Moderator (Retired)
Moderator (Retired)

Hey @jasperb182, our Gigafast broadband has a dedicated team that will be able to help.  You can contact the Gigafast support team buy caling 191, free from a Vodafone mobile. Also you can call 03333 040 191 from other UK landlines or mobiles (standard call charges apply)

 

Blair

Mozambezi
4: Newbie

Through Speeds for me on 100 Mb line (non issues )

Download around 30Mbp/s 

Upload 110 Mbp/s

 

Regular line drops  and server disconnections when gaming. It is not line related but Exchange oversubscribed.

 

Generally I feel cheated. First 3-4 months it was 100/100 

Hi. Cheated sounds a bit strong! It's still much better service and probably cheaper than what you were paying before?! Take care how you measure it as well. SpeedTest and the like aren'e always the most accurate. Are you on the Vodafone supplied router? I've not had any drops since a 1 day outage a few months ago (see separate post). I'd be surprised too if the Exchange was oversubscribed for FTTP. That was a common problem for FTTC connections but the numbers for FTTP in MK are a lot lower at the current time. 

mbames
13: Advanced Member

Could someone on VodaFone's GigaSlow service post a couple of traceroutes.

 

bbc.co.uk

img.com

reddit.com

ookla.btlancashire.co.uk

speedtest.vodafone.co.uk

 

It would be interestsing to see if they route traffic over the same shonky network that the FTTC users are forced to use.

Here are a few of those. Wireless onto the Gigafast100 service

 

$ traceroute bbc.co.uk

traceroute: Warning: bbc.co.uk has multiple addresses; using 151.101.192.81

traceroute to bbc.co.uk (151.101.192.81), 64 hops max, 52 byte packets

1  192.168.50.1 (192.168.50.1)  4.591 ms  10.882 ms  3.903 ms

2  host-212-158-250-36.dslgb.com (212.158.250.36)  9.731 ms  22.872 ms  8.453 ms

3  63.130.104.198 (63.130.104.198)  8.783 ms  49.539 ms  8.628 ms

4  ae11-100-xcr1.hex.cw.net (195.89.96.1)  14.997 ms  10.636 ms  22.757 ms

5  lag-10.ear1.london1.level3.net (4.68.72.93)  10.181 ms  12.295 ms  10.176 ms

6  ae-1-3112.edge6.london1.level3.net (4.69.141.246)  10.153 ms

    ae-2-3212.edge6.london1.level3.net (4.69.141.250)  9.935 ms

    ae-1-3112.edge6.london1.level3.net (4.69.141.246)  17.942 ms

7  * * *

8  * * *

9  * * *

10  * * *

^C

$ traceroute speedtest.vodafone.co.uk

traceroute to speedtest.vodafone.co.uk (212.183.159.229), 64 hops max, 52 byte packets

1  192.168.50.1 (192.168.50.1)  4.517 ms  2.317 ms  4.018 ms

2  host-212-158-250-36.dslgb.com (212.158.250.36)  26.133 ms  25.647 ms  8.128 ms

3  63.130.104.198 (63.130.104.198)  62.239 ms  10.466 ms  13.589 ms

4  213.185.195.233 (213.185.195.233)  10.819 ms  10.743 ms  28.005 ms

5  * * *

6  * * *

^C

$ traceroute ookla.btlancashire.co.uk

traceroute to ookla.btlancashire.co.uk (194.150.176.123), 64 hops max, 52 byte packets

1  192.168.50.1 (192.168.50.1)  4.331 ms  3.974 ms  3.876 ms

2  host-212-158-250-36.dslgb.com (212.158.250.36)  8.789 ms  8.037 ms  8.528 ms

3  63.130.104.198 (63.130.104.198)  8.914 ms  18.192 ms  18.844 ms

4  linx-gw1.ja.net (195.66.224.15)  10.193 ms  10.663 ms  15.372 ms

5  ae23.londtt-sbr1.ja.net (146.97.35.169)  12.047 ms  10.871 ms  10.332 ms

6  ae27.erdiss-sbr2.ja.net (146.97.33.14)  14.604 ms  14.756 ms  15.133 ms

7  ae29.manckh-sbr2.ja.net (146.97.33.42)  18.695 ms  15.651 ms  23.228 ms

8  ae25.manckh-ban1.ja.net (146.97.35.50)  15.062 ms  16.537 ms  18.893 ms

9  lancs-council.manckh-ban1.ja.net (146.97.40.50)  14.938 ms  15.379 ms  15.411 ms

10  * * *

11  * * *

12  *^C

Chriss-MacBook-Pro-2:~ christagg$

High ping and delays on Vodafone exchange hub.  No problems before and after. It just confirming what I said. VF infrastructure slowing down internet  traffic

This timing is not look so good. I was thinking to swap ISP and become gigafast customers, but my actuall ping looks better with PlusNet at the moment;

traceroute speedtest.vodafone.co.uk
traceroute to speedtest.vodafone.co.uk (212.183.159.229), 30 hops max, 60 byte packets
1 router (192.168.1.1) 0.316 ms 0.373 ms 0.443 ms
2 gi12-0-1-451.ptn-ag04.plus.net (84.93.253.80) 4.869 ms 4.880 ms 5.054 ms
3 84.93.253.87 (84.93.253.87) 5.830 ms 5.919 ms 6.055 ms
4 195.99.125.136 (195.99.125.136) 5.770 ms core1-be1.colindale.ukcore.bt.net (195.99.125.132) 5.983 ms 195.99.125.144 (195.99.125.144) 6.387 ms
5 peer7-et-0-1-1.telehouse.ukcore.bt.net (109.159.252.148) 6.080 ms peer7-et-3-0-1.telehouse.ukcore.bt.net (109.159.252.152) 6.434 ms peer7-et-4-1-4.telehouse.ukcore.bt.net (194.72.16.140) 6.286 ms
6 166-49-128-32.eu.bt.net (166.49.128.32) 6.795 ms 52.184 ms 6.056 ms
7 166-49-211-254.eu.bt.net (166.49.211.254) 5.643 ms 5.065 ms 8.203 ms
8 ae9-xcr1.lsh.cw.net (195.2.25.169) 5.344 ms 5.347 ms 5.403 ms

*

*

 

traceroute bbc.co.uk
traceroute to bbc.co.uk (151.101.192.81), 30 hops max, 60 byte packets
1 router (192.168.1.1) 0.303 ms 0.376 ms 0.448 ms
2 gi12-0-1-451.ptn-ag04.plus.net (84.93.253.80) 5.873 ms 6.453 ms 6.462 ms
3 84.93.253.83 (84.93.253.83) 10.421 ms 84.93.253.87 (84.93.253.87) 10.490 ms 10.435 ms
4 core1-be1.colindale.ukcore.bt.net (195.99.125.132) 10.252 ms 195.99.125.144 (195.99.125.144) 10.533 ms 195.99.125.140 (195.99.125.140) 10.312 ms
5 peer7-et-7-0-1.telehouse.ukcore.bt.net (109.159.252.92) 10.572 ms peer2-et3-1-4.slough.ukcore.bt.net (62.172.103.220) 10.670 ms 194.72.16.58 (194.72.16.58) 10.699 ms
6 * * *
7 * * *
8 * * *

ping bbc.co.uk
PING bbc.co.uk (151.101.64.81) 56(84) bytes of data.
64 bytes from 151.101.64.81: icmp_seq=1 ttl=58 time=4.73 ms
64 bytes from 151.101.64.81: icmp_seq=2 ttl=58 time=4.28 ms
64 bytes from 151.101.64.81: icmp_seq=3 ttl=58 time=5.00 ms

 

traceroute google.co.uk
traceroute to google.co.uk (216.58.206.99), 30 hops max, 60 byte packets
1 router (192.168.1.1) 0.262 ms 0.359 ms 0.432 ms
2 gi12-0-1-451.ptn-ag04.plus.net (84.93.253.80) 5.377 ms 5.371 ms 5.393 ms
3 84.93.253.87 (84.93.253.87) 6.194 ms 84.93.253.83 (84.93.253.83) 6.032 ms 84.93.253.87 (84.93.253.87) 6.222 ms
4 core1-be1.colindale.ukcore.bt.net (195.99.125.132) 6.070 ms 6.090 ms 195.99.125.144 (195.99.125.144) 5.995 ms
5 peer2-et0-1-4.slough.ukcore.bt.net (62.172.103.208) 7.069 ms 194.72.16.58 (194.72.16.58) 7.079 ms peer7-et-0-1-1.telehouse.ukcore.bt.net (109.159.252.148) 6.530 ms
6 peer2-xe3-1-3.telehouse.ukcore.bt.net (109.159.253.5) 7.143 ms 109.159.253.235 (109.159.253.235) 5.206 ms 109.159.253.71 (109.159.253.71) 5.665 ms
7 * * *
8 172.253.71.200 (172.253.71.200) 7.364 ms 172.253.50.222 (172.253.50.222) 6.202 ms 64.233.175.106 (64.233.175.106) 7.991 ms
9 74.125.242.82 (74.125.242.82) 6.173 ms 216.239.58.223 (216.239.58.223) 6.549 ms 7.331 ms
10 lhr25s14-in-f3.1e100.net (216.58.206.99) 6.456 ms 6.467 ms 216.239.58.131 (216.239.58.131) 7.134 ms

 

ping google.co.uk
PING google.co.uk (216.58.206.99) 56(84) bytes of data.
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=1 ttl=54 time=6.35 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=2 ttl=54 time=6.25 ms
64 bytes from lhr25s14-in-f3.1e100.net (216.58.206.99): icmp_seq=3 ttl=54 time=6.72 ms

 

Looks like you are routing those tests via PlusNet so surely that's not a representative test of Vodafone Gigafast?

All standard, all working . I'm IT engineer. What follows from your reply - here is a traffic management in place. I like to watch IP HD TV.

 

In comparison with EE or BT broadband VF is cheaper indeed. But if I'm limited to 34 Mbps then it is more expensive than EE. Well ping now is 5ms against 9ms I had before.