Howdy, Stranger!

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


Prometeus 256MB 5GB SSD 100GB Xen PV in Pune, India - Page 2
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.

Prometeus 256MB 5GB SSD 100GB Xen PV in Pune, India

2»

Comments

  • rm_rm_ IPv6 Advocate, Veteran
    edited November 2013

    earl said: Tempting offer, but not sure what I would do with an Indian VPS? other than DNS, what are you guys using it for?

    If you or your visitors/clients are in Asia, getting an Asian VPS is absolutely the best choice not only due to low ping, but also for long term reasons... You're actually helping if just a tiny bit, to improve the local Internet and high-tech infrastructure by 'investing' a bit of money (even if just a LEB's price) into local services, and this in turn pays for stuff like pulling new cables and creates local high-tech jobs, in turn creating demand for higher education, etc.

    Whereas buying an US VPS you're just paying to an already rich, but dumb and greedy country who thinks it owns the world and the internet, and also support things like NSA's PRISM.

    Let's end this "need low ping for Asia => get a LA VPS" nonsense. :)

  • Hmmm, India. Interesting location, might pick up one

  • Awesome stuff, Sal. Quality as always. Thanks for the dns too :)

  • What the hey.. I got one!

    Pretty impressed with setup, I got my server info before I received my payment confirmation from paypal.. Premium stuff this Prometeus :)

  • InfinityInfinity Member, Host Rep

    @prometeus said:
    The looking glass wasn't ready

    For those interested; http://lg-pune.prometeus.net/ is now up.

  • @rm_ said:
    Let's end this "need low ping for Asia => get a LA VPS" nonsense. :)

    I like your comment :)

    Thanked by 1ErawanArifNugroho
  • Increasing the bandwidth will be great

  • gbshousegbshouse Member, Host Rep

    I like it!

    Trace to our NS1

    traceroute to 176.124.112.100 (176.124.112.100), 30 hops max, 60 byte packets
    1  194.71.224.2 (194.71.224.2)  0.162 ms  0.152 ms  0.142 ms
    2  103.12.211.1 (103.12.211.1)  0.446 ms  0.548 ms  0.619 ms
    3  14.140.128.97 (14.140.128.97)  1.758 ms  1.814 ms  1.918 ms
    4  172.29.251.33 (172.29.251.33)  22.970 ms  23.059 ms  23.129 ms
    5  172.25.82.66 (172.25.82.66)  24.413 ms  24.370 ms  24.474 ms
    6  172.25.82.66 (172.25.82.66)  24.582 ms  24.075 ms  23.888 ms
    7  59.163.105.169 (59.163.105.169)  26.327 ms  26.921 ms  26.263 ms
    8  180.179.37.94 (180.179.37.94)  25.957 ms  25.999 ms  26.063 ms
    9  180.179.33.246 (180.179.33.246)  27.087 ms  27.178 ms  27.268 ms
    10  ns1.r4ns.com (176.124.112.100)  27.771 ms  27.661 ms  27.552 ms

    Trace to our NS2

    traceroute to 176.124.113.200 (176.124.113.200), 30 hops max, 60 byte packets
    1  194.71.224.2 (194.71.224.2)  0.148 ms  0.131 ms  0.118 ms
    2  ns2.r4ns.com (176.124.113.200)  0.869 ms  0.757 ms  0.651 ms
  • Via Maxis 3.75G connection.

    C:\Users\budi>ping -n 10 194.71.224.14
    
    Pinging 194.71.224.14 with 32 bytes of data:
    Reply from 194.71.224.14: bytes=32 time=154ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=155ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=155ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=153ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=155ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=155ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=295ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=155ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=153ms TTL=48
    Reply from 194.71.224.14: bytes=32 time=153ms TTL=48
    
    Ping statistics for 194.71.224.14:
        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 153ms, Maximum = 295ms, Average = 168ms
    
    C:\Users\budi>tracert 194.71.224.14
    
    Tracing route to 194.71.224.14 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    35 ms    33 ms    35 ms  10.213.46.106
      4    36 ms    33 ms    35 ms  202.179.116.37
      5    38 ms    37 ms    35 ms  202.75.188.201
      6    78 ms    39 ms    39 ms  202.151.252.201
      7    35 ms    33 ms    35 ms  202.151.241.154
      8    73 ms    73 ms    71 ms  202.151.241.157
      9    75 ms    73 ms    73 ms  p-0-7-0-0.shtt-core78b.maxis.net.my [202.151.241
    .138]
     10    74 ms    71 ms    75 ms  202.151.241.149
     11    72 ms    71 ms    73 ms  p-1-0-0.hkpc-bdr1.maxis.net.my [202.122.151.254]
    
     12   144 ms    71 ms    71 ms  teleglobe-10G.hkix.net [202.40.161.224]
     13   137 ms   132 ms   137 ms  116.0.67.122
     14   153 ms   173 ms   153 ms  172.31.19.94
     15   154 ms   193 ms   165 ms  172.25.81.130
     16   153 ms   153 ms   271 ms  172.25.81.130
     17   155 ms   155 ms   153 ms  14.140.128.98.static-vsnl.net.in [14.140.128.98]
    
     18   157 ms   171 ms   161 ms  103.12.211.136
     19   158 ms   157 ms   157 ms  194.71.224.14
    
    Trace complete.
    
  • rm_rm_ IPv6 Advocate, Veteran

    Infinity said: For those interested; http://lg-pune.prometeus.net/ is now up.

    It's now down on IPv6:

    PING lg-pune.prometeus.net(2a00:dcc7:1aff:2405::4f7d:29ab) 56 data bytes
    ^C
    --- lg-pune.prometeus.net ping statistics ---
    9 packets transmitted, 0 received, 100% packet loss, time 8064ms
  • prometeusprometeus Member, Host Rep

    @rm_ said:
    9 packets transmitted, 0 received, 100% packet loss, time 8064ms

    We are being ddossed since Erawan posted. Not looking good.

  • How much traffic of ddos uncle Sal

  • prometeusprometeus Member, Host Rep
    edited November 2013

    @horas said:
    How much traffic of ddos uncle Sal

    I dont have details right now.... I'm out with family first time after months :-P

    Thanked by 1jcaleb
  • 61.4 ms ping to Sri Lanka and thats bad! Even the Singapore is ~40ms away

  • rm_rm_ IPv6 Advocate, Veteran
    edited November 2013

    Ruchirablog said: 61.4 ms ping to Sri Lanka and thats bad

    If you want anyone to look at why is this so, and if anything can be done about it, you post a traceroute, not just complain with a useless ping number.

    Thanked by 1Amfy
  • Traceroute to Pune

    Ruchiras-MacBook-Pro:~ Lion$ traceroute 194.71.224.14
    traceroute to 194.71.224.14 (194.71.224.14), 64 hops max, 52 byte packets
     1  10.0.0.1 (10.0.0.1)  1.231 ms  0.853 ms  0.544 ms
     2  192.168.1.1 (192.168.1.1)  1.006 ms  0.939 ms  0.787 ms
     3  220.247.232.96 (220.247.232.96)  6.875 ms  7.261 ms  6.589 ms
     4  222.165.184.150 (222.165.184.150)  6.959 ms  6.955 ms  10.319 ms
     5  222.165.175.46 (222.165.175.46)  7.113 ms  7.712 ms  6.892 ms
     6  222.165.177.10 (222.165.177.10)  6.924 ms  7.328 ms  7.162 ms
     7  static.ill.210.212.70.54/24.bsnl.in (210.212.70.54)  24.743 ms  25.314 ms  24.961 ms
     8  * * *
     9  172.25.81.37 (172.25.81.37)  48.748 ms  48.959 ms
        172.25.80.53 (172.25.80.53)  51.014 ms
    10  172.25.81.118 (172.25.81.118)  47.015 ms
        172.25.81.130 (172.25.81.130)  47.358 ms
        172.25.81.118 (172.25.81.118)  47.369 ms
    11  172.25.81.130 (172.25.81.130)  57.197 ms  50.431 ms
        172.25.81.118 (172.25.81.118)  49.054 ms
    12  14.140.128.98.static-vsnl.net.in (14.140.128.98)  56.080 ms  48.400 ms  47.711 ms
    13  103.12.211.135 (103.12.211.135)  47.979 ms  49.227 ms  48.690 ms
    14  194.71.224.14 (194.71.224.14)  55.871 ms  51.783 ms  52.089 ms

    Traceroute to Milan

    Ruchiras-MacBook-Pro:~ Lion$ traceroute 37.247.53.10
    traceroute to 37.247.53.10 (37.247.53.10), 64 hops max, 52 byte packets
     1  10.0.0.1 (10.0.0.1)  1.249 ms  0.630 ms  0.543 ms
     2  192.168.1.1 (192.168.1.1)  1.056 ms  0.966 ms  0.837 ms
     3  220.247.232.96 (220.247.232.96)  8.576 ms  6.961 ms  7.360 ms
     4  222.165.184.150 (222.165.184.150)  7.107 ms  7.752 ms  7.160 ms
     5  222.165.175.18 (222.165.175.18)  10.515 ms  8.210 ms  10.202 ms
     6  pos0-15-3-3.palermo16.pal.seabone.net (195.22.198.16)  120.399 ms  121.155 ms  120.750 ms
     7  te8-2.milano52.mil.seabone.net (195.22.205.241)  144.283 ms  141.976 ms  145.104 ms
     8  cdlan.milano52.mil.seabone.net (195.22.192.3)  149.550 ms  148.244 ms  182.301 ms
     9  217.171.46.241 (217.171.46.241)  143.813 ms  144.196 ms  144.118 ms
    10  punc03.sk5r.com (37.247.53.10)  142.188 ms  142.293 ms  142.147 ms
  • @rm_ said:
    If you want anyone to look at why is this so, and if anything can be done about it, you post a traceroute, not just complain with a useless ping number.

    yeah I know. Had the same argument with the leapswitch guys while ago and I was too lazy to post a traceroute. It seems like problem still exists.

  • prometeusprometeus Member, Host Rep

    Hope this will get better with time, the change need to be driven from the bottom. If we leave big players to dictate rules, then their motivations will be the only which matter.

    Ipv6 is an example, Asia is on the last /8 since the last year, yet infrasructure for ipv6 is not progressing ad much as it should. Small isp and clients must do as much pressure they can.

    I'm putting the money I can, even if it will be a loss, I think it's the right thing to do as a long term project. You know I'm from Italy, not exactly the center of Internet :-)

  • I'm so sorry Uncle Sal, this is what I'm afraid of. :(

    Maybe I have to move to another place for a moment, and please keep the vps off until it's safe.

  • prometeusprometeus Member, Host Rep

    @ErawanArifNugroho said:
    I'm so sorry Uncle Sal, this is what I'm afraid of. :(

    Maybe I have to move to another place for a moment, and please keep the vps off until it's safe.

    No problem, I still don't understand why people need to target innocents.

    S.

  • prometeusprometeus Member, Host Rep

    @Liam said:
    Congrats on the launch 'Uncle.

    Thanks :-)

  • leapswitchleapswitch Patron Provider, Veteran

    Hello,
    I was also away on a trip when the DDOS attacks happened. I am back in office now and we are implementing an automated system with great help from Prometeus to protect against such issues in the future.
    We are also in talks with TATA to implement their cloud based mDDOS solution.

  • @prometeus does the Mirkotik Cloud Core router do good netflow collecting / exporting?

    Thanked by 1nocom
Sign In or Register to comment.