Connected at last, ping times are a huge disappointment though

Help and support
1

Finally got connected, might take up to 72 hours to switch to a static ip though, hoping it doesn’t take that long to be honest!

One thing I’m not happy about is the latency, that’s almost tripled, was getting 4-5ms ping to bbc site, 6ms to google on my old giganet connection, bbc site is now 15ms on average, 21ms to google! I play a lot of fps multiplayer games and need the lowest ping I can get, are those ping times down to being on the initial 154.56.254.xxx range & will it improve once I’m moved over to a static ip which will be in the new 217 range.

Edit : Now been moved to 217.180.37.xxx, is that one of your static ips?

2

Welcome to Yayzi :slight_smile:

Firstly, you will not notice a difference between 6ms and 21ms. The difference in ping will be due to different routes to the internet via peers.

The human brain typically can’t perceive differences in latency below about 20-30ms. Both 6ms and 21ms are below this threshold.

As for the static, I’m not sure this will have to answered by @Yayzi_Team

3

Your right in a way but it’s still disappointing to see that latency being reported, especially when I’ve always had around 5ms with my previous isp & I see other yayzi users reporting similar low pings.

2 Likes
5

Tested on my pc connected by ethernet, would never test ping over a wireless connection. Might setup a think broadband ping trace to monitor it.

Routing was my first thought once I saw the increase so I ran a tracert to check, it’s high from the very first hop.

6

217 is static - Is the latency lower? - I don’t think we’ve ever had an issue with latency before, we’ve always had fairly low latency (area dependent)

7

Hi,

Ping to bbc remained the same, google dropped from low 20s to 13/14ms on average after the IP change. I’d seen comments on this community I think and on reddit of people posting latency info from their connection and it was in single digits, that’s why I was a bit surprised to see it so high (relatively speaking). I’m in Weston-Super-Mare, North Somerset.

8

Hi Frostie36

I am on the 141.11.200.xxx range and my pings for bbc & google are 16-17ms average on each. I’m not quite sure what you are expecting but the pings on Yayzi are more then adequate. I dont struggle to do anything on my connection from streaming to gaming.

9

Hi @Frostie36

I am on the 141.11.200.xxx range and my pings for bbc & google are 11-12ms average on each. I’m not quite sure what you are expecting but the pings on Yayzi are more then adequate. I dont struggle to do anything on my connection from streaming to gaming.

10

Which router are you using?

I’m on 141.11.200.xx and get decent latency to both google and bbc.

image
image817×980 16.6 KB

11

what I was expecting was latency at least as good my previous isp, sadly that’s not the case.

12

Now that’s the latency I was expecting to see, I’m using an Asus GT-AXE16000, tracert show zero latency being introduced by the router as expected.

The ip address of the bbc & google sites is slightly different for me though.

{835B8946-AB7D-4754-9EE5-C710A4B1BDF0}
{835B8946-AB7D-4754-9EE5-C710A4B1BDF0}1007×784 23.7 KB

13

Ping the same IP addresses as in my screenshot to see if its any different, could be that you are routing to a slightly different CDN.

14

Interesting as back in August my pings more than doubled for 2 or 3 days before going back down to what they were beforehand, so something was going on there. I think @CraigT1976 is having similar sorts of issues now as well.

15

just pinged the same ip addresses, no change in latency.

16

I seem to remember @mikekilley being in Weston Super mare, if @mikekilley could provide ping outputs and its the same 12-14ms, its likely it’s routing in that area.

17

Similar size pings for me here also in Weston-super-Mare, using an Asus ZenWiFi Pro ET12 on a wired connection.

image

18

Thanks for sharing that info Mike, maybe yayzi can look into their routing in our area.

1 Like
19

I am yes unfortunately, mine changed a few weeks ago overnight and have not improved since :confused:

20

Have you tried ipv6 ping? You might see better results with:
ping -6 bbc.co.uk

21

Use WinMTR and let it run for 60 seconds, and then report back the results. It’ll help highlight which hops where the issue could be, as the issue could be past Yayzi’s network.

Not on Yayzi, but your not that far from London, so I would of expected sub 10ms to bbc.co.uk. Could be the CityFibre network is taking a long way around, but not sure if Yayzi can do much about that, but MTR may help more.

I’m assuming Yayzi LNS is in the London area, like Telehouse or something like that.