[alphanorway]

Hey Just bought a killercreation Battlefield 2 server. But players fro DENMARK ping 70 on it??? I mean, are you kidding me? The same players Im talking off ping between 20-30 on a xxxx.com server.

Can you admins explane this? Cause Im close to getting a xxxx server instead, this ping is simply ridicules from danish players on a UK server.

[discoveryuk]

First off, don't post this in pre-sales. If you bought it, you already paid

As for the ping times, are you referring to all players from Denmark, or just a select few friends? It might be worth you finding that out before making rash decisions. I can safely say this is one of the best companies I have used, and wouldn't change to another without a very good reason, not simply Danish people get a bad ping. Run through all the normal steps of rebooting the router in the evening and such, and checking if the ISP has reported any connection issues. I have Danish people playing on my servers (although I have a dedicated server) and they report the pings are perfectly fine (around 30-40 in most cases, although those with poor connections are a little higher at 60-70).

[KC-Luke]

Hi alphanorway

Do you know any of the players getting the bad ping? If so, could you please get them to make a tracert for us and email it to support@killercreation.co.uk or alternatively join our IRC channel (#killercreation.co.uk @ Quakenet) where we will be able to assist them further.

Kind Regards,

[alphanorway]

Well Ive sent back the tracerts to you on email, but no respone. Hoping for answer quickly

[KC-Justin]

Hi,

To shed some light on this, the issue you are seeing alphanorway relates to a congested peering link between TInet (one of our transit peers) and Telenor who provide transit services for many smaller ISP's. One of the ISP's affected is Cybercity DK that provide ADSL based connections for home users in Denmark.

To help resolve the issue, we have contacted TInet's NOC with the trace routes received from you via email and should hopefully hear back shortly.

Please note, this is only affecting end users who ISP's are utilizing Telenor and not all Danish ISP's. For example, I have included a trace below from another Danish ISP called Tele DK (TDC).

traceroute to 81.19.208.21:

1 vlan275.slttdk18nxc1.ip.tele.dk (193.162.154.29) 0.363 ms 0.307 ms 0.500 ms
2 ge-4-2-0.sltnxu4.dk.ip.tdc.net (83.88.25.97) 0.303 ms 0.240 ms 0.216 ms
3 xe-0-0-0.slt27nxu5.dk.ip.tdc.net (83.88.2.161) 0.465 ms 0.446 ms 0.427 ms
4 xe-0-0-3.arcnqt1.dk.ip.tdc.net (83.88.22.104) 27.558 ms 0.566 ms 0.547 ms
5 ae-0.boanqt1.dk.ip.tdc.net (83.88.13.41) 3.014 ms 2.954 ms 2.889 ms
6 ae-0.alb2nqt1.dk.ip.tdc.net (83.88.13.43) 14.483 ms 3.830 ms 3.144 ms
7 te3-2.alb2nxc7.dk.ip.tdc.net (83.88.23.58) 4.920 ms 3.984 ms 3.853 ms
8 peer.ge2-15-1000M.alb2nxc7.peer.tele.dk (195.215.109.58) 3.818 ms 3.806 ms 3.832 ms
9 xe-5-1-0.lon10.ip4.tinet.net (89.149.187.25) 27.676 ms
xe-3-0-0.lon10.ip4.tinet.net (89.149.186.189) 27.694 ms 39.010 ms
10 tiscali.killercreation.co.uk (77.67.65.34) 27.866 ms 27.786 ms 27.857 ms
11 rt-2-centro.killercreation.co.uk (217.146.94.2) 28.659 ms 28.602 ms 28.610 ms
12 server.killercreation.co.uk (81.19.208.21) 28.612 ms 28.685 ms 28.671 ms

[KC-Justin]

We have received an update from TInet regarding this. The issue, as suspected, appears to be a congested TInet / Telenor private peering link affecting certain hours of the day.

Here is a trace I've just done around 01:30 tonight from us to affected ISP Cybercity DK.

1 gateway.killercreation.co.uk (81.19.219.1) 0.345 ms 0.206 ms 0.399 ms
2 rt-1-thn.killercreation.co.uk (217.146.94.1) 1.114 ms 0.942 ms 0.968 ms
3 tiscali.killercreation.co.uk (77.67.65.33) 0.944 ms 0.919 ms 0.933 ms
4 xe-10-1-0.ams20.ip4.tinet.net (89.149.184.166) 8.438 ms 8.388 ms 8.452 ms
5 213.200.75.18 (213.200.75.18) 8.701 ms 8.450 ms 8.450 ms
6 ti3004c310-ae2-0.ti.telenor.net (146.172.105.53) 30.930 ms 30.923 ms 30.899 ms
7 ti3004b300-ae0-0.ti.telenor.net (146.172.105.42) 31.144 ms 30.922 ms 30.913 ms
8 148.122.9.26 (148.122.9.26) 31.409 ms 31.418 ms 31.434 ms
9 ae0-0.mcr1-albx.ip.cybercity.dk (212.242.6.169) 31.393 ms 31.415 ms 31.408 ms
10 lag0-10.mxc1-albx.ip.cybercity.dk (212.242.7.154) 34.655 ms 35.906 ms 37.154 ms
11 77.215.155.5 (77.215.155.5) 36.395 ms 36.399 ms 36.652 ms

If you compare that with earlier this evening:

traceroute to 77.215.155.5 (77.215.155.5), 30 hops max, 40 byte packets
1 gateway.killercreation.co.uk (81.19.219.1) 0.374 ms 0.345 ms 0.362 ms
2 rt-1-thn.killercreation.co.uk (217.146.94.1) 1.067 ms 0.939 ms 1.061 ms
3 tiscali.killercreation.co.uk (77.67.65.33) 0.940 ms 0.923 ms 1.057 ms
4 xe-10-1-0.ams20.ip4.tinet.net (89.149.184.166) 8.679 ms 8.665 ms 8.616 ms
5 213.200.75.18 (213.200.75.18) 8.763 ms 8.763 ms 8.762 ms
6 ti3004c310-ae2-0.ti.telenor.net (146.172.105.53) 30.949 ms 30.745 ms 30.990 ms
7 ti3004b300-ae0-0.ti.telenor.net (146.172.105.42) 48.497 ms 47.135 ms 46.655 ms
8 148.122.9.26 (148.122.9.26) 31.218 ms 31.376 ms 31.318 ms
9 ae0-0.mcr1-albx.ip.cybercity.dk (212.242.6.169) 31.412 ms 31.431 ms 31.400 ms
10 lag0-10.mxc1-albx.ip.cybercity.dk (212.242.7.154) 33.396 ms 33.142 ms 32.895 ms
11 77.215.155.5 (77.215.155.5) 69.368 ms 69.647 ms 69.603 ms

TInet have opened up a ticket with Telenor to track and resolve the issue. Most likely addtional peering capacity will have to be arranged between them but in the mean time, I imagine each party will look to routing some traffic around the congested peer.

As soon as we hear anything further I'll update the thread.

[alphanorway]

Thank you for good reply, hope this can be sorted out

[alphanorway]

So whats happening???

[KC-Justin]

Hi alphanorway,

TInet replied this morning suggesting they have introduced some traffic engineering to get around the issue. From my intial tests, all appears to be ok, see below:

1 gateway.killercreation.co.uk (81.19.219.1) 0.394 ms 0.232 ms 0.351 ms
2 rt-1-thn.killercreation.co.uk (217.146.94.1) 1.071 ms 0.925 ms 0.940 ms
3 tiscali.killercreation.co.uk (77.67.65.33) 0.911 ms 1.089 ms 0.881 ms
4 xe-10-1-0.ams20.ip4.tinet.net (89.149.184.166) 8.400 ms 8.345 ms 8.562 ms
5 213.200.75.18 (213.200.75.18) 8.556 ms 8.557 ms 8.558 ms
6 ti3004c310-ae2-0.ti.telenor.net (146.172.105.53) 31.042 ms 31.022 ms 31.022 ms
7 ti3004b300-ae0-0.ti.telenor.net (146.172.105.42) 43.266 ms 31.149 ms 31.079 ms
8 148.122.9.26 (148.122.9.26) 38.158 ms 38.107 ms 37.628 ms
9 ae0-0.mcr1-albx.ip.cybercity.dk (212.242.6.169) 31.394 ms 31.388 ms 31.395 ms
10 lag0-10.mxc1-albx.ip.cybercity.dk (212.242.7.154) 33.391 ms 32.894 ms 32.641 ms
11 77.215.155.5 (77.215.155.5) 36.389 ms 36.632 ms 36.614 ms

If you could confirm later this evening by either updating this thread or mailing us, that would be great..

[alphanorway]

KC-Justin, on 07 October 2009 - 09:33 AM, said:

Hi alphanorway,

TInet replied this morning suggesting they have introduced some traffic engineering to get around the issue. From my intial tests, all appears to be ok, see below:

1 gateway.killercreation.co.uk (81.19.219.1) 0.394 ms 0.232 ms 0.351 ms
2 rt-1-thn.killercreation.co.uk (217.146.94.1) 1.071 ms 0.925 ms 0.940 ms
3 tiscali.killercreation.co.uk (77.67.65.33) 0.911 ms 1.089 ms 0.881 ms
4 xe-10-1-0.ams20.ip4.tinet.net (89.149.184.166) 8.400 ms 8.345 ms 8.562 ms
5 213.200.75.18 (213.200.75.18) 8.556 ms 8.557 ms 8.558 ms
6 ti3004c310-ae2-0.ti.telenor.net (146.172.105.53) 31.042 ms 31.022 ms 31.022 ms
7 ti3004b300-ae0-0.ti.telenor.net (146.172.105.42) 43.266 ms 31.149 ms 31.079 ms
8 148.122.9.26 (148.122.9.26) 38.158 ms 38.107 ms 37.628 ms
9 ae0-0.mcr1-albx.ip.cybercity.dk (212.242.6.169) 31.394 ms 31.388 ms 31.395 ms
10 lag0-10.mxc1-albx.ip.cybercity.dk (212.242.7.154) 33.391 ms 32.894 ms 32.641 ms
11 77.215.155.5 (77.215.155.5) 36.389 ms 36.632 ms 36.614 ms

If you could confirm later this evening by either updating this thread or mailing us, that would be great..

Confirmed

[UberMensch]

Once again, KC goes above and beyond the call of duty for their customers. You guys need more awards!

[IXL]

This is the perfect example why Ive moved to KC. Ive used a variety of providers before, and so far nothing has come close to the help and depth of support. It really is a all in one, round solution.

Keep it up guys.

[itsthem]

UberMensch, on 12 October 2009 - 08:12 AM, said:

Once again, KC goes above and beyond the call of duty for their customers. You guys need more awards!

Have to agree, shame the OP couldn't say thank you.

[EvilEddy]

itsthem, on 18 September 2010 - 06:52 PM, said:

Have to agree, shame the OP couldn't say thank you.

You should check the date the OP made the post.