Author Topic: Lag? Traceroute reporting.  (Read 6827 times)

MisanOne

  • Moderator
  • Hero Member
  • *****
  • Posts: 1507
    • View Profile
Lag? Traceroute reporting.
« on: September 04, 2013, 02:30:53 pm »
In an effort to accurately determine why some of our customers may be experiencing lag I request those experiencing lag to submit a traceroute.
Submitting this data will help us pinpoint why you may be lagging and if we can do anything to remedy the issue.

Please post only the results of your trace route while you are experiencing lag
Data gained during any other period of time will be of no help in pinpointing potential lag sources.

Using my traceroute below as an example. Open command prompt and type  tracert aika.t3fun.com
Copy and paste the results as shown below.


C:\Windows\system32>tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.4.42] over a maximum of 30 hops:

  1    38 ms    27 ms    29 ms  c-69-245-96-1.hsd1.mi.comcast.net [69.245.96.1]
  2    12 ms    17 ms    13 ms  te-5-1-ur02.southfield.mi.michigan.comcast.net [68.86.121.125]
  3    15 ms    31 ms    15 ms  te-0-11-0-4-ar01.pontiac.mi.michigan.comcast.net [69.139.254.97]
  4    39 ms    23 ms    23 ms  he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.90.221]
  5    21 ms    21 ms    21 ms  he-0-10-0-1-pe04.350ecermak.il.ibone.comcast.net [68.86.83.54]
  6    21 ms    20 ms    35 ms  chp-edge-01.inet.qwest.net [216.207.8.189]
  7     *        *        *     Request timed out.
  8    37 ms    35 ms    35 ms  67.133.224.206
  9    51 ms    37 ms    37 ms  205.251.245.29
 10    37 ms    37 ms    36 ms  205.251.245.121  http://whois.arin.net/rest/net/NET-205-251-192-0-1
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    38 ms    36 ms    37 ms  ec2-54-208-4-42.compute-1.amazonaws.com [54.208.4.42]
Trace complete.


I will in the future give a more in depth description as to what the value behind these results are. It would take quite a bit to explain everything about a traceroute but I will try to condense it into something short and easily understandable.

For now whats most relevant are the latency times (the set of 3 numbers on each hop).


MisanOne
Lead Moderator, AikaNA
« Last Edit: September 05, 2013, 03:31:13 pm by MisanOne »
MisanOne - Lead Moderator, AikaNA

iSweft

  • Guest
Re: Lag? Traceroute results.
« Reply #1 on: September 04, 2013, 03:46:54 pm »
I was playing from Malaysia and my lag/skill delay was OP expecially in relic war when it participated by 1 raid+ per nation. Sometimes I only can stun other player after 2-3 sec i press the key. I believe it is not my connection problem because I play other onlines too, and didnt face any lag as bad as AikaNa. Below is my tracert result, while I was autohunting in soul dump(autohunting with lag, sometimes will come notification "u are using speed hack or having other problem"). I really hope i can play this game without such bad lag/delay.  :-\

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\User>tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.8.129]
over a maximum of 30 hops:

  1     6 ms     5 ms     9 ms  192.168.1.1
  2    32 ms    32 ms    32 ms  175.137.109.222
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.



LotusNine

  • Hero Member
  • *****
  • Posts: 3173
  • WoopWoop!
    • View Profile
Re: Lag? Traceroute reporting.
« Reply #2 on: September 04, 2013, 05:49:12 pm »
I just timed out 30 times... dont get it...

Ayiana

  • Full Member
  • ***
  • Posts: 119
    • View Profile
Re: Lag? Traceroute reporting.
« Reply #3 on: September 04, 2013, 06:41:11 pm »
this isn't a solution...  to my lag. i lag and Dc by the time this barely finished first line ...
so this was made while i was just in game  running around , which this last 3 days gets me dc constantly... awesome isn't it?


C:\Users\user>tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.4.42]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   120 ms   120 ms   119 ms  ec2-54-208-4-42.compute-1.amazonaws.com [54.208.
4.42]

Trace complete.


We need a real solution

rogerrabbit

  • Guest
Re: Lag? Traceroute reporting.
« Reply #4 on: September 05, 2013, 03:04:52 pm »
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\rick>tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.8.129]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     7 ms    16 ms     7 ms  nott-core-2a-ae7-3651.network.virginmedia.net [8
0.7.83.29]
  3     9 ms    11 ms    12 ms  leed-bb-1c-ae4-0.network.virginmedia.net [62.253
.174.61]
  4     9 ms     9 ms    11 ms  leed-bb-1b-ae10-0.network.virginmedia.net [62.25
3.174.25]
  5     *        *        *     Request timed out.
  6    16 ms    46 ms    15 ms  tele-ic-4-ae0-0.network.virginmedia.net [62.253.
174.18]
  7    93 ms    92 ms    93 ms  equinix03-iad2.amazon.com [206.126.237.68]
  8    91 ms    90 ms    91 ms  205.251.245.11
  9    92 ms    95 ms    92 ms  205.251.245.47
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    91 ms    91 ms    92 ms  ec2-54-208-8-129.compute-1.amazonaws.com [54.208
.8.129]

Trace complete.

LotusNine

  • Hero Member
  • *****
  • Posts: 3173
  • WoopWoop!
    • View Profile
Re: Lag? Traceroute reporting.
« Reply #5 on: September 06, 2013, 01:12:19 am »
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.8.129]
over a maximum of 30 hops:

  1    25 ms     2 ms     2 ms  192.168.1.1
  2    12 ms    12 ms    12 ms  73.98.180.1
  3    14 ms    13 ms    13 ms  te-0-2-0-5-ur07.burien.wa.seattle.comcast.net [6
8.87.206.1]
  4    11 ms    12 ms    11 ms  ae-21-0-ar03.burien.wa.seattle.comcast.net [69.1
39.164.137]
  5    14 ms    12 ms    12 ms  ae-2-0-ar03.seattle.wa.seattle.comcast.net [68.8
6.177.146]
  6    14 ms    14 ms    15 ms  he-1-6-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.94.69]
  7    14 ms    14 ms    13 ms  be-16-pe03.seattle.wa.ibone.comcast.net [68.86.8
3.10]
  8    21 ms    19 ms    19 ms  sea-edge-13.inet.qwest.net [67.135.42.153]
  9     *        *        *     Request timed out.
 10    97 ms    93 ms    94 ms  72.165.86.74
 11    99 ms    98 ms    99 ms  205.251.245.21
 12    95 ms   121 ms   103 ms  205.251.245.121
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16    99 ms    99 ms    98 ms  ec2-54-208-8-129.compute-1.amazonaws.com [54.208
.8.129]

Trace complete.

looks about acurate... Would this be effecting issues like LAGSKIP? i assumed that was a hardware issue

Skipalicious

  • Moderator
  • Hero Member
  • *****
  • Posts: 2163
  • Your stalker!
    • View Profile
Re: Lag? Traceroute reporting.
« Reply #6 on: September 06, 2013, 02:02:21 am »
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\ChibiJin>tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.4.42]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.1.1
  2    14 ms    14 ms    15 ms  175.137.109.238
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.


I AM IN THE FUTURE! 12 Hours ahead of you!  MY TIME : GMT+8
IGN     :
1) Skipalicious - Nationless
2) Skipal1cious - Vanov

MisanOne

  • Moderator
  • Hero Member
  • *****
  • Posts: 1507
    • View Profile
Re: Lag? Traceroute reporting.
« Reply #7 on: September 06, 2013, 03:06:48 pm »
Each hop is a router your data passes through on its way to its destination. The traceroute pgm throws out 3 packets to each hop and waits for them to return. Any latency over 150ms would cause noticeable lag.

Request timed out returns can mean a few things. Most commonly it is received because the router its requesting info from is set up to ignore icmp requests.

The 1st hop is many times your own router/modem.
2nd hop is the first router you encounter on your own ISP.
From there on it can vary.
MisanOne - Lead Moderator, AikaNA

vulcan421

  • Guest
Re: Lag? Traceroute reporting.
« Reply #8 on: September 06, 2013, 04:46:23 pm »
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\aarons> tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.8.129]
over a maximum of 30 hops:

  1    13 ms    10 ms    11 ms  10.106.208.1
  2    12 ms    12 ms    22 ms  192.168.38.65
  3    74 ms    59 ms    20 ms  192.168.102.22
  4   131 ms     *       88 ms  te-3-2.car1.KansasCity1.Level3.net [4.53.32.93]

  5    72 ms    74 ms    58 ms  ae-5-5.ebr2.Dallas1.Level3.net [4.69.135.230]
  6    60 ms    59 ms    66 ms  ae-82-82.csw3.Dallas1.Level3.net [4.69.151.153]

  7    80 ms    61 ms    58 ms  ae-83-83.ebr3.Dallas1.Level3.net [4.69.151.158]

  8    60 ms    58 ms    62 ms  ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
  9    60 ms    64 ms    89 ms  ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

 10    60 ms    60 ms    57 ms  ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
 11    91 ms    61 ms    58 ms  ae-1-60.edge1.Washington1.Level3.net [4.69.149.1
3]
 12    60 ms    83 ms    58 ms  AMAZON.COM.edge1.Washington1.Level3.net [4.28.12
5.110]
 13    63 ms    75 ms    67 ms  205.251.245.25
 14    92 ms    68 ms    60 ms  205.251.245.121
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18    59 ms    61 ms    60 ms  ec2-54-208-8-129.compute-1.amazonaws.com [54.208
.8.129]

Trace complete.

ChuChuCute

  • Guest
Re: Lag? Traceroute reporting.
« Reply #9 on: October 11, 2013, 01:48:26 pm »
Tracing route to aika.t3fun.com [54.208.8.129]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2   132 ms    87 ms    61 ms  10.223.7.174
  3     *      884 ms    69 ms  10.223.28.117
  4   168 ms   159 ms   161 ms  172.27.254.1
  5   150 ms   159 ms   159 ms  203.82.73.6
  6     *        *     1621 ms  203.82.73.233
  7   775 ms   139 ms   139 ms  203.82.74.178
  8    78 ms    79 ms   151 ms  1.9.244.45
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11   386 ms   389 ms   399 ms  205.251.245.7
 12   398 ms   390 ms   399 ms  205.251.245.123
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16  2037 ms   679 ms  1074 ms  ec2-54-208-8-129.compute-1.amazonaws.com [54.208
.8.129]

Trace complete.


THis is mine , im a player in malaysia, when farming also sometimes came out saying i using speed hack or experiencing problem

EnjoyDownSyndrome

  • Guest
Re: Lag? Traceroute reporting.
« Reply #10 on: December 07, 2013, 04:00:10 am »
may not be the perfect solution for everyone, but it worked for me while I was searching for a better lag latency fix with mine.
- BACK UP BACK UP BACK UP BACK UP BACK UP BACK UP " regedit " make a copy before editing any settings, CREATE CREATE CREATE CREATE CREATE a restore point as plan B.

Run as Admin - " regedit "

- expand [HKEY_LOCAL_MACHINE]
- expand [CurrentControlSet]
- expand [services]
- expand [Tcpip]
- expand [Parameters]
- expand [Interfaces] * this section may contain 3 to 4 folders, look for the folder that contains this string "DhcpIPAddress" the value should be the IP of your machine, confirm it http://www.ipcow.com/ to make sure and once done, inside the same folder that contains your DchpIPAddress,
- create [DWORD] * doesn't matter if you are using 32/64 bit, name the new string "TcpAckFrequency" its [case sensitive] and set its value [Hexadecimal] to 1.

- Under the same folder tree [HKEY_LOCAL_MACHINE] scroll up,

- expand [SOFTWARE]
- expand [Microsoft] * if you don't have [MSMQ] skip this part, for others who do have this folder *
- expand [MSMQ] * if there is no way to expand this folder because it does not contain any other [Key] then create one by right clicking it [New] > [Key] it should create a new folder or key inside it, name the folder [Parameters] *
- create [DWORD] name it " TCPNoDelay " again its [case sensitive] set value [Hexadecimal] to 1.

- Restart

http://en.wikipedia.org/wiki/Nagle's_algorithm

- my trace ( had to erase 2 sections on both screenshots, security purpose ) but I can honestly say with the minor tweak I detailed above, it did resolved some minor packet loss.

« Last Edit: March 26, 2014, 01:22:35 am by xCiaoXIII »

MisanOne

  • Moderator
  • Hero Member
  • *****
  • Posts: 1507
    • View Profile
Re: Lag? Traceroute reporting.
« Reply #11 on: March 01, 2014, 02:14:03 am »
Yes, disabling nagle will show some slight improvement for online gaming and i've done this on every computer i've owned (it can in certain instances increase latency for other activities such as web browsing but i've found the increase to be almost imperceptible). Other methods ones can research are disabling QoS, unparking cpus, router optimization and tcp optimization. Each mod when used alone can achieve minimal gains depending on how your system is configured. I've done them all and I can say i rarely suffer for large latency issues.

I will say that if one is unfamiliar with modifying registry values they should probably skip attempting to do so without assistance. Either way as xCiaoXIII mentioned make a back up copy of your registry.
MisanOne - Lead Moderator, AikaNA

ProSeller

  • Guest
Re: Lag? Traceroute reporting.
« Reply #12 on: March 25, 2014, 08:17:31 am »
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Admin>tracert aika.t3fun.com

Tracing route to aika.t3fun.com [54.208.8.129]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    26 ms    28 ms    29 ms  dsl.49.145.128.1.pldt.net [49.145.128.1]
  3    28 ms    27 ms    28 ms  122.2.159.29.static.pldt.net [122.2.159.29]
  4    40 ms    29 ms    29 ms  210.213.131.66.static.pldt.net [210.213.131.66]

  5    26 ms    26 ms    87 ms  210.213.131.89.static.pldt.net [210.213.131.89]

  6   205 ms   206 ms   206 ms  129.250.197.1
  7     *      252 ms   255 ms  ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.1
19]
  8   218 ms   213 ms   214 ms  129.250.5.56
  9   273 ms   252 ms   272 ms  ae-5.r21.dllstx09.us.bb.gin.ntt.net [129.250.4.2
4]
 10   253 ms     *        *     ae-2.r08.dllstx09.us.bb.gin.ntt.net [129.250.3.8
1]
 11     *        *        *     Request timed out.
 12   280 ms   311 ms   276 ms  54.240.229.104
 13   313 ms   315 ms   314 ms  54.240.229.20
 14   314 ms   313 ms   314 ms  54.240.229.174
 15     *        *        *     Request timed out.
 16   313 ms   289 ms   291 ms  72.21.220.8
 17     *        *      276 ms  205.251.245.31
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *      301 ms     *     ec2-54-208-8-129.compute-1.amazonaws.com [54.208
.8.129]
 23   273 ms   300 ms   294 ms  ec2-54-208-8-129.compute-1.amazonaws.com [54.208
.8.129]

Trace complete.

C:\Documents and Settings\Admin>

Tricks08

  • Guest
Re: Lag? Traceroute reporting.
« Reply #13 on: March 26, 2014, 12:43:20 am »
I played aika for about 6 months now and i never had any issue about lags and delay in game. My lag and delays started since monday and i noticed that many PH players are also experiencing this issue. Please find a way to fix it GMs. Ty :)


Tracing route to aika.t3fun.com [54.208.8.129]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    19 ms    20 ms    20 ms  112.208.96.1.pldt.net [112.208.96.1]
  3    20 ms    20 ms    20 ms  119.93.255.197
  4    20 ms    19 ms    20 ms  210.213.131.66.static.pldt.net [210.213.131.66]

  5    19 ms    18 ms    18 ms  210.213.131.89.static.pldt.net [210.213.131.89]

  6   194 ms   194 ms   196 ms  129.250.197.1
  7   241 ms   237 ms   239 ms  ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.1
19]
  8   202 ms   200 ms   200 ms  ae-8.r21.snjsca04.us.bb.gin.ntt.net [129.250.5.5
6]
  9   241 ms   243 ms   250 ms  ae-5.r21.dllstx09.us.bb.gin.ntt.net [129.250.4.2
4]
 10   241 ms   242 ms   242 ms  ae-2.r08.dllstx09.us.bb.gin.ntt.net [129.250.3.8
1]
 11     *        *        *     Request timed out.
 12   274 ms   275 ms   268 ms  54.240.229.94
 13   273 ms     *      279 ms  54.240.228.254
 14   272 ms   280 ms     *     54.240.229.160
 15     *        *        *     Request timed out.
 16   278 ms   278 ms   282 ms  72.21.220.18
 17     *      274 ms     *     205.251.245.3
 18   264 ms   261 ms   264 ms  205.251.245.47
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22   269 ms   267 ms   266 ms  ec2-54-208-8-129.compute-1.amazonaws.com [54.208
.8.129]

Trace complete.

C:\Users\eeeeeeeeeee>
« Last Edit: March 26, 2014, 12:50:38 am by Tricks08 »

Daddy

  • Jr. Member
  • **
  • Posts: 54
    • View Profile
Re: Lag? Traceroute reporting.
« Reply #14 on: April 08, 2014, 12:24:25 pm »
Here's mine:

Tracing route to aika.t3fun.com [54.208.4.42]
over a maximum of 30 hops:

  1     4 ms     5 ms     4 ms  192.168.1.1
  2    25 ms    21 ms    26 ms  83.244.94.174
  3    21 ms    20 ms    19 ms  10.1.2.1
  4    21 ms    87 ms    36 ms  83.244.54.21
  5    21 ms    23 ms    21 ms  82.213.5.126
  6    81 ms    73 ms    79 ms  195.16.161.53
  7   172 ms   179 ms     *     vlan70.csw2.Frankfurt1.Level3.net [4.69.154.126]

  8   164 ms   192 ms   165 ms  ae-71-71.ebr1.Frankfurt1.Level3.net [4.69.140.5]

  9   173 ms   170 ms   186 ms  ae-46-46.ebr2.Paris1.Level3.net [4.69.143.138]
 10   169 ms   160 ms   167 ms  ae-42-42.ebr2.Washington1.Level3.net [4.69.137.5
4]
 11   200 ms   175 ms   163 ms  ae-92-92.csw4.Washington1.Level3.net [4.69.134.1
58]
 12   160 ms   168 ms   163 ms  ae-4-90.edge1.Washington1.Level3.net [4.69.149.2
05]
 13   167 ms   173 ms   185 ms  AMAZON.COM.edge1.Washington1.Level3.net [4.28.12
5.110]
 14   169 ms   168 ms   184 ms  205.251.245.25
 15   171 ms   172 ms   171 ms  205.251.245.121
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19   170 ms   175 ms   167 ms  ec2-54-208-4-42.compute-1.amazonaws.com [54.208.
4.42]

Trace complete.