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 - Page 4
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

124»

Comments

  • Via my school internet connection, location +- 100km to Singapore.

    C:\Documents and Settings\user>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=24ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=28ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=26ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=24ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=25ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=29ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=24ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=25ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=26ms TTL=49
    Reply from 192.71.144.254: bytes=32 time=25ms 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 = 24ms, Maximum = 29ms, Average = 25ms
    
    C:\Documents and Settings\user>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  xxx.xxx.xxx.xxx
      2    1 ms    1 ms    1 ms  xxx.xxx.xxx.xxx
      3    1 ms    1 ms    1 ms  xxx.xxx.xxx.xxx
      4    1 ms    1 ms    1 ms  xxx.xxx.xxx.xxx
      5    1 ms    1 ms    1 ms  xxx.xxx.xxx.xxx
      6    10 ms     9 ms    10 ms  161.142.5.217
      7    13 ms    12 ms    11 ms  ge0-2-0-0.mlk95.jaring.my [61.6.58.65]
      8    19 ms    15 ms    15 ms  pos0-2-0-0.drc96.jaring.my [161.142.25.85]
      9    16 ms    14 ms    15 ms  te0-2-0-0.bkj95.jaring.my [61.6.51.17]
     10    14 ms    13 ms    13 ms  ge-2-1-6.r03.kslrml01.my.bb.gin.ntt.net [203.78.193.117]
     11    20 ms    20 ms    20 ms  as-2.r20.sngpsi02.sg.bb.gin.ntt.net [129.250.2.187]
     12    20 ms    20 ms    20 ms  ae-1.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.143]
     13    20 ms    20 ms    20 ms  ae-0.softlayer.sngpsi02.sg.bb.gin.ntt.net [116.51.17.54]
     14    23 ms    22 ms    28 ms  ae5.dar02.sr03.sng01.networklayer.com [50.97.18.199]
     15    22 ms    21 ms    22 ms  po2.fcr01.sr03.sng01.networklayer.com [174.133.118.133]
     16     *        *        *     Request timed out.
     17     *        *        *     Request timed out.
     18   379 ms    26 ms    26 ms  192.71.144.3
     19    24 ms    24 ms    25 ms  192.71.144.254
    
    Trace complete.
    
  • @William said:
    As this is a new announced space the routes adjust themself over a few weeks while whitelisting on all upstreams is running through, it's the same as EDIS does.

    Fair point, that it isnt something i had considered, makes sense. Generally found SL routing to be very good (to HK and Thailand anyway).

  • @nonuby

    Like I said earlier, some of their routes can be weird. This is what I got in Singapore via Singnet:

    Pinging 192.71.144.254 with 32 bytes of data:
    Reply from 192.71.144.254: bytes=32 time=165ms TTL=46
    Reply from 192.71.144.254: bytes=32 time=106ms TTL=46
    Reply from 192.71.144.254: bytes=32 time=116ms TTL=46
    Reply from 192.71.144.254: bytes=32 time=108ms TTL=46
    
    3    24 ms    23 ms    23 ms  202.166.119.97
    4    23 ms    21 ms    25 ms  xe-2-0-0-3600.tp-ar09.singnet.com.sg [202.166.124.149]
    5    22 ms    23 ms    23 ms  xe-5-1-0.singha.singnet.com.sg [202.166.126.1]
    6    25 ms    30 ms    20 ms  ae3-0.pepsi.singnet.com.sg [202.166.126.125]
    7    29 ms    30 ms    23 ms  203.208.190.89
    8    30 ms    26 ms    75 ms  203.208.166.57
    9   115 ms    23 ms    99 ms  so-5-2-3-0.toknf-cr3.ix.singtel.com [203.208.154.18]
    10   218 ms    94 ms    90 ms  203.208.152.158
    11   219 ms   227 ms   218 ms  i-0-1-0-0.siko02.bi.telstraglobal.net [202.84.148.78]
    12   274 ms   225 ms   232 ms  i-0-4-0-0.siko-core04.bi.telstraglobal.net [202.84.148.77]
    13   268 ms   256 ms   252 ms  i-0-2-0-0.hkhh01.bi.telstraglobal.net [202.84.143.42]
    14   283 ms   253 ms   104 ms  unknown.telstraglobal.net [134.159.100.98]
    15   107 ms   107 ms   105 ms  ae0.bbr02.eq01.sng02.networklayer.com [50.97.18.172]
    16   103 ms   103 ms   109 ms  ae0.bbr02.eq01.sng02.networklayer.com [50.97.18.172]
    17   107 ms    99 ms   107 ms  ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
    18   103 ms   102 ms   109 ms  ae5.dar01.sr03.sng01.networklayer.com [50.97.18.197]
    19     *        *        *     Request timed out.
    20     *        *        *     Request timed out.
    21     *        *        *     Request timed out.
    22   110 ms   104 ms   109 ms  192.71.144.3
    23   106 ms   117 ms   111 ms  192.71.144.254
    
  • blackeyeblackeye Veteran
    edited November 2013

    here from indonesia .

    but I'm confused this is singapore or sweden ? ( sorry I'm don't know about this )

    and how about port speed ?

    thanks

  • how about original 64 mb vps ? ;) just need to host 1 static website there. If the lowest package is 128 I'll take that, anyway.

  • WilliamWilliam Member
    edited November 2013

    @nonuby said:
    Fair point, that it isnt something i had considered, makes sense. Generally found SL routing to be very good (to HK and Thailand anyway).

    This is also not 100TB, not sure how you get to that conclusion, SL SG is used as upstream by local companies as well (i.e. without dedicated, SL offers no colo at all) unlike in the US.

  • terafireterafire Member
    edited November 2013

    @blackeye Geolocation will be adjusted properly by the time our LET offer is posted.

  • Looks like our thread got force-sunk.

  • terafire said: Looks like our thread got force-sunk.

    Nah.

Sign In or Register to comment.