Forum Discussion

zenman's avatar
zenman
Freshman
5 years ago

Best way to test latency?

What is the best way to test my latency? Is the one on testmy.net a good, accurate one? It gives you locations to choose from for the test -- Miami, NY, Tokyo, google, amazon, etc. Which location shou...
Performance
  • maratsade's avatar
    maratsade
    5 years ago

    Yes, 600-700 is normal for satellite internet. 

     

    Keep in mind that websites add to the delay because they have so much stuff on them that needs to load, such as images or videos.  So on top of the normal server to server delay, you will have added delay from website content. 

zenman's avatar
zenman
Freshman
Ok, I discovered that for chromebook, the command is tracepath instead of tracert. That worked, and I got results, but I don't know how to read them, and I don't see any guidance on that link you provided about how to read the results. And what is the typical amount of latency for Hughes?
maratsade's avatar
maratsade
Distinguished Professor IV
5 years ago

Post a screenshot of your results, please.

 

Like I said before, the average latency for satellite internet is between 600-700 ms.  This may vary based on many factors. 

  • zenman's avatar
    zenman
    Freshman
    5 years ago
    Ughh, I can't figure out how to paste a screenshot here. I can copy a screenshot to clipboard and then paste (ctrl+v) it into a google doc no problem, but when I try to paste into this message window, nothing happens.
    • maratsade's avatar
      maratsade
      Distinguished Professor IV
      5 years ago
      • You will need to upload the screenshot. 
      • Once you take the screenshot, you need to save it to your Chromebook. 
      • Then you come back here, and start writing a response. To upload the image, click on the "photos" icon (see screenshot below), then follow the instructions to upload the image.

       

  • zenman's avatar
    zenman
    Freshman
    5 years ago
    I've tried everything I can think of to paste a screenshot here, and googled for solutions, and came up with nothing. What the hey is going on?
    • maratsade's avatar
      maratsade
      Distinguished Professor IV
      5 years ago

      Check my previous post. :)

  • zenman's avatar
    zenman
    Freshman
    5 years ago

    Finally realized I needed to use the insertion tool here instead of copy/pasting! What a dingdong I am, trying to focus on too many things at once. So here's those tracepath results. One for Netflix and one for Google.

    • maratsade's avatar
      maratsade
      Distinguished Professor IV
      5 years ago

      Are those the whole screenshots? They both look cut off at the bottom.  

    • GabeU's avatar
      GabeU
      Distinguished Professor IV
      5 years ago

      zenman 

       

      I think a firewall or something else may be blocking access for the tracepath.  Something's not right, as most of those "no reply" lines should instead be filled with IP addresses and latency results.  

       

      Do you have a separate firewall device or firewall program that you're using?  If so, it would be a good idea to disable it while running the tracepath, as it appears that something is blocking its ability to test anything outside of your own network. 

       

      I'm not at all familiar with Chromebooks, nor their OS, so I have no idea what else to try.  :(

      • maratsade's avatar
        maratsade
        Distinguished Professor IV
        5 years ago

        I wonder if the "no reply" is similar to the *** of the Windows traceroute.  I'd test this but my Chromebook is many miles away and I won't see it until 1/13.

         

        EDIT:

         

        See, like this:

         

        1: 192.168.0.14 0.131ms pmtu 1500
        1: no reply
        2: dynamic-76-73-172-97.knology.net 119.110ms
        3: 76-73-168-104.knology.net 97.118ms
        4: xe-9-3-0.bar1.Cleveland1.Level3.net 102.568ms asymm 5
        5: no reply
        6: no reply
        7: ae-104-3504.edge1.Washington12.Level3.net 135.317ms
        8: att-level3-te.washingtondc12.Level3.net 102.696ms
        9: cr1.wswdc.ip.att.net 101.485ms asymm 20
        10: cr2.rlgnc.ip.att.net 102.262ms asymm 19
        11: cr1.rlgnc.ip.att.net 193.578ms asymm 18
        12: cr82.chlnc.ip.att.net 102.323ms asymm 17
        13: 12.123.138.157 178.434ms asymm 16
        14: 12.125.220.30 107.549ms asymm 17

         

         

         

        GabeU wrote:

         

        I think a firewall or something else may be blocking access for the tracepath.  Something's not right, as most of those "no reply" lines should instead be filled with IP addresses and latency results.  

         

        Do you have a separate firewall device or firewall program that you're using?  If so, it would be a good idea to disable it while running the tracepath, as it appears that something is blocking its ability to test anything outside of your own network. 

         

        I'm not at all familiar with Chromebooks, nor their OS, so I have no idea what else to try.  :(