RamNode OpenVZ SSD 128MB (NL)

[mikeyur]

Upload is terrible to Singapore, Sydney and NewZealand.

Seattle location seems better for Australia and Asia as compared to their EU/Netherlands location.

You should test out the new los angeles location, perhaps it'll give some better results for Australia/Asia. http://lg.la.ramnode.com/

 

[bibo]

I have to buy a VM or request someone who already have one to test the network speed.

LG would only provide connectivity, route and latency from and to a specific location.

 

[mikeyur]

I have to buy a VM or request someone who already have one to test the network speed. LG would only provide connectivity, route and latency from and to a specific location.

I know, I was just sharing that it could potentially be a better option than Seattle.

 

[bibo]

I agree, i am hopping that too.
I think i'll ask Nick@support

Lets see what they have to say.

 

[wlanboy]

Time for an update:



1 hour and 33 minutes of downtime since the last update.

The vps itself does have an uptime of 49 days.

CPU and I/O are great.

Network could be better:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-02-23 04:16:25--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: '/dev/null'

100%[========================================================>] 104,857,600 43.1MB/s   in 2.3s

2015-02-23 04:16:28 (43.1 MB/s) - '/dev/null' saved [104857600/104857600]

 

[wlanboy]

Time for an update:



0 minutes of downtime since the last update.

The vps itself does have an uptime of 82 days.

CPU and I/O are great.

Network could be better:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-03-28 01:50:24--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: '/dev/null'

100%[========================================================>] 104,857,600 45.2MB/s   in 2.2s

2015-03-28 01:50:27 (45.2 MB/s) - '/dev/null' saved [104857600/104857600]

 

[wlanboy]

Time for an update:



35 minutes of downtime since the last update.
The vps itself does have an uptime of 104 days.

CPU and I/O are great.

Network could be better:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-08-03 08:01:41--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: '/dev/null'

100%[===========================================================================================================================================>] 104,857,600 62.5MB/s   in 1.6s

2015-08-03 08:01:43 (62.5 MB/s) - '/dev/null' saved [104857600/104857600]

 

[wlanboy]

Time for an update:



15 minutes of downtime since the last update.
The vps itself does have an uptime of 18 days.

CPU and I/O are great.

Network could be better:

wget cachefly.cachefly.net/100mb.test -O /dev/null
--2015-09-01 14:33:28--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: '/dev/null'

100%[===================================================================================================>] 104,857,600 50.3MB/s   in 2.0s

2015-09-01 14:33:30 (50.3 MB/s) - '/dev/null' saved [104857600/104857600]

 

[wlanboy]

Time for an update:





0 minutes of downtime since the last update.
CPU and I/O are great.


Network is ok.

 

[HalfEatenPie]

I love these long-term data collection thread.  Thanks @wlanboy for all your hard work! 

 

[wlanboy]

58 minutes of downtime since the last update.
CPU and I/O are good.


Network is good.

 

[wlanboy]

Time for an update:





0 minutes of downtime since the last update.
CPU and I/O are good.


Network is good.

 

[wlanboy]

Time for an update:





41 minutes of network downtime since the last update.
CPU and I/O are good.


Network is good.