[pieman]

Hi there,

I'm timing out a lot on connections to the 69er.co.uk TF2 servers. It's been happening for the last 2 days. The problem is intermittent but highly regular, at first I thought it was my ISP(freedom2surf, which is now owned by Tiscali, sigh), throttling or something. But it appears to be on your end, here's 2 traceroutes (1st successful, 2nd failed) :


C:\Documents and Settings\nick>tracert 81.19.219.161

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

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 14 ms 14 ms 20 ms l1.ar10.f2s.hx4.dsl.pipex.net [62.241.161.237]
3 14 ms 14 ms 14 ms ge-2-1-2.2.cr01.hx4.dsl.pipex.net [62.241.167.13
]
4 14 ms 14 ms 13 ms po3-102.cr05.hx2.bb.gxn.net [62.72.139.21]
5 14 ms 14 ms 14 ms lonap2.enta.net [193.203.5.135]
6 15 ms 14 ms 15 ms te4-1.telehouse-north.core.enta.net [87.127.236.
38]
7 15 ms 15 ms 15 ms Transit-enta.KillerCreation.co.uk [62.249.255.18
6]
8 15 ms 15 ms 15 ms server.killercreation.co.uk [81.19.219.161]

Trace complete.

Now when it fails (more often than not).

C:\Documents and Settings\nick>tracert 81.19.219.161

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

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 14 ms 14 ms 14 ms l1.ar10.f2s.hx4.dsl.pipex.net [62.241.161.237]
3 14 ms 14 ms 14 ms ge-2-1-2.2.cr01.hx4.dsl.pipex.net [62.241.167.13
]
4 14 ms 14 ms 14 ms po3-102.cr05.hx2.bb.gxn.net [62.72.139.21]
5 14 ms 14 ms 15 ms lonap2.enta.net [193.203.5.135]
6 15 ms 14 ms 14 ms te4-1.telehouse-north.core.enta.net [87.127.236.
38]
7 * 15 ms * Transit-enta.KillerCreation.co.uk [62.249.255.18
6]
8 * * * Request timed out.
9 * * * Request timed out.
10 etc

On further investigation, after trying all of 69er's servers, it seems to be all killer creation servers. It actually times out a lot more on the Transit-enta subdomain. I don't have this problem with any other(none killercreation) servers.

I hope this helps you find the problem.

This post has been edited by pieman: 05 May 2008 - 10:22 PM

[KC-Justin]

Hi Pieman

Thanks for the trace. We were aware of the issue yesterday and made some changes to our routing config last night to bypass a particular upstream provider that appeared to be causing this.

With routing there is obviously your connection to us and our connection back to you, you won't always see the same provider for the in and out trace. As you can see you were coming in over Pipex > Lonap > ENTA > KillerCreation and our connection back to you went KillerCreation > Goscomb > Datahop > Pipex.

What appeared to you as a problem with ENTA was actually at the Goscomb/datahop hop in the trace back to you - something which you can't see your end.

We've made some changes that should see traffic being pushed over our partial transit provider ENTA and our global provider Telewest. Below I've pasted the back route from KC to Pipex, let us know if you have any further issues.

1 gateway (81.19.219.1) 0.330 ms 0.293 ms 0.283 ms
2 gi1-5.telehouse-north.core.enta.net (62.249.255.185) 1.246 ms 1.199 ms 1. 111 ms
3 te5-3.telehouse-east2.core.enta.net (87.127.236.37) 1.237 ms 1.212 ms 1.1 74 ms
4 te2-3.cr05.hx2.bb.gxn.net (193.203.5.14) 1.479 ms 1.452 ms 1.358 ms
5 ae0-104.cr02.hx4.dsl.pipex.net (62.72.139.26) 1.252 ms 1.221 ms 1.225 ms
6 l1.ar10.f2s.hx4.dsl.pipex.net (62.241.161.237) 2.355 ms 2.069 ms 1.975 ms

[pieman]

Cheers for the swift reply Justin.

I played for ~90 minutes tonight and it is all superb. No timing out or anything, just nice smooth low ping gameplay.

Thanks for providing quality hosting at a reasonable price with great servers and support, and I'm not even a customer.