Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Best european server location for connectivity to Asia.
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Best european server location for connectivity to Asia.

eloieloi Member
edited February 2012 in General

Hi
I wondering what is the best server location for connectivity to Asia. Like the best country and maybe even the Data centre beside going to every single one to do a download test.

«1

Comments

  • Try Germany

  • This has been mentioned before, but this may help you get a better idea of where to look, so here it is again: cablemap.info/ You will notice on this map that your best bets are going to actualy be West Coast USA, Australia, or India. It just depends what your bandwidth requirements are of course, in some areas you are going to pay an arm and a leg to get decent peering. If you are just trying to find a server for a vpn to your self your best bet is to figure out what peering your ISP has and then try to find a data center that shares similar peering with your isp and also has good peering to the places you want to access. Peeringdb.com is a good resource for finding out who peers with who.

    This may be more advanced than the answer you were looking for, but I like to provide people with the tools to answer their own questions. Hopefully this helps you learn a bit about how networks work, and find the answer to your question at the same time.

    Good Luck!

    Thanked by 2upfreak roykem
  • Hi
    Thanks TheLinuxBug this is exactly what I am looking for. For those direct places where Singapore have good connectivity to is pretty obvious for me since those information is easy to get but once you want a specific area like South America or Europe where there is no direct link it get complicated.

  • fanfan Veteran

    Not sure about other parts of Asia, but as far as I know, most EU datacenters don't have nice connectivity with Northeast Asia (China, Japan, S. Korea), bear in mind that the latency may be very high like 300ms+.

  • AndriAndri Member
    edited February 2012

    I have one box at XenVZ from their Maidenhead data center, average latency from Indonesia around 260ms. So far, it's the best I could find. Try this: 149.255.96.39

  • DamianDamian Member
    edited February 2012

    For what it's worth, transiting from a VPS in Turkey to a VPS in Australia goes through Europe->United States:

     1  46-45-178-194.turkrdns.com (46.45.178.194)  0.034 ms
     2  10.250.0.9 (10.250.0.9)  0.260 ms
     3  212.156.129.149.static.turktelekom.com.tr (212.156.129.149)  0.798 ms
     4  lvnt-3-2-lvnt-3-1.turktelekom.com.tr (81.212.219.222)  1.261 ms
     5  gyrttpe-2-3-lvnt-3-2.turktelekom.com.tr (81.212.199.205)  1.085 ms
     6  ln-col-2-gyrttpe-2-3.turktelekom.com.tr (212.156.103.25)  56.974 ms
     7  10gigabitethernet1-1.core1.lon1.he.net (195.66.224.21)  65.764 ms
     8  10gigabitethernet7-4.core1.nyc4.he.net (72.52.92.241)  139.929 ms
     9  10gigabitethernet10-2.core1.sjc2.he.net (184.105.213.197)  195.566 ms
    10  10gigabitethernet1-4.core1.sjc1.he.net (72.52.92.117)  197.452 ms
    11  vocus.gigabitethernet2-13.core1.sjc1.he.net (64.71.184.46)  193.100 ms
    12  ten-0-2-0.bdr01.sjc01.ca.VOCUS.net.au (114.31.199.116)  365.577 ms
    13  pos-0-0-1.cor01.syd03.nsw.VOCUS.net.au (114.31.199.45)  350.661 ms
    14  ge-0-0-3.bdr02.adl01.sa.VOCUS.net.au (114.31.192.213)  368.864 ms
    15  ge-0-2.bdr01.adl01.sa.VOCUS.net.au (114.31.198.32)  386.372 ms
    16  as9297.bdr01.adl01.sa.VOCUS.net.au (119.161.94.6)  371.073 ms
    17  f3-48.c45.dc2.colocity.com (119.252.0.66)  370.387 ms
    18  v901.c45.cor.dc1.colocity.com (119.252.31.97)  370.431 ms
    19  g1-1.c45.distd.adl.colocity.com (119.252.31.242)  370.901 ms
    20  iam.oli.id.au (119.252.16.200)  370.162 ms
    21  119-252-16-219.rc1dd.adl.colocity.com (119.252.16.219)  370.025 ms
    

    So, most likely, transit from Europe is going to go through the United States, instead of through mainland Europe/Asia.

  • SpiritSpirit Member
    edited February 2012

    @Damian said: So, most likely, transit from Europe is going to go through the United States, instead of through mainland Europe/Asia.

    Not necessary. That's actually some strange routing in your case. In most cases pick telia and it's direct through mainland Europe/Asia (telia -> singaporetelecom.telia -> optus.net.au)

  • @Spirit: Ah, that would make sense. This is the only Australian connection I have, so I was unable to test further. :)

  • @Spirit said: Not necessary. That's actually some strange routing in your case. In most cases pick telia and it's direct through mainland Europe/Asia (telia -> singaporetelecom.telia -> optus.net.au)

    Can you talk more about this?

  • SpiritSpirit Member
    edited February 2012

    I was wrong. Seriously, I was wrong with this australian IP from Damian. :-) I tryed my home connection and it went through telia then I tryed TUShosting (not so LEB) server and it went through telia again but when I later tryed few others (hetzner, netrouting, inception..) they all went through HE as @Damian stated so I am corrected now.

    7 32 ms 21 ms 20 ms win-b4-link.telia.net [213.248.75.109]
    8 27 ms 25 ms 29 ms prag-bb1-link.telia.net [80.91.246.200]
    9 43 ms 43 ms 43 ms ffm-bb1-link.telia.net [213.155.133.50]
    10 53 ms 192 ms 54 ms prs-bb1-link.telia.net [80.91.245.101]
    11 219 ms 217 ms 214 ms sjo-bb1-link.telia.net [213.155.130.213]
    12 205 ms 272 ms 209 ms sjo-bb1-link.telia.net [80.91.248.188]
    13 360 ms 359 ms 201 ms singaporetelecom-ic-150841-sjo-bb1.c.telia.net [195.12.255.234]
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 396 ms 400 ms 388 ms Amcom.55drc76fg.optus.net.au [61.88.163.14]
    17 438 ms 380 ms 382 ms ge2-1.cr01.sa.amcom.net.au [202.189.64.2]
    18 388 ms 376 ms 376 ms ge2-1.cr01.sa.amcom.net.au [202.189.64.2]
    19 399 ms 399 ms 406 ms 202.189.75.74
    20 417 ms 401 ms 404 ms 202.189.75.74
    21 400 ms 403 ms 403 ms g1-1.c45.distd.adl.colocity.com [119.252.31.242]
    22 401 ms 396 ms 395 ms iam.oli.id.au [119.252.16.200]
    23 395 ms 395 ms 396 ms 119-252-16-219.rc1dd.adl.colocity.com [119.252.16.219]

    And it's not even better than this what Damian posted. Mea culpa.

  • AmfyAmfy Member
    edited February 2012

    $ traceroute 223.25.238.3
    traceroute to 223.25.238.3 (223.25.238.3), 30 hops max, 60 byte packets
    1 mydedicatedatom (84.200.xxx.xx) 0.097 ms 0.034 ms 0.031 ms
    2 accelerated.de (84.200.xxx.xx) 0.409 ms 0.364 ms 0.393 ms
    3 80.156.160.161 (80.156.160.161) 0.370 ms 0.376 ms 0.404 ms
    4 sin-sb1-i.SIN.SG.NET.DTAG.DE (62.154.5.170) 185.271 ms 185.130 ms 185.043 ms
    5 tsystems-r.equinix.transit.vqbn.com (202.73.47.65) 188.621 ms 188.584 ms 188.724 ms
    6 fibernet-r1.vqbn.com (202.73.47.250) 195.440 ms 195.521 ms 195.534 ms
    7 202.73.47.227 (202.73.47.227) 195.854 ms 195.757 ms 195.823 ms
    8 202.73.52.32 (202.73.52.32) 189.002 ms 189.238 ms 189.201 ms
    9 gw1.sin1.singhost.com (202.73.56.226) 192.148 ms 192.604 ms 192.524 ms
    10 223-25-238-3.rev.expertvm.com (223.25.238.3) 192.819 ms 192.736 ms 192.645 ms

    From Frankfurt in Germany.

  • AnthonySmithAnthonySmith Member, Patron Provider

    Pretty horrible from NL:

    
    
     1:  hosted-by.inceptionhosting.com (x.x.x.x)        0.068ms pmtu 1500
     1:  hosted-by-snel.com (x.x.x.x)                     0.733ms
     2:  84.244.128.97 (84.244.128.97)                          0.552ms
     3:  cr01-sr-ams.we-dare.net (92.48.225.1)                  1.787ms
     4:  20gigabitethernet1-3.core1.ams1.he.net (195.69.145.150)  11.344ms
     5:  10gigabitethernet2-1.core1.par2.he.net (184.105.213.102)  12.018ms
     6:  10gigabitethernet7-1.core1.ash1.he.net (184.105.213.93)  90.680ms
     7:  10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) asymm  8 157.817ms
     8:  10gigabitethernet3-4.core1.sjc1.he.net (72.52.92.114) 156.054ms
     9:  vocus.gigabitethernet2-13.core1.sjc1.he.net (64.71.184.46) 153.764ms
    10:  pos-0-0-1.cor02.syd03.nsw.VOCUS.net.au (114.31.199.47) asymm 13 308.929ms
    11:  ten-1-3-0.cor01.syd03.nsw.VOCUS.net.au (114.31.192.86) 310.508ms
    12:  ge-0-0-3.bdr02.adl01.sa.VOCUS.net.au (114.31.192.213) 331.861ms
    13:  ge-0-2.bdr01.adl01.sa.VOCUS.net.au (114.31.198.32)   331.459ms
    14:  as9297.bdr01.adl01.sa.VOCUS.net.au (119.161.94.6)    asymm 17 334.397ms
    15:  f3-48.c45.dc2.colocity.com (119.252.0.66)            asymm 18 335.044ms
    16:  v901.c45.cor.dc1.colocity.com (119.252.31.97)        asymm 17 335.988ms
    17:  g1-1.c45.distd.adl.colocity.com (119.252.31.242)     asymm 18 339.936ms
    18:  iam.oli.id.au (119.252.16.200)                       asymm 19 336.162ms
    19:  119-252-16-219.rc1dd.adl.colocity.com (119.252.16.219) 334.902ms reached
    

    About the same from the UK

  • SpiritSpirit Member
    edited February 2012

    Second IP from @Amfy. Tracert from Inceptionhosting .nl

    traceroute to 223.25.238.3 (x.x.x.x), 30 hops max, 60 byte packets
    1 hosted-by.snelis.com (x.x.x.x) 0.545 ms 0.597 ms 0.644 ms
    2 ge-10-0-0.ar9.ams2.gblx.net (64.214.147.45) 1.686 ms 1.673 ms 1.648 ms
    3 po6-40G.ar4.LAX1.gblx.net (67.16.129.202) 162.212 ms 162.236 ms 162.307 ms
    4 67.17.192.6 (67.17.192.6) 144.624 ms 144.624 ms 144.598 ms
    5 ge-4-0-0-0.laxow-cr2.ix.singtel.com (203.208.183.150) 149.795 ms so-2-0-3-0.sngtp-cr1.ix.singtel.com (203.208.149.245) 185.935 ms ge-5-0-0-0.sngc3-ar3.ix.singtel.com (203.208.149.137) 191.052 ms
    6 so-2-0-2-0.sngc3-cr1.ix.singtel.com (203.208.151.117) 331.294 ms ge-0-3-0-0.laxow-ar1.ix.singtel.com (203.208.149.37) 158.385 ms 203.208.153.121 (203.208.153.121) 309.029 ms
    7 203.208.171.85 (203.208.171.85) 318.716 ms POS0-0-0.venus.ix.singtel.com (203.208.172.10) 345.281 ms 203.208.153.246 (203.208.153.246) 328.725 ms
    8 203.208.190.242 (203.208.190.242) 323.967 ms 203.208.153.254 (203.208.153.254) 318.741 ms xe-0-0-0-0.sngc3-cr2.ix.singtel.com (203.208.183.14) 340.065 ms
    9 203.208.152.230 (203.208.152.230) 328.351 ms fibernet-r1.vqbn.com (202.73.47.250) 329.074 ms 328.875 ms
    10 203.208.190.242 (203.208.190.242) 314.179 ms 318.903 ms 202.73.47.227 (202.73.47.227) 334.430 ms
    11 202.73.52.32 (202.73.52.32) 329.411 ms 331.844 ms 332.162 ms
    12 gw1.sin1.singhost.com (202.73.56.226) 323.969 ms 322.943 ms 326.370 ms
    13 202.73.52.32 (202.73.52.32) 334.611 ms 223-25-238-3.rev.expertvm.com (223.25.238.3) 326.963 ms 323.183 ms

  • I dont get why the routing from SingTel/ SingNet is required here...

  • @Boltersdriveer

    That's just how peering works. Like it or not, it's all business (i.e. $) decisions.

  • Oh wait, I thought that was into Netherlands... zzz. Just realised this was into Singapore. Anyway, anyone wanna help traceroute one IP for me? 116.89.117.21 / 116.89.117.1 . I think it should be the same routes if I'm not wrong but... making sure.

  • From Finland

    tux@S205:~$ traceroute 119.252.16.219
    traceroute to 119.252.16.219 (119.252.16.219), 30 hops max, 60 byte packets
     1  . (10.0.0.2)  3.006 ms  3.219 ms  3.752 ms
     2  dsl-trebrasgw1-fe40fa00-1.dhcp.inet.fi (84.250.64.1)  10.607 ms  11.305 ms  11.413 ms
     3  trecredger01-e-2-2.datanet.tele.fi (141.208.151.149)  13.265 ms  13.722 ms  14.109 ms
     4  trecore3-o-0-1-0-0.datanet.tele.fi (141.208.204.25)  14.527 ms  15.183 ms  16.167 ms
     5  hkicore2-o-7-1-2-0.datanet.tele.fi (141.208.25.125)  41.907 ms  42.105 ms  42.835 ms                                                                                                        
     6  hkiasbr2-s0-0-0.datanet.tele.fi (141.208.8.14)  22.708 ms hkiasbr1-o-4.datanet.tele.fi (141.208.25.86)  160.434 ms  16.356 ms                                                               
     7  hls-b2-link.telia.net (213.248.75.17)  11.394 ms hls-b1-link.telia.net (213.248.68.209)  12.000 ms hls-b2-link.telia.net (213.248.75.17)  13.035 ms                                         
     8  s-bb2-link.telia.net (213.155.134.104)  21.435 ms s-bb2-link.telia.net (213.155.134.110)  22.547 ms s-bb2-link.telia.net (80.91.246.86)  23.387 ms                                          
     9  kbn-bb2-link.telia.net (213.155.134.143)  103.732 ms kbn-bb2-link.telia.net (80.91.247.163)  140.071 ms kbn-bb2-link.telia.net (213.155.134.141)  105.182 ms                                
    10  nyk-bb2-link.telia.net (213.155.130.155)  176.708 ms  176.807 ms  177.522 ms                                                                                                                
    11  sjo-bb1-link.telia.net (213.155.130.131)  204.274 ms sjo-bb1-link.telia.net (80.91.254.177)  203.660 ms sjo-bb1-link.telia.net (80.91.245.96)  190.185 ms                                   
    12  singaporetelecom-ic-150841-sjo-bb1.c.telia.net (195.12.255.234)  191.369 ms  192.146 ms  193.764 ms
    13  203.208.174.78 (203.208.174.78)  355.628 ms  357.766 ms  357.217 ms
    14  * * *
    15  * * *
    16  Amcom.55drc76fg.optus.net.au (61.88.163.14)  379.865 ms  381.390 ms  381.546 ms
    17  ge2-1.cr01.sa.amcom.net.au (202.189.64.2)  385.447 ms  380.436 ms  382.455 ms
    18  ge1-1.gw01.sa.amcom.net.au (202.189.64.22)  376.394 ms  379.703 ms  378.876 ms
    19  202.189.75.74 (202.189.75.74)  376.385 ms  377.046 ms  377.689 ms
    20  c45.cor-e.adl.colocity.com (119.252.31.194)  383.673 ms  384.239 ms  377.775 ms
    21  g1-1.c45.distd.adl.colocity.com (119.252.31.242)  372.902 ms  372.385 ms  373.606 ms
    22  iam.oli.id.au (119.252.16.200)  375.971 ms  377.924 ms  379.031 ms
    23  119-252-16-219.rc1dd.adl.colocity.com (119.252.16.219)  376.104 ms  375.467 ms  375.472 ms
  • @Boltersdriveer
    1 - 4 local and isp

    
      5.|-- 62.subnet118-98-61.astinet.telkom.net.id 90.0%    10   92.5  92.5  92.5  92.5   0.0
      6.|-- 180.240.128.174                           0.0%    10   97.2 103.1  86.4 129.8  13.0
      7.|-- 203.117.36.45                            10.0%    10   94.9  92.1  80.3  97.2   5.5
      8.|-- 203.117.34.38                            10.0%    10   88.7  91.3  80.8 102.5   6.9
      9.|-- 203.117.34.54                             0.0%    10   99.0  92.4  82.2  99.0   4.9
     10.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
     11.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
     12.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
     13.|-- cm21.iota117.maxonline.com.sg            10.0%    10  109.8 111.6  93.8 134.3  12.2
    
    same result for both of ip x.x.x.1 and x.x.x.21
    
  • Thanks, @Mon5t3r!

  • ExpertVMExpertVM Member, Host Rep

    @spirit: can you perform the trace route again? Let me see if I can improve it

  • SpiritSpirit Member
    edited February 2012

    @ExpertVM sure.

    From snel DC (Netherland) - Inceptionhosting .nl vps

    traceroute to 223.25.238.3 (223.25.238.3), 30 hops max, 60 byte packets
    1 x.snelis.com (x.x.x.x) 0.605 ms 0.614 ms 0.697 ms
    2 ge-10-0-0.ar9.ams2.gblx.net (64.214.147.45) 1.657 ms 1.638 ms 1.637 ms
    3 po2-40G.ar4.LAX1.gblx.net (67.17.95.214) 141.811 ms po6-40G.ar4.LAX1.gblx.net (67.16.129.202) 141.893 ms 139.822 ms
    4 67.17.192.6 (67.17.192.6) 150.020 ms 150.104 ms 151.910 ms
    5 ge-0-0-0-0.laxow-dr1.ix.singtel.com (203.208.171.65) 151.784 ms 203.208.149.33 (203.208.149.33) 152.051 ms xe-0-0-0-0.laxow-dr3.ix.singtel.com (203.208.149.106) 149.975 ms
    6 203.208.171.85 (203.208.171.85) 318.995 ms so-2-0-3-0.sngc3-cr1.ix.singtel.com (203.208.149.237) 331.432 ms 203.208.178.185 (203.208.178.185) 335.912 ms
    7 203.208.153.242 (203.208.153.242) 336.569 ms 203.208.153.246 (203.208.153.246) 414.397 ms 203.208.154.45 (203.208.154.45) 334.310 ms
    8 203.208.153.254 (203.208.153.254) 326.340 ms 203.208.190.242 (203.208.190.242) 335.076 ms 335.134 ms
    9 203.208.152.230 (203.208.152.230) 334.812 ms 203.208.153.242 (203.208.153.242) 324.031 ms fibernet-r1.vqbn.com (202.73.47.250) 330.797 ms
    10 202.73.47.227 (202.73.47.227) 336.585 ms 203.208.190.242 (203.208.190.242) 327.302 ms 202.73.47.227 (202.73.47.227) 333.518 ms
    11 202.73.52.32 (202.73.52.32) 333.961 ms fibernet-r1.vqbn.com (202.73.47.250) 330.958 ms 202.73.52.32 (202.73.52.32) 343.402 ms
    12 202.73.47.227 (202.73.47.227) 332.218 ms 337.110 ms 336.096 ms
    13 202.73.52.32 (202.73.52.32) 329.578 ms 331.954 ms 223-25-238-3.rev.expertvm.com (223.25.238.3) 332.918 ms

    From EDIS DC (Austria)

    traceroute to 223.25.238.3 (223.25.238.3), 30 hops max, 40 byte packets
    1 x-x-x-x.static.edis.at (x.x.x.x) 0.338 ms 0.385 ms 0.450 ms
    2 217-085-143-095.as39912.net (95.143.85.217) 3.475 ms 3.512 ms 3.505 ms
    3 c76-1.ix1.vie.at.as39912.net (95.143.80.5) 3.898 ms 3.923 ms 3.998 ms
    4 212.73.202.9 (212.73.202.9) 19.903 ms 19.969 ms 19.988 ms
    5 ae-6-6.ebr1.Frankfurt1.Level3.net (4.69.135.34) 15.111 ms 15.130 ms 15.139 ms
    6 ae-45-45.ebr2.Paris1.Level3.net (4.69.143.134) 32.294 ms ae-46-46.ebr2.Paris1.Level3.net (4.69.143.138) 32.278 ms ae-45-45.ebr2.Paris1.Level3.net (4.69.143.134) 32.218 ms
    7 ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62) 104.454 ms ae-41-41.ebr2.Washington1.Level3.net (4.69.137.50) 104.293 ms ae-43-43.ebr2.Washington1.Level3.net (4.69.137.58) 104.598 ms
    8 ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 104.837 ms ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 103.226 ms ae-92-92.csw4.Washington1.Level3.net (4.69.134.158) 113.911 ms
    9 ae-74-74.ebr4.Washington1.Level3.net (4.69.134.181) 110.973 ms ae-94-94.ebr4.Washington1.Level3.net (4.69.134.189) 110.941 ms ae-64-64.ebr4.Washington1.Level3.net (4.69.134.177) 110.857 ms
    10 ae-4-4.ebr3.LosAngeles1.Level3.net (4.69.132.81) 170.651 ms 167.274 ms 168.181 ms
    11 ae-93-93.csw4.LosAngeles1.Level3.net (4.69.137.46) 168.154 ms ae-63-63.csw1.LosAngeles1.Level3.net (4.69.137.34) 171.147 ms ae-83-83.csw3.LosAngeles1.Level3.net (4.69.137.42) 170.200 ms
    12 ae-2-70.edge1.LosAngeles6.Level3.net (4.69.144.80) 167.342 ms ae-4-90.edge1.LosAngeles6.Level3.net (4.69.144.208) 168.338 ms 168.413 ms
    13 TELEKOMUNIK.edge1.LosAngeles6.Level3.net (4.26.0.154) 362.173 ms 363.407 ms 362.060 ms
    14 p18106.sgw.equinix.com (202.79.197.6) 362.543 ms 363.755 ms 362.494 ms
    15 fibernet-r1.vqbn.com (202.73.47.250) 269.358 ms 268.232 ms 268.091 ms
    16 202.73.47.227 (202.73.47.227) 269.568 ms 268.516 ms 269.657 ms
    17 202.73.52.32 (202.73.52.32) 268.871 ms 268.490 ms 268.071 ms
    18 gw1.sin1.singhost.com (202.73.56.226) 268.287 ms 269.751 ms 268.938 ms
    19 223-25-238-3.rev.expertvm.com (223.25.238.3) 268.754 ms 268.595 ms 268.585 ms

    From Hetzner DC (Germany)

    traceroute to 223.25.238.3 (223.25.238.3), 30 hops max, 60 byte packets
    1 x.x.com (x.x.x.x) 0.030 ms 0.010 ms 0.009 ms
    2 hos-tr1.juniper1.rz10.hetzner.de (213.239.224.1) 0.168 ms hos-tr2.juniper1.rz10.hetzner.de (213.239.224.33) 0.148 ms hos-tr1.juniper1.rz10.hetzner.de (213.239.224.1) 0.142 ms
    3 hos-bb1.juniper4.ffm.hetzner.de (213.239.240.230) 9.844 ms 9.828 ms 9.797 ms
    4 r1fra1.core.init7.net (82.197.166.85) 14.836 ms 14.905 ms r1fra1.core.init7.net (77.109.135.17) 10.426 ms
    5 r1lon1.core.init7.net (77.109.128.37) 22.174 ms 22.520 ms 22.626 ms
    6 r1nyc1.core.init7.net (77.109.140.194) 85.267 ms 85.284 ms 85.260 ms
    7 r1lax1.core.init7.net (82.197.168.69) 158.822 ms 158.795 ms 158.903 ms
    8 * * *
    9 ge-5-0-0-0.laxow-cr2.ix.singtel.com (203.208.183.157) 158.762 ms 158.807 ms 203.208.153.141 (203.208.153.141) 158.754 ms
    10 xe-1-0-0-0.laxow-cr1.ix.singtel.com (203.208.183.145) 158.971 ms 203.208.154.45 (203.208.154.45) 341.982 ms ge-1-0-9-0.plapx-dr2.ix.singtel.com (203.208.149.25) 158.606 ms
    11 203.208.178.185 (203.208.178.185) 342.236 ms 203.208.166.202 (203.208.166.202) 328.216 ms POS0-0-0.venus.ix.singtel.com (203.208.172.10) 338.546 ms
    12 203.208.190.242 (203.208.190.242) 363.890 ms xe-0-0-0-0.laxow-cr2.ix.singtel.com (203.208.183.153) 339.784 ms 203.208.190.242 (203.208.190.242) 349.128 ms
    13 203.208.166.202 (203.208.166.202) 391.051 ms POS0-0-0.venus.ix.singtel.com (203.208.172.10) 328.762 ms 203.208.166.202 (203.208.166.202) 391.082 ms
    14 202.73.47.227 (202.73.47.227) 338.372 ms 338.685 ms 339.219 ms
    15 202.73.52.32 (202.73.52.32) 333.914 ms fibernet-r1.vqbn.com (202.73.47.250) 333.914 ms 202.73.52.32 (202.73.52.32) 329.087 ms
    16 202.73.47.227 (202.73.47.227) 338.518 ms gw1.sin1.singhost.com (202.73.56.226) 342.929 ms 202.73.47.227 (202.73.47.227) 338.950 ms
    17 223-25-238-3.rev.expertvm.com (223.25.238.3) 338.058 ms 202.73.52.32 (202.73.52.32) 328.909 ms 333.738 ms

    From OVH DC (France)

    traceroute to 223.25.238.3 (223.25.238.3), 30 hops max, 60 byte packets
    1 (x.x.x.x) 0.035 ms 0.019 ms 0.018 ms
    2 rbx-g2-a9.fr.eu (178.33.100.70) 1.077 ms 1.473 ms 1.582 ms
    3 * ams-5-6k.nl.eu (94.23.122.190) 5.784 ms ams-5-6k.nl.eu (91.121.131.170) 5.895 ms
    4 gblx.as3549.nl.eu (94.23.122.85) 5.937 ms 5.765 ms 5.804 ms
    5 67.17.192.6 (67.17.192.6) 144.081 ms 143.938 ms 144.105 ms
    6 xe-0-0-0-0.laxow-dr3.ix.singtel.com (203.208.149.106) 141.085 ms so-2-0-3-0.sngtp-cr1.ix.singtel.com (203.208.149.245) 145.527 ms ge-0-0-0-0.laxow-dr1.ix.singtel.com (203.208.171.65) 144.063 ms
    7 xe-1-0-0-0.laxow-cr1.ix.singtel.com (203.208.183.145) 145.448 ms 203.208.178.185 (203.208.178.185) 327.739 ms ge-0-1-3-0.laxow-dr1.ix.singtel.com (203.208.149.38) 162.573 ms
    8 ge-2-3-0-0.laxow-ar2.ix.singtel.com (203.208.171.9) 325.498 ms 203.208.152.230 (203.208.152.230) 305.858 ms 203.208.153.246 (203.208.153.246) 322.688 ms
    9 203.208.190.242 (203.208.190.242) 254.416 ms 256.067 ms xe-0-0-0-0.laxow-cr2.ix.singtel.com (203.208.183.153) 320.718 ms
    10 fibernet-r1.vqbn.com (202.73.47.250) 259.058 ms POS6-0-0.sngtp-ar5.ix.singtel.com (203.208.172.42) 318.096 ms 203.208.166.202 (203.208.166.202) 327.926 ms
    11 203.208.190.242 (203.208.190.242) 258.974 ms 202.73.47.227 (202.73.47.227) 254.870 ms 203.208.190.242 (203.208.190.242) 258.973 ms
    12 202.73.52.32 (202.73.52.32) 249.520 ms 256.352 ms fibernet-r1.vqbn.com (202.73.47.250) 253.874 ms
    13 202.73.47.227 (202.73.47.227) 259.188 ms gw1.sin1.singhost.com (202.73.56.226) 259.160 ms 202.73.47.227 (202.73.47.227) 259.564 ms
    14 223-25-238-3.rev.expertvm.com (223.25.238.3) 259.135 ms 259.198 ms 259.312 ms

  • ExpertVMExpertVM Member, Host Rep

    @Spirit,

    I need the source IP for this

    From snel DC (Netherland) - Inceptionhosting .nl vps

    traceroute to 223.25.238.3 (223.25.238.3), 30 hops max, 60 byte packets
    1 x.snelis.com (x.x.x.x) 0.605 ms 0.614 ms 0.697 ms
    2 ge-10-0-0.ar9.ams2.gblx.net (64.214.147.45) 1.657 ms 1.638 ms 1.637 ms

    Thanks!

  • @ExpertVM I don't mind to help however I will not post my vps IP here, sorry. You can easily find IP from this network, or even same subnet in few seconds by typing something like "InceptionHosting test IP" in google.

  • 
    root@irc:~# 223.25.238.3
    -bash: 223.25.238.3: command not found
    root@irc:~# traceroute 223.25.238.3
    traceroute to 223.25.238.3 (223.25.238.3), 30 hops max, 60 byte packets
     1  hosted-by.snelis.com (89.207.130.1)  0.377 ms  0.468 ms  0.544 ms
     2  ge-10-0-0.ar9.ams2.gblx.net (64.214.147.45)  1.629 ms  1.623 ms  1.607 ms
     3  po2-40G.ar4.LAX1.gblx.net (67.17.95.214)  139.687 ms po6-40G.ar4.LAX1.gblx.net (67.16.129.202)  139.695 ms po2-40G.ar4.LAX1.gblx.net (67.17.95.214)  139.770 ms
     4  67.17.192.6 (67.17.192.6)  144.558 ms  144.566 ms  144.565 ms
     5  so-3-0-3-0.sngc3-cr1.ix.singtel.com (203.208.151.233)  144.545 ms ge-4-0-0-0.laxow-cr2.ix.singtel.com (203.208.183.150)  149.847 ms 203.208.171.229 (203.208.171.229)  149.822 ms
     6  xe-1-0-0-0.laxow-cr1.ix.singtel.com (203.208.183.145)  144.687 ms 203.208.171.234 (203.208.171.234)  150.042 ms xe-1-0-0-0.laxow-cr1.ix.singtel.com (203.208.183.145)  144.775 ms
     7  203.208.166.202 (203.208.166.202)  466.498 ms  466.401 ms 203.208.153.121 (203.208.153.121)  364.489 ms
     8  203.208.190.242 (203.208.190.242)  327.644 ms ge-7-0-0-0.laxow-dr1.ix.singtel.com (203.208.183.154)  318.712 ms 203.208.190.242 (203.208.190.242)  327.658 ms
     9  fibernet-r1.vqbn.com (202.73.47.250)  319.215 ms  319.261 ms 203.208.152.230 (203.208.152.230)  328.453 ms
    10  203.208.190.242 (203.208.190.242)  326.726 ms  327.810 ms  327.691 ms
    11  fibernet-r1.vqbn.com (202.73.47.250)  315.831 ms 202.73.52.32 (202.73.52.32)  326.842 ms  331.850 ms
    12  202.73.47.227 (202.73.47.227)  332.282 ms  332.336 ms gw1.sin1.singhost.com (202.73.56.226)  324.467 ms
    13  223-25-238-3.rev.expertvm.com (223.25.238.3)  319.692 ms 202.73.52.32 (202.73.52.32)  332.339 ms  332.173 ms
    

    The source IP is 89.207.130.148.

  • ExpertVMExpertVM Member, Host Rep

    @spirit and @ElliotJ

    Can you guys try again?

    Thanks

  • The exact same route, sorry.
    Looks like it's going the wrong way round the planet.

  • Sorry for bump,

    Which location & provider i should pick if most visitor ONLY from eu & asia? (No need good connection to USA)

    The Netherlands or Germany ?

  • Try Russian hosting,100Mbps and unmetered..guess represented in two continents :) Faster and less ping than from Western Europe.

  • NekkiNekki Veteran

    fitvpn said: Try Russian hosting,100Mbps and unmetered..guess represented in two continents :) Faster and less ping than from Western Europe.

    I always assumed that you did not try Russian hosting, but Russian Hosting tried you.

    Thanked by 2rokok Francisco
  • But im not sure about connection reliability of Russia

Sign In or Register to comment.