ADSL24 High Ping on Weekends

I hope this is the right section. This is specifically related to game servers in Counter-Strike: Source and Team Fortress 2.

This only happens during weekends, during peak daytime hours, i.e. 11am-11pm roughly. Where I usually have 20ms in Steam's server browser, almost every server increases by up to 100ms. Speedtests seem to be completely unaltered from times when this is affecting me to when it isn't. I get around 36Mb down and 1.5 up no matter what. It began last weekend or the one before that.

My server browser. It isn't too bad right now, but notice how the UK server highlighted is ~70ms whereas it is usually in the low 20s.

Here is a trace route to that UK server. It seems to get stopped at 4.68.110.113. Here is another tracert to a server in the Netherlands on which I usually have 30ms.

This is the view of net_graph in Team Fortress which tracks your ping and packets lost. Notice the 1000ms spikes and just how [censored] unstable it is. In the past it has been a horizontal line right at the bottom of the graph.

This is my exchange.

Thanks for any help you can give.

Edited by deleted (Sun 29-Apr-12 19:23:52)

Your traceroutes show your pings are perfectly low and stable until well after they leave your ISPs network. In fact, the problem appears to be in peering between tinet and level3, both 3rd-party transit providers.

I find it strange that your ISP needs to go through two different transit providers to reach a London IP when it already has a POP in London. By the looks of things, routing is broken, both on your ISPs network and off it, the latter only showing up as a result of the former

Hm, okay. Is this an issue I should be taking up with my ISP, do you think?

Yes, kind of.

While the problem doesn't seem to be on your ISPs network, they do appear to be directly traffic strangely. I can't really say more than that, since I don't know what "normal" routing looks like for your ISP

But even so the extra hop to get to the destination is not causing any latency issues or packet loss so should not be relevent.

Here's a traceroute from our office line:

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

1 <1 ms <1 ms <1 ms x.x.x.x
2 12 ms 12 ms 12 ms lns2.uan.the.uk.murphx.net [94.30.127.73]
3 11 ms 11 ms 11 ms er1.uan.the.uk.murphx.net [94.30.127.65]
4 11 ms 11 ms 11 ms ge2-6-1.crs2.core.the.uk.murphx.net [94.30.127.233]
5 29 ms 28 ms 28 ms 195.50.122.69
6 29 ms 29 ms 28 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
7 35 ms 37 ms 37 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
8 38 ms 38 ms 40 ms ae-46-46.ebr2.Amsterdam1.Level3.net [4.69.143.73]
9 38 ms 40 ms 48 ms ae-58-223.csw2.Amsterdam1.Level3.net [4.69.153.210]
10 38 ms 38 ms 38 ms ae-2-52.edge3.Amsterdam1.Level3.net [4.69.139.169]
11 41 ms 44 ms 47 ms TRANSIP-BV.edge3.Amsterdam1.Level3.net [212.72.33.110]
12 47 ms 49 ms 51 ms www.creativehosting.nl [80.69.77.156]

Trace complete.

On the contrary, I would say 17ms to cross London and 36ms to reach Amsterdam is a latency problem. That latency should be <1ms and <10ms respectively.

Here's a traceroute from my home line in Scotland, which has 15ms of interleaving on it and an extra 400 miles to travel - i.e. a total disadvantage of 27ms. It's still reaching the destination faster than from London on your network:

1 <1 ms <1 ms <1 ms n1.lan [10.1.0.11]
2 20 ms 20 ms 20 ms gateway.bt [217.32.142.104]
3 20 ms 20 ms 20 ms route-1.dc0-h1.bt [217.32.142.158]
4 26 ms 26 ms 26 ms route-3.dc1-h2.bt [213.120.163.26]
5 28 ms 27 ms 27 ms 217.32.27.78
6 26 ms 26 ms 26 ms route-0.dc1-h4.bt [217.32.27.178]
7 26 ms 26 ms 32 ms route-1.mr-h5.bt [109.159.250.94]
8 41 ms 35 ms 35 ms core1-te0-4-0-0.ealing.ukcore.bt.net [109.159.250.1]
9 33 ms 33 ms 33 ms transit1-pos1-0-0.telehouse.ukcore.bt.net [62.6.201.82]
10 32 ms 32 ms 32 ms t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
11 32 ms 32 ms 32 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.17]
12 32 ms 33 ms 32 ms te0-3-0-6.ccr21.lon01.atlas.cogentco.com [130.117.14.49]
13 41 ms 41 ms 41 ms te0-2-0-4.ccr21.lon13.atlas.cogentco.com [154.54.57.114]
14 41 ms 41 ms 41 ms te0-1-0-0.ccr21.ams03.atlas.cogentco.com [130.117.1.37]
15 41 ms 51 ms 40 ms te3-1.ccr01.ams02.atlas.cogentco.com [154.54.60.126]
16 40 ms 40 ms 40 ms transip-bv.demarc.cogentco.com [149.6.128.66]
17 40 ms 41 ms 40 ms www.creativehosting.nl [80.69.77.156]

Trace complete.

Your traceroute should be reaching the server in 20ms, not 47-51.

Same here, that's very high for UK

Sky LLU test

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 39 ms ************bb.sky.com [*.*.*.*]
3 11 ms 11 ms 10 ms ip-84-38-37-12.easynet.co.uk [84.38.37.12]
4 11 ms 10 ms 11 ms te0-6-0-2.er10.txlon.ov.easynet.net [89.200.134.
121]
5 10 ms 8 ms 10 ms bu4.gr10.bllon.uk.easynet.net [89.200.135.143]
6 15 ms 15 ms 14 ms te1-0-0.gr10.saams.nl.easynet.net [87.86.77.60]

7 15 ms 15 ms 15 ms amsix.router1.dcg.transip.net [195.69.144.244]
8 16 ms 15 ms 15 ms www.creativehosting.nl [80.69.72.146]

Trace complete

Here is mine on my BE retail connection Fastpath enabled From the north west , Another example of how bad Telefonica's routing is , when you compare it to that of what was Easynet,now sky,

I had gotten used to how good their routing /peering was when i was with Ukonline Be retail

From telefonica onwards the latency is too high , and why it gets routed via Germany then the Netherlands i don't know, seems a longer route

Edited by tommy45 (Mon 30-Apr-12 17:31:02)

Thanks for all the responses.

For reference, this is my tracert to the same NL server right now. It's only during weekends when I get silly lag and it becomes unplayable. If it were a steady it would be manageable but my ping jumps around all over the place. In Team Fortress especially some packets seem to get lost (as you can see on the Team Fortress net_graph I linked in the original post).

Edited by deleted (Mon 30-Apr-12 18:08:05)

Looking back at both of ltadsl's and Adsl24's traceroutes, the problems appear to be with Level3 transit. In both cases, problems start when the traffic has left your ISP and hit Level 3's network. For ltadsl, traffic goes through tinet first, but there are no problems until it reaches Level3.

The problem could be either the link between your ISP and Level3 or Level3's network itself. Possibly more likely the latter, because traffic not going direct from your ISP to level3 is also affected (although when I route my traffic via the same hops its not affected, but then it's not the weekend right now either so its not exactly conclusive).

The UK server is actually hosted on Level3's network, so going via Level3 is unavoidable. The Netherlands server isn't, so your ISP could conceivably re-route traffic over a different provider until the problem with Level3 is resolved.

Thanks so much for your help.

Level 3 being the problem would make sense as the server I have the most trouble with is that UK one. It's where the lag is the worst by far. I will attempt to contact ADSL24 in the near future with all the information from this thread and see what they say (unless James replies again with any other advice).

It just started happening (7.49pm GMT) so it looks like during any peak times I start lagging and most online games become unplayable.

Edited by deleted (Mon 30-Apr-12 19:50:08)

In reply to a post by ltadsl:

Thanks so much for your help.

Level 3 being the problem would make sense as the server I have the most trouble with is that UK one. It's where the lag is the worst by far. I will attempt to contact ADSL24 in the near future with all the information from this thread and see what they say (unless James replies again with any other advice).

It just started happening (7.49pm GMT) so it looks like during any peak times I start lagging and most online games become unplayable.

Left ping plotter pinging that host, It now shows even higher latency and packet loss!! packet loss is only across the level 3 hops ,but latency has increased from around 19:30

The first two of the tracerts below were taken hours ago, but I deliberately left the Command Window open.

The third was taken just before writing this post, as I thought my results relevant to the reference to Level 3.

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    14 ms    14 ms    14 ms  lo0-central7.ptn-ag04.plus.net [195.166.130.129]
  3    20 ms    13 ms    13 ms  84.93.251.155
  4    14 ms    14 ms    13 ms  po6.ptw-gw01.plus.net [212.159.1.136]
  5    64 ms    14 ms    14 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  6    16 ms    27 ms    20 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120]
  7    14 ms    14 ms    14 ms  ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
  8    21 ms    21 ms    21 ms  ae-46-46.ebr2.Amsterdam1.Level3.net [4.69.143.73]
  9    22 ms    21 ms    22 ms  ae-59-224.csw2.Amsterdam1.Level3.net [4.69.153.214]
 10    21 ms    21 ms    21 ms  ae-2-52.edge3.Amsterdam1.Level3.net [4.69.139.169]
 11    51 ms    24 ms    21 ms  TRANSIP-BV.edge3.Amsterdam1.Level3.net [212.72.33.110]
 12    22 ms    24 ms    22 ms  www.creativehosting.nl [80.69.72.146]

Trace complete.

C:\Users\Bob>tracert 80.69.77.156

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

  1     1 ms    <1 ms    <1 ms  192.168.11.1
  2    15 ms    15 ms    14 ms  lo0-central7.ptn-ag04.plus.net [195.166.130.129]
  3    14 ms    17 ms    14 ms  84.93.251.155
  4    17 ms    19 ms    14 ms  po6.ptw-gw01.plus.net [212.159.1.136]
  5    67 ms    26 ms    14 ms  te-4-2.car5.London1.Level3.net [217.163.45.249]
  6    26 ms    21 ms    23 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120]
  7    28 ms    15 ms    14 ms  ae-59-224.ebr2.London1.Level3.net [4.69.153.141]
  8    23 ms    22 ms    22 ms  ae-48-48.ebr2.Amsterdam1.Level3.net [4.69.143.81]
  9    21 ms    21 ms    24 ms  ae-59-224.csw2.Amsterdam1.Level3.net [4.69.153.214]
 10    23 ms    21 ms    21 ms  ae-2-52.edge3.Amsterdam1.Level3.net [4.69.139.169]
 11    22 ms    22 ms    57 ms  TRANSIP-BV.edge3.Amsterdam1.Level3.net [212.72.33.110]
 12    22 ms    22 ms    22 ms  www.creativehosting.nl [80.69.77.156]

Trace complete.

C:\Users\Bob>tracert www.creativehosting.nl

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    29 ms    20 ms    16 ms  lo0-central7.ptn-ag04.plus.net [195.166.130.129]
  3    17 ms    15 ms    13 ms  84.93.251.155
  4    14 ms    14 ms    24 ms  po6.ptw-gw01.plus.net [212.159.1.136]
  5    14 ms    14 ms    13 ms  te-3-4.car5.London1.Level3.net [217.163.45.181]
  6    23 ms    24 ms    23 ms  ae-52-52.csw2.London1.Level3.net [4.69.139.120]
  7    15 ms    14 ms    14 ms  ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
  8    21 ms    21 ms    21 ms  ae-46-46.ebr2.Amsterdam1.Level3.net [4.69.143.73]
  9    24 ms    22 ms    21 ms  ae-59-224.csw2.Amsterdam1.Level3.net [4.69.153.214]
 10    21 ms    21 ms    21 ms  ae-2-52.edge3.Amsterdam1.Level3.net [4.69.139.169]
 11    22 ms    22 ms    50 ms  TRANSIP-BV.edge3.Amsterdam1.Level3.net [212.72.33.110]
 12    22 ms    21 ms    21 ms  www.creativehosting.nl [80.69.72.146]

Trace complete.

There doesn't seem to be a problem with it for me.

I contacted ADSL24 through their ticket system and after a little back and forth received this response:

Many thanks for the additional data and screen shot results.
I have spoken to a management individual and can confirm that interleaving is automatically turned off on our Fibre service for all our customers. So that option is exhausted.

Unfortunately theres no way of controlling how data travels over servers.
Looking at your tracerts again ...its evident its out of our realm of control and again ...nothing we can do so every to help you in this matter.

I would advise speaking with your server administrators or server technicians or game support advisors as they might be best to help directly with this issue.

hope this helps.,
If you require any further assistance ...do not hesitate to contact us.

I'm not really sure who to speak to now, if ADSL24 say they can't help. Any ideas?

If your ISP is unable or unwilling to help there's not a lot else you can do. If they run their own network then they're the ones with the control, whether they choose to use it or not, of how your traffic is routed and what transit providers they use. If they don't run their own network, they'll have an agreement with someone else to do it for them and will need to make a complaint on your behalf.

Your options are really limited to complaining again, waiting until it "fixes itself", or moving to a different ISP.

That's what I figured. Cheers anyway. You've been an enormous help.

I believe I'm on a monthly rolling contract so if ADSL24 is unwilling/able to do anything more perhaps it is time to switch to someone who has lower pings. I'm sure there will be information here about who is best.

Edited by deleted (Tue 01-May-12 16:55:46)

Seems at the moment something isn't right at ADSL24, others have posted about poor customer service and then the continuing delays of the FTTC 80/20 service.

As they only resell the service, the problem is with Daisy Networks but you'd of thought that any ISP that values custom would attempt to chase it up with them.

You've got several Tracerts from other ISP's and the Sky LLU seems the best option but all depends on what you want.

Delays on the 80/20 product is nothing to do with us delaying, the issue is that the commercial product manager at one of our wholesale providers has been off the past few weeks due to personal circumstances so regrettably the pricing and packages that we should have been able to launch a while ago have had to be delayed whist someone else takes over that position and finishes the task.

Similarly, we have very, very few complaints about any latency issues in general and as others point out the latency spikes are on a hop past our suppliers network, so nothing on our side is causing the increase in latency on that particular hop.

In this case we've already raised the issue with their NOC team who are looking in to it, but nothing has changed at ADSL24 and forums are generally only a place where you will see a small minority of customers who post about a problem as oppose to the many thousands that don't have any problem at present - just to put that in to perspective

Sorry to jump in on this thread but, do you have a timescale for when 80/20 will be available - also will we have to give 30 days notice to change to it?

And are people who were on the trial, still on the 80/20 service?

Thanks in advance

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.

Thanks very much for the update, Good news about not needing 30 days notice.

Can't wait for the upload!

Thanks again

In reply to a post by Adsl24:

In this case we've already raised the issue with their NOC team who are looking in to it,

This is good to know. As a reseller (presuming based on previous posts) this is what I'd expect you to do, so it's good that it is being done.

On the other hand, this begs the question that, if you have passed this issue on appropriately, why the OP received a message to the contrary, i.e. "nothing we can do so every [sic] to help you in this matter."

isp needs to ditch tinet routing. If they cant or refuse ditch the isp (sorry adsl24).

routing peering issues can be frustrating for customers as I have found 80-90% of time isp's like to play pass the buck and generally dont like fixing such issues.

When I was on a murphx reseller I wasnt happy with the quality of the routing either and left the service although at the same time I dropped adsl altogether so it wasnt my prime reason.

In reply to a post by Adsl24:

In this case we've already raised the issue with their NOC team who are looking in to it, but nothing has changed at ADSL24 and forums are generally only a place where you will see a small minority of customers who post about a problem as oppose to the many thousands that don't have any problem at present - just to put that in to perspective

Thanks for taking the time, James. Does this mean my issue is being looked into?

edit: Up til now I've had a perfect service with ADSL24 and I'm honestly surprised now that my internet has become unusable for gaming during peak hours. Unfortunately due to work these are the only hours I am able to use it.

Edited by deleted (Wed 02-May-12 08:14:19)

Yes, but I'm not sure anything will come back that will be of much use. We'll see what the NOC team say.

I agree, I am with Xilo and the 'local' service is great but the line is outperformed a lot of the time by a SKY BB in the same house. Murphx routing / peering / bandwidth is clearly inferior.

A great example for me is YouTube, frequently unusable on XILO but perfect via SKY.

Have you raised this with us?

You should do if not. Can't recall any tickets referring to YouTube... but we'll be certainly happy to look.

You'll find routing is mostly GXN for the service you're on who have a very extensive network but I could also say similar things for a backup Sky service I have at home to some US-based sites. Normally only used to benchmark and use in emergencies if our own routed network (AS44574) has issues.

Matt

Edited by uno (Wed 02-May-12 20:04:07)

Is there any update on this?

Hi, I am also a ADSL24 customer and have been noticing high latency recently although I am standard broadband not fibre. I am logged into the same Teamspeak server every day and have had a ping of around 17ms for a good year now but starting a week ago, during peak times my ping varies right up as high as 200ms. It's the same for a lot of game servers too, download speed is unaffected and some servers still seem to give the good ping. Any chance this issue is related?

I don't understand most of the tech talk in this thread but i just want to know if this is a problem that is being looked into or if i should just change ISP..

Thanks in advance.
Jak

Well, as discussed in the thread to date, the latency is not occurring on our network, but on one of the peer network that is used to route to the destination server.

We're not having any tickets or support calls raised about latency at the moment so there is certainly no real problem that we are aware of.

We would need you to provide a trace route to the IP of the server you are using so we can see where the latency may be coming from.

To do this, presuming you are on Windows, click on Start and type CMD in the search/run box - then press enter. This will open the command prompt window.

Type: tracert x.x.x.x and press enter, replacing x.x.x.x with the IP of the server you are experiencing the latency on.

Once it completes, right click with the mouse and choose Select All, then right click Copy.

You can then paste the results here for us to advise

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.