Howdy, Stranger!

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


Uruguay / South America new location (VPS/Dedicated/Colocation) Feedback Needed!
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.

Uruguay / South America new location (VPS/Dedicated/Colocation) Feedback Needed!

Hey there!, we're currently finishing the negotiations with the DC in the title's location (Uruguay / South America / http://en.wikipedia.org/wiki/Uruguay), and as always people/(future/current) clients & LET community feedback is important to us, mostly because it gives us the opportunity to bring better and more interesting services to people.

So in this occasion it could be interesting to ask you for your opinion....

(if you're curious, test IP is 200.108.192.1)

Thank you !!

Would you Choose Uruguay as a location for your services ? Why ? (or why not?)
  1. Would you Choose Uruguay as a location for your services ? Why ? (or why not?)43 votes
    1. I'll choose Uruguay because my clients are very near (ex: Argentina, Chile, etc)
      11.63%
    2. I'll choose Uruguay because I have multiple points in the world and I need one more
      60.47%
    3. Wow I didn't know Uruguay as a country existed, but you got me interested!
        9.30%
    4. I wouldn't choose Uruguay at all.
      16.28%
    5. Other (please comment) :)
        2.33%
«1

Comments

  • aglodekaglodek Member
    edited November 2013

    @Increhost said: Would you Choose Uruguay as a location...

    YES, contingent on connectivity to neighboring countries (i.e. Argentina, BRAZIL (!!), Chile, Paraguay, etc.). Experience shows that Latin American providers - most recently a LEB provider in Panama - interconnect via Miami, rather than directly.

    Second consideration will be pricing - in Latin America usually bordering on the ridiculous (from a US perspective, of course).

    These concerns aside - FABULOUS project! :)

  • 200.108.192.1

    Peers are Level 3 and Telekom Argentina so I'm assuming good connectivity to Argentina and maybe Paraguay but connections to Brazil, Venezuela, etc will probably be routed through Miami?

  • Sure! You already know that I'm interested ;)

    Connectivity is great!

  • @Amfy said:
    Sure! You already know that I'm interested ;)

    Connectivity is great!

    Sure, there's already one with your name on it :) !!

    Thanked by 1Amfy
  • @DomainBop said:
    Peers are Level 3 and Telekom Argentina so I'm assuming good connectivity to
    Argentina and maybe Paraguay but connections to Brazil, Venezuela, etc will probably > be routed through Miami?

    Hi @DomainBop, indeed, that's mainly why we have the Miami location too, so we can cover the whole Latin America Area.

    To Argentina we have really good latency at that point, another goody is the freedom
    on the use of cryptography, personal information, and such.

    Thank you for voting !

  • Looking forward to testing a vps there. We'd love to have a point of presence in Uruguay.

  • @aglodek said:
    These concerns aside - FABULOUS project! :)

    Thks!

    IP pricing is expensive, but mostly until you get enough customers that justify LACNIC assignment really, after that is expensive but not so much.

    Nicce think is that traffic is unmetered, downside is bandwidth, but for a not so bandwidth intensive project it would be great.

    Cheers!

  • @NodePing said:
    Looking forward to testing a vps there. We'd love to have a point of presence in
    Uruguay.

    What specs would be interesting for you ?

    Thanks!

  • @DomainBop said:
    Peers are Level 3 and Telekom Argentina so I'm assuming good connectivity to Argentina and maybe Paraguay but connections to Brazil, Venezuela, etc will probably be routed through Miami?

    Sad but true :/

                                                    Packets               Pings
     Host                                         Loss%   Snt   Last   Avg  Best  Wrst StDev
    
    embratel-T0-4-0-3-uacc01.cas.embratel.net  4.2%    24   48.1  45.2  40.8  54.5   3.5
    ebt-T0-8-0-3-tcore01.cas.embratel.net.br   0.0%    24   46.5  48.3  42.6  72.4   7.0
    ebt-BP11931-intl03.mianap.embratel.net.br  4.2%    24  148.5 160.8 141.5 208.0  23.2
    ae54.edge4.Miami1.Level3.net               0.0%    24  357.6 314.1 295.0 380.4  19.2
    ae-2-52.edge2.Miami2.Level3.net            0.0%    24  304.3 303.7 293.3 321.4   6.8
    globalcrossing-level3-te.miami2.level3.ne  0.0%    24  208.3 168.7 157.3 208.3  14.5
    1-servidores.dedicado.com.uy               0.0%    24  298.8 299.2 293.8 311.9   4.7
    
  • IncrehostIncrehost Member
    edited November 2013

    @Darwin said:
    Sad but true :/

    Yes, and the same from other uruguayan ISPs, that's because mainly there's no
    Coutry-peering or nearby routes to some countries, it really depends from the
    bandwidth is taken.

    That's probably why the focus on our miami location to serve LATAM :)

      2.|-- cor1bras1.antel.net.uy     0.0%    10   13.0  14.3   8.3  20.0   3.5
      3.|-- ibb2cor1-7-2-92.antel.net  0.0%    10   12.7  15.2  10.8  19.0   2.9
      4.|-- ibb2agu1-1-3.antel.net.uy  0.0%    10  164.6 161.1 154.3 164.6   3.7
      5.|-- ibr2nap3-0-2-1-0.antel.ne  0.0%    10  166.4 164.8 156.6 169.3   3.8
      6.|-- 176.52.252.93              0.0%    10  162.4 161.2 155.5 164.9   3.2
      7.|-- Xe4-0-0-0-grtwaseq1.red.t  0.0%    10  212.7 203.8 183.2 262.1  23.5
      8.|-- 213.140.52.34              0.0%    10  197.6 193.4 187.2 198.8   3.2
      9.|-- be2113.mpd21.dca01.atlas.  0.0%    10  197.3 193.7 188.7 198.5   3.0
     10.|-- be2170.mpd21.atl01.atlas.  0.0%    10  194.3 192.3 185.2 198.1   4.2
     11.|-- be2175.mpd22.iah01.atlas.  0.0%    10  210.8 207.2 203.0 214.3   3.8
     12.|-- te2-6.ccr01.aus02.atlas.c 10.0%    10  259.1 258.1 205.1 410.2  81.2
     13.|-- te2-3.ccr01.aus04.atlas.c 10.0%    10  207.0 207.9 205.4 214.3   2.8
     14.|-- 38.122.254.14             10.0%    10  225.8 229.2 222.0 237.6   4.2
     15.|-- 208.91.197.132            10.0%    10  209.5 213.8 209.5 218.5   3.3
    
  • emreemre Member, LIR

    this is the best ever traceroute for me to South America

    just 9 hops! because of level 3 :)

    6. bursa-t2-1-cekirge-t3-1.turktelekom.com.tr.204.212.81.in-addr.arpa 0.0% 13 11.0 9.1 7.2 17.4 2.6 7. lon-col-3-bursa-t2-1.turktelekom.com.tr.103.156.212.in-addr.arpa 0.0% 13 63.9 66.2 63.9 67.9 1.1 8. 204.245.38.153 0.0% 13 65.6 66.4 65.3 68.5 0.6 9. 1-servidores.dedicado.com.uy 0.0% 13 290.7 295.9 290.7 300.0 2.4

  • emreemre Member, LIR
    edited November 2013

    Bursa/Turkey to London directly to level 3 to destination. Cool. Never seen a traceroute even to North America like this one, till today..

  • Too bad latency is too high for me.

  • @emre said:
    this is the best ever traceroute for me to South America

    This is from our Frankfurt (DE) node to the UY test IP:

    HOST: ovidius.increhost.com       Loss%   Snt   Last   Avg  Best  Wrst StDev
      1. 82.211.1.1                             0.0%    10    0.2   4.3   0.2  28.6   9.4
      2. xe-4-2-1-311.edge4.Frankfurt  0.0%    10    0.5   1.2   0.5   6.7   1.9
      3. glbx-level3-10G.Frankfurt1.L    0.0%    10   85.3   9.2   0.7  85.3  26.7
      4. 1-servidores.dedicado.com.uy  0.0%    10  238.4 249.5 238.4 262.4   9.3
    
  • @budi1413 said:
    Too bad latency is too high for me.

    Where are you in ?

  • budi1413budi1413 Member
    edited November 2013

    @Increhost Malaysia.

  • @budi1413 said:
    Increhost Malaysia.

    @budi1413 Great, for the Asian area we have our LA node, you can check latency in here: http://la.lg.increhost.com

    When there's too much distance, it's really going to be a lot of latency involved,
    but in case someone for some reason needs a special exotic or different location,
    this could be it (maybe) :)

    Thank you!

  • Increhost said: What specs would be interesting for you ?

    4 cpu cores
    1GB RAM
    5GB Disk space
    400GB monthly transfer

  • Ping from Indonesia :

    # ping 200.108.192.1
    
    Pinging 200.108.192.1 with 32 bytes of data:
    
    Reply from 200.108.192.1: bytes=32 time=409ms TTL=236
    Reply from 200.108.192.1: bytes=32 time=409ms TTL=236
    Reply from 200.108.192.1: bytes=32 time=414ms TTL=236
    Reply from 200.108.192.1: bytes=32 time=410ms TTL=236
    
    Ping statistics for 200.108.192.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 409ms, Maximum = 414ms, Average = 410ms
    

    Traceroute from Indonesia

    # tracert 200.108.192.1
    
    Tracing route to 1-servidores.dedicado.com.uy [200.108.192.1]
    over a maximum of 30 hops:
    
      1    1 ms    1 ms    1 ms  192.168.1.1
      2    18 ms    17 ms    17 ms  180.245.xxx.xxx
      3    22 ms    21 ms    20 ms  180.252.2.49
      4    22 ms    21 ms    22 ms  61.94.171.69
      5    42 ms    39 ms    39 ms  41.subnet118-98-59.astinet.telkom.net.id [118.98
    .59.41]
      6    37 ms    36 ms    36 ms  42.subnet118-98-59.astinet.telkom.net.id [118.98
    .59.42]
      7    36 ms    37 ms    38 ms  180.240.190.13
      8   210 ms   310 ms   247 ms  xe-10-0-0.edge1.LosAngeles6.Level3.net [4.26.0.1
    53]
      9   328 ms   217 ms     *     ae-4-90.edge1.LosAngeles9.Level3.net [4.69.144.2
    02]
     10     *      214 ms   214 ms  4.68.111.22
     11   390 ms   391 ms   390 ms  po4.asr1.EZE1.gblx.net [67.16.146.150]
     12   414 ms   415 ms   413 ms  1-servidores.dedicado.com.uy [200.108.192.1]
    
    Trace complete.
    
  • skunkskunk Member
    edited November 2013

    from @chile, Sur America ISP Telefonica Movistar


    1 1 ms 1 ms 1 ms AC9E0101.ipt.aol.com [172.158.1.1]
    2 197 ms 25 ms 24 ms 10.52.193.3
    3 24 ms 24 ms 24 ms 10.50.1.117
    4 25 ms 29 ms 31 ms 10.50.1.118
    5 32 ms 31 ms 32 ms hundred0-7-0-0.ppal.mundo.movistar.cl [200.91.11.77]
    6 89 ms 36 ms 100 ms 176.52.253.9
    7 122 ms 121 ms 119 ms Xe11-0-4-0-grtmiabr3.red.telefonica-wholesale.net [94.142.121.182]
    8 186 ms 150 ms 150 ms Xe0-1-3-0-grtdaleq2.red.telefonica-wholesale.net [213.140.36.37]
    9 151 ms 165 ms 150 ms xe4-0-1-10G.ar7.DAL2.gblx.net [64.208.27.165]
    10 477 ms 416 ms 327 ms po4.asr1.EZE1.gblx.net [67.16.146.150]
    11 336 ms 341 ms 353 ms 1-servidores.dedicado.com.uy [200.108.192.1]


    Haciendo ping a 200.108.192.1 con 32 bytes de datos:
    Respuesta desde 200.108.192.1: bytes=32 tiempo=338ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=356ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=367ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=377ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=367ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=372ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=374ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=373ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=343ms TTL=244
    Respuesta desde 200.108.192.1: bytes=32 tiempo=370ms TTL=244
    Estadísticas de ping para 200.108.192.1:
    Paquetes: enviados = 10, recibidos = 10, perdidos = 0
    (0% perdidos),
    Tiempos aproximados de ida y vuelta en milisegundos:
    Mínimo = 338ms, Máximo = 377ms, Media = 363ms

    :wq

  • budi1413budi1413 Member
    edited November 2013

    Increhost said: When there's too much distance, it's really going to be a lot of latency involved, but in case someone for some reason needs a special exotic or different location, this could be it (maybe) :)

    Well sometime want to try new location. :D

    ErawanArifNugroho said: Reply from 200.108.192.1: bytes=32 time=409ms TTL=236 Reply from 200.108.192.1: bytes=32 time=409ms TTL=236 Reply from 200.108.192.1: bytes=32 time=414ms TTL=236 Reply from 200.108.192.1: bytes=32 time=410ms TTL=236

    About same as me.

  • @skunk said:
    from chile, Sur America ISP Telefonica Movistar

    Hi @skunk, thks for the trace, indeed some ISP's just don't have direct connection
    with Argentina and so, with us neither.

    Miami is the big router, but despite that I heard (never tested) that there are some
    providers who has some fiber crossing the "Cordillera de los Andes".

    Is that true? are you aware of which provider is it?

    Cheers !

  • WilliamWilliam Member
    edited November 2013

    Yea, entel and GBLX- Entel sells mainly transport though.

  • gbshousegbshouse Member, Host Rep

    From our PoP in Brazil

    traceroute to 200.108.192.1 (200.108.192.1), 30 hops max, 60 byte packets
     1  186.192.128.37 (186.192.128.37)  47.500 ms  47.481 ms  47.459 ms
     2  200.170.81.241 (200.170.81.241)  0.594 ms  0.587 ms  0.637 ms
     3  ge3-1-0-2502.sanpaolo1.spa.seabone.net (195.22.219.116)  1.038 ms  1.026 ms  1.010 ms
     4  telecom-argentina.baires1.bai.seabone.net (195.22.220.54)  38.086 ms  38.076 ms  38.061 ms
     5  host165.190-225-252.telecom.net.ar (190.225.252.165)  31.557 ms  31.551 ms  31.535 ms
     6  host18.200-117-124.telecom.net.ar (200.117.124.18)  32.610 ms  32.149 ms  32.133 ms
     7  * * *
     8  * * *
    
  • risharderisharde Patron Provider, Veteran

    Even though my pings from the caribbean show ~220ms which is really high, I'd root for this location since I want an additional location on the worldmap.

  • @risharde said:
    Even though my pings from the caribbean show ~220ms which is really high, I'd root for this location > since I want an additional location on the worldmap.

    great, just PM your contact info so we will keep you up to date when the server is up and ready :)

    btw, which location are you in ?

    Thank you!

  • SwordfishBESwordfishBE Member
    edited November 2013
    traceroute to 200.108.192.1 (200.108.192.1), 30 hops max, 60 byte packets
     1  locutus-sagem-gw (192.168.1.1)  2.836 ms  3.103 ms  3.139 ms
     2  ip-213-49-90-1.dsl.scarlet.be (213.49.90.1)  22.578 ms  23.652 ms  25.332 ms
     3  ae-67-200.iarstr2.isp.belgacom.be (91.183.242.28)  30.491 ms  30.865 ms  119.332 ms
     4  ae-13-1000.ibrstr3.isp.belgacom.be (91.183.246.74)  31.159 ms  33.388 ms  33.100 ms
     5  146.82.32.117 (146.82.32.117)  34.128 ms  34.611 ms  34.601 ms
     6  GLOBAL-CROSSING-ARGENTINA-S-A.Port-channel1.409.asr1.EZE1.gblx.net (207.138.122.86)  259.246 ms  256.446 ms  256.599 ms
    

    From Belgium

  • @SwordfishBE said:
    From Belgium

    thks for the trace! btw, have you looked your latency to our servers in Germany?

    http://frankfurt.lg.increhost.com

    cheers!

  • ndelaespadandelaespada Member, Host Rep

    from Panama City, Panama:

    traceroute to 200.108.192.1 (200.108.192.1), 30 hops max, 60 byte packets 1 * * * 2 10.48.40.29 (10.48.40.29) 16.215 ms 16.209 ms 16.203 ms 3 201.218.92.205 (201.218.92.205) 15.018 ms 14.032 ms 15.006 ms 4 64.215.185.73 (64.215.185.73) 16.141 ms 16.143 ms 16.130 ms 5 GLOBAL-CROSSING-ARGENTINA-S-A.Port-channel1.409.asr1.EZE1.gblx.net (207.138.122.86) 107.046 ms 108.014 ms 108.010 ms

Sign In or Register to comment.