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
3,59 Mbps Download,
1,14 Mbps Upload
from Antalya, Turkey
based on the Mini Speedtest.net Widget on SG DO Test IP 128.199.255.139
Edit:
Also, pinged from terminal; ~345ms from TR
Edit 2:
They have added more peering connections, e.g. now HE.net SG is no longer 390msec, but sub-1msec as it should be. So if their routing was bad for you, it's time to re-test.
faster about 10 ms. And they've add equinix.com. Great!
My apartment Singtel internet is still routing through NTT HK.
which means that your local ISP does not have peering with EQX
Singtel is one of the bigger providers here...that's my point.
I know Sometimes, it could be that they don't want to peer with others that much for cost reasons or they have some issues with them.
Hi @rm_, may I know from which network you performed the test from? Possible to open up a ticket with us with the result with ping/traceroute results for us to investigate?
Thank you.
Guess you have missed this? http://lowendtalk.com/discussion/19618/simplercloud-1-month-review The speeds to your VPS from any of the test files are 2-3 megabits at most. Only Cloudflare is somewhat fast, but even it, is much lower than 100 Mbit.
Compare to DigitalOcean: http://lowendtalk.com/discussion/comment/473310/#Comment_473310
more than 100 megabit easily to many destinations, tens of megabits to others, gigabit within Singapore!
@indrapr also I wanted to check your website, but it doesn't even load
http://s.lowendshare.com/1/1392646113.540.2014-02-17T140747Z-sc.png
forgot to restart mysql maybe
Error establishing a database connection
Routing seems to be horrible. This is from India and it goes all around the world.
ishan@ishan-desktop:~$ ping 128.199.236.162
PING 128.199.236.162 (128.199.236.162) 56(84) bytes of data.
64 bytes from 128.199.236.162: icmp_seq=1 ttl=50 time=453 ms
64 bytes from 128.199.236.162: icmp_seq=2 ttl=50 time=480 ms
--- 128.199.236.162 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 453.127/467.058/480.990/13.948 ms
ishan@ishan-desktop:~$ traceroute 128.199.236.162
traceroute to 128.199.236.162 (128.199.236.162), 30 hops max, 60 byte packets
1 DD-WRT (192.168.1.1) 0.883 ms 1.182 ms 1.485 ms
2 121.246.214.1.static-pune.vsnl.net.in (121.246.214.1) 26.901 ms 27.441 ms 28.421 ms
3 202.54.10.36 (202.54.10.36) 30.200 ms 30.190 ms 31.225 ms
4 * * 172.29.250.33 (172.29.250.33) 41.154 ms
5 * * ix-0-100.tcore1.MLV-Mumbai.as6453.net (180.87.38.5) 38.628 ms
6 * * *
7 if-8-1600.tcore1.PYE-Paris.as6453.net (80.231.217.6) 224.952 ms 219.139 ms *
8 * if-3-6.tcore1.L78-London.as6453.net (80.231.130.85) 222.339 ms 227.911 ms
9 if-7-2.tcore1.NJY-Newark.as6453.net (66.198.70.25) 228.816 ms if-2-2.tcore2.L78-London.as6453.net (80.231.131.1) 220.716 ms if-7-2.tcore1.NJY-Newark.as6453.net (66.198.70.25) 228.449 ms
10 63.243.128.37 (63.243.128.37) 214.041 ms 216.971 ms if-2-2.tcore2.NJY-Newark.as6453.net (66.198.70.2) 215.158 ms
11 ae-9.r05.nycmny01.us.bb.gin.ntt.net (129.250.9.213) 228.114 ms 222.085 ms if-14-14.tcore2.NTO-NewYork.as6453.net (66.198.111.126) 233.857 ms
12 63.243.128.69 (63.243.128.69) 223.292 ms ae-1.r23.nycmny01.us.bb.gin.ntt.net (129.250.4.68) 237.984 ms 63.243.128.69 (63.243.128.69) 231.277 ms
13 ae-9.r05.nycmny01.us.bb.gin.ntt.net (129.250.9.213) 228.633 ms 227.351 ms 222.518 ms
14 ae-1.r23.nycmny01.us.bb.gin.ntt.net (129.250.4.68) 233.275 ms ae-7.r23.nycmny01.us.bb.gin.ntt.net (129.250.4.165) 236.077 ms ae-1.r23.nycmny01.us.bb.gin.ntt.net (129.250.4.68) 237.914 ms
15 ae-9.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.149) 232.735 ms 241.782 ms 242.077 ms
16 ae-0.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.5) 226.171 ms * *
17 ae-4.r20.snjsca04.us.bb.gin.ntt.net (129.250.4.103) 292.787 ms 289.809 ms ae-2.r00.sngpsi02.sg.bb.gin.ntt.net (129.250.3.147) 474.773 ms
18 116.51.27.150 (116.51.27.150) 485.896 ms ae-2.r20.sngpsi05.sg.bb.gin.ntt.net (129.250.3.49) 486.799 ms 486.490 ms
19 103.253.144.242 (103.253.144.242) 461.206 ms ae-2.r00.sngpsi02.sg.bb.gin.ntt.net (129.250.3.147) 462.240 ms 103.253.144.242 (103.253.144.242) 464.457 ms
20 116.51.27.150 (116.51.27.150) 477.430 ms aws1.leapswitch.com (128.199.236.162) 476.755 ms 116.51.27.150 (116.51.27.150) 485.080 ms
True. I get lower pings on my US server from India then this SG server, Hope this work out well soon.
@leapswitch
I am getting good ping...any my ISP routing seems to be just fine...i am using Vodafone Internet
http://postimg.org/image/fg9atr8q1/
then Vodafone has peering with Equinix while what leapswitch uses doesn't so his traceroute results is not as good as yours.
Hi @rm_, sorry just saw this -- yes I think I might have missed quite a lot.
As per our discussion on the other thread: http://lowendtalk.com/discussion/19618/simplercloud-1-month-review , you have tested and our network is now better compared to the last testing done. Thanks for the re-test.
That might be during the time when the mysql was unstable - we have since fixed the problem and it has been much stable since. We also setup monitoring system which will restart the mysql service if it's down.
Again, thank you for your feedback.
Cheers.