Xbox one

[steve singh]

What latency rates are you getting on detailed network stats?

I'm getting 160ms on fibre - 16 meg down and 6 up?

Is that any good?

[mmm-five]

I'm on Virgin 120meg package and am seeing (although through a power line adapter)...

- Download speed: 90.77 Mbps (varies: 90-99 Mbps)
- Upload speed: 11.61 Mbps (stays around the 11 Mbps mark)
- Download packet loss: 0% (only ever seen 0%)
- Upload packet loss: 0% (only ever seen 0%)
- MTU: 1480 (stays the same)
- Latency: 175ms (varies: 160ms-180ms)

A speediest on a computer wired directly to the Superhub shows:
- Download speed: 121.84 Mbps
- Upload speed: 11.48 Mbps
- Ping: 30ms



The latency is probably this bad due to connecting to US servers. Hopefully once MS fix all the other issues with the XB1 then they'll also put some of their millions of servers in the EU (or maybe a few in each country).

Edited by mmm-five on Saturday 1st February 13:40

[MattyB_]

160 is pretty poor for twitch-based shooters. As mentioned, probably due to being US based.

I remember playing Counter-Strike back in the late 90's on 33.6 and getting 200-220ms

[steve singh]

Thanks gents.

When i ping bbc from my pc i get 18ms - not sure if that is good or not???

[TimmyWimmyWoo]

I read that the latency figure in the Xbox One dashboard is from pinging a US server, so it tends to be about 160ms for anyone in the UK. I get 160ms and I struggle to get connected at 4Mb here in the sticks.

[mmm-five]

steve singh said:

Thanks gents.

When i ping bbc from my pc i get 18ms - not sure if that is good or not???

That's fine.

Ping/latency are just measures of how long it takes to get from A-B.

The bigger the distance (not necessarily as the crow flies) then the bigger the latency/ping times.

So pinging your computer from another on the same household network might give you a 2ms response, but pinging the Mars rover may take almost 2,000,000ms



There are some flaws to this though, as networks will try to route your signal through the fastest/best it can, but don't always get it right, especially when there's a problem somewhere.

So, 160ms to a US server is about right.