@StevenC, @Isengard
Hi Gents
Those tracert results are actually just about perfect, just slightly confusing and this is something I have clarified with our engineers before. Because our international circuits are tunneled to the London POP you don't see the WACS routing on the trace. So when the latency jumps on hop 5 this is when you are actually hitting the London side of the link, which in fact makes that ping pleasantly low
You will also note that between that hop and your international destination the latency only increases by around 10 - 20ms - if that was local latency that would be, well just impossible
You can verify this very easily by running a continuous ping test to both an international and a local address. If that latency was on a local hop then you would see it locally as well.
I just ran these two tests quickly from my desktop, which are valid as our office LAN traffic in CPT follows the exact same routing as the ADSL network. The first is to Mybroadband, the second to the BBC.
Ping statistics for 41.203.21.137:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 53ms, Average = 33ms
Ping statistics for 212.58.241.131:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 146ms, Average = 145ms
Which is not to say that I'm disputing the fact that you're experiencing a problem, we're just going to have to dig a little further to establish the actual cause.
I will run some tests myself on my own GW2 experience to see how it compares and ask the Gamezone team to double check with the engineers on GW2 traffic signatures for starters, maybe there is a simple explanation for this.