Pinging 217.146.93.31 with 32 bytes of data:

Reply from 217.146.93.31: bytes=32 time=21ms TTL=120
Reply from 217.146.93.31: bytes=32 time=19ms TTL=120
Reply from 217.146.93.31: bytes=32 time=19ms TTL=120
Reply from 217.146.93.31: bytes=32 time=18ms TTL=120

Ping statistics for 217.146.93.31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 21ms, Average = 19ms


Tracing route to Service.alpha-networks.co.uk [217.146.93.31]
over a maximum of 30 hops:

1 8 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 12 ms 12 ms 11 ms gay-dsl1.wh.zen.net.uk [62.3.83.20]
3 11 ms 28 ms 12 ms bolzano-ae-0-232.wh.zen.net.uk [62.3.80.233]
4 12 ms 12 ms 13 ms 193.189.130.26
5 23 ms 23 ms 23 ms 194.117.136.217
6 28 ms 27 ms 26 ms 194.117.136.178
7 29 ms 29 ms 26 ms tele1-know-rab.telewest.net [194.117.136.158]
8 24 ms 23 ms 23 ms 194.117.136.146
9 27 ms 240 ms 24 ms 194.117.136.162
10 24 ms 25 ms 26 ms telewest.transit.as25369.net [194.117.147.66]
11 28 ms 30 ms 29 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
12 26 ms 27 ms 27 ms Service.alpha-networks.co.uk [217.146.93.31]

Trace complete.

I have to say I missed it. I'll bring it to the attention of the appropriate bods tomorrow.

Personally getting the following at 20:32 (ignore the SpeedTouch ):

traceroute to 217.146.93.31 (217.146.93.31), 64 hops max, 40 byte packets
1 speedtouch (192.168.1.254) 42.465 ms 97.522 ms 99.611 ms
2 gaius-dsl1.wh.zen.net.uk (62.3.83.27) 37.142 ms 37.413 ms 37.302 ms
3 bolzano-ae-0-236.wh.zen.net.uk (62.3.80.237) 36.983 ms 37.602 ms 37.364 ms
4 193.189.130.26 (193.189.130.26) 36.947 ms 37.140 ms 36.951 ms
5 194.117.136.221 (194.117.136.221) 46.270 ms 45.706 ms 47.365 ms
6 194.117.136.150 (194.117.136.150) 46.229 ms 46.349 ms 46.945 ms
7 194.117.136.166 (194.117.136.166) 46.848 ms 46.187 ms 46.075 ms
8 tele2-gw4.telewest.net (194.117.136.197) 46.476 ms 52.908 ms 46.554 ms
9 telewest.transit.as25369.net (194.117.147.66) 45.277 ms 44.934 ms 45.268 ms
10 sov-r1-rtr1.4u.net.uk (217.146.81.254) 45.354 ms 43.909 ms 45.280 ms
11 service.alpha-networks.co.uk (217.146.93.31) 45.371 ms 44.803 ms 45.027 ms

ta,
P.

If it helps I ran a long ping plot on Nildram and the ping spikes can be seen from there as well, but they have no impact on the destination ping so just looks like Telewest routers getting a bit busy.

Sorry the columns don't line up too well.

Target Name: Service.alpha-networks.co.uk
IP: 217.146.93.31
Date/Time: 19/07/2007 20:28:02 to 19/07/2007 20:32:47

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 20 0 0.0 0 0 0 www.routerlogin.com [192.168.0.1]
2 20 0 0.0 9 167 20 l5.ar21.gs1.dsl.pipex.net [195.112.5.10]
3 20 0 0.0 9 12 10 ge-2-0-1.1.cr01.gs1.dsl.pipex.net [62.241.167.49]
4 20 0 0.0 9 61 17 pc24.cr05.tn5.bb.pipex.net [62.72.141.21]
5 20 0 0.0 9 58 12 telewest-pipex-pvtpeer.telewest.net [194.117.147.37]
6 20 0 0.0 9 43 12 telewest.transit.as25369.net [194.117.147.66]
7 20 0 0.0 9 68 13 sov-r1-rtr1.4u.net.uk [217.146.81.254]
8 20 0 0.0 9 17 10 Service.alpha-networks.co.uk [217.146.93.31]

In reply to:

---

(ignore the SpeedTouch ):

---

Mine does that as well, any reason behind it?

I've a speedtouch too, and the only real reason that I've found so far is that "It's just slow to respond to ICMP pings".

It's not a problem though as the first 'proper' hop is always fast, so it's something that can genuinely be ignored.

Something has happened, had no problems over the last 2 nights

Tracing route to Service.alpha-networks.co.uk [217.146.93.31]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 31 ms 31 ms 31 ms gay-dsl1.wh.zen.net.uk [62.3.83.20]
3 31 ms 31 ms 32 ms gay-dsl1.wh.zen.net.uk [62.3.80.233]
4 32 ms 31 ms 31 ms 193.189.130.26
5 41 ms 43 ms 43 ms 194.117.136.217
6 40 ms 40 ms 39 ms 194.117.136.178
7 39 ms 41 ms 42 ms 194.117.136.150
8 39 ms 41 ms 40 ms 194.117.136.166
9 42 ms 42 ms 41 ms tele2-gw4.telewest.net [194.117.136.197]
10 40 ms 40 ms 40 ms telewest.transit.as25369.net [194.117.147.66]
11 41 ms 43 ms 42 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
12 50 ms 49 ms 53 ms Service.alpha-networks.co.uk [217.146.93.31]

Trace complete.

Looking good

Spoke too soon

Tracing route to server109-180.4u-servers.co.uk [195.20.109.180]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 33 ms 32 ms 31 ms gay-dsl1.wh.zen.net.uk [62.3.83.5]
3 33 ms 31 ms 32 ms gay-dsl1.wh.zen.net.uk [62.3.80.229]
4 32 ms 34 ms 31 ms 193.189.130.26
5 121 ms 119 ms 117 ms gay-dsl1.wh.zen.net.uk [62.30.249.153]
6 122 ms 122 ms 120 ms 194.117.136.178
7 115 ms 114 ms 114 ms tele1-know-rab.telewest.net [194.117.136.158]
8 114 ms 110 ms 110 ms 194.117.136.146
9 106 ms 104 ms 107 ms 194.117.136.162
10 107 ms 106 ms 106 ms telewest.transit.as25369.net [194.117.147.66]
11 110 ms 109 ms 110 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
12 115 ms 114 ms 115 ms server109-180.4u-servers.co.uk [195.20.109.180]


Trace complete.

starts at 5
and another server I use

Tracing route to gay-dsl1.wh.zen.net.uk [81.19.219.111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 32 ms 32 ms 32 ms gay-dsl1.wh.zen.net.uk [62.3.83.5]
3 42 ms 31 ms 32 ms gay-dsl1.wh.zen.net.uk [62.3.80.229]
4 32 ms 32 ms 33 ms 193.189.130.26
5 115 ms 114 ms 115 ms gay-dsl1.wh.zen.net.uk [62.30.249.153]
6 117 ms 116 ms 116 ms 194.117.136.178
7 119 ms 116 ms 118 ms tele1-know-rab.telewest.net [194.117.136.158]
8 115 ms 115 ms 117 ms 194.117.136.146
9 114 ms 114 ms 118 ms 194.117.136.162
10 188 ms 161 ms 224 ms telewest.transit.as25369.net [194.117.147.66]
11 120 ms 119 ms 118 ms gay-dsl1.wh.zen.net.uk [81.19.219.111]

Trace complete.

Your tracerts seem abit weird, i dont understand why your tracert goes through the gateway (gay-ds1) 3 times. Heres examples from my connection to same ip's

Tracing route to server109-180.4u-servers.co.uk [195.20.109.180]
over a maximum of 30 hops:

1 16 ms 14 ms 18 ms gauss-dsl.zen.net.uk [62.3.82.18]
2 15 ms 19 ms 15 ms lotze-ge-0-0-1-1.hq.zen.net.uk [62.3.80.129]
3 14 ms 15 ms 15 ms spinoza-ae1-0.hq.zen.net.uk [62.3.80.65]
4 15 ms 17 ms 14 ms bolzano-ae2-0.wh.zen.net.uk [62.3.80.53]
5 16 ms 15 ms 15 ms 193.189.130.26
6 53 ms 53 ms 58 ms pc-62-30-249-153-ha.blueyonder.co.uk [62.30.249.
153]
7 55 ms 55 ms 54 ms 194.117.136.178
8 55 ms 58 ms 57 ms 194.117.136.150
9 59 ms 57 ms 58 ms 194.117.136.166
10 53 ms 51 ms 50 ms tele2-gw4.telewest.net [194.117.136.197]
11 48 ms 48 ms 47 ms telewest.transit.as25369.net [194.117.147.66]
12 45 ms 46 ms 47 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
13 47 ms 47 ms 48 ms server109-180.4u-servers.co.uk [195.20.109.180]


Trace complete.

In that tracert the ping problem seems to occur outside of zens network when it enters telewest blueyonders network.

2nd one.

Tracing route to server.killercreation.co.uk [81.19.219.111]
over a maximum of 30 hops:

1 14 ms 14 ms 15 ms gauss-dsl.zen.net.uk [62.3.82.18]
2 15 ms 14 ms * lotze-ge-0-0-1-1.hq.zen.net.uk [62.3.80.129]
3 15 ms 17 ms 14 ms spinoza-ae1-0.hq.zen.net.uk [62.3.80.65]
4 15 ms 15 ms 14 ms bolzano-ae2-0.wh.zen.net.uk [62.3.80.53]
5 15 ms 15 ms 18 ms 193.189.130.26
6 24 ms 25 ms 25 ms 194.117.136.221
7 24 ms 24 ms 26 ms 194.117.136.150
8 29 ms 23 ms 25 ms 194.117.136.166
9 89 ms 211 ms 220 ms tele2-gw4.telewest.net [194.117.136.197]
10 22 ms 24 ms 24 ms telewest.transit.as25369.net [194.117.147.66]
11 25 ms 24 ms 24 ms server.killercreation.co.uk [81.19.219.111]

Trace complete.

Ok thats not too bad there but in your tracert to that server its even weirder you appear to go in a circle back to the zen gateway again at end.
But its ip is for the killercreation server.

Blackmesa8

In reply to:

---

i dont understand why your tracert goes through the gateway (gay-ds1) 3 times.

---

Looks like the OP is using a DrayTek router - there's a known bug in most of their firmwares that can cause DNS lookups to return dodgy information (when using the router as a DNS server), as the traceroute shows.

If you check the IP's of the respective hops though, it does pass through different equipment at each hop.

hth

Thinking of migrating to ADSL24 their network goes nowhere near telewest to the servers I use

1 1 ms 1 ms 1 ms x.x.x.x
2 17 ms 17 ms 16 ms dogwood.dsl.enta.net [84.45.242.69]
3 17 ms 16 ms 17 ms vlan4001.global-switch.dsl.enta.net [84.45.242.65]
4 16 ms 16 ms 17 ms gi3-8.telehouse-east.dsl.enta.net [84.45.242.50]
5 16 ms 20 ms 17 ms te5-2.telehouse-east.core.enta.net [62.249.192.121]
6 15 ms 17 ms 17 ms te5-1.telehouse-east2.core.enta.net [87.127.236.98]
7 17 ms 17 ms 16 ms te4-1.telehouse-north.core.enta.net [87.127.236.38]
8 17 ms 16 ms 16 ms 62-249-255-186.no-dns-yet.enta.net [62.249.255.186]
9 17 ms 16 ms 17 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
10 17 ms 15 ms 15 ms Service.alpha-networks.co.uk [217.146.93.31]

This was done by someone from manchester so my pings should in the 30
compared to Zen

Tracing route to Service.alpha-networks.co.uk [217.146.93.31]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 33 ms 34 ms 33 ms gauss-dsl.zen.net.uk [62.3.82.18]
3 33 ms 33 ms 33 ms lotze-ge-0-0-1-1.hq.zen.net.uk [62.3.80.129]
4 33 ms 34 ms 33 ms spinoza-ae1-0.hq.zen.net.uk [62.3.80.65]
5 46 ms 34 ms 43 ms bolzano-ae2-0.wh.zen.net.uk [62.3.80.53]
6 36 ms 34 ms 35 ms 193.189.130.26
7 162 ms 165 ms 162 ms 194.117.136.217
8 163 ms 161 ms 162 ms 194.117.136.178
9 159 ms 160 ms 160 ms 194.117.136.150
10 161 ms 161 ms 159 ms 194.117.136.166
11 158 ms 158 ms 157 ms tele2-gw4.telewest.net [194.117.136.197]
12 151 ms 154 ms 153 ms telewest.transit.as25369.net [194.117.147.66]
13 154 ms 152 ms 163 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
14 149 ms 147 ms 149 ms Service.alpha-networks.co.uk [217.146.93.31]

Dont know where hops 6, 7 and 8 are but zen routing through telewest is the problem for me.