In reply to a post by Adsl24:

Yes, the people on the trial are still on the 80/20 service, we have not put them back on 40/10.

it should be within the next week, it's not something that can be rushed and the commercials have to be sustainable, so it will be better long term to have the best possible package available.

Once we have the packages we can do a mid-month regrade, it won't require 30 days notice.

Hi James,

Is 80/20 launching this week?

Thanks

Thats poor tbh


And my ping isn't the best on BT, due to the poor Ilford/ealing hop us northerners get. it would be about 11ms otherwise to that NL site.

2 5 ms 4 ms 4 ms 217.32.144.162
3 5 ms 5 ms 5 ms 217.32.144.206
4 7 ms 7 ms 7 ms 213.120.181.206
5 7 ms 7 ms 7 ms 217.41.169.207
6 8 ms 7 ms 7 ms 217.41.169.109
7 7 ms 7 ms 7 ms acc2-10GigE-11-3-0.sf.21cn-ipp.bt.net [109.159.2
51.227]
8 16 ms 15 ms 16 ms core1-te0-2-2-0.ilford.ukcore.bt.net [109.159.25
1.145]
9 12 ms 12 ms 12 ms transit1-pos9-0.telehouse.ukcore.bt.net [62.6.20
1.118]
10 12 ms 12 ms 12 ms t2as1-tge4-4.uk-lon1.eu.bt.net [166.49.211.145]

11 15 ms 15 ms 14 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 13 ms 13 ms 13 ms te0-3-0-6.ccr21.lon01.atlas.cogentco.com [130.11
7.14.49]
13 21 ms 21 ms 21 ms te0-0-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.110]
14 20 ms 20 ms 20 ms te0-3-0-0.ccr21.ams03.atlas.cogentco.com [130.11
7.48.142]
15 21 ms 20 ms 32 ms te3-1.ccr01.ams02.atlas.cogentco.com [154.54.60.
126]
16 21 ms 20 ms 21 ms transip-bv.demarc.cogentco.com [149.6.128.66]
17 21 ms 21 ms 21 ms www.creativehosting.nl [80.69.72.146]

Trace complete.

Thanks for the fast response, I ran the tests a minute ago but at the moment the latency seems normal, I will run them again later when they inviolately go bad.

Wed 9th May
12:56

TF2 Server:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\JAK>tracert 94.23.226.200

Tracing route to eu1.skial.com [94.23.226.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 14 ms 13 ms 14 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 14 ms 13 ms 14 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 14 ms 13 ms 14 ms ge2-6-1.cr2.core.thn.uk.murphx.net [89.145.254.1
69]
5 14 ms 14 ms 13 ms ge1-2-1.crs1.core.thn.uk.murphx.net [109.170.249
.45]
6 14 ms 14 ms 15 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
7 19 ms 14 ms 15 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
8 14 ms * 14 ms ldn-1-6.uk.eu [94.23.122.125]
9 20 ms 20 ms 21 ms rbx-g1-a9.fr.eu [91.121.215.145]
10 18 ms 18 ms 19 ms vss-2-6k.fr.eu [94.23.122.173]
11 32 ms 33 ms 33 ms eu1.skial.com [94.23.226.200]

Trace complete.

Teamspeak Server:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\JAK>tracert 176.31.108.191

Tracing route to ks392140.kimsufi.com [176.31.108.191]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 15 ms 13 ms 13 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 14 ms 14 ms 13 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 13 ms 13 ms 14 ms ge2-6-1.cr2.core.thn.uk.murphx.net [89.145.254.1
69]
5 13 ms 14 ms 13 ms ge1-2-1.crs1.core.thn.uk.murphx.net [109.170.249
.45]
6 14 ms 14 ms 14 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
7 35 ms 36 ms 37 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
8 * 14 ms * ldn-1-6.uk.eu [94.23.122.125]
9 42 ms 44 ms 41 ms rbx-g1-a9.fr.eu [213.251.130.73]
10 58 ms * 48 ms vss-6b-6k.fr.eu [91.121.128.42]
11 40 ms 41 ms 40 ms ks392140.kimsufi.com [176.31.108.191]

Trace complete.

The high delay in ADSL24's tracert is when it hits Level3 though. By comparison, just a couple of minutes ago I got this on Plusnet.

Tracing route to creativehosting.nl [80.69.72.146]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  192.168.11.1
  2    19 ms    14 ms    14 ms  lo0-central7.ptn-ag04.plus.net [195.166.130.129]
  3    15 ms    22 ms    14 ms  84.93.251.155
  4    14 ms    13 ms    14 ms  po4.ptn-gw01.plus.net [212.159.1.138]
  5    27 ms    17 ms    14 ms  ae3.ptw-cr01.plus.net [195.166.129.32]
  6    34 ms    16 ms    38 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  7    22 ms    24 ms    23 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120]
  8    15 ms    14 ms    15 ms  ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
  9    21 ms    21 ms    21 ms  ae-46-46.ebr2.Amsterdam1.Level3.net [4.69.143.73]
 10    22 ms    21 ms    21 ms  ae-56-221.csw2.Amsterdam1.Level3.net [4.69.153.202]
 11    21 ms    21 ms    27 ms  ae-2-52.edge3.Amsterdam1.Level3.net [4.69.139.169]
 12    22 ms    24 ms    24 ms  TRANSIP-BV.edge3.Amsterdam1.Level3.net [212.72.33.110]
 13    22 ms    22 ms    22 ms  www.creativehosting.nl [80.69.72.146]

Trace complete.

That is much the same result as yours.

Pointing to a possible issue at Level3 at times. So for a valid comparison of yours with James's the tests would need to be close together.

Here are 2 tracerts to the teamspeak server taken at 17:09 9th May. These were done back to back.


Tracing route to ks392140.kimsufi.com [176.31.108.191]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 14 ms 14 ms 14 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 14 ms 14 ms 13 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 89 ms 219 ms 219 ms ge2-6-1.cr2.core.thn.uk.murphx.net [89.145.254.1
69]
5 14 ms 14 ms 13 ms ge1-2-1.crs1.core.thn.uk.murphx.net [109.170.249
.45]
6 15 ms 14 ms 13 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
7 79 ms 101 ms 91 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
8 43 ms * 15 ms ldn-1-6.uk.eu [94.23.122.125]
9 79 ms 82 ms 87 ms rbx-g1-a9.fr.eu [213.251.130.73]
10 84 ms 90 ms 87 ms vss-6b-6k.fr.eu [91.121.128.42]
11 78 ms 78 ms 84 ms ks392140.kimsufi.com [176.31.108.191]

Trace complete.

C:\Users\JAK>tracert 176.31.108.191

Tracing route to ks392140.kimsufi.com [176.31.108.191]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 14 ms 15 ms 17 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 15 ms 15 ms 14 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 14 ms 14 ms 14 ms ge2-6-1.cr2.core.thn.uk.murphx.net [89.145.254.1
69]
5 14 ms 14 ms 15 ms ge1-2-1.crs1.core.thn.uk.murphx.net [109.170.249
.45]
6 14 ms 14 ms 14 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
7 78 ms 78 ms 74 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
8 14 ms * 15 ms ldn-1-6.uk.eu [94.23.122.125]
9 90 ms 92 ms 96 ms rbx-g1-a9.fr.eu [213.251.130.73]
10 96 ms 93 ms 88 ms vss-6b-6k.fr.eu [91.121.128.42]
11 78 ms 78 ms 76 ms ks392140.kimsufi.com [176.31.108.191]

Trace complete.

C:\Users\JAK>

Also here are 2 more traceroutes, one to bbc.co.uk and one to the teamspeak server when i am getting rubbish ping. These were taken at around 21:30 9th may.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\JAK>tracert bbc.co.uk

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

1 <1 ms <1 ms 1 ms 192.168.2.1
2 14 ms 14 ms 13 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 15 ms 14 ms 14 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 15 ms 14 ms 13 ms ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.1
61]
5 16 ms 14 ms 14 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
6 * * * Request timed out.
7 * * * Request timed out.
8 14 ms 14 ms 15 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
9 15 ms 14 ms 14 ms 132.185.255.134
10 15 ms 14 ms 14 ms 212.58.241.131

Trace complete.

C:\Users\JAK>tracert 176.31.108.191

Tracing route to ks392140.kimsufi.com [176.31.108.191]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 15 ms 14 ms 14 ms lns5.uan.thn.uk.murphx.net [89.145.254.75]
3 15 ms 17 ms 13 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
4 125 ms 217 ms 219 ms ge2-6-1.cr2.core.thn.uk.murphx.net [89.145.254.1
69]
5 15 ms 14 ms 14 ms ge1-2-1.crs1.core.thn.uk.murphx.net [109.170.249
.45]
6 15 ms 14 ms 14 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
7 72 ms 55 ms 51 ms ge1-0.ar2.lon2.gblx.net [195.66.224.112]
8 144 ms * 104 ms ldn-1-6.uk.eu [94.23.122.125]
9 143 ms 143 ms 145 ms rbx-g1-a9.fr.eu [213.251.130.73]
10 142 ms * 159 ms vss-6b-6k.fr.eu [91.121.128.42]
11 164 ms 160 ms 159 ms ks392140.kimsufi.com [176.31.108.191]

Trace complete.

C:\Users\JAK>

Problems with gblx.net transit too now? That doesn't look good

I think ADSL24 are having some issues that they are not willing to admit at current. I am also an ADSL24 customer, have been for about 6 months with no issues until the last two or three weeks.

I play Counter-Strike most evenings on my Clan server with a ping of around 30-40ms. Suddenly, almost every evening my ping varies from 100-200ms.

Nothing has changed in my set-up of my computer or router. I also know another ADSL24 customer who plays counter-strike and is having the EXACT same issue and almost identicle ping as me (100-200) and at the same times.

I know i've been sending support tickets for the last week and so has he. This is clearly a problem that lies with ADSL24 as everyone else I know of on UK ADSL Broadband can play on this server absolutly fine.

I went with ADSL24 because of good reviews but now i'm seriously regretting it and wanting to change ISPs.