Low Latency on fttc

Target Name: www.bbc.co.uk
IP: 212.58.246.94
Date/Time: 26/12/2013 21:53:44 to 26/12/2013 21:53:52

1 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms [192.168.1.254]
2 10 ms 10 ms 9 ms 9 ms 15 ms 9 ms 9 ms 10 ms 11 ms lo0-central10.pcl-ag08.plus.net [195.166.128.189]
3 9 ms 10 ms 9 ms 9 ms 10 ms 9 ms 9 ms 10 ms N/A link-b-central10.pcl-gw02.plus.net [212.159.2.190]
4 9 ms 10 ms 9 ms 9 ms 11 ms 9 ms 9 ms 9 ms N/A xe-9-1-0.pcl-cr02.plus.net [212.159.0.222]
5 12 ms 10 ms 10 ms 14 ms 31 ms 10 ms 12 ms 9 ms N/A ae1.ptw-cr02.plus.net [195.166.129.2]
6 9 ms 10 ms 9 ms 9 ms 9 ms 9 ms 10 ms 13 ms N/A ae2.ptw-cr01.plus.net [195.166.129.4]
7 10 ms 31 ms 54 ms 9 ms 21 ms 9 ms 9 ms 14 ms N/A kingston-gw.thdo.bbc.co.uk [212.58.239.6]
8 * * * * * N/A N/A N/A N/A [-]
9 11 ms 11 ms 11 ms 10 ms 10 ms 10 ms 10 ms 10 ms N/A ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 11 ms 10 ms 11 ms 11 ms 11 ms 10 ms 11 ms 11 ms N/A [132.185.255.165]
11 10 ms 11 ms 11 ms 10 ms 10 ms 10 ms 10 ms 11 ms N/A bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Ping statistics for www.bbc.co.uk
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 10ms, Maximum = 11ms, Average = 10ms

It is like I left never my LAN

Edited by Stanman_24 (Thu 26-Dec-13 21:54:39)

You want to post issues about you connection...you do it with acceptable language please.

The packets did leave your LAN.

The traceroute times are NOT cummulative but as list of time from the start point to each successive router listed. You also have to allow that the system sending the reply is generally a lower priority task on a router than normal packet routing.

1. Time from your PC to the first router
2. Time from your PC to the second router
3. Time from your PC to the third router

So, from your trace route it takes 1ms from your PC to your local router, 10 ms from your PC to lo0-central10, 9 ms from your PC to link-b-central 10 etc

Yes, it does seem to be faster to a further point but this is because the traceroute mechanism was not designed to provide the sort of timing people want from it. The mechanism used to probe the network uses a packet that is designed to exceed its hop count and for the router to eventually report this. The results on fast links is that a significant part on the time is made up how long it takes the route to 'bother' to get round to sending a reply.

If you can ping www.bbc.co.uk then the packets left your router.

From the traceroute it looks like the plusnet & bbc networks are fast and uncongested.

What is the point of this post?

In reply to a post by kasg:

What is the point of this post?

I don't know, but those round trip times look a bit high compared to mine.

Ping statistics for www.bbc.co.uk
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Minimum = 2ms, Maximum = 2ms, Average = 2ms

pmsl

Looks a bit as though the OP misunderstands what tracert does, but it has now been explained .

In reply to a post by locutus:

I don't know, but those round trip times look a bit high compared to mine.

Ping statistics for www.bbc.co.uk
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Minimum = 2ms, Maximum = 2ms, Average = 2ms

Where are you, at the BBC? I can do better:

Ping statistics for www.bbc.co.uk
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Post deleted by seb

I haven't a clue what that post is about - a few of us are simply asking what the problem is. We can't see one, and bsdnazz has explained why.

What exactly, as kasg asks, is the point of this thread, particularly since the explanation of tracert that you may be ignoring?