2 min read

[Solved] - A little weird case with RamNode SSD Cached VZ2

I know it’s hard for me to write this, but I have to.
Several days ago, I just noticed some slow connection and other thing with my RamNode SSD Cached VZ2.

  • VPN connection is loading very slow, but I don’t have problem last week.
  • Playing a music from WordPress took so long time to buffer.

I know it might be just my network, but it’s weird if compared to my Prometeus VZ5 which is hosting my blog. My Prometeus VZ5 only took a little time to play the music from my wordpress blog, while at RamNode, it could took more than 5 minutes.
I’ve asked Nick about this, but he said that the node where my vps located is on low traffic, so in the other words I shouldn’t have a problem with the connection.
Let’s see about my traceroute bellow :
Traceroute from my modem to Prometeus VZ 5 :

# tracert www.erawanarifnugroho.com
Tracing route to www.erawanarifnugroho.com [194.14.179.132]
over a maximum of 30 hops:
  1    1 ms    1 ms    <1 ms  192.168.1.1
  2    19 ms    19 ms    50 ms  180.245.xxx.xxx
  3    35 ms    50 ms    25 ms  180.252.xxx.xxx
  4    34 ms    22 ms    22 ms  61.94.114.105
  5    50 ms    55 ms    47 ms  61.subnet118-98-61.astinet.telkom.net.id [118.98
.61.61]
  6    54 ms    51 ms    76 ms  62.subnet118-98-61.astinet.telkom.net.id [118.98
.61.62]
  7   240 ms   180 ms    56 ms  xe-0-1-0.singapore2.sin.seabone.net [93.186.133.
57]
  8   317 ms   320 ms   317 ms  te8-2.milano52.mil.seabone.net [195.22.205.241]
  9   316 ms   318 ms   253 ms  225.128.240.180.telin.sg [180.240.128.225]
 10   317 ms   139 ms   176 ms  217.171.46.241
 11   311 ms    16 ms   312 ms  194.14.179.252
 12   329 ms   316 ms   346 ms  it.erawanarifnugroho.com [194.14.179.132]
Trace complete.

And this is the traceroute to my RamNode :

# tracert www.erawan.me
Tracing route to www.erawan.me [199.241.31.150]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  192.168.1.1
  2    23 ms    27 ms    22 ms  180.245.xxx.xxx
  3    54 ms    32 ms    22 ms  180.252.xxx.xxx
  4   277 ms    63 ms    23 ms  61.94.114.105
  5    47 ms    62 ms    57 ms  226.128.240.180.telin.sg [180.240.128.226]
  6   138 ms    42 ms    63 ms  225.128.240.180.telin.sg [180.240.128.225]
  7   562 ms   220 ms   219 ms  xe-10-0-0.edge1.LosAngeles6.Level3.net [4.26.0.1
53]
  8   577 ms   224 ms     *     IntelQ-Tinet-level3-te.LosAngeles6.level3.net [4
.68.62.2]
  9     *      289 ms   289 ms  xe-2-0-0.atl11.ip4.tinet.net [89.149.185.53]
 10   283 ms   284 ms   288 ms  ramnode-gw.ip4.tinet.net [77.67.78.254]
 11   291 ms   291 ms     *     atlcvz2.ramnode.com [199.241.30.49]
 12   290 ms   294 ms   289 ms  at.erawan.me [199.241.31.150]
Trace complete.

From the traceroute to my RamNode VPS, I get the same hops compared to my Prometeus VPS, but the speed is slow. I hope my ISP fix the problem immediately 🙁
Update  27-02-2013

  • Nick  moved me to another node ( ATLCVZ12 ), and now it’s loading faster. The IO speed is also nice, arround 1GB/s.
  • Thank you very much. Case solved