Sorry I see no loss, or high pings to speak of to the last hop on the trace. If you have nothing better to do on December 21st than run endless traceroutes to try and find issues that's your prerogative. I do
As has been mentioned to me you may not be conversant with these technologies.
So...
Tracing route to pear.nildram.net [195.149.20.145]
over a maximum of 30 hops:
1
10 ms 1 ms 1 ms 192.168.11.1 <<
This is router setting up Network Address Translation table entry and new Stateful Packet Inspection firewall ruleset entry.
2 7 ms 6 ms 7 ms 172.17.0.1
3 7 ms 7 ms 7 ms gr1-stbc-rtr1.homechoice.co.uk [81.1.112.62]
4 11 ms 7 ms 10 ms 81-1-67-48.homechoice.co.uk [81.1.67.48]
5 7 ms 8 ms 8 ms 81-1-67-16.homechoice.co.uk [81.1.67.16]
6 8 ms 7 ms 7 ms 195.50.117.113
7
111 ms 8 ms 7 ms so-1-3-0.gar2.London1.Level3.net [212.113.3.29] <<
This is the Level 3 router giving CPU priority to its' rpd (route processor daemon) process, as it's a Juniper (indicated by its' DNS and the so-1-3-0 bit specifically) rather than icmpd its' Internet Control Message Protocol daemon. These are both low priority however ICMP is subterranean.
8 14 ms 8 ms 12 ms unknown.Level3.net [212.187.131.156]
9 9 ms 8 ms 8 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
10 8 ms 8 ms 8 ms ldn-bb1-pos0-3-0.telia.net [213.248.74.5]
11 8 ms 8 ms 8 ms ldn-b3-pos6-0.telia.net [213.248.65.238]
12 8 ms 8 ms 8 ms pipex-110586-ldn-b3.c.telia.net [213.248.100.30]
13 9 ms 8 ms 8 ms lon1-9.nildram.net [84.12.224.14]
14 9 ms 8 ms 8 ms pear.nildram.net [195.149.20.145] <<
end of the trace, a web server which responds in a timely fashion to the queries, however if I were to continue tracing it it would probably respond late every so often or not at all simply because its' getting too many pings and is preserving resources as an anti-denial of service measure.
---------- Post added at 17:25 ---------- Previous post was at 17:11 ----------
[QUOTE=Bill C]2 15 ms 10 ms 8 ms 16 ms 8 ms 25 ms 58 ms 9 ms 12 ms 6 ms 8 ms 24 ms 17 ms 21 ms 54 ms 14 ms [10.15.16.1]
Cisco uBR 7246VXR
3 7 ms 8 ms 9 ms 57 ms 5 ms 11 ms 27 ms 25 ms 7 ms 7 ms 6 ms 5 ms 9 ms 6 ms 23 ms 6 ms bagu-t2cam1-a-v121.inet.ntl.com [80.5.162.85]
Cisco
4 16 ms 8 ms 12 ms 9 ms 7 ms 9 ms 42 ms 38 ms 10 ms 19 ms 7 ms 8 ms 7 ms 7 ms 39 ms 18 ms bagu-t2core-a-ge-wan63.inet.ntl.com [80.5.161.17]
Cisco
5 6 ms 8 ms 7 ms 7 ms 9 ms 19 ms 59 ms 27 ms 6 ms 7 ms 9 ms 8 ms 8 ms 7 ms 12 ms 9 ms man-bb-a-so-100-0.inet.ntl.com [62.253.188.25]
Juniper
6 8 ms 34 ms 9 ms 7 ms 17 ms 15 ms 28 ms 24 ms 9 ms 93 ms 24 ms 8 ms 8 ms 10 ms 31 ms 29 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
Juniper
7 12 ms 15 ms 27 ms 20 ms 15 ms 14 ms 56 ms 20 ms 12 ms 17 ms 40 ms 14 ms 16 ms 26 ms 13 ms 56 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
Juniper
8 51 ms 46 ms 39 ms 19 ms 32 ms 20 ms 89 ms
227 ms 25 ms 20 ms 13 ms 13 ms 12 ms 14 ms 46 ms 25 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]
Busy Cisco, VLAN not real interface
9 16 ms 15 ms 14 ms 13 ms 12 ms 17 ms 58 ms
221 ms 20 ms 14 ms 21 ms 18 ms 14 ms 14 ms 64 ms 49 ms
www.ntlworld.com [212.250.162.47]
Load balanced web cluster, not a 'real' device but collection of them