Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Ping Testing ISPs (Help a gamer out #2)

Options
  • 06-11-2021 2:14pm
    #1
    Registered Users Posts: 33


    Hi Folks,

    I'm back again and looking for a new IPS for routing to the US. Pure telecom has had awful routing for the last few months and wondering if there is a better ISP currently while my contract is about to be up.

    I play competitive tournaments for Midair Community Edition (check it out https://midair.gg/) -which most of the matches are played on a New York server and currently pinging around 120ms again ( i use to ping 80ms)

    If people could ping test the New York gaming server: 45.56.99.226 by running the windows cmd and enter ping 45.56.99.226 and posting the average ms of the ping, I'd be very grateful.

    Any help or advice would be appreciated.



Comments

  • Moderators, Science, Health & Environment Moderators Posts: 16,878 Mod ✭✭✭✭Gonzo


    Eir FTTH, pings not too bad considering it's east coast United States

    Pinging 45.56.99.226 with 32 bytes of data:

    Reply from 45.56.99.226: bytes=32 time=80ms TTL=50

    Reply from 45.56.99.226: bytes=32 time=79ms TTL=50

    Reply from 45.56.99.226: bytes=32 time=79ms TTL=50

    Reply from 45.56.99.226: bytes=32 time=79ms TTL=50


    Ping statistics for 45.56.99.226:

      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

      Minimum = 79ms, Maximum = 80ms, Average = 79ms



  • Registered Users Posts: 1,097 ✭✭✭dam099


    Vodafone SIRO FTTH

    Pinging 45.56.99.226 with 32 bytes of data:

    Reply from 45.56.99.226: bytes=32 time=81ms TTL=54

    Reply from 45.56.99.226: bytes=32 time=82ms TTL=54

    Reply from 45.56.99.226: bytes=32 time=83ms TTL=54

    Reply from 45.56.99.226: bytes=32 time=81ms TTL=54


    Ping statistics for 45.56.99.226:

      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

      Minimum = 81ms, Maximum = 83ms, Average = 81ms



  • Registered Users Posts: 33 t1Ringo


    Thanks Gonzo,

    some difference compared to my pure

    Reply from 64.225.63.89: bytes=32 time=115ms TTL=48

    Reply from 64.225.63.89: bytes=32 time=115ms TTL=48

    Reply from 64.225.63.89: bytes=32 time=114ms TTL=48

    Reply from 64.225.63.89: bytes=32 time=114ms TTL=48


    Keep them coming folks



  • Registered Users Posts: 36,167 ✭✭✭✭ED E


    VM-IE seem to send all their traffic to the continent before bouncing back to hit US-East regions. Similarly crap.


    You can probably rent a VPS in DUB that has decent transit to the US and run a VPN that way. Thus you wouldnt need to ISP hop.



  • Registered Users Posts: 75 ✭✭johndanielmoore


    Virgin Media

    As ED E said crap

    Pinging 45.55.99.226 with 32 bytes of data:

    Reply from 45.55.99.226: bytes=32 time=125ms TTL=50

    Reply from 45.55.99.226: bytes=32 time=149ms TTL=50

    Reply from 45.55.99.226: bytes=32 time=117ms TTL=50

    Reply from 45.55.99.226: bytes=32 time=104ms TTL=50


    Ping statistics for 45.55.99.226:

      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

      Minimum = 104ms, Maximum = 149ms, Average = 123ms



  • Advertisement
  • Registered Users Posts: 5,617 ✭✭✭CalamariFritti


    digiweb 100mbits fttc dsl

    PING 45.56.99.226 (45.56.99.226): 56 data bytes

    64 bytes from 45.56.99.226: icmp_seq=0 ttl=55 time=89.957 ms

    64 bytes from 45.56.99.226: icmp_seq=1 ttl=55 time=90.560 ms

    64 bytes from 45.56.99.226: icmp_seq=2 ttl=55 time=89.933 ms

    64 bytes from 45.56.99.226: icmp_seq=3 ttl=55 time=93.788 ms

    64 bytes from 45.56.99.226: icmp_seq=4 ttl=55 time=89.567 ms

    64 bytes from 45.56.99.226: icmp_seq=5 ttl=55 time=88.417 ms

    64 bytes from 45.56.99.226: icmp_seq=6 ttl=55 time=91.099 ms

    64 bytes from 45.56.99.226: icmp_seq=7 ttl=55 time=91.961 ms

    --- 45.56.99.226 ping statistics ---

    8 packets transmitted, 8 packets received, 0.0% packet loss

    round-trip min/avg/max/stddev = 88.417/90.660/93.788/1.538 ms



  • Registered Users Posts: 4,125 ✭✭✭smuggler.ie


    Three mobile

    Pinging 45.56.99.226 with 32 bytes of data:

    Reply from 45.56.99.226: bytes=32 time=127ms TTL=49

    Reply from 45.56.99.226: bytes=32 time=122ms TTL=49

    Reply from 45.56.99.226: bytes=32 time=130ms TTL=49

    Reply from 45.56.99.226: bytes=32 time=124ms TTL=49


    Ping statistics for 45.56.99.226:

       Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

    Approximate round trip times in milli-seconds:

       Minimum = 122ms, Maximum = 130ms, Average = 125ms



  • Registered Users Posts: 1,477 ✭✭✭KildareP


    Digiweb VDSL residential connection is 90-91ms

    For comparison, on a corporate fibre line from them (through their parent Viatel) it is a steady 78ms



  • Registered Users Posts: 484 ✭✭Adriatic


    Net1 (fixed wireless)

    Pinging 45.56.99.226 with 32 bytes of data:

    Reply from 45.56.99.226: bytes=32 time=84ms TTL=46

    Reply from 45.56.99.226: bytes=32 time=101ms TTL=46

    Reply from 45.56.99.226: bytes=32 time=90ms TTL=46

    Reply from 45.56.99.226: bytes=32 time=86ms TTL=46


    Ping statistics for 45.56.99.226:

       Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

       Minimum = 84ms, Maximum = 101ms, Average = 90ms



  • Registered Users Posts: 33 t1Ringo


    Cheers folks, looks like I'll be switching to vodaphone as it has nice ping and price plan.

    Thanks again 😁



  • Advertisement
Advertisement