First of all thanks for the information about the command prompt

Tracing route to bbc.co.uk [212.58.246.78]
over a maximum of 30 hops:

1 11 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 11 ms 11 ms 11 ms 213.1.175.250
3 10 ms 10 ms 11 ms 213.1.175.161
4 18 ms 18 ms 17 ms 213.1.69.42
5 17 ms 18 ms 18 ms 213.120.180.169
6 18 ms 18 ms 18 ms 213.120.179.83
7 17 ms 17 ms 17 ms acc2-xe-0-3-1.sf.21cn-ipp.bt.net [109.159.251.237]
8 25 ms 22 ms 22 ms core1-te-0-13-0-10.ilford.ukcore.bt.net [109.159.251.191]
9 27 ms 25 ms 26 ms peer1-xe4-2-0.redbus.ukcore.bt.net [109.159.255.130]
10 27 ms 29 ms 26 ms 195.99.126.101
11 * * * Request timed out.
12 25 ms 24 ms 25 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
13 29 ms 25 ms 38 ms 132.185.255.165
14 23 ms 23 ms 23 ms bbc.co.uk [212.58.246.78]

Trace complete.

Here are the results on a 3.8Mbts connection

No the PN Technicolor is wired to the PC, not sure why the 1st hop is like that ...... a bug?

This seems OK though:-

C:\Users\A>tracert -4 192.168.1.254

Tracing route to 192.168.1.254 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.254

The high latency in your earlier post was transient rather than endemic, as it was not reflected in any later hop. Your router must have been quite busy with some other task at the time.

Responding to pings has to be the least important thing a router does. It's only when high readings are continued in all or nearly all later hops there is anything to worry about, as it could indicate congestion at that point.

In reply to a post by RobertoS:

The high latency in your earlier post was transient rather than endemic, as it was not reflected in any later hop. Your router must have been quite busy with some other task at the time.

Responding to pings has to be the least important thing a router does. It's only when high readings are continued in all or nearly all later hops there is anything to worry about, as it could indicate congestion at that point.

I was about the say that

Paul

In reply to a post by RobertoS:

The high latency in your earlier post was transient rather than endemic, as it was not reflected in any later hop. Your router must have been quite busy with some other task at the time.

Responding to pings has to be the least important thing a router does. It's only when high readings are continued in all or nearly all later hops there is anything to worry about, as it could indicate congestion at that point.

Thanks Bob, having had a cup of tea and time to reflect on the matter I was thiking along those lines too

Coffee boosts the energies.

Tea clears the mind .

In reply to a post by RobertoS:

Coffee boosts the energies.

Tea clears the mind .

Only when you raise the little finger while drinking

Paul