1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Greetings Guest!!

    In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.

    Dismiss Notice

high ping and packet loss

Discussion in 'UO Resources' started by Varrius, Dec 22, 2010.

  1. Varrius

    Varrius Sage
    Stratics Veteran

    Joined:
    Feb 12, 2010
    Messages:
    610
    Likes Received:
    67
    Normally I ping around 50 to Atlantic, today it's 137 with a 25-50% packet loss. I ran a tracer and this is what came up, but I have no idea what exactly it means. Anyone have an idea?

    [​IMG]
     
  2. Farsight

    Farsight Crazed Zealot
    Stratics Veteran

    Joined:
    May 12, 2008
    Messages:
    3,191
    Likes Received:
    36
    Step 1. This is you. You should edit the picture to get rid of step one.

    Steps 2-8: These are routers, ISP's or whatever in the area you live in. The difference between any of these two hops should be small. Less than 10 ms per hop can be expected. More than 50ms per hop can be a "suspect" if you have lag.

    Steps 9-13: These are the UO server's local routers, ISP's, etc. The thing to note here is the "Level3" which has been known at times in the past to cause packet loss/lag issues. And other times, it runs like a charm. Again, expect low ping differences between each step. If you were European (like me), the difference between local to me and local to the server can be quite large (over 100 ms at bad times for me).

    Step 14: This is your problem. You can tell because the size of the hop is 90ms, which is not what you want from a gaming server. Note the ea.com name in the server/router "name". This means that the problem is either at whatever is at IP address #13 or IP address #14. It's not likely that us-as-customers can narrow it down any further, but it is enough to send to EA to say "You need to look into this!"

    You do need to be careful in tracing routes, as sometimes there's a step which looks bad, but actually isn't. Having a good benchmark is highly recommended (so you can say "this is the good one, that is what I have now").