Howdy, Stranger!

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


VPS in North America with great latency to Europe & Brazil.
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.

VPS in North America with great latency to Europe & Brazil.

Hi, i have a problem.
I want to find best place where latency between Europe & Brazil minimum as it possible.
I already know about Dallas & Miami datacenters, but maby who else know another place like in Canada or somewhere in USA where ping to Europe (london) < 80-90ms; And to Brazil < 140,150; And to Chile < 170
Thank you!
I already test a lot different VPS'es)

Comments

  • jimpopjimpop Member
    edited October 2013

    RamNode ATL can get ~130ms to Sao Paulo, and ~110ms to London and Netherlands

    Edit: also ~120ms to Chile (cl.edis.at)

    Thanked by 1Nick_A
  • Increhost in Miami gets ~110ms to Sao Paulo, ~105ms to Chile, and ~100ms to London.

  • DomainBopDomainBop Member
    edited October 2013

    somewhere in USA where ping to Europe (london) < 80-90ms; And to Brazil < 140,150; And to Chile < 170 Thank you!

    NYC. Shorter pings to Europe than from Miami but longer pings to South America, pings below are from Iniz/NYC

    PING uk.edis.at (46.17.63.250) 56(84) bytes of data.
    64 bytes from 46.17.63.250: icmp_req=1 ttl=52 time=75.3 ms
    64 bytes from 46.17.63.250: icmp_req=2 ttl=52 time=75.4 ms
    64 bytes from 46.17.63.250: icmp_req=3 ttl=52 time=75.3 ms
    64 bytes from 46.17.63.250: icmp_req=4 ttl=52 time=75.4 ms
    64 bytes from 46.17.63.250: icmp_req=5 ttl=52 time=75.3 ms
    PING cl.edis.at (37.235.52.10) 56(84) bytes of data.
    64 bytes from 10-52-235-37.static.edis.at (37.235.52.10): icmp_req=1 ttl=48 time=140 ms
    64 bytes from 10-52-235-37.static.edis.at (37.235.52.10): icmp_req=2 ttl=48 time=140 ms
    64 bytes from 10-52-235-37.static.edis.at (37.235.52.10): icmp_req=3 ttl=48 time=138 ms
    64 bytes from 10-52-235-37.static.edis.at (37.235.52.10): icmp_req=4 ttl=48 time=139 ms
    64 bytes from 10-52-235-37.static.edis.at (37.235.52.10): icmp_req=5 ttl=48 time=139 ms
    ING hostdime.com.br (187.45.185.3) 56(84) bytes of data.
    64 bytes from 187.45.185.3.static.dimenoc.com (187.45.185.3): icmp_req=1 ttl=47 time=169 ms
    64 bytes from 187.45.185.3.static.dimenoc.com (187.45.185.3): icmp_req=2 ttl=47 time=172 ms
    64 bytes from 187.45.185.3.static.dimenoc.com (187.45.185.3): icmp_req=3 ttl=47 time=173 ms
    64 bytes from 187.45.185.3.static.dimenoc.com (187.45.185.3): icmp_req=4 ttl=47 time=170 ms
    64 bytes from 187.45.185.3.static.dimenoc.com (187.45.185.3): icmp_req=5 ttl=47 time=170 ms
  • huh, i find a website where i can check latency to different test ip frm different ISP.
    http://www.traceroute.org/

  • @neqste said:
    huh, i find a website where i can check latency to different test ip frm different ISP.
    http://www.traceroute.org/

    Also checkout http://www.bgp4.as/looking-glasses/

  • MaouniqueMaounique Host Rep, Veteran

    You wont be getting pings below 90 to EU in other places than on east coast.
    A balanced approach would be to go with something in atlanta, should be 100+ ms to London and a better ping to brazil, however, I think what DomainBop said is a good situation. If you target more EU, go with east coast if you target more brazil, got to Orlando.

  • Nick_ANick_A Member, Top Host, Host Rep

    Yeah Atlanta or Florida are good options to Brazil and EU if you need both.

  • @neqste are you a fan of Kurumin Linux? :D

  • Your best bet is probably something in the Choopa datacenter (New Jersey). You can get 70-100 to Europe, 110-150 to Brazil, and 150-170 to Chile.

  • rogriveracrogriverac Member
    edited October 2013

    Your best ping to Brazil and Central/South America will always come from Miami, FL

    From MIAMI, FL:

    TO UK

    [root@velocihost ~]$ ping 46.17.63.250
    PING 46.17.63.250 (46.17.63.250) 56(84) bytes of data.
    64 bytes from 46.17.63.250: icmp_seq=1 ttl=47 time=114 ms
    64 bytes from 46.17.63.250: icmp_seq=2 ttl=48 time=110 ms
    64 bytes from 46.17.63.250: icmp_seq=3 ttl=48 time=110 ms
    64 bytes from 46.17.63.250: icmp_seq=4 ttl=48 time=110 ms
    64 bytes from 46.17.63.250: icmp_seq=5 ttl=48 time=110 ms
    ^C
    --- 46.17.63.250 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4482ms
    rtt min/avg/max/mdev = 110.359/111.379/114.820/1.774 ms
    

    TO CHILE

    [root@velocihost ~]$ ping 37.235.52.10
    PING 37.235.52.10 (37.235.52.10) 56(84) bytes of data.
    64 bytes from 37.235.52.10: icmp_seq=1 ttl=53 time=108 ms
    64 bytes from 37.235.52.10: icmp_seq=2 ttl=53 time=107 ms
    64 bytes from 37.235.52.10: icmp_seq=3 ttl=53 time=114 ms
    64 bytes from 37.235.52.10: icmp_seq=4 ttl=53 time=109 ms
    64 bytes from 37.235.52.10: icmp_seq=5 ttl=53 time=109 ms
    ^C
    --- 37.235.52.10 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4478ms
    rtt min/avg/max/mdev = 107.794/109.958/114.990/2.645 ms
    

    TO BRAZIL

    [root@velocihost ~]$ ping 187.45.185.3
    PING 187.45.185.3 (187.45.185.3) 56(84) bytes of data.
    64 bytes from 187.45.185.3: icmp_seq=1 ttl=53 time=118 ms
    64 bytes from 187.45.185.3: icmp_seq=2 ttl=53 time=119 ms
    64 bytes from 187.45.185.3: icmp_seq=3 ttl=53 time=118 ms
    64 bytes from 187.45.185.3: icmp_seq=4 ttl=53 time=118 ms
    64 bytes from 187.45.185.3: icmp_seq=5 ttl=53 time=118 ms
    ^C
    --- 187.45.185.3 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4438ms
    rtt min/avg/max/mdev = 118.938/118.975/119.081/0.313 ms
    
  • I got VPS nodes in Atlanta get about 90MS to london your more then welcome to give a VPS a 48 hour trial if your interested we start from 2.99 a month at http://bigrobsweb.co.uk

  • I'm a bit shocked ping to Brazil is as poor as it is from Charlotte, but surprised it did as well to UK

    [root@e5clt01 ~]# ping -c5 46.17.63.250
    PING 46.17.63.250 (46.17.63.250) 56(84) bytes of data.
    64 bytes from 46.17.63.250: icmp_seq=1 ttl=48 time=84.2 ms
    64 bytes from 46.17.63.250: icmp_seq=2 ttl=48 time=83.7 ms
    64 bytes from 46.17.63.250: icmp_seq=3 ttl=48 time=84.0 ms
    64 bytes from 46.17.63.250: icmp_seq=4 ttl=48 time=84.1 ms
    64 bytes from 46.17.63.250: icmp_seq=5 ttl=48 time=83.7 ms
    
    --- 46.17.63.250 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4088ms
    rtt min/avg/max/mdev = 83.773/83.988/84.228/0.409 ms
    [root@e5clt01 ~]# ping -c5 187.45.185.3
    PING 187.45.185.3 (187.45.185.3) 56(84) bytes of data.
    64 bytes from 187.45.185.3: icmp_seq=1 ttl=48 time=178 ms
    64 bytes from 187.45.185.3: icmp_seq=2 ttl=48 time=189 ms
    64 bytes from 187.45.185.3: icmp_seq=3 ttl=48 time=188 ms
    64 bytes from 187.45.185.3: icmp_seq=4 ttl=48 time=179 ms
    64 bytes from 187.45.185.3: icmp_seq=5 ttl=48 time=184 ms
    
    --- 187.45.185.3 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4188ms
    rtt min/avg/max/mdev = 178.473/184.023/189.058/4.243 ms
    [root@e5clt01 ~]# 
    

    http://lowendtalk.com/discussion/14360/us-10yr-128mb-or-7mo-2gb-highspeedweb

  • DomainBopDomainBop Member
    edited October 2013

    @miTgiB said:
    I'm a bit shocked ping to Brazil is as poor as it is from Charlotte

    Is the traceroute from Charlotte exiting the US through Miami or is it going up to NYC?

    The main US to Brazil submarine cables are in (or near) Miami and NYC.
    http://submarinecablemap.com/#/submarine-cable/seabras-1
    http://submarinecablemap.com/#/submarine-cable/globenet

  • I see it going to Atlanta then not sure

    [root@e5clt20 ~]# traceroute 187.45.185.3
    traceroute to 187.45.185.3 (187.45.185.3), 30 hops max, 60 byte packets
     1  174.34.253.33 (174.34.253.33)  0.211 ms  0.177 ms  0.198 ms
     2  hostigation-gw.caro.net (174.34.252.177)  0.661 ms  0.694 ms  0.733 ms
     3  edge1-xb1-vl4.caro.net (69.59.18.11)  0.893 ms  0.964 ms  0.955 ms
     4  te7-3.ccr01.clt01.atlas.cogentco.com (38.104.168.89)  1.124 ms  1.148 ms  1.217 ms
     5  te0-7-0-16.mpd22.atl01.atlas.cogentco.com (154.54.85.1)  6.381 ms  6.371 ms te0-7-0-16.mpd21.atl01.atlas.cogentco.com (154.54.84.237)  6.321 ms
     6  be2037.ccr21.atl04.atlas.cogentco.com (154.54.3.170)  6.704 ms be2035.ccr21.atl04.atlas.cogentco.com (154.54.6.122)  6.484 ms  6.414 ms
     7  gblx.atl04.atlas.cogentco.com (154.54.11.154)  5.729 ms  5.676 ms  5.662 ms
     8  ae0-0-40G.ar5.GRU1.gblx.net (67.16.156.78)  132.029 ms ae1-0-40G.ar5.GRU1.gblx.net (67.16.156.82)  148.152 ms  133.912 ms
     9  187.52.125.189.static.impsat.net.br (189.125.52.187)  132.332 ms  153.033 ms  132.312 ms
    10  * * *
    11  * * *
    12  67.171.126.177.static.sp2.alog.com.br (177.126.171.67)  132.039 ms  181.202 ms  132.043 ms
    13  187.45.185.2.static.dimenoc.com (187.45.185.2)  132.004 ms  132.487 ms  131.974 ms
    14  187.45.185.3.static.dimenoc.com (187.45.185.3)  132.074 ms  132.129 ms  132.052 ms
    [root@e5clt20 ~]#
    
  • gbshousegbshouse Member, Host Rep
    edited October 2013

    Just for comparison (our DNS PoP in Miami)

    To UK

    PING 46.17.63.250 (46.17.63.250) 56(84) bytes of data.
    64 bytes from 46.17.63.250: icmp_req=1 ttl=45 time=114 ms
    64 bytes from 46.17.63.250: icmp_req=4 ttl=45 time=114 ms
    64 bytes from 46.17.63.250: icmp_req=5 ttl=45 time=109 ms

    To Chile

    PING 37.235.52.10 (37.235.52.10) 56(84) bytes of data.
    64 bytes from 37.235.52.10: icmp_req=1 ttl=50 time=108 ms
    64 bytes from 37.235.52.10: icmp_req=2 ttl=50 time=109 ms
    64 bytes from 37.235.52.10: icmp_req=3 ttl=50 time=108 ms

    To Brazil

    PING 187.45.185.3 (187.45.185.3) 56(84) bytes of data.
    64 bytes from 187.45.185.3: icmp_req=1 ttl=55 time=118 ms
    64 bytes from 187.45.185.3: icmp_req=2 ttl=55 time=118 ms
    64 bytes from 187.45.185.3: icmp_req=3 ttl=55 time=118 ms
  • servarica_haniservarica_hani Member, Patron Provider

    we have it

    in Montreal, Canada

    ~ 140ms to chile

    ~ 190ms to Brazil

    ~ 80ms to UK

  • MaouniqueMaounique Host Rep, Veteran

    @gbshouse said:
    Just for comparison (our DNS PoP in Miami)

    Yeah, it seems to be just in the middle however, for better EU speed and lower Brazil, you need to move further to the east coast. For balanced speeds, orlando/miami should do great.

  • @Hani said:
    we have it

    in Montreal, Canada

    ~ 140ms to chile

    ~ 190ms to Brazil

    ~ 80ms to UK

    Montreal looking very good (i dunno why) for South America & Asia. Strange.

  • MaouniqueMaounique Host Rep, Veteran
    edited October 2013

    Well, not really, it is somewhat inbetween. With sane routing, actuall geographical location should resemble network latency.

  • @jimpop said:
    Increhost in Miami gets ~110ms to Sao Paulo, ~105ms to Chile, and ~100ms to London.

    Thank you for the info!

    Just to add, in http://miami.lg.increhost.com you can check your times to
    Brazil, depending on the carrier they use, we saw ~140ms to Porto Alegre (which is
    really at the south or Brazil).

    Good luck !

  • Not US, but i know we have NTT in London and France, should give good routes to Asia. South-America 50:50.

    (try http://uk.edis.at )

Sign In or Register to comment.