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

Ask

2

Reply

3

Solution

Ping/Latency way higher Gigafast 900

htyaH
13: Advanced Member

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?

768 REPLIES 768

Jayach
16: Advanced member
16: Advanced member

@purrbox wrote:

It didn't contain anything like that. It was just a summary of a phone call I had with the support team explaining the issues and the solution they are working on.


Was it this one, it seemed to suddenly appear, it may have been caught by the filter because of the phone number.

Re: Ping/Latency way higher Gigafast 900 - Page 26 - Community home (vodafone.co.uk)

Anonymous
Not applicable

@Jayach  "Was it this one, it seemed to suddenly appear, it may have been caught by the filter because of the phone number."

 

If this is @purrbox  missing evidence, it doesn't match the original assertion that CityFibre was causing countrywide issues because of problems with its main hub. The assertion, until I pointed out that my ping was perfect, was that "Every single voda customer on city fibre has the high pings".   Purrbox is now merely reporting an upgrade to the street box and to numerous street boxes across the country.   Why didn't he say that in the first place, because that is something we all knew already? In any case, unless someone tells me different, CityFibre upgrading street boxes has nothing to do with Vodafone's routing issues.

The problem is caused by city fibre as it's city fibre who own the cabinets and connect people to the appropriate BNG's. This is what vodafone told me, if that's incorrect I apologise but both Vodafone and city fibre have now told me this.

 

When I last called I again mentioned the city fibre engineer thinks pings upto 100ms are normal and acceptable. The Vodafone engineer said that's not normal but the fact remains this is city fibres view. Other people in this thread have also been told the same thing by city fibre. That's what continues to worry me. 

 

The city fibre engjneer told him in the chat that they are upgrading our local box and we will continue to be routed via Manchester until the work is done.

 

Having thought about it, I've had the problem for over 6 months now and the fact cityfibre don't care about pings, I think I / vodafone was probably just fobbed off again.

 

I feel arguing over who's fault it is doesn't really help us the end users. Ultimately, there are still people on BNG's miles away from their location and that needs to be fixed.

 

My only hope is this thread remains alive until someone senior at Vodafone picks this up and contacts cityfibre and demand that all customers are routed by their local BNG. This will fix the high pings.

Ripshod
16: Advanced member
16: Advanced member

"The problem is caused by city fibre" 

It's vodafone doing the routing though. It's vodafone who are "load balancing" while servers are upgraded, and not Cityfibre who have zero direct access to Vodafone infrastructure. 

I still don't understand the blame going on Cityfibre when openreach customers are affected too.

You're either the target of a massive hoax or you're just plain making this up. 

Here's a trace route run  from my routers network tools page. I'm not making it up. What would be the point?

 

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 * * *
2 63.130.105.134 (63.130.105.134) 22.494 ms 22.407 ms 22.332 ms
3 90.255.251.2 (90.255.251.2) 23.620 ms 72.14.216.236 (72.14.216.236) 26.100 ms 90.255.251.2 (90.255.251.2) 23.549 ms
4 * * *
5 dns.google (8.8.8.8) 22.825 ms 22.813 ms 22.797 ms

 

It's just not good enough for what I need. My old BT copper connection had pings that were a fraction of this. I can't wait for this contract to expire.

Ripshod
16: Advanced member
16: Advanced member

How does that prove it's Cityfibre's fault? It's non-specific.

We want your evidence. 

[Removed]

[MOD EDIT: This post has been edited to remove inappropriate content, please see Community Guidelines]

Ripshod
16: Advanced member
16: Advanced member

I'll jump on anyone suggesting only Cityfibre clients are affected on a thread where it's already proven that openreach clients are also affected.

I want this thread to stay on track - it's helped me and it will help others. 

Jayach
16: Advanced member
16: Advanced member

@purrbox wrote:

I'm beginning to think you work for city fibre as you seem obsessed in jumping on anybody that says anything negative about them.


@purrbox 

Sorry are you suggesting we all work for CityFibre? There is nobody here who agrees with your opinion it is CityFibre at fault. I personally am just sick and tired of correcting you, so haven't said anything. (recently)

[Removed]

[MOD EDIT: This post has been edited to remove inappropriate content, please see Community Guidelines]