How to trace route IdleServer.Com

Discussion in 'Reports' started by wing, Aug 23, 2013.

  1. wing
    Dreaming

    wing Administrator Staff Member Owner

    This link explains in detail: http://support.microsoft.com/kb/314868

    You need to run CMD in windows. Go to start run and type cmd or on windows 8 just press start button type cmd and press enter.

    inside cmd type
    Code:
    tracert  192.227.249.131
    This will take a couple seconds to trace out the path from You to the Server

    Right click "Select all" then press Ctrl-C to copy. You now have the information you can paste into email or forum report.

    If you are having latency issues this information will allow us to tell if it is something we can work to fix or if it is your connection.

    We are always glad to help you can email Support@idleserver.com for any support related concerns.
     
  2. wing
    Dreaming

    wing Administrator Staff Member Owner

    Here is my example. It takes me 76ms under best circumstances to reach server. You can run this muliple times and see if the results vary

    Code:
    C:\Windows\system32>tracert 192.227.249.130
    
    Tracing route to 216.218.226.50 over a maximum of 30 hops
      1    1 ms    1 ms    <1 ms  192.168.1.254
      2  100 ms    25 ms    24 ms  xxx-xxx-xxx-x.lightspeed.okcbok.sbcglobal.net [xxx.xxx.xxx.x]
      3    *        *        *    Request timed out.
      4    24 ms    22 ms    23 ms  12.83.42.9
      5    28 ms    27 ms    28 ms  dlstx02jt.ip.att.net [12.122.214.245]
      6    43 ms    43 ms    32 ms  192.205.37.50
      7    63 ms    63 ms    63 ms  las-bb1-link.telia.net [213.155.134.124]
      8    64 ms    68 ms    78 ms  hurricane-ic-138362-las-bb1.c.telia.net [213.248
    .67.142]
      9    85 ms    75 ms    76 ms  100gigabitethernet15-1.core1.sjc2.he.net [184.10
    5.223.249]
    10    76 ms    77 ms    86 ms  10gigabitethernet3-2.core3.fmt2.he.net [184.105.
    222.13]
    11    82 ms    76 ms    76 ms  216.218.226.50
    Trace complete.
    Trace route explained:
    1. It took me 25ms to get out of my house and down the street to At&t
    2. 28ms I was down at At&t in Dallas which offloaded me onto telia.net
    3. From 32ms-64ms is At&t bullshitting getting us over to telia.net which somehow routes thru Europe.. What ever the case we reach HE arriving on 100gig port
    4. 75ms HE took me in on their 100gig into datacenter in Fremont, California
    5. 76ms HE multiplexed us down onto 10gb port inside datacenter
    6. We arrive off the 10gig switch to our 1gig port in 76ms
    I know its weird the route they took but look it's only 76ms and I'm in Fremont, California passing packets 1357 miles away.
     
Live Thread addon by sonnb

Share This Page