Espoo located in USA?

Many users in Thailand suffers local ISP AIS routing. All traffic to Espoo is routed via USA.


tracert freedome-fi-gw.f-secure.akadns.net

 

Tracing route to freedome-fi-gw.f-secure.akadns.net [95.175.104.29] over a maximum of 30 hops:

 

// THAILAND

  1     1 ms    <1 ms     1 ms  Universum1st [192.168.1.1]

  2    38 ms    18 ms    17 ms  10.247.2.138

  3    20 ms    18 ms    16 ms  10.247.2.137

  4    18 ms    17 ms    17 ms  10.154.0.27

  5    18 ms    20 ms    19 ms  49.228.0.101

  6    18 ms    18 ms    21 ms  49.228.0.118

  7    29 ms    26 ms    26 ms  49-231-44-129.sbn-idc.com [49.231.44.129]

  8    43 ms    40 ms    44 ms  49-231-45-231.ais-idc.com [49.231.45.231]

  9    48 ms    47 ms    46 ms  124.158.228.85

// MALAYSIA!!!

10   238 ms   235 ms   239 ms  xe-0-0-0-0.cr-gw-2-kul-pip.my.globaltransit.net [61.11.210.130]

11   245 ms   234 ms   235 ms  61.11.212.58

// USA

12   236 ms   234 ms   234 ms  ae-2.br-gw-1-lax-pip.us.globaltransit.net [124.158.224.18]

13   285 ms   274 ms   227 ms  te0-9-0-24.ccr41.lax04.atlas.cogentco.com [38.104.210.81]

14   286 ms   294 ms   317 ms  be2964.ccr21.lax01.atlas.cogentco.com [154.54.44.77]

15   235 ms   279 ms   233 ms  be2931.ccr21.phx02.atlas.cogentco.com [154.54.44.85]

16   255 ms   252 ms   252 ms  be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]

17   262 ms   266 ms   263 ms  be2928.ccr22.iah01.atlas.cogentco.com [154.54.30.161]

18   286 ms   292 ms   285 ms  be2690.ccr42.atl01.atlas.cogentco.com [154.54.28.129]

19   294 ms   295 ms   303 ms  be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]

20   284 ms   289 ms   287 ms  be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]

// UK

21   373 ms   373 ms   376 ms  be2490.ccr42.lon13.atlas.cogentco.com [154.54.42.86]

// NL

22   373 ms   368 ms   368 ms  be12488.ccr42.ams03.atlas.cogentco.com [130.117.51.42]

// DE

23   398 ms   394 ms   399 ms  be2816.ccr42.ham01.atlas.cogentco.com [154.54.38.210]

// SE

24   429 ms   433 ms   429 ms  be2282.ccr22.sto03.atlas.cogentco.com [154.54.72.106]

25   406 ms   408 ms   408 ms  be2397.ccr21.sto01.atlas.cogentco.com [130.117.50.130]

26   412 ms   414 ms   414 ms  149.11.164.2

// FI

27   424 ms   422 ms   420 ms  rma1-tr2.dnaip.fi [62.78.104.84]

28   412 ms   411 ms   419 ms  hol1-tr2.dnaip.fi [62.78.107.97]

29   421 ms   421 ms   418 ms  lah1-er24.dnaip.fi [62.78.108.211]

30     *        *        *     Request timed out.

 

Trace complete.

Comments

  • LakshLaksh Posts: 4,442 Community Manager

    Hi Jongunranta,

     

    I had a word with the Product team about your post.

    We can’t affect at all how the ISP's worldwide route their traffic. This is up to their contracts with different network providers, and the contracts between those network providers. It seems to be fairly common that the network traffic from South-East Asia gets routed through the USA to Europe – it is probably cheaper for many network providers to do that than route the traffic to Europe through the shorter paths in Asia.

     

  • Ain't that funny other servers located in Finland and behind dnaip are routed properly straight (via Singpore-Europe). Maybe your product and tech teams need some training?

  • LakshLaksh Posts: 4,442 Community Manager

    Hi Jongunranta,

     

    Appreciate your feedback; but the situation remains the same. We cannot affect the ISP's routing.

This discussion has been closed.