Hi, as I am sure some of you guys know, I play on your PoE:2 server quite often (Probably one of the best servers around BTW!). But recently, since Fri 10th Nov, I have been experiencing some quite awfull pings on your server.
I'm based in the UK and usually idle at around 100ms to 120ms, which is fine for me considering the gamplay I am getting in return.
However, since Friday I have been anywhere between 600ms and 800ms, sometimes more!, which is obviously way too high to play with. The strange thing is that other servers seem to be still pinging ok!
I have done tracert and ping command in MS DOS and have the results for you below, I will be taking this up with my ISP to see if they can give me any answers for the sudden change in ping times, but I thought I'd post it here aswell, just incase any of the server admins/tech guys are able to identify a problem at your end and/or give me some feedback.

Thanks in advance and here's hoping I'll be back on the TG server soon!

Oh BTW, where exactly is the Server located? Just incase my ISP ask

Ping and tracert results....

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Primary User>ping 64.34.165.134 -t

Pinging 64.34.165.134 with 32 bytes of data:

Reply from 64.34.165.134: bytes=32 time=643ms TTL=113
Reply from 64.34.165.134: bytes=32 time=679ms TTL=113
Reply from 64.34.165.134: bytes=32 time=701ms TTL=113
Reply from 64.34.165.134: bytes=32 time=695ms TTL=113
Reply from 64.34.165.134: bytes=32 time=661ms TTL=113
Reply from 64.34.165.134: bytes=32 time=654ms TTL=113
Reply from 64.34.165.134: bytes=32 time=656ms TTL=113
Reply from 64.34.165.134: bytes=32 time=649ms TTL=113
Reply from 64.34.165.134: bytes=32 time=654ms TTL=113
Reply from 64.34.165.134: bytes=32 time=629ms TTL=113
Reply from 64.34.165.134: bytes=32 time=623ms TTL=113
Reply from 64.34.165.134: bytes=32 time=608ms TTL=113
Reply from 64.34.165.134: bytes=32 time=641ms TTL=113
Reply from 64.34.165.134: bytes=32 time=656ms TTL=113
Reply from 64.34.165.134: bytes=32 time=661ms TTL=113
Reply from 64.34.165.134: bytes=32 time=633ms TTL=113
Reply from 64.34.165.134: bytes=32 time=617ms TTL=113
Reply from 64.34.165.134: bytes=32 time=609ms TTL=113
Reply from 64.34.165.134: bytes=32 time=606ms TTL=113
Reply from 64.34.165.134: bytes=32 time=601ms TTL=113

Ping statistics for 64.34.165.134:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 601ms, Maximum = 701ms, Average = 643ms
Control-C
^C
C:\Documents and Settings\Primary User>tracert 64.34.165.134

Tracing route to flexsrv3.tacticalgamer.com [64.34.165.134]
over a maximum of 30 hops:

1 7 ms 7 ms 12 ms 10.90.72.1
2 10 ms 8 ms 8 ms oldh-t2cam1-a-ge-wan43-117.inet.ntl.com [80.5.164.69]
3 8 ms 8 ms 17 ms manc-t3core-1a-ge-112-0.inet.ntl.com [195.182.175.77]
4 8 ms 30 ms 33 ms man-bb-a-so-020-0.inet.ntl.com [213.105.175.1]
5 23 ms 11 ms 11 ms lee-bb-b-so-100-0.inet.ntl.com [62.253.185.194]
6 10 ms 8 ms 29 ms lee-bb-a-ge-000-0.inet.ntl.com [62.253.187.185]
7 45 ms 14 ms 12 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 27 ms 26 ms 26 ms so-7-0-0-dcr1.tsd.cw.net [166.63.211.129]
9 25 ms 25 ms 25 ms as0-dcr2.tsd.cw.net [195.2.10.166]
10 143 ms 127 ms 134 ms so-0-0-0-dcr1.nyk.cw.net [195.2.10.109]
11 125 ms 127 ms 127 ms so-0-0-0-ecr1.nyk.cw.net [195.2.3.14]
12 485 ms 484 ms 491 ms nyiix.peer1.net [198.32.160.65]
13 495 ms 507 ms 496 ms oc48-pos4-0.nyc-telx-dis-a.peer1.net [216.187.115.165]
14 500 ms 511 ms 509 ms oc48pos0-0.wdc-sp2-cor-2.peer1.net [216.187.115.222]
15 103 ms 101 ms 111 ms oc48-pos2-0.wdc-sp2-cor-1.peer1.net [216.187.115.245]
16 505 ms 515 ms 521 ms oc48-pos6-0.wdc-sbsp2-dis-1.serverbeach.com [216.187.115.238]
17 550 ms 554 ms 556 ms flexsrv3.tacticalgamer.com [64.34.165.134]

Trace complete.

C:\Documents and Settings\Primary User>