Lag report

Posted on by

Guys if you have lag, please do the following:

Open a command prompt (in windows, click start, then enter “cmd” in the text box above) and type “tracert uncovery.net”, make a screenshot of the results and send it to me (minecraft@uncovery.net).  It should look like the one above.

9 thoughts on “Lag report”

  2. Sorry, I cant send one. My comp. says “tracert” is not a recognizalbe command….

  3. Done on 2011.03.25 @ 10:02 +0900

    Tracing route to uncovery.net [184.168.67.13]
    over a maximum of 30 hops:

    1 4 ms 2 ms 1 ms 192.168.1.1
    2 * * * Request timed out.
    3 11 ms 10 ms 17 ms 217-140-165-209.static.gci.net [209.165.140.217]
    4 52 ms 68 ms 47 ms 2-251-223-66.gci.net [66.223.251.2]
    5 59 ms 65 ms 74 ms 200-128-165-209.gci.net [209.165.128.200]
    6 50 ms 48 ms 48 ms 52-129-165-209.gci.net [209.165.129.52]
    7 75 ms 61 ms 49 ms 217-129-165-209.gci.net [209.165.129.217]
    8 53 ms 52 ms 57 ms sl-gw12-sea-4-3-0.sprintlink.net [144.224.113.85]
    9 70 ms 55 ms 108 ms sea-brdr-01.inet.qwest.net [63.146.26.197]
    10 95 ms 87 ms 98 ms phn-core-01.inet.qwest.net [67.14.19.38]
    11 87 ms 88 ms 84 ms phn-edge-06.inet.qwest.net [205.171.12.142]
    12 92 ms 83 ms 87 ms 63-234-235-102.dia.static.qwest.net [63.234.235.102]
    13 * * * Request timed out.
    14 115 ms 87 ms 109 ms ip-208-109-113-161.ip.secureserver.net [208.109.113.161]
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * 157 ms * ip-208-109-113-146.ip.secureserver.net [208.109.113.146]
    18 123 ms * * ip-184-168-67-13.ip.secureserver.net [184.168.67.13]
    19 * * 150 ms ip-184-168-67-13.ip.secureserver.net [184.168.67.13]

    Trace complete.

  4. @Ontopic Ill do so when I have lagg.

    @Offtopic Why are you paying so many attention to lagg? The only person who I know that has lagg, is you :/

    – I never had server-side lagg for quite a LONG time –

Comments are closed.