Quote:
|
Originally Posted by th'engineer
Somebody has switched them on again  back to slow browsing
1 <10 ms <10 ms <10 ms 192.168.2.1
2 14 ms 14 ms 13 ms 10.23.48.1
3 14 ms <10 ms <10 ms oldh-t2cam1-a-ge910.inet.ntl.com [80.5.164.61]
4 302 ms 13 ms 14 ms mant-t2core-a-ge-wan62.inet.ntl.com [213.104.24
41]
5 14 ms 14 ms 13 ms man-bb-a-so-230-0.inet.ntl.com [62.253.184.57]
6 14 ms 13 ms 14 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 28 ms 14 ms 27 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]
8 14 ms 27 ms 14 ms win-dc-a-v900.inet.ntl.com [62.253.188.162]
9 14 ms 28 ms 13 ms www.ntlworld.com [62.253.162.30] |
[16:33] * theng (~theng@spcx-roch1-6-0-custx.manc.broadband.ntl.com) has joined #nthellworld
[16:34] <theng> look at the p9ings BBK in the thread
I'll jump in for BBKing here and say this again as I did in previous page...
Pings are not affected by caches
That looks like a bit of activity on the line - note 1st hop and last hop are equal latency... I wouldn't mind pings like those to be honest:
1 1 ms <1 ms 1 ms gatelock-corporate.inside.net [192.168.253.1]
2 1 ms 1 ms 1 ms x-modem.inside.net [10.0.0.2]
3 17 ms 16 ms 17 ms 81-86-224-1.dsl.pipex.com [81.86.224.1]
4 16 ms 17 ms 15 ms sms10k2-2.cr1.uk5.systems.pipex.net [62.241.161.45]
5 18 ms 23 ms 17 ms ge-1-2-0.cr1.gs1.systems.pipex.net [62.241.161.97]
6 28 ms 17 ms 17 ms tmp.xchangepoint.net [217.79.160.89]
7 17 ms 18 ms 17 ms bre-bb-a-so-310-0.inet.ntl.com [62.253.188.105]
8 19 ms 19 ms 19 ms win-bb-b-so-600-0.inet.ntl.com [62.253.185.198]
9 20 ms 18 ms 19 ms win-bb-a-ae0-0.inet.ntl.com [213.105.172.161]
10 19 ms 19 ms 17 ms win-dc-a-v902.inet.ntl.com [62.253.187.222]
11 19 ms 19 ms 19 ms
www.ntlworld.com [62.253.162.30]