1. Click here to join our community discord server.

New testserver Brasil, please ping it

Discussion in 'General Discussion' started by marvel, May 10, 2011.

  1. marvel

    marvel Head Administrator Staff Member

    Please ping this server and post your results in this topic. This goes especially for people from south america. Please post your location and latency in ms.

    189.113.43.90

    This is from Amsterdam so looks very good (current is 290 ms).

    PING 189.113.43.90 (189.113.43.90) 56(84) bytes of data.
    64 bytes from 189.113.43.90: icmp_req=1 ttl=52 time=198 ms
    64 bytes from 189.113.43.90: icmp_req=2 ttl=52 time=200 ms
    64 bytes from 189.113.43.90: icmp_req=3 ttl=52 time=199 ms
     
    marvel, May 10, 2011
    #1
  2. Nova

    Nova Senior Member

    Pinging 189.113.43.90 with 32 bytes of data:
    Reply from 189.113.43.90: bytes=32 time=234ms TTL=46
    Reply from 189.113.43.90: bytes=32 time=206ms TTL=46
    Reply from 189.113.43.90: bytes=32 time=202ms TTL=46
    Reply from 189.113.43.90: bytes=32 time=206ms TTL=46

    ping from high traffic connection in France
     
    Nova, May 10, 2011
    #2
  3. Stefeman

    Stefeman Head Administrator Staff Member

    Pinging 189.113.43.90 with 32 bytes of data:
    Reply from 189.113.43.90: bytes=32 time=240ms TTL=52
    Reply from 189.113.43.90: bytes=32 time=249ms TTL=52
    Reply from 189.113.43.90: bytes=32 time=237ms TTL=52
    Reply from 189.113.43.90: bytes=32 time=237ms TTL=52

    Pinged from Finland.
     
    Stefeman, May 10, 2011
    #3
  4. Dragon

    Dragon MG Donor

    Pinging 189.113.43.90 with 32 bytes of data:
    Reply from 189.113.43.90: bytes=32 time=157ms TTL=52
    Reply from 189.113.43.90: bytes=32 time=161ms TTL=52
    Reply from 189.113.43.90: bytes=32 time=164ms TTL=52
    Reply from 189.113.43.90: bytes=32 time=161ms TTL=52

    Pinged from Peru.
     
    Dragon, May 10, 2011
    #4
  5. Syd

    Syd Member

    Disparando 189.113.43.90 com 32 bytes de dados:
    Resposta de 189.113.43.90: bytes=32 tempo=19ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=24ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=19ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=18ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=20ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=19ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=21ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=20ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=18ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=20ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=20ms TTL=52
    Resposta de 189.113.43.90: bytes=32 tempo=18ms TTL=52

    Pinged from Brazil, looking good.
     
    Syd, May 10, 2011
    #5
  6. marvel

    marvel Head Administrator Staff Member

    That's awesome, great ping. Way better than the other host. Now let's hope the hardware is good enough (it's a VMWare machine). I'm bringing coop online on it soon so we can test.

    I could even check honorcode's ping by pinging his gateway:

    PING 201.215.170.254 (201.215.170.254) 56(84) bytes of data.
    64 bytes from 201.215.170.254: icmp_seq=1 ttl=54 time=61.7 ms
    64 bytes from 201.215.170.254: icmp_seq=2 ttl=54 time=61.6 ms
    64 bytes from 201.215.170.254: icmp_seq=3 ttl=54 time=63.6 ms

    Current Brazil to HC:

    PING 201.215.170.254 (201.215.170.254) 56(84) bytes of data.
    64 bytes from 201.215.170.254: icmp_req=1 ttl=52 time=354 ms
    64 bytes from 201.215.170.254: icmp_req=2 ttl=52 time=364 ms
    64 bytes from 201.215.170.254: icmp_req=3 ttl=52 time=365 ms

    Big difference! :)

    If it all works out I'll cancel hostdime and move to this host.
     
    marvel, May 10, 2011
    #6
  7. Kitties

    Kitties Head Administrator

    Pinged from Washington, USA

    PING 189.113.43.90 (189.113.43.90): 56 data bytes
    64 bytes from 189.113.43.90: icmp_seq=0 ttl=52 time=200.608 ms
    64 bytes from 189.113.43.90: icmp_seq=1 ttl=52 time=201.825 ms
    64 bytes from 189.113.43.90: icmp_seq=2 ttl=52 time=201.284 ms
    64 bytes from 189.113.43.90: icmp_seq=3 ttl=52 time=200.784 ms
    64 bytes from 189.113.43.90: icmp_seq=4 ttl=52 time=200.509 ms
    64 bytes from 189.113.43.90: icmp_seq=5 ttl=52 time=201.660 ms
    64 bytes from 189.113.43.90: icmp_seq=6 ttl=52 time=200.635 ms
    64 bytes from 189.113.43.90: icmp_seq=7 ttl=52 time=200.811 ms
     
    Kitties, May 10, 2011
    #7
  8. HonorCode

    HonorCode Head Administrator Staff Member

    Santiago, Chile
    Code:
    Microsoft Windows [Versi
     
    HonorCode, May 10, 2011
    #8
  9. L1teHawk

    L1teHawk Senior Member

    Pinging 189.113.43.90 with 32 bytes of data:

    Reply from 189.113.43.90: bytes=32 time=213ms TTL=51
    Reply from 189.113.43.90: bytes=32 time=213ms TTL=51
    Reply from 189.113.43.90: bytes=32 time=219ms TTL=51
    Reply from 189.113.43.90: bytes=32 time=249ms TTL=51

    Ping statistics for 189.113.43.90:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 213ms, Maximum = 249ms, Average = 223ms


    Looks fine to me :)
     
    L1teHawk, May 10, 2011
    #9
  10. Bonekeep

    Bonekeep Guest

    Pinging 189.113.43.90 with 32 bytes of data:
    Reply from 189.113.43.90: bytes=32 time=211ms TTL=48
    Reply from 189.113.43.90: bytes=32 time=222ms TTL=48
    Reply from 189.113.43.90: bytes=32 time=220ms TTL=48
    Reply from 189.113.43.90: bytes=32 time=247ms TTL=48

    From Southern California...
     
    Bonekeep, May 11, 2011
    #10