Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GigabitEthernet]

I migrated to Zen yesterday and I have gone from a ping of about 30ms to 50ms. Interleaving was turned on when I had pings of 30ms so it can't be that. Any ideas?

[burakkucat]

Assuming you are using the same ping target, the most obvious reason could be different routing, perhaps? 

[kitz]

It could be the depth of interleaving that is slightly higher...  it could also depend on your location. 
Some of Zens gateways are in Manchester (or at least used to be - azakka correct me if Im wrong), in which case say you live in London, your routing could be going London -> Manchester -> London.  However 20ms is a bit high for what I'd expect that to be the cause.   

You could try a reconnect as they have a few gateways, some up north and some down south.   
You can usually tell from a tracert which gateway you connect via.   A treacert may also be able to identify where any latency is occurring.

[GigabitEthernet]

It's a bit odd. If I run a traceroute, I get pings of about 35ms, but if I use Pingtest.net, I get this:



Note: I used to get 30ms pings on this.

[GigabitEthernet]

Here's a traceroute:

traceroute to bbc.co.uk (212.58.241.131), 64 hops max, 72 byte packets
 1  home.gateway.home.gateway (192.168.1.254)  1.632 ms  1.015 ms  0.907 ms
 2  losubs.subs.dsl2.mbr-roch.zen.net.uk (62.3.82.19)  30.597 ms  32.067 ms  30.183 ms
 3  ae0.140.dr1.mbr-roch.zen.net.uk (62.3.80.141)  72.233 ms  29.203 ms  29.534 ms
 4  ae2-0.cr1.kp-leeds.zen.net.uk (62.3.80.70)  32.187 ms  30.818 ms  31.650 ms
 5  ge-3-1-0-0.cr2.kp-leeds.zen.net.uk (62.3.80.74)  30.854 ms  29.715 ms  30.894 ms
 6  ge-3-0-0-0.cr1.th-lon.zen.net.uk (62.3.80.78)  36.876 ms  36.415 ms  36.182 ms
 7  82.71.254.134 (82.71.254.134)  36.845 ms  35.744 ms  36.581 ms
 8  * * *
 9  ae1.er01.rbsov.bbc.co.uk (132.185.254.46)  100.030 ms  36.326 ms  37.132 ms
10  132.185.255.134 (132.185.255.134)  37.271 ms  37.055 ms  39.149 ms
11  212.58.241.131 (212.58.241.131)  36.244 ms  36.822 ms  37.049 ms

[.Griff.]

I've never found Pingtest.net to be all that reliable so I wouldn't place too much faith in it.

As Kitz touched upon there's different levels/depths at which interleaving can be applied to the connection which could explain the increase in latency as you've migrated from one ISP to another.

Either way you've only been with your new ISP for a day so I'd wait until a week is up before getting overly concerned.

Just for clarification who was your previous ISP? Was it another BTw reseller or an LLU provider by any chance?

[kitz]

Can you try a different server...   this is what I get at Newbury



This is what I really see
C:\Documents and Settings\kitz>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:

Reply from 212.58.241.131: bytes=32 time=13ms TTL=246
Reply from 212.58.241.131: bytes=32 time=13ms TTL=246
Reply from 212.58.241.131: bytes=32 time=13ms TTL=246
Reply from 212.58.241.131: bytes=32 time=13ms TTL=246

Ping statistics for 212.58.241.131:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 13ms, Average = 13ms


----------------
Edited to add.. 
I think theres definitely something wrong with the Newbury server its continually adding about 30+ ms to my ping time and showing increased jitter..  I cant get anything less than >40ms from newbury.

yet

[GigabitEthernet]

Just for clarification who was your previous ISP? Was it another BTw reseller or an LLU provider by any chance?

Vivaciti. They are a BTw reseller and I was on 20CN like I am now.

[GigabitEthernet]

Here's a Pingtest.net ping test from Maidenhead:

[kitz]

omg..  hmm thats better! Not!
 

I think, like griff says,  I'd believe what your own tracert is telling you.

[GigabitEthernet]

It's just very odd since Pingtest.net always gave the same results as pinging a website before!

Very odd!

[GigabitEthernet]

It's WiFi!!!!



It's odd because WiFi never made a difference before. Oh well, at least that solves the issue.

[GigabitEthernet]

Got even better:



(That is over LAN by the way).

[jeffbb]

Hi
I get this ping test from maidenhead



Then this speedtest with about double the ping ??



then ping the xilo server

C:\Users\jeff>ping www.xilo.net

Pinging xilo.net [91.199.78.20] with 32 bytes of data:
Reply from 91.199.78.20: bytes=32 time=38ms TTL=54
Reply from 91.199.78.20: bytes=32 time=40ms TTL=54
Reply from 91.199.78.20: bytes=32 time=41ms TTL=54
Reply from 91.199.78.20: bytes=32 time=41ms TTL=54

Ping statistics for 91.199.78.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 38ms, Maximum = 41ms, Average = 40ms

using RS to generate ping
Pinging xilo.net [91.199.78.20] with 32 bytes of data:
Reply from 91.199.78.20: bytes=32 time=39ms TTL=54
Reply from 91.199.78.20: bytes=32 time=52ms TTL=54
Reply from 91.199.78.20: bytes=32 time=40ms TTL=54

Ping statistics for 91.199.78.20:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 52ms, Average = 43ms
 
using RS to ping BBC
Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=41ms TTL=244
Reply from 212.58.241.131: bytes=32 time=38ms TTL=244
Reply from 212.58.241.131: bytes=32 time=37ms TTL=244

Ping statistics for 212.58.241.131:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 41ms, Average = 38ms

CMD

C:\Users\jeff>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=36ms TTL=244
Reply from 212.58.241.131: bytes=32 time=38ms TTL=244
Reply from 212.58.241.131: bytes=32 time=36ms TTL=244
Reply from 212.58.241.131: bytes=32 time=38ms TTL=244

Ping statistics for 212.58.241.131:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 38ms, Average = 37ms

Newbury seems to be inconsistent .

seems best to do own ping test.

The RS ping tab is quite handy 
Regards Jeff


edit duplicate
seems best to do own ping test.

[AdrianH]

There is only one way to get an accurate ping test and that is through the Command Prompt, preferably from Safe Mode with Networking.
The "Ping test " sites are meaningless as they go through your browser and any security products you run.  Ping the same server through 3 different browsers and you will see 3 different results.
Ping from many of the Speedtest.net sites via Opera is often 3 times the same ping to IP via CMD Prompt . There is a Speedtest.net server located only 8 miles from my home, the ping is 547ms .....  if I test Xilo in Manchester ping is only 32ms.
Forget Pingtest et al. they are useless.