Ping/Latency way higher Gigafast 900

[htyaH]

I used to get 5ms ping to London (from Coventry), now I am being auto connected to Edinburugh and I get 15 ping to there, when I try to speedtest to London or even right next to me in Leicester I am getting pings above 22...I called in and they just said "they added new servers and there's nothing much we can do"...

any help?

[purrbox]

I'll be going straight back to BT infinity copper 80mb / 20mb. 

Before moving to Vodafone, I was with BT for over 10 years and everything always went through my local BNG and then London telehouse.

I did phone BT tech support just to check that this weird routing thing wasn't some kind of new UK trend. They confirmed that BT would never ever route someone via Edinburgh and that be would considered a serious network fault prompting immediate resolution.

[Gerry_Atric]

I have mentioned before that the routing changes happened because of congestion on the network and VF's complaints team confirmed that they were due to upgrade connectivity to the BNGs to 10Gb links. Once done they said routing would return to normal. Obviously it's an individual decision as to whether or not it's worth waiting for that to be done before jumping ship. 

Disadvantage with Openreach FTTP products is that you will sacrifice upload bandwidth as you will on VM too. They are not symmetrical like CF and other alt nets are. 

[Anonymous]

@purrbox wrote, "He (the CEO's office) stated that the BNG's are in fact owned by city fibre (we know this isn't true) and anybody who posts in this forum stating otherwise should be ignored as they do not work at Vodafone."

I'm not sure why 'he' should tell you that the BNGs are owned by CF when everybody knows they are not. Why would VF carry out publicly announced trials of disaggregated broadband gateway with Nokia, Cisco if CF owned the BNGs? Disaggregated BNG Trial  

I find your account bizarre,  as I do the rest of the story about the long-term  migration of  increasing numbers of clients up to Edinburgh for their BNG.  If that is your reason for leaving VF when you had concluded earlier that the issue was only with one of your connections, I think you are leaving for no good reason, especially since the Openreach alternative will give you only 110Mb upstream in their 900Mb product. 

Good luck anyway.

 

[Jayach]

@purrbox says they are going back to FTTC, not FTTP on Openreach.

But yes, why believe what the CEO office says, when you have proof it is not true.

[Dobs]

Figured I should post an update. At some point this week it's dropped me back onto a Birmingham one which, for now, has mostly resolved my latency issues:

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

  1    <1 ms    <1 ms    <1 ms  vodafone.broadband [192.168.1.1]
  2     4 ms     3 ms     4 ms  84.65.192.1
  3     7 ms     7 ms     7 ms  63.130.172.37
  4    11 ms    11 ms    10 ms  90.255.251.117
  5     7 ms     7 ms    12 ms  151.101.64.81

Trace complete.

Hopefully others in the Midlands might see an improvement too if VF's work is potentially complete?

[prs1000]

---

@Dobs wrote:

Figured I should post an update. At some point this week it's dropped me back onto a Birmingham one which, for now, has mostly resolved my latency issues:

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

  1    <1 ms    <1 ms    <1 ms  vodafone.broadband [192.168.1.1]
  2     4 ms     3 ms     4 ms  84.65.192.1
  3     7 ms     7 ms     7 ms  63.130.172.37
  4    11 ms    11 ms    10 ms  90.255.251.117
  5     7 ms     7 ms    12 ms  151.101.64.81

Trace complete.

Hopefully others in the Midlands might see an improvement too if VF's work is potentially complete?

---

I'm in Worcester. I'd love to be routed through Birmingham. Fingers crossed 😉

[Jayach]

I think (hope) eventually we will all be on the most suitable gateways. Until the next time.

[Anonymous]

@Dobs Yes, that looks pretty normal for those of us on Birmingham. I'm in Coventry. Ping to the Beeb is 6ms as it is to 1.1.1.1 and 8.8.8.8. 

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

1 <1 ms <1 ms <1 ms GT-AX11000-CBB0 [192.168.1.1]
2 3 ms 3 ms 2 ms 84.65.192.1
3 6 ms 7 ms 6 ms 63.130.172.37
4 10 ms 10 ms 10 ms 90.255.251.117
5 11 ms 5 ms 5 ms 151.101.128.81

Trace complete.

[ZinGeRs]

Numbers I can only dream of in Nottingham albeit the best I have seen in ages but a far cry from my 5ms max before August

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

1 <1 ms <1 ms <1 ms TUF-AX5400-8608 [192.168.0.1]
 2 13 ms 11 ms 12 ms 84.65.0.1
3 12 ms 13 ms 13 ms 63.130.172.27
4 15 ms 14 ms 14 ms 90.255.251.103
5 14 ms 13 ms 12 ms 151.101.128.81

Trace complete.

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms TUF-AX5400-8608 [192.168.0.1]
2 14 ms 12 ms 12 ms 84.65.0.1
3 12 ms 27 ms 41 ms 63.130.127.213
4 13 ms 14 ms 14 ms 90.255.251.31
5 17 ms 16 ms 16 ms 216.239.62.75
6 13 ms 13 ms 13 ms 142.251.52.145
7 15 ms 14 ms 13 ms dns.google [8.8.8.8]

Trace complete.

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TUF-AX5400-8608 [192.168.0.1]
2 13 ms 13 ms 14 ms 84.65.0.1
3 13 ms 14 ms 15 ms 63.130.105.130
4 14 ms 14 ms 25 ms 90.255.251.33
5 16 ms 20 ms 15 ms 141.101.71.2
6 17 ms 13 ms 14 ms one.one.one.one [1.1.1.1]

[purrbox]

Enjoy those pings whilst you can. As more people subscribe to FTTP gigafast, most of you will be moved onto Edinburgh which is to become the main (backup) BNG. When I first joined, my ping to the beeb was 5ms!

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

1 1 ms 1 ms 1 ms RT-AX92U-6090 [192.168.50.1]
2 122 ms 115 ms 115 ms 90.247.128.1
3 141 ms 122 ms 122 ms 63.130.172.35
4 * * * Request timed out.
5 * * * Request timed out.
6 126 ms 128 ms 127 ms 132.185.254.213
7 128 ms 131 ms 126 ms 132.185.254.2
8 * * * Request timed out.
9 127 ms 126 ms 127 ms ae2.er01.lbh.bbc.co.uk [132.185.249.7]
10 133 ms 138 ms 147 ms 132.185.252.126
11 127 ms 127 ms 126 ms 212.58.234.3
12 137 ms 127 ms 126 ms 212.58.233.254

Trace complete.

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms RT-AX92U-6090 [192.168.50.1]
2 123 ms 115 ms 115 ms 90.247.128.1
3 127 ms 128 ms 124 ms 63.130.105.134
4 142 ms 127 ms 125 ms 72.14.216.236
5 135 ms 127 ms 127 ms 216.239.42.41
6 143 ms 128 ms 126 ms 172.253.66.101
7 125 ms 125 ms 126 ms dns.google [8.8.8.8]

Trace complete.