Testing your connection and download speeds

[ichilton]

Wow, that's really good! - the adsl's we have at work are like 60ms to a well connected uk server so I was thinking 35ms was great but now you've said that it's only 'ok' :-)

[Saturday]

Originally Posted by ichilton

humm, i'm getting ~33ms,

I'm still getting sub 20ms pings so not sure why you're at 33ms

Is that a wired connection or wireless?

[ichilton]

Hi,

Odd - have tried wired and wired, Linux and Windows...

Here is a traceroute:

 Host                                                                                                                                                               Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. O2WirelessBox.lan                                                                                                                                                0.0%   140   86.7  51.1   2.3  99.9  30.3
 2. 87-194-96-1.bethere.co.uk                                                                                                                                        0.0%   140   27.0  27.7  26.6  31.8   0.8
 3. 10.1.2.169                                                                                                                                                      80.4%   139   33.7  33.9  33.0  40.4   1.4
 4. 83.245.126.93                                                                                                                                                    1.4%   139   41.6  40.9  32.7 178.5  24.4
 5. 212.58.238.129                                                                                                                                                   2.2%   139   32.9  34.3  32.4 140.9   9.8
 6. rdirslb0.thdo.bbc.co.uk                                                                                                                                          0.0%   139   33.8  33.2  32.3  36.5   0.5
 7. virtual3.rbsov.bbc.co.uk                                                                                                                                         0.0%   139   33.9  36.4  33.4 316.0  23.9

What do you see?

Thanks,

Ian

[Undecided adrian]

I take a different path from step 1-4 then converge on hop 5, so I would assume that the first 4 servers I go though are slightly less congested than the 4 that your on, but at the sub 50ms time range it is all very good.

[ichilton]

Interesting! - please could you post a traceroute?

Saturday - do you see the same as Adrian?

PS: That IP on hop 5 is owned by BBC - so I am obviously taking a whole different route through O2's network...

I assume you are both on O2 itself like me, rather than Be?

Thanks,

Ian

[Saturday]

Um - what are you trying to show with a traceroute (ICMP Time To Live)

If you want to see the routing then use a traceroute - and put up with the fact that some servers will see that as low priority traffic and fail to respond in a timely manner, or not at all.

If you want to measure ping times then use a ping (ICMP echo request) command.

With regard to your traceroute the first step is your router, the second where you break into the O2/Be network (i.e. where your exchange equipment routes to), the third is internal O2/Be routing, fourth is peering infrastructure, fifth and onwards is the BBC.

[ichilton]

Hi,

We know the ping times are higher for me - I was using traceroute to see the route and work out why mine was higher (which is obviously because i'm going a different route to you guys).

Please could you post a traceroute so I can see your path?

Thanks,

Ian

[Saturday]

Originally Posted by ichilton

(which is obviously because i'm going a different route to you guys).

Not "obviously" at all. Ping times are affected by many factors with the routing being possibly the more minor one.

Your route is taking just 7 hops in total, which is very short. Mine is taking 6 as I'm not hopping through the peering infrastructure. The peering infrastructure is not showing as causing any problems in the traceroute you posted.

Please clear up some questions in my mind: what ping time do you get for bbc.co.uk using a ping command wired (post the results); the traceroute you posted is showing very odd results for your router - was that wireless?

[ichilton]

Hi,

This is from a Linux laptop, wired to a switch, which is wired to the O2 router (in a different room):

ian@dipsy:~$ ping bbc.co.uk
PING bbc.co.uk (212.58.254.252) 56(84) bytes of data.
64 bytes from virtual3.rbsov.bbc.co.uk (212.58.254.252): icmp_seq=1 ttl=247 time=35.6 ms
64 bytes from virtual3.rbsov.bbc.co.uk (212.58.254.252): icmp_seq=2 ttl=247 time=33.2 ms
64 bytes from virtual3.rbsov.bbc.co.uk (212.58.254.252): icmp_seq=3 ttl=247 time=33.8 ms
64 bytes from virtual3.rbsov.bbc.co.uk (212.58.254.252): icmp_seq=4 ttl=247 time=33.4 ms
64 bytes from virtual3.rbsov.bbc.co.uk (212.58.254.252): icmp_seq=5 ttl=247 time=33.1 ms
64 bytes from virtual3.rbsov.bbc.co.uk (212.58.254.252): icmp_seq=6 ttl=247 time=33.1 ms
^C
--- bbc.co.uk ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5019ms
rtt min/avg/max/mdev = 33.127/33.730/35.611/0.888 ms

and here is pinging the router across the network just to check there is no problem there:

ian@dipsy:~$ ping 10.30.1.1
PING 10.30.1.1 (10.30.1.1) 56(84) bytes of data.
64 bytes from 10.30.1.1: icmp_seq=1 ttl=64 time=1.67 ms
64 bytes from 10.30.1.1: icmp_seq=2 ttl=64 time=0.753 ms
64 bytes from 10.30.1.1: icmp_seq=3 ttl=64 time=0.744 ms
64 bytes from 10.30.1.1: icmp_seq=4 ttl=64 time=0.745 ms
^C
--- 10.30.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 0.744/0.980/1.678/0.403 ms

Here is a traceroute:

ian@dipsy:~$ traceroute bbc.co.uk
traceroute to bbc.co.uk (212.58.254.252), 30 hops max, 40 byte packets
 1  O2WirelessBox.lan (10.30.1.1)  25.709 ms  25.119 ms  24.542 ms
 2  87-194-96-1.bethere.co.uk (87.194.96.1)  588.350 ms  589.890 ms  589.869 ms
 3  * * *
 4  83.245.126.93 (83.245.126.93)  48.366 ms  51.737 ms  51.713 ms
 5  212.58.238.129 (212.58.238.129)  52.635 ms  56.045 ms  56.020 ms
 6  rdirslb0.thdo.bbc.co.uk (212.58.224.136)  58.026 ms  37.302 ms  36.994 ms
 7  virtual3.rbsov.bbc.co.uk (212.58.254.252)  36.217 ms  34.548 ms  36.843 ms

And here is ping's to the 1st hop after the ADSL:

ian@dipsy:~$ ping 87.194.96.1
PING 87.194.96.1 (87.194.96.1) 56(84) bytes of data.
64 bytes from 87.194.96.1: icmp_seq=1 ttl=63 time=28.4 ms
64 bytes from 87.194.96.1: icmp_seq=2 ttl=63 time=27.3 ms
64 bytes from 87.194.96.1: icmp_seq=3 ttl=63 time=27.3 ms
64 bytes from 87.194.96.1: icmp_seq=4 ttl=63 time=27.0 ms
^C
--- 87.194.96.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3009ms
rtt min/avg/max/mdev = 27.067/27.526/28.412/0.559 ms

It looks like that's where mine is taking longer than yours? - what do you see if you ping that 1st hop?

Thanks,

Ian

[Saturday]

Pinging any intermediate hop is meaningless as I said before - the servers have plenty to do other than respond to low priority ICMP requests. Since you ask, I get a result of 1558ms (or no response or any other number if I keep trying) but that doesn't have any impact on the 19ms ping I'm currently getting to bbc.co.uk.

There's nothing in anything you've posted that suggests a problem with your routing. There may be but a traceroute isn't showing anything.

You appear to be getting ~33ms when pinging the bbc. That's not too shabby at all but not as good as normal for O2.

Assuming it's not a problem with your laptop, your home network (not sure why you're using a Class A private address), or your router then yes it could be down to the O2 network.

In which case only O2 can sort this for you. Try calling them and have a chat with their 2nd level technicians and see if they can do anything (unlikely as that will be in the control of the network specialists).

One last thing: I see you have an O2 IP in the 87 range. IIRC this has been known to give problems in the past (out of date bogon filters in "internet land"). Doubt this is the issue here but you could always try forcing an IP change by using a different router or spoofing a new MAC and see if you get a different range.