Strange routing to Germany

[Echo147]

This is to a friend's Quake 3 server - in the last few days it's started routing through the USA east coast before getting to Germany

1    <1 ms    <1 ms    <1 ms  my.router [192.168.1.1]
  2    17 ms    16 ms    20 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    18 ms    16 ms    16 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    17 ms    20 ms    17 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    20 ms    18 ms    17 ms  ae-32-56.ebr2.London1.Level3.net [4.68.116.190]
  6    85 ms    88 ms    89 ms  ae-4.ebr1.NewYork1.Level3.net [4.69.132.109]
  7    97 ms    89 ms    90 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
  8    97 ms    90 ms    90 ms  ae-74-74.ebr4.NewYork1.Level3.net [4.69.134.117]
  9    92 ms    91 ms    90 ms  ae-3.ebr4.Washington1.Level3.net [4.69.132.93]
10    92 ms    92 ms    90 ms  ae-94-94.csw4.Washington1.Level3.net [4.69.134.190]
11    93 ms    92 ms    92 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.141]
12     *      116 ms   108 ms  ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
13     *        *        *     Request timed out.
14   108 ms   106 ms   107 ms  ae-11-51.car1.Atlanta1.Level3.net [4.68.103.2]
15   115 ms   117 ms   113 ms  198.xe-1-3-0.cr1.atl1.us.scnet.net [4.71.20.2]
16   107 ms   107 ms   108 ms  216.246.113.14
17   106 ms   107 ms   106 ms  3-1.r1.dc.hwng.net [69.16.191.65]
18   105 ms   105 ms   107 ms  2-3.r1.dc.hwng.net [69.16.190.25]
19   121 ms   120 ms   121 ms  1-1.r1.am.hwng.net [69.16.191.61]
20   127 ms   126 ms   128 ms  1-1.r1.fr.hwng.net [69.16.191.82]
21   127 ms   130 ms   129 ms  81.171.40.22
22   127 ms   127 ms   128 ms  r5-r7.gatewayrouter.net [89.149.218.1]
23   127 ms   132 ms   128 ms  89-149-218-18.internetserviceteam.com [89.149.218.18]
24   129 ms   128 ms   130 ms  endboss.org [89.149.208.93]

[Lance]

Welcome to the forum, echo! Have a welcome karma!

The best thing you can do is email support who may be able to change the route. I agree it is a strange way to be routed and although it is outside of idnet's control the actual route it takes, they may be able to change the route after hop 3.

[Sebby]

As Lance says, a quick email/call to support should get to the bottom of this.

[Echo147]

Ok will do, thanks both

[Lance]

Let us know how you get on!

[Echo147]

Just to update: Had a quick response from a nice chap in support on Mon 3rd - seems sorted now

Reply from 89.149.208.93: seq=0000 time=30.457ms TTL=49 ID=1a8c
Reply from 89.149.208.93: seq=0001 time=32.533ms TTL=49 ID=1a8d
Reply from 89.149.208.93: seq=0002 time=31.428ms TTL=49 ID=1a8e
Reply from 89.149.208.93: seq=0003 time=30.980ms TTL=49 ID=1a8f

Statistics for endboss.org:
    Packets: sent=4, rcvd=4, error=0, lost=0 (0% loss) in 1.530980 sec
    RTTs of replies in ms: min/avg/max: 30.457 / 31.349 / 32.533

IDNet for the win!

[Sebby]

Excellent.

[Rik]

We've seen IDNet do this for customers before, if they can find a way to solve a problem, they will. Thanks for letting us know.