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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Two out of three: http://lowendbox.com/blog/host1plus-com-2month-256mb-openvz-in-south-africa-brazil-germany-or-the-usa/
EDIT: EDIS has russia also: http://www.edis.at/en/server/linux-vserver/russia/
Thanks, got what I needed Knew this would be the right place to ask.
This company offers some cheap VPS in Brazil, but they only allow boleto( some kind of bank transfer here in Brazil)
http://www.emmex.com.br/servidor-dedicado-vps-start
Just for you to know - edis have VERY weak connection in Moscow. Their choosed data center have 40+ ms inside Moscow to most of providers.
Well this is easy to test, http://ru.edis.at/
Which providers do you mean? I tried tracing to Corbina/Akado/Onlime/Starlink/Meganet, all within 3ms.
Traffic was routed through RETN (Frankfurt) at start of a year. Seems like it's changed now.
http://lowendbox.com/blog/host1plus-com-2month-256mb-openvz-in-south-africa-brazil-germany-or-the-usa/ this one have good promo too use coupon code WORLDCUP -20%.
Getting 50ms to London.
Hi guys! all connections within Moscow are definitely < 5ms
40+ ms sounds like a connection to Frankfurt, ...
The datacenter we use has ReTN uplinks and works smoothly to western Europe.
So do we in our own plant in Vienna (ReTN uplinks), to assure best connections to Eastern Europe
PING YANDEX.RU (213.180.204.11) 56(84) bytes of data.
64 bytes from yandex.ru (213.180.204.11): icmp_req=1 ttl=58 time=2.24 ms
64 bytes from yandex.ru (213.180.204.11): icmp_req=2 ttl=58 time=1.82 ms
64 bytes from yandex.ru (213.180.204.11): icmp_req=3 ttl=58 time=2.18 ms
64 bytes from yandex.ru (213.180.204.11): icmp_req=4 ttl=58 time=1.78 ms
cheers, Gerhard /EDIS
Strange that I get other results as you do, and I am running a private DNS server there for the fact that the netowrk is fairly stable and performant in Russia/Moscow.
root@mow1ru:~# fping -c 10 -p 100 ru.pool.ntp.org ru.pool.ntp.org : [0], 96 bytes, 4.98 ms (4.98 avg, 0% loss) ru.pool.ntp.org : [1], 96 bytes, 3.43 ms (4.20 avg, 0% loss) ru.pool.ntp.org : [2], 96 bytes, 3.35 ms (3.92 avg, 0% loss) ru.pool.ntp.org : [3], 96 bytes, 2.88 ms (3.66 avg, 0% loss) ru.pool.ntp.org : [4], 96 bytes, 3.52 ms (3.63 avg, 0% loss) ru.pool.ntp.org : [5], 96 bytes, 3.97 ms (3.68 avg, 0% loss) ru.pool.ntp.org : [6], 96 bytes, 5.43 ms (3.93 avg, 0% loss) ru.pool.ntp.org : [7], 96 bytes, 3.06 ms (3.82 avg, 0% loss) ru.pool.ntp.org : [8], 96 bytes, 5.34 ms (3.99 avg, 0% loss) ru.pool.ntp.org : [9], 96 bytes, 9.12 ms (4.50 avg, 0% loss) ru.pool.ntp.org : xmt/rcv/%loss = 10/10/0%, min/avg/max = 2.88/4.50/9.12
And as Gerhard already said, 40ms really sounds like a connection to Frankfurt:
root@mow1ru:~# fping -c 10 -p 100 84.200.83.161 84.200.83.161 : [0], 84 bytes, 38.0 ms (38.0 avg, 0% loss) 84.200.83.161 : [1], 84 bytes, 38.0 ms (38.0 avg, 0% loss) 84.200.83.161 : [2], 84 bytes, 37.9 ms (38.0 avg, 0% loss) 84.200.83.161 : [3], 84 bytes, 43.2 ms (39.3 avg, 0% loss) 84.200.83.161 : [4], 84 bytes, 38.7 ms (39.2 avg, 0% loss) 84.200.83.161 : [5], 84 bytes, 38.2 ms (39.0 avg, 0% loss) 84.200.83.161 : [6], 84 bytes, 38.3 ms (38.9 avg, 0% loss) 84.200.83.161 : [7], 84 bytes, 42.6 ms (39.4 avg, 0% loss) 84.200.83.161 : [8], 84 bytes, 39.1 ms (39.3 avg, 0% loss) 84.200.83.161 : [9], 84 bytes, 38.0 ms (39.2 avg, 0% loss) 84.200.83.161 : xmt/rcv/%loss = 10/10/0%, min/avg/max = 37.9/39.2/43.2
-- Fusl