Howdy, Stranger!

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


TeraFire, LLC || New location in Singapore
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.

TeraFire, LLC || New location in Singapore

terafireterafire Member
edited November 2013 in Providers

Hello everyone
We're pleased to announce we have launched our new location at Softlayer Singapore.

We're offering both KVM and OpenVZ, so look out for our post next week :)

dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync; unlink test 16384+0 records in 16384+0 records out 1073741824 bytes (1.1 GB) copied, 5.62686 s, 191 MB/s

http://sing-lg.terafire.net is LookingGlass for those curious.

Thanks for listening :)

Reaction
  1. How do you feel about this?63 votes
    1. Shutup and take my money
      47.62%
    2. Nobody cares
      22.22%
    3. I like falafels
      30.16%
«134

Comments

  • budi1413budi1413 Member
    edited November 2013

    Shut up and take my money if you do leb kvm offer. :p

    Thanked by 2terafire typh0n
  • We're going to be doing a KVM 256 that will be in the LEB price range.

  • I will be waiting for it!!!

    Thanked by 1terafire
  • rm_rm_ IPv6 Advocate, Veteran

    @terafire mtr and traceroute do not work in your LG.

  • Traceroute works for me on two boxes, MTR should be working now, albeit slowly.

  • Congratulations on the new location! :)

    Thanked by 1terafire
  • Me claps

    Good to see more Asia market (better for economy and most VPS bought via LEB/LET just idle lol)

    Thanked by 1terafire
  • Im in!! Cant wait.

    Thanked by 1terafire
  • Yummy falafels congrats on the new location!

    Thanked by 1terafire
  • The packages are ready, the node is ready. We're ready to deploy VMs. We'll be waiting for next week for our LEB post to announce it here :)

  • 256mb + decent bandwidth shut up and take my money.

  • @cosmicgate we have kvm and openvz for that on our site if you want to check it out

  • StarryStarry Member, Host Rep

    Not good network to China either.

    Pinging 192.71.144.254 with 32 bytes of data: Reply from 192.71.144.254: bytes=32 time=233ms TTL=49 Reply from 192.71.144.254: bytes=32 time=232ms TTL=49 Reply from 192.71.144.254: bytes=32 time=233ms TTL=49 Reply from 192.71.144.254: bytes=32 time=232ms TTL=49

    `|------------------------------------------------------------------------------------------|

    | WinMTR statistics |

    | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

    |------------------------------------------------|------|------|------|------|------|------|

    | 113.98.95.77 - 0 | 54 | 54 | 8 | 19 | 79 | 13 |

    | 121.8.90.9 - 0 | 54 | 54 | 6 | 20 | 89 | 6 |

    | 61.144.3.2 - 0 | 54 | 54 | 8 | 16 | 74 | 12 |

    | 202.97.35.254 - 0 | 54 | 54 | 6 | 20 | 89 | 7 |

    | 202.97.60.206 - 0 | 54 | 54 | 7 | 18 | 79 | 9 |

    | 202.97.51.134 - 0 | 53 | 53 | 176 | 185 | 244 | 181 |

    | 202.97.90.78 - 0 | 53 | 53 | 190 | 203 | 255 | 193 |

    | ge9-9.br02.sjo01.pccwbtn.net - 0 | 53 | 53 | 200 | 220 | 358 | 345 |

    | TenGE8-2.br02.sin02.pccwbtn.net - 0 | 53 | 53 | 227 | 244 | 390 | 232 |

    | softlayer.te7-5.br02.sin02.pccwbtn.net - 0 | 53 | 53 | 228 | 238 | 298 | 233 |

    | ae6.dar01.sr03.sng01.networklayer.com - 0 | 53 | 53 | 228 | 243 | 303 | 233 |

    | po1.fcr01.sr03.sng01.networklayer.com - 84 | 12 | 2 | 0 | 232 | 233 | 232 |

    | No response from host - 100 | 10 | 0 | 0 | 0 | 0 | 0 |

    | No response from host - 100 | 10 | 0 | 0 | 0 | 0 | 0 |

    | 192.71.144.3 - 0 | 53 | 53 | 232 | 249 | 308 | 234 |

    | 192.71.144.254 - 0 | 53 | 53 | 232 | 247 | 309 | 232 |

    |________________________________________________|______|______|______|______|______|______|

    WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider`

  • But, let me guess, your VPS provider is sooooo much better, right?

  • how much traffic it will be ?

  • @arieonline From 200GB-1TB

  • What is host node specification? :D

  • terafireterafire Member
    edited November 2013

    Dual L5520s
    48gb ram.
    4 x 450gb SAS 15k rpm drives hardware RAID 10.

  • Softlayer Singapore has some "weird" routing, the network speed may be good for some but not everyone.

  • Cool! here's my ping test @terafire

    Pinging 192.71.144.254 with 32 bytes of data:
    Reply from 192.71.144.254: bytes=32 time=17ms TTL=53
    Reply from 192.71.144.254: bytes=32 time=27ms TTL=53
    Reply from 192.71.144.254: bytes=32 time=26ms TTL=53
    Reply from 192.71.144.254: bytes=32 time=30ms TTL=53
    Reply from 192.71.144.254: bytes=32 time=20ms TTL=53
    Reply from 192.71.144.254: bytes=32 time=17ms TTL=53
    Reply from 192.71.144.254: bytes=32 time=39ms TTL=53
    
    Ping statistics for 192.71.144.254:
        Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 17ms, Maximum = 39ms, Average = 25ms
    
  • Nice! Where do you live @ravenchad

  • @terafire said:
    Nice! Where do you live ravenchad

    Lols. here in SG :D, that's why :p

  • Makes sense :D

  • ravenchadravenchad Member
    edited November 2013

    Tracing route to 192.71.144.254 over a maximum of 30 hops

    1 1 ms <1 ms <1 ms 192.168.0.2
    2 8 ms 23 ms 11 ms cm1.kappa168.maxonline.com.sg [58.182.168.1]
    3 15 ms 10 ms 11 ms 172.20.42.1
    4 10 ms 14 ms 14 ms 172.26.42.1
    5 * * * Request timed out.
    6 9 ms 22 ms 11 ms 172.20.9.30
    7 20 ms 15 ms 27 ms 203.117.36.97
    8 15 ms 29 ms 11 ms 203.117.34.229
    9 48 ms 14 ms 22 ms 203.117.34.201
    10 12 ms 37 ms 10 ms 203.117.36.22
    11 26 ms 28 ms 70 ms v101.bbr01.eq01.sng02.networklayer.com [50.97.16
    .9]
    12 15 ms 15 ms 14 ms ae5.dar01.sr03.sng01.networklayer.com [50.97.18.
    197]
    13 14 ms 15 ms 14 ms po1.fcr01.sr03.sng01.networklayer.com [174.133.1
    18.131]
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 31 ms 18 ms 26 ms 192.71.144.3
    17 44 ms 43 ms 18 ms 192.71.144.254

  • @ravenchad said:
    Cool! here's my ping test terafire

    > Pinging 192.71.144.254 with 32 bytes of data:
    > Reply from 192.71.144.254: bytes=32 time=17ms TTL=53
    > Reply from 192.71.144.254: bytes=32 time=27ms TTL=53
    > Reply from 192.71.144.254: bytes=32 time=26ms TTL=53
    > Reply from 192.71.144.254: bytes=32 time=30ms TTL=53
    > Reply from 192.71.144.254: bytes=32 time=20ms TTL=53
    > Reply from 192.71.144.254: bytes=32 time=17ms TTL=53
    > Reply from 192.71.144.254: bytes=32 time=39ms TTL=53
    > 
    > Ping statistics for 192.71.144.254:
    >     Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
    > Approximate round trip times in milli-seconds:
    >     Minimum = 17ms, Maximum = 39ms, Average = 25ms
    > 

    I had better ping result than yours and I'm not even at sg lol

    wcypierre:~$ ping 192.71.144.254
    PING 192.71.144.254 (192.71.144.254) 56(84) bytes of data.
    64 bytes from 192.71.144.254: icmp_seq=1 ttl=56 time=17.5 ms
    64 bytes from 192.71.144.254: icmp_seq=2 ttl=56 time=16.8 ms
    64 bytes from 192.71.144.254: icmp_seq=3 ttl=56 time=20.4 ms
    64 bytes from 192.71.144.254: icmp_seq=4 ttl=56 time=16.6 ms
    64 bytes from 192.71.144.254: icmp_seq=5 ttl=56 time=15.6 ms
    64 bytes from 192.71.144.254: icmp_seq=6 ttl=56 time=17.3 ms
    64 bytes from 192.71.144.254: icmp_seq=7 ttl=56 time=15.3 ms
    
    --- 192.71.144.254 ping statistics ---
    7 packets transmitted, 7 received, 0% packet loss, time 6009ms
    rtt min/avg/max/mdev = 15.329/17.105/20.417/1.557 ms
    
  • @wcypierre said:

    That's lol. sorry about that mate, i'm just using mobile(LTE) to ping :P

  • Pinging 192.71.144.254 with 32 bytes of data:
    
    Reply from 192.71.144.254: bytes=32 time=336ms TTL=46
    Reply from 192.71.144.254: bytes=32 time=330ms TTL=46
    Reply from 192.71.144.254: bytes=32 time=338ms TTL=46
    Reply from 192.71.144.254: bytes=32 time=331ms TTL=46
    
    Ping statistics for 192.71.144.254:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 330ms, Maximum = 338ms, Average = 333ms
  • budi1413budi1413 Member
    edited November 2013

    Via Maxis 3.75G connection.

    C:\Users\budi>ping -n 10 192.71.144.254
    
    Pinging 192.71.144.254 with 32 bytes of data:
    Reply from 192.71.144.254: bytes=32 time=65ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=63ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=71ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=221ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=63ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=68ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=70ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=76ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=68ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=70ms TTL=49
    
    Ping statistics for 192.71.144.254:
        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 63ms, Maximum = 221ms, Average = 83ms
    
    C:\Users\budi>tracert 192.71.144.254
    
    Tracing route to 192.71.144.254 over a maximum of 30 hops
    
      1    1 ms    1 ms    1 ms  router.budi.my [192.168.1.1]
      2     *        *        *     Request timed out.
      3   116 ms    77 ms    79 ms  10.213.46.106
      4   115 ms    79 ms    80 ms  202.179.116.37
      5   115 ms    77 ms    81 ms  202.75.188.201
      6   123 ms    85 ms    81 ms  202.151.252.201
      7   119 ms    77 ms    79 ms  202.151.241.154
      8   170 ms    76 ms    81 ms  202.151.241.153
      9   131 ms    85 ms    78 ms  202.151.241.134
     10    76 ms    77 ms    79 ms  202.151.241.142
     11   132 ms    87 ms    99 ms  202.151.252.250
     12    78 ms    91 ms    87 ms  36351.sgw.equinix.com [202.79.197.69]
     13    80 ms    99 ms    85 ms  ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
     14     *        *        *     Request timed out.
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
     17   272 ms   379 ms   369 ms  192.71.144.3
     18   273 ms   685 ms    59 ms  192.71.144.254
    
    Trace complete.
    

    I'll try using my school internet connection this Monday. :D

  • @ravenchad said:
    That's lol. sorry about that mate, i'm just using mobile(LTE) to ping :P

    ahh.... no wonder. I'm on a fixed line. It seemed a bit weird at first that I had better ping than you but now it has been resolved :D

    @budi1413 said:
    Via Maxis 3.75G connection.

    > C:\Users\budi>ping -n 10 192.71.144.254
    > 
    > Pinging 192.71.144.254 with 32 bytes of data:
    > Reply from 192.71.144.254: bytes=32 time=65ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=63ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=71ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=221ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=63ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=68ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=70ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=76ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=68ms TTL=49
    > Reply from 192.71.144.254: bytes=32 time=70ms TTL=49
    > 
    > Ping statistics for 192.71.144.254:
    >     Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    > Approximate round trip times in milli-seconds:
    >     Minimum = 63ms, Maximum = 221ms, Average = 83ms
    > 
    > C:\Users\budi>tracert 192.71.144.254
    > 
    > Tracing route to 192.71.144.254 over a maximum of 30 hops
    > 
    >   1    1 ms    1 ms    1 ms  router.budi.my [192.168.1.1]
    >   2     *        *        *     Request timed out.
    >   3   116 ms    77 ms    79 ms  10.213.46.106
    >   4   115 ms    79 ms    80 ms  202.179.116.37
    >   5   115 ms    77 ms    81 ms  202.75.188.201
    >   6   123 ms    85 ms    81 ms  202.151.252.201
    >   7   119 ms    77 ms    79 ms  202.151.241.154
    >   8   170 ms    76 ms    81 ms  202.151.241.153
    >   9   131 ms    85 ms    78 ms  202.151.241.134
    >  10    76 ms    77 ms    79 ms  202.151.241.142
    >  11   132 ms    87 ms    99 ms  202.151.252.250
    >  12    78 ms    91 ms    87 ms  36351.sgw.equinix.com [202.79.197.69]
    >  13    80 ms    99 ms    85 ms  ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
    >  14     *        *        *     Request timed out.
    >  15     *        *        *     Request timed out.
    >  16     *        *        *     Request timed out.
    >  17   272 ms   379 ms   369 ms  192.71.144.3
    >  18   273 ms   685 ms    59 ms  192.71.144.254
    > 
    > Trace complete.
    > 

    I'll try using my school internet connection this Monday. :D

    I think that you'll get something similar to mine at your school ;)

Sign In or Register to comment.