Pings

Just moved to Zen, with nildram pings were <30 to a game server i use a lot. Now with Zen they are


1 <1 ms <1 ms
2 34 ms 35 ms 36 ms gandhi-dsl1.wh.zen.net.uk [62.3.83.5]
3 52 ms 35 ms 35 ms gandhi-dsl1.wh.zen.net.uk [62.3.80.229]
4 35 ms 35 ms 35 ms 193.189.130.26
5 114 ms 112 ms 112 ms 194.117.136.217
6 113 ms 111 ms 114 ms 194.117.136.178
7 117 ms 116 ms 119 ms 194.117.136.150
8 130 ms 121 ms 119 ms 194.117.136.166
9 126 ms 125 ms 123 ms tele2-gw4.telewest.net [194.117.136.197]
10 119 ms 119 ms 116 ms telewest.transit.as25369.net [194.117.147.66]
11 120 ms 121 ms 121 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
12 126 ms 128 ms 130 ms Service.alpha-networks.co.uk [217.146.93.31]

Trace complete.

????????

Same sort of times here :

traceroute to 217.146.93.31 (217.146.93.31), 30 hops max, 38 byte packets
1 speedtouch.lan (192.168.1.254) 56.051 ms 98.348 ms 99.967 ms
2 gauthier-dsl1.hq.zen.net.uk (62.3.82.17) 17.085 ms 16.103 ms 16.525 ms
3 lotze-ge-0-0-1-136.hq.zen.net.uk (62.3.80.137) 56.374 ms 17.573 ms 16.015 ms
4 spinoza-ae1-0.hq.zen.net.uk (62.3.80.65) 16.021 ms 17.550 ms 16.432 ms
5 bolzano-ae2-0.wh.zen.net.uk (62.3.80.53) 16.515 ms 30.656 ms 16.043 ms
6 193.189.130.26 (193.189.130.26) 15.965 ms 17.112 ms 16.557 ms
7 pc-62-30-249-153-ha.blueyonder.co.uk (62.30.249.153) 136.977 ms 137.902 ms 138.369 ms
8 194.117.136.178 (194.117.136.178) 136.569 ms 139.599 ms 133.544 ms
9 tele1-know-rab.telewest.net (194.117.136.158) 133.515 ms 132.157 ms 133.298 ms
10 194.117.136.146 (194.117.136.146) 131.556 ms 131.708 ms 143.370 ms
11 194.117.136.162 (194.117.136.162) 138.528 ms 131.690 ms 132.551 ms
12 telewest.transit.as25369.net (194.117.147.66) 134.043 ms 132.052 ms 130.832 ms
13 sov-r1-rtr1.4u.net.uk (217.146.81.254) 131.083 ms 130.096 ms 131.543 ms
14 Service.alpha-networks.co.uk (217.146.93.31) 131.628 ms 130.170 ms 130.301 ms

I notice it slows down when it hits Blueyonder (Virgin) - essentially they are the cause of the high ping rate as Zens' servers respond in the correct manner.

Perhaps the flooding has effected Blueyonder or it could be a part of Virgins general troubles getting a decent service for end users (see the Virgin ADSL forum here and also the (Cable) one).

For reference, my router is on 'fast path' and not interleaved as an interleaved connection will raise pings anyway.

This is mine WITH interleave.

Tracing route to Service.alpha-networks.co.uk [217.146.93.31] with TTL of 32:



 1  42ms   88ms   89ms   speedtouch.lan [192.168.1.254]

 2  33ms   32ms   32ms   gandhi-dsl1.wh.zen.net.uk [62.3.83.5]

 3  33ms   32ms   33ms   bolzano-ge-0-0-1-3.wh.zen.net.uk [62.3.80.229]

 4  33ms   33ms   33ms   193.189.130.26

 5  43ms   41ms   41ms   194.117.136.221

 6  42ms   41ms   41ms   tele1-know-rab.telewest.net [194.117.136.158]

 7  41ms   41ms   42ms   194.117.136.174

 8  42ms   41ms   41ms   tele2-gw4.telewest.net [194.117.136.197]

 9  39ms   40ms   41ms   telewest.transit.as25369.net [194.117.147.66]

10  41ms   39ms   39ms   sov-r1-rtr1.4u.net.uk [217.146.81.254]

11  40ms   39ms   39ms   Service.alpha-networks.co.uk [217.146.93.31]



Traceroute complete.

mine are very good non interleaved.

C:\Documents and Settings\Blackmesa8>tracert 217.146.93.31

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

1 15 ms 15 ms 14 ms gauthier-dsl1.hq.zen.net.uk [62.3.82.17]
2 16 ms 20 ms 17 ms lotze-ge-0-0-1-136.hq.zen.net.uk [62.3.80.137]
3 15 ms 16 ms 17 ms spinoza-ae1-0.hq.zen.net.uk [62.3.80.65]
4 15 ms 16 ms 26 ms bolzano-ae2-0.wh.zen.net.uk [62.3.80.53]
5 16 ms 17 ms 16 ms 193.189.130.26
6 25 ms 27 ms 25 ms 194.117.136.217
7 26 ms 26 ms 25 ms 194.117.136.178
8 26 ms 26 ms 26 ms tele1-know-rab.telewest.net [194.117.136.158]
9 26 ms 31 ms 24 ms 194.117.136.146
10 24 ms 26 ms 24 ms 194.117.136.162
11 24 ms 24 ms 23 ms telewest.transit.as25369.net [194.117.147.66]
12 25 ms 23 ms 23 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
13 23 ms 23 ms 23 ms Service.alpha-networks.co.uk [217.146.93.31]

Trace complete.

It might be worth shooting the server admins an email. Zen and 4u Networks both peer at Linx and Lonap and would benefit from connecting more directly.

TT

I noticed the same problem for the past 2 weeks., since the 13/06/2007, which is the date of my first Traceroute when I noticed the problem.

I play a lot of Call of Duty 2 online in various servers, of which during this time I have noticed that several of my favorites have had increased pings usually between the hours of 8:00pm and 9:30pm. (But could be anytime between 7:30pm and 10:30pm).
If you look at the times of the results already posted here, you'll see the affected fall within this range.

Here's a few more similarly affected Game Server IP's:
195.20.109.109
81.19.219.45
81.19.223.60

I have done some traces using WinMTR before, after and during the affected times.

The one thing in common is that they all appear to be hosted within or pass through the TeleWest / BlueYonder network which seems to me to be the cause.
Particularly - 194.117.136.217 or 62.30.249.153

Theory 1
From what I could tell, the routing of the servers don't tend to change, just the pings during these times. Obviously this is the main Peak time which most people will use the internet, which could mean that it's due to the Load on the TW network or due to some sort of Traffic Shaping or Load Balancing during Peak times.

Theory 2
I have a friend who is still connected with TeleWest Broadband, he has told me that they are doing server / network upgrading across the backbone of their network. From what I've been told, this may not be finished for another month.

Unless anyone else has any resolutions or feedback or opinions on this.

Either way. I hope the problem is only temporary and get resolved.


PS.
I'm using a Speedtouch 585iv6, usually around the 4000kbits range @9dB SNR (prefer stability to speed), Forced 'Fast Path', Wireless Turned off, Master Socket Filtered with ADSL Nation XTE-2005 Faceplate. PC is Spyware and Virus free.

I'm not an expert as this sort of thing, so feel free to point out any errors or correct anything that I have said above.


Sorry for this Post being a bit long.... er.

OK here!

Pinging 217.146.93.31 with 32 bytes of data:

Reply from 217.146.93.31: bytes=32 time=21ms TTL=118
Reply from 217.146.93.31: bytes=32 time=20ms TTL=118
Reply from 217.146.93.31: bytes=32 time=20ms TTL=118
Reply from 217.146.93.31: bytes=32 time=20ms TTL=118

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



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

1 64 ms 99 ms 100 ms dsldevice.lan [192.168.1.254]
2 13 ms 14 ms 13 ms gauthier-dsl1.hq.zen.net.uk [62.3.82.17]
3 14 ms 14 ms 14 ms lotze-ge-0-0-1-136.hq.zen.net.uk [62.3.80.137]
4 14 ms 13 ms 13 ms spinoza-ae1-0.hq.zen.net.uk [62.3.80.65]
5 23 ms 14 ms 14 ms bolzano-ae2-0.wh.zen.net.uk [62.3.80.53]
6 14 ms 14 ms 14 ms 193.189.130.26
7 24 ms 23 ms 23 ms 194.117.136.217
8 23 ms 23 ms 24 ms 194.117.136.178
9 22 ms 23 ms 22 ms tele1-know-rab.telewest.net [194.117.136.158]
10 23 ms 22 ms 23 ms 194.117.136.146
11 23 ms 24 ms 23 ms 194.117.136.162
12 22 ms 22 ms 21 ms telewest.transit.as25369.net [194.117.147.66]
13 21 ms 21 ms 23 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
14 22 ms 21 ms 21 ms Service.alpha-networks.co.uk [217.146.93.31]

Trace complete.

Looking good here from A&A - no virgin media involved!!

C:\Users\Jon>tracert 217.146.93.31



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  aaisp-gw.barnsley.jongreen.co.uk [90.155.84.1]

  2    17 ms    18 ms    18 ms  careless.aaisp.net.uk [81.187.81.72]

  3    17 ms    17 ms    17 ms  aimless.aaisp.net.uk [217.169.20.3]

  4    17 ms    18 ms    18 ms  lipex.thn-1.as25369.net [193.109.219.38]

  5    19 ms    18 ms    19 ms  sov-r1-rtr1.4u.net.uk [217.146.81.254]

  6    19 ms    18 ms    18 ms  Service.alpha-networks.co.uk [217.146.93.31]



Trace complete.



C:\Users\Jon>

Entanet:
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 10.0.0.1
2 17 ms 17 ms 16 ms larch.dsl.enta.net [87.127.229.36]
3 16 ms 16 ms 16 ms vlan4003.telehouse-east2.dsl.enta.net [87.127.229.33]
4 16 ms 16 ms 16 ms gi2-8.telehouse-east.dsl.enta.net [84.45.242.53]
5 24 ms 39 ms 16 ms te5-2.telehouse-east.core.enta.net [62.249.192.121]
6 16 ms 16 ms 19 ms te5-1.telehouse-east2.core.enta.net [87.127.236.98]
7 16 ms 15 ms 16 ms te4-1.telehouse-north.core.enta.net [87.127.236.38]
8 45 ms 15 ms 15 ms 62-249-255-186.no-dns-yet.enta.net [62.249.255.186]
9 17 ms 16 ms 16 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
10 16 ms 34 ms 16 ms Service.alpha-networks.co.uk [217.146.93.31]

Trace complete.

guys wtf all of the people who just said "yeah everythings fine for me etc"

you have done the tracer route at either first thing in the morning or gone 12 at night! Sorry but it's just no reliable to do it then. Re-do the test at around 8.30pm for a true result.

I had solid pings with Nildram of 30-40 with nildram constant no matter what time of the day; i hope i haven't just migrated to zen to be greeted with [censored] pings in the evenings else i'll be out and cancel the service asap

Well here's a tracert and a ping at 13:14 today. Sorry I couldn't make it 20:30 but I'll have other, more interesting things to do then.

tracert -d 217.146.93.31
Tracing route to 217.146.93.31 over a maximum of 30 hops
1 1 ms <10 ms <10 ms 192.168.1.1
2 40 ms 42 ms 41 ms 62.3.83.20
3 41 ms 42 ms 42 ms 62.3.80.233
4 41 ms 41 ms 41 ms 193.189.130.26
5 53 ms 50 ms 52 ms 194.117.136.217
6 50 ms 52 ms 51 ms 194.117.136.178
7 51 ms 48 ms 51 ms 194.117.136.150
8 51 ms 72 ms 50 ms 194.117.136.166
9 133 ms 242 ms 211 ms 194.117.136.197
10 53 ms 195 ms 199 ms 194.117.147.66
11 117 ms 207 ms 218 ms 217.146.81.254
12 50 ms 49 ms 49 ms 217.146.93.31
Trace complete.

ping 217.146.93.31
Pinging 217.146.93.31 with 32 bytes of data:
Reply from 217.146.93.31: bytes=32 time=49ms TTL=120
Reply from 217.146.93.31: bytes=32 time=48ms TTL=120
Reply from 217.146.93.31: bytes=32 time=47ms TTL=120
Reply from 217.146.93.31: bytes=32 time=49ms 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 = 47ms, Maximum = 49ms, Average = 48ms

On a line with interleaving on.

In reply to:

---

you have done the tracer route at either first thing in the morning or gone 12 at night! Sorry but it's just no reliable to do it then. Re-do the test at around 8.30pm for a true result.

---

Seems to contradict what you then say:

In reply to:

---

I had solid pings with Nildram of 30-40 with nildram constant no matter what time of the day

---

With Nildram pings stayed solid 24hrs a day, but with zen come the busy time in the evening they shoot up to over 100 making gaming unplayable. And before you ask I would have stayed with Nildram but have suffered under Tiscali before and will not again. Got good reports about zen but obviously not from gamers.

It's been repeatedly pointed out that the spikes don't occur in Zen's network but in the Blueyonder/Telewest one.

Have you raised this with Zen or Telewest to see why their peering links seem so congested at peak times?

Wonder why SkyFire or anyone else from zen havn't added anything yet?

If you want to get an official response from Zen, you should really contact support with the details.

Most of my internet use is for games! 25ms to Dutch servers and 18ms to UK servers at anytime of the day or night!

I'd say that was good!!!

Ps: If I remember I'll ping to the address in the OP at 20.30 and post results.

Edited by deleted (Thu 19-Jul-07 17:29:54)

"Have you raised this with Zen or Telewest to see why their peering links seem so congested at peak times?"

Zen can organise peering with folks who host the servers as they're both on LINX. I think I made this point a few weeks ago. Come on Zen, get the peering organised.

TT

I think you did - but did they notice?

I think the OP should contact support to make sure they are aware of it.

interleaving ON
1 <1 ms <1 ms <1 ms SpeedTouch.lan [10.0.0.138]
2 34 ms 31 ms 36 ms gay-dsl1.wh.zen.net.uk [62.3.83.20]
3 28 ms 44 ms 32 ms bolzano-ae-0-232.wh.zen.net.uk [62.3.80.233]
4 32 ms 38 ms 31 ms 193.189.130.26
5 40 ms 42 ms 43 ms pc-62-30-249-153-ha.blueyonder.co.uk [62.30.249.153]
6 91 ms 41 ms 44 ms 194.117.136.178
7 106 ms 137 ms 214 ms 194.117.136.150
8 47 ms 42 ms 42 ms 194.117.136.166
9 43 ms 42 ms 38 ms tele2-gw4.telewest.net [194.117.136.197]
10 40 ms 38 ms 38 ms telewest.transit.as25369.net [194.117.147.66]
11 41 ms 39 ms 44 ms sov-r1-rtr1.4u.net.uk [217.146.81.254]
12 41 ms 36 ms 40 ms Service.alpha-networks.co.uk [217.146.93.31]

at 18:20

"I think you did - but did they notice?"

I'd be surprised if they didn't. They're usually quick off the mark.

TT

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.

In reply to:

---

Well here's a tracert and a ping at 13:14 today. Sorry I couldn't make it 20:30 but I'll have other, more interesting things to do then.

---

why get cheeky you little retard? 13:14 IS NOT WHEN THERE IS MOST TRAFFIC IN THE SLIGHTEST. And you have 'more interesting things to do?1' ahaha don't kid yourself.

I've just moved from Nildram fixed 2mb, if this up to 8 meg package with zen turns out to be shoddy for online gaming i'll be cancelling ASAP and try elsewhere.

Fixed 2mb with nildram was between 25 - 40 ping ANYTIME of the day. I won't be going back with them, but that would be a giggle if i'm now looking to get 100 ping plus in the evenings.

In reply to:

---

why get cheeky you little retard?

---

Because quite frankly a few milliseconds isn't worth fretting over.

In reply to:

---

13:14 IS NOT WHEN THERE IS MOST TRAFFIC IN THE SLIGHTEST.

---

Wel, that's a matter for debate. Perhaps it isn't the key time for you. It most likely is for businesses.

In reply to:

---

And you have 'more interesting things to do?1' ahaha don't kid yourself.

---

Very presumptious of you. Indeed I did have something better to do - I was practicing archery. You know, get out, do some real world stuff.

>why get cheeky you little retard? 13:14 IS NOT WHEN THERE IS MOST TRAFFIC IN THE SLIGHTEST. And you have 'more interesting things to do?1' ahaha don't kid yourself.

No need whatsoever to be aggressive in attitude and so rude, this sort of behaviour is not tolerated on this BBS, desist.

@ _adz_ in your other post you said-

In reply to:

---

you have done the tracer route at either first thing in the morning or gone 12 at night! Sorry but it's just no reliable to do it then. Re-do the test at around 8.30pm for a true result.

I had solid pings with Nildram of 30-40 with nildram constant no matter what time of the day

---

I did do the ping and tracert test at 20.30 and you never commented on that!!! http://bbs.adslguide.org.uk/showthreaded.php?Cat=&Board=zen&Number=3066537&page=0&view=expanded&sb=5&o=7

Guess the figures speak for themselves Blows Nildrams pings away

We have a Dutch gaming server with i3D and I get pings to that of 23ms every night, so I'd say YES Zen are good for gamers!

Edited by deleted (Tue 24-Jul-07 09:44:02)

I shouldn't have said little retard - sorry
but didn't appreciate the blatent 'trying to be a smart ass' attitude!

I guess time will tell, i'm being swapped over to zen tonight at some point.

To the actual thread started - have you resolved the issue or is this a recurring issue still each evening?

Hi all,

Okay - I have some feedback on this now. I've spoken to our engineers and they confirm the issue is with Telewest. 4u purchase their transit from Telewest, and we handover to them in Manchester.

We recommend contacting 4u so they can address the issues with the provider they are purchasing transit from. 4u really should be investigating these performance issues with their transit provider.

In the meantime our engineers will look at the feasibility of peering; but we can't guarantee we will do this. There are elements involved in the peering equation that may not make it a viable option.

kind regards,
Phil.

Edited by deleted (Tue 24-Jul-07 10:47:07)

>I shouldn't have said little retard - sorry

Well said, appreciated.

>>...but didn't appreciate the blatent 'trying to be a smart ass' attitude!

Don't think you will get on with 90% of our posters then.......or me.

LOL

Well said that man - watch out for low flying toys around these threads though, schools are obviously out!

Zen customer services provided my mac within 5 mins on their online support.
I have had no problems with disconnections or download speeds, if the pings had been the same as my old isp I would have stayed with Zen. I will post a tracert to my problem servers when connected with my new isp.

In reply to:

---

...watch out for low flying toys around these threads though, schools are obviously out!

---

Doesn't need school holidays for low flying toys around here
http://www.youtube.com/watch?v=ZbKVG4G9M_0

I moved to BT from zen cause i'm a gamer....i'm utterly stunned by the low pings I get with BT ?

I play BF2 , CS:S, my pings to BF2 are around 16 compared with 30-50 with zen, and pings to my CS:S are sometimes around 5 - 10, amazing !

Edited by deleted (Tue 24-Jul-07 18:00:04)

In reply to:

---

I play BF2 , CS:S, my pings to BF2 are around 16 compared with 30-50 with zen, and pings to my CS:S are sometimes around 5 - 10, amazing !

---

Indeed - and I'm not doubting that they are for one second - but to which servers specifically? If we're to compare the relative performance of one ISP with another then it's only fair that you tell us which servers so that others here (if they are inclined) can see what they get with Zen.

Oh, and is that with or without interleaving?

BTW I could say that my pings are sub 1ms (if I were speaking about my PC to my router!)

To the same servers that I rent when i was still with zen, and interleaving is on.

Downloading is pants with BT from 1600 - 2359 but, I'm not into downloading.

1 x 32 insurgency server 81.19.223.121:27015

1 x 20 css server 81.19.223.98:27015

1 x 20 slot css 81.19.223.99:27045

1 x 32 ranked bf2 server 81.19.223.148:16567

These are my servers.

Edited by deleted (Tue 24-Jul-07 19:37:53)

But one thing that wouldn't want me to migrate to BT is that Peak Traffic Shaping they introduce. Which for someone I know, he gets about 5MB off-peak, but throttled down to 30kb/s peak time. Which is a real pain for him if he has to download maps from the Call of Duty 2 game server.

But then with this current issues, has n't stopped me from trying to play on some of my usual CoD2 servers with a ping of 120 - 200 (including last night).
Which I still managed to come within the top 3 of the maps, which is a bit worrying in some manner.

Edited by Clovis (Tue 24-Jul-07 19:44:10)

Thanks for the info,

I decided to ring up Tech Support today to make sure that they knew of the problem, got a call back and got the same info from the guy from Tech Support and told me that a representative had put a post in this forum few minutes before.


But on other news, a guy I play online with who knows someone who works for Telewest / NTL said that the Server upgrading that was taking place is now finished.
Which I mentioned in Here in Theory 2

but the problem is that they are now charging more for the bandwidth they supply, so most companies may be looking elsewhere or hiring less.

Edited by Clovis (Tue 24-Jul-07 20:00:36)

I got my BB y'day. Up to 8mb Lite package

First impressions? Connect at 5.4mb, DL rate 430kbs, looking good.. hopefully i can maintain that after a week or two when it's more stable

Though the one that i haven't been impressed with was the pings on counterstrike! I'm now getting between 40 & 55 on uk servs and european ones looking at 60-70. (this ws tested at 7pm in the eve and 23.45

This isn't a patch on nildram's, but hey ho; see how it goes.

Strange how a few people are having trouble with their pings! One of the reasons I'm staying with Zen is because I have good pings!!! Otherwise I'd be off to Be*

Not available in my area yet else i would have been too lol.

Oh P2P looked good at the 23.45 go, had a go on a 50meg file, did it at 160kbs so that's decent!