Ask a question
Search in Internet Forums

Internet Forum

Reply
Posted Mar 8, 2013
7:25:22 PM
View profile
Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

Hi, i'm an online gamer that has purchased at&t uverse. I have a 6meg connection that at certain times is very laggy. I talked to one of the server owners and he suggested I run a tracert from my cmd prompt to his server to check for lag. He mentioned it was client side and I should ask my isp for help so here's the tracerts, times and any advice how to stabilize this would be appreciated. ip is 192. 168.1.254

 

[1st tracert @3:25pm central]

 

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

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [] over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  dsldevice.att.net []

  2    18 ms    12 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglobal.net [108.213.44.3]  

  3    20 ms    12 ms     *     71.144.225.38

  4     *        *        *     Request timed out.  

  5     *        *        *     Request timed out.  

  6    15 ms    13 ms    11 ms  12.83.40.5  

  7    32 ms    45 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]  

  8    33 ms    32 ms    33 ms  144.232.7.41  

  9    35 ms    35 ms    35 ms  144.232.11.181  

 10    43 ms    42 ms    42 ms  144.232.11.224  

 11    42 ms    42 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [144.232.4.44 ]  

 12    48 ms    47 ms    47 ms  144.232.5.209  

 13    48 ms    48 ms    48 ms  144.232.10.44  

 14    49 ms    48 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [144.232.19.228]  

 15    53 ms    49 ms    48 ms  sl-nlaye-428976-0.sprintlink.net [144.228.205.94]  

 16    48 ms    48 ms    48 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31.31.181]  

  17    99 ms    48 ms    48 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlayer.net [69.31.30.21]  

  18    59 ms    74 ms    49 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.119.69]  

  19    48 ms    48 ms    48 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.4 3.122]  

  20    48 ms    48 ms    48 ms  ash.xfactorservers.com [75.102.41.52]

 

[2nd tracert @ 3:27pm central]

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    12 ms    14 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglobal.net [108.213.44.3]  

3     *        *        *     Request timed out.  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    14 ms    11 ms    12 ms  12.83.40.5  

7    31 ms    33 ms    31 ms  dlstx02jt.ip.att.net [12.122.214.249]  

8    33 ms    32 ms    33 ms  144.232.7.41  

9    36 ms    35 ms    35 ms  144.232.11.181  

10    42 ms    42 ms    42 ms  144.232.11.224  

11    42 ms    42 ms    41 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [144.232.4.44]  

12    47 ms    47 ms    47 ms  144.232.5.209  

13    49 ms    48 ms    48 ms  144.232.10.44  

14    49 ms    49 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [144.232.19.2 28]  

15    51 ms    49 ms    49 ms  sl-nlaye-428976-0.sprintlink.net [144.228.205.94 ]  

16    47 ms    48 ms    47 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31.31.181]  

17    48 ms    48 ms    47 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlayer.net [69.31.30.21]

 18    48 ms    48 ms    48 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.119.69]  

19    48 ms    48 ms    48 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.43.122]

 20    48 ms    48 ms    48 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

[3rd tracert 3:30pm central]

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    15 ms    12 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglobal.net [18.213.44.3]  

3    14 ms    31 ms    12 ms  71.144.225.38  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    12 ms    15 ms    11 ms  12.83.40.5  

7    31 ms    31 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]  

8    32 ms    33 ms    32 ms  144.232.7.41  

9    35 ms    35 ms    36 ms  144.232.11.181  

10    43 ms    42 ms    43 ms  144.232.11.224  

11    42 ms    42 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [144.232.4.4]

 12    47 ms    47 ms    47 ms  144.232.5.209  

13    48 ms    48 ms    48 ms  144.232.10.44

 14    49 ms    48 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [144.232.19.228]  

15    50 ms    56 ms    52 ms  sl-nlaye-428976-0.sprintlink.net [144.228.205.9]  

16    48 ms    48 ms    48 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31.31.181]

 17    97 ms    48 ms    48 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlayer.net [69.31.30.21]  

18    57 ms    47 ms    48 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.119.69]  

19    48 ms    48 ms    48 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.4 3.122]  

20    48 ms    48 ms    48 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

Now my connection goes to poop at 5pm central to 11pm and these are just a few tracerts from around 8:30 pm central time..

 

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

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [75.102.41.52] over a maximum of 30 hops:

  1     1 ms     1 ms     4 ms  dsldevice.att.net []  

2    12 ms    11 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglo8.213.44.3]  

3    14 ms    12 ms     *     71.144.225.38  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    13 ms    11 ms    15 ms  12.83.40.5  

7    32 ms    32 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]

  8    33 ms    32 ms    32 ms  144.232.7.41  

9    36 ms    35 ms    35 ms  144.232.11.181  

10    43 ms    43 ms    43 ms  144.232.11.224  

11    41 ms    42 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [1]  

12    48 ms    47 ms    47 ms  144.232.5.209

 13    49 ms    48 ms    48 ms  144.232.10.44  

14    49 ms    48 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [128]

 15    79 ms    78 ms    74 ms  sl-nlaye-428976-0.sprintlink.net [144]  

16    59 ms    60 ms    59 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31  

17    68 ms    70 ms    69 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlay31.30.21]

 18    79 ms    81 ms    82 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.

 19    82 ms    81 ms    82 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.ne3.122]  

20    81 ms    65 ms    63 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [75.102.41.52] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    13 ms    11 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglo8.213.44.3]  

3    12 ms    12 ms     *     71.144.225.38  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    14 ms    17 ms    13 ms  12.83.40.5  

7    32 ms    31 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]  

8    33 ms    32 ms    33 ms  144.232.7.41  

9    35 ms    35 ms    35 ms  144.232.11.181  

10    45 ms   101 ms    43 ms  144.232.11.224  

11    42 ms    41 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [1]  

12    47 ms    47 ms    47 ms  144.232.5.209  

13    85 ms    49 ms    49 ms  144.232.10.44  

14    48 ms    48 ms    49 ms  sl-st30-ash-0-1-0-0.sprintlink.net [128]  

15    92 ms    92 ms    88 ms  sl-nlaye-428976-0.sprintlink.net [144]

 16    63 ms    63 ms    63 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31  

17    84 ms    77 ms    78 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlay31.30.21]  

18    94 ms    86 ms    84 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.  

19    78 ms    78 ms    78 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.ne3.122]

 20    59 ms    55 ms    60 ms  ash.xfactorservers.com [75.102.41.52]

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [75.102.41.52] over a maximum of 30 hops:

  1     3 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    12 ms    11 ms     *     108-213-44-3.lightspeed.stlsmo.sbcglo8.213.44.3]  

3     *        *        *     Request timed out.  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    14 ms    11 ms    15 ms  12.83.40.5  

7    32 ms    31 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]

  8    33 ms    33 ms    33 ms  144.232.7.41  

9    36 ms    34 ms    36 ms  144.232.11.181  

10    57 ms    43 ms    43 ms  144.232.11.224  

11    42 ms    42 ms    43 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [1]

 12    47 ms    47 ms    46 ms  144.232.5.209  

13    48 ms    48 ms    47 ms  144.232.10.44  

14    49 ms    48 ms    49 ms  sl-st30-ash-0-1-0-0.sprintlink.net [128]  

15    91 ms    95 ms    95 ms  sl-nlaye-428976-0.sprintlink.net [144]  

16   120 ms    84 ms    84 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31  

17    97 ms    83 ms    82 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlay31.30.21]  

18    87 ms    88 ms    85 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.  

19    86 ms    83 ms    80 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.ne3.122]

 20    80 ms    63 ms    74 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

Hi, i'm an online gamer that has purchased at&t uverse. I have a 6meg connection that at certain times is very laggy. I talked to one of the server owners and he suggested I run a tracert from my cmd prompt to his server to check for lag. He mentioned it was client side and I should ask my isp for help so here's the tracerts, times and any advice how to stabilize this would be appreciated. ip is 192. 168.1.254

 

[1st tracert @3:25pm central]

 

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

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [] over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  dsldevice.att.net []

  2    18 ms    12 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglobal.net [108.213.44.3]  

  3    20 ms    12 ms     *     71.144.225.38

  4     *        *        *     Request timed out.  

  5     *        *        *     Request timed out.  

  6    15 ms    13 ms    11 ms  12.83.40.5  

  7    32 ms    45 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]  

  8    33 ms    32 ms    33 ms  144.232.7.41  

  9    35 ms    35 ms    35 ms  144.232.11.181  

 10    43 ms    42 ms    42 ms  144.232.11.224  

 11    42 ms    42 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [144.232.4.44 ]  

 12    48 ms    47 ms    47 ms  144.232.5.209  

 13    48 ms    48 ms    48 ms  144.232.10.44  

 14    49 ms    48 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [144.232.19.228]  

 15    53 ms    49 ms    48 ms  sl-nlaye-428976-0.sprintlink.net [144.228.205.94]  

 16    48 ms    48 ms    48 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31.31.181]  

  17    99 ms    48 ms    48 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlayer.net [69.31.30.21]  

  18    59 ms    74 ms    49 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.119.69]  

  19    48 ms    48 ms    48 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.4 3.122]  

  20    48 ms    48 ms    48 ms  ash.xfactorservers.com [75.102.41.52]

 

[2nd tracert @ 3:27pm central]

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    12 ms    14 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglobal.net [108.213.44.3]  

3     *        *        *     Request timed out.  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    14 ms    11 ms    12 ms  12.83.40.5  

7    31 ms    33 ms    31 ms  dlstx02jt.ip.att.net [12.122.214.249]  

8    33 ms    32 ms    33 ms  144.232.7.41  

9    36 ms    35 ms    35 ms  144.232.11.181  

10    42 ms    42 ms    42 ms  144.232.11.224  

11    42 ms    42 ms    41 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [144.232.4.44]  

12    47 ms    47 ms    47 ms  144.232.5.209  

13    49 ms    48 ms    48 ms  144.232.10.44  

14    49 ms    49 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [144.232.19.2 28]  

15    51 ms    49 ms    49 ms  sl-nlaye-428976-0.sprintlink.net [144.228.205.94 ]  

16    47 ms    48 ms    47 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31.31.181]  

17    48 ms    48 ms    47 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlayer.net [69.31.30.21]

 18    48 ms    48 ms    48 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.119.69]  

19    48 ms    48 ms    48 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.43.122]

 20    48 ms    48 ms    48 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

[3rd tracert 3:30pm central]

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    15 ms    12 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglobal.net [18.213.44.3]  

3    14 ms    31 ms    12 ms  71.144.225.38  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    12 ms    15 ms    11 ms  12.83.40.5  

7    31 ms    31 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]  

8    32 ms    33 ms    32 ms  144.232.7.41  

9    35 ms    35 ms    36 ms  144.232.11.181  

10    43 ms    42 ms    43 ms  144.232.11.224  

11    42 ms    42 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [144.232.4.4]

 12    47 ms    47 ms    47 ms  144.232.5.209  

13    48 ms    48 ms    48 ms  144.232.10.44

 14    49 ms    48 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [144.232.19.228]  

15    50 ms    56 ms    52 ms  sl-nlaye-428976-0.sprintlink.net [144.228.205.9]  

16    48 ms    48 ms    48 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31.31.181]

 17    97 ms    48 ms    48 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlayer.net [69.31.30.21]  

18    57 ms    47 ms    48 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.119.69]  

19    48 ms    48 ms    48 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.net [75.102.4 3.122]  

20    48 ms    48 ms    48 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

Now my connection goes to poop at 5pm central to 11pm and these are just a few tracerts from around 8:30 pm central time..

 

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

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [75.102.41.52] over a maximum of 30 hops:

  1     1 ms     1 ms     4 ms  dsldevice.att.net []  

2    12 ms    11 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglo8.213.44.3]  

3    14 ms    12 ms     *     71.144.225.38  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    13 ms    11 ms    15 ms  12.83.40.5  

7    32 ms    32 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]

  8    33 ms    32 ms    32 ms  144.232.7.41  

9    36 ms    35 ms    35 ms  144.232.11.181  

10    43 ms    43 ms    43 ms  144.232.11.224  

11    41 ms    42 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [1]  

12    48 ms    47 ms    47 ms  144.232.5.209

 13    49 ms    48 ms    48 ms  144.232.10.44  

14    49 ms    48 ms    48 ms  sl-st30-ash-0-1-0-0.sprintlink.net [128]

 15    79 ms    78 ms    74 ms  sl-nlaye-428976-0.sprintlink.net [144]  

16    59 ms    60 ms    59 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31  

17    68 ms    70 ms    69 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlay31.30.21]

 18    79 ms    81 ms    82 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.

 19    82 ms    81 ms    82 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.ne3.122]  

20    81 ms    65 ms    63 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [75.102.41.52] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    13 ms    11 ms    11 ms  108-213-44-3.lightspeed.stlsmo.sbcglo8.213.44.3]  

3    12 ms    12 ms     *     71.144.225.38  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    14 ms    17 ms    13 ms  12.83.40.5  

7    32 ms    31 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]  

8    33 ms    32 ms    33 ms  144.232.7.41  

9    35 ms    35 ms    35 ms  144.232.11.181  

10    45 ms   101 ms    43 ms  144.232.11.224  

11    42 ms    41 ms    42 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [1]  

12    47 ms    47 ms    47 ms  144.232.5.209  

13    85 ms    49 ms    49 ms  144.232.10.44  

14    48 ms    48 ms    49 ms  sl-st30-ash-0-1-0-0.sprintlink.net [128]  

15    92 ms    92 ms    88 ms  sl-nlaye-428976-0.sprintlink.net [144]

 16    63 ms    63 ms    63 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31  

17    84 ms    77 ms    78 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlay31.30.21]  

18    94 ms    86 ms    84 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.  

19    78 ms    78 ms    78 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.ne3.122]

 20    59 ms    55 ms    60 ms  ash.xfactorservers.com [75.102.41.52]

 

C:\Users\Gaming>tracert 75.102.41.52

Tracing route to ash.xfactorservers.com [75.102.41.52] over a maximum of 30 hops:

  1     3 ms    <1 ms    <1 ms  dsldevice.att.net []  

2    12 ms    11 ms     *     108-213-44-3.lightspeed.stlsmo.sbcglo8.213.44.3]  

3     *        *        *     Request timed out.  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6    14 ms    11 ms    15 ms  12.83.40.5  

7    32 ms    31 ms    32 ms  dlstx02jt.ip.att.net [12.122.214.249]

  8    33 ms    33 ms    33 ms  144.232.7.41  

9    36 ms    34 ms    36 ms  144.232.11.181  

10    57 ms    43 ms    43 ms  144.232.11.224  

11    42 ms    42 ms    43 ms  sl-crs1-atl-0-3-0-0.sprintlink.net [1]

 12    47 ms    47 ms    46 ms  144.232.5.209  

13    48 ms    48 ms    47 ms  144.232.10.44  

14    49 ms    48 ms    49 ms  sl-st30-ash-0-1-0-0.sprintlink.net [128]  

15    91 ms    95 ms    95 ms  sl-nlaye-428976-0.sprintlink.net [144]  

16   120 ms    84 ms    84 ms  ae4-30g.cr1.iad1.us.nlayer.net [69.31  

17    97 ms    83 ms    82 ms  as23352.xe-1-3-0-101.cr1.iad1.us.nlay31.30.21]  

18    87 ms    88 ms    85 ms  50.ae0.cr2.iad1.us.scnet.net [64.202.  

19    86 ms    83 ms    80 ms  as36352.ge-1-1-5.cr2.iad1.us.scnet.ne3.122]

 20    80 ms    63 ms    74 ms  ash.xfactorservers.com [75.102.41.52]

Trace complete.

 

Accepted Solution

Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

3,784 views
10 replies
(0) Me too
(0) Me too
Reply
View all replies
(10)
0
(0)
  • Rate this reply
View profile
Mar 8, 2013 7:36:23 PM
0
(0)
ACE - Expert

Your target server is in Ashburn, VA.  You're being routed to an AT&T Node at Dallas/Fort Worth, TX, and being handed over to to the server's ISP network (SprintLink.Net).  You're going through Atlanta to Ashburn, where you bounce around a bit and land at your server.

 

Your number of hops looks pretty normal.  Your PING times are about 50 ms when you say things are not bad, and about 80 ms when you say they are.

 

Note that the ping time to hop 13, Ashburn, VA, is pretty much the same in all traceroutes.  The fluctuation appears to be in the Ashburn, VA area.  This is either in your server provider's own network or in his ISP.  I think you need to talk to them some more.

 

 

 

Your target server is in Ashburn, VA.  You're being routed to an AT&T Node at Dallas/Fort Worth, TX, and being handed over to to the server's ISP network (SprintLink.Net).  You're going through Atlanta to Ashburn, where you bounce around a bit and land at your server.

 

Your number of hops looks pretty normal.  Your PING times are about 50 ms when you say things are not bad, and about 80 ms when you say they are.

 

Note that the ping time to hop 13, Ashburn, VA, is pretty much the same in all traceroutes.  The fluctuation appears to be in the Ashburn, VA area.  This is either in your server provider's own network or in his ISP.  I think you need to talk to them some more.

 

 

 

*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

2 of 11 (3,779 Views)
0
(0)
  • Rate this reply
View profile
Mar 8, 2013 9:58:16 PM
0
(0)
Professor
I really see nothing wrong with those stats on the ATT side. The problems lie outside their network, and there is nothing ATT can do about it.

Also the fact that at that time, you have jr. high, high school, college kids hitting the same servers, creating a huge demand on a poorly designed server hosting system.
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________
I really see nothing wrong with those stats on the ATT side. The problems lie outside their network, and there is nothing ATT can do about it.

Also the fact that at that time, you have jr. high, high school, college kids hitting the same servers, creating a huge demand on a poorly designed server hosting system.
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

3 of 11 (3,744 Views)
0
(0)
  • Rate this reply
View profile
Mar 8, 2013 10:01:33 PM
0
(0)
Professor
Atlanta, remember you are talking a couple of huge colleges & universities, along with major corporations, and European corporations based in that area Jeffer. It does not surprise me that the load increases around that time, in that area.
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________
Atlanta, remember you are talking a couple of huge colleges & universities, along with major corporations, and European corporations based in that area Jeffer. It does not surprise me that the load increases around that time, in that area.
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

4 of 11 (3,742 Views)
0
(0)
  • Rate this reply
View profile
Mar 9, 2013 6:19:16 AM
0
(0)
ACE - Expert

gregzoll_1 wrote:
Atlanta, remember you are talking a couple of huge colleges & universities, along with major corporations, and European corporations based in that area Jeffer. It does not surprise me that the load increases around that time, in that area.

Actually, the time through Atlanta is pretty consistant.  It's when it gets to Ashburn, VA (in the Washington, DC area), where the latency increases during his "problem" times.

 

But as you said, this is outside of AT&T's network and control.

 


gregzoll_1 wrote:
Atlanta, remember you are talking a couple of huge colleges & universities, along with major corporations, and European corporations based in that area Jeffer. It does not surprise me that the load increases around that time, in that area.

Actually, the time through Atlanta is pretty consistant.  It's when it gets to Ashburn, VA (in the Washington, DC area), where the latency increases during his "problem" times.

 

But as you said, this is outside of AT&T's network and control.

 

*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

5 of 11 (3,720 Views)
0
(0)
  • Rate this reply
View profile
Mar 9, 2013 2:19:27 PM
0
(0)
Professor

JefferMC wrote:

gregzoll_1 wrote:
Atlanta, remember you are talking a couple of huge colleges & universities, along with major corporations, and European corporations based in that area Jeffer. It does not surprise me that the load increases around that time, in that area.

Actually, the time through Atlanta is pretty consistant.  It's when it gets to Ashburn, VA (in the Washington, DC area), where the latency increases during his "problem" times.

 

But as you said, this is outside of AT&T's network and control.

 


Of course you & I both know that because a person is a ATT customer, or customer of xyz ISP, it must be a issue with the ISP they are with, due to they do not take the time to look at the info and grasp the concept of how to read it like a road map.

 

Now of course, what some do not realize, is that you can do a visual trace route with a couple of sites.

 

When I run the trace at http://www.yougetsignal.com/tools/visual-tracert/ I get a route from LA to Florida, to Mo, to Chicago.  Now when I run the trace at http://traceroute.monitis.com/ I am getting Wa, LA, Mo, Chicago for the trace. Both of them are showing 76ms, so it looks like the OP just had a issue of heavy server load on one of those traces.

________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________

JefferMC wrote:

gregzoll_1 wrote:
Atlanta, remember you are talking a couple of huge colleges & universities, along with major corporations, and European corporations based in that area Jeffer. It does not surprise me that the load increases around that time, in that area.

Actually, the time through Atlanta is pretty consistant.  It's when it gets to Ashburn, VA (in the Washington, DC area), where the latency increases during his "problem" times.

 

But as you said, this is outside of AT&T's network and control.

 


Of course you & I both know that because a person is a ATT customer, or customer of xyz ISP, it must be a issue with the ISP they are with, due to they do not take the time to look at the info and grasp the concept of how to read it like a road map.

 

Now of course, what some do not realize, is that you can do a visual trace route with a couple of sites.

 

When I run the trace at http://www.yougetsignal.com/tools/visual-tracert/ I get a route from LA to Florida, to Mo, to Chicago.  Now when I run the trace at http://traceroute.monitis.com/ I am getting Wa, LA, Mo, Chicago for the trace. Both of them are showing 76ms, so it looks like the OP just had a issue of heavy server load on one of those traces.

________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

6 of 11 (3,667 Views)
0
(0)
  • Rate this reply
View profile
Mar 11, 2013 2:45:04 PM
0
(0)
Voyager
Edited by infrared on Mar 11, 2013 at 3:16:52 PM

Thank you for the responses, but is there no problem within the first few timeout areas? Honestly it's not as much of a ping issue as it is a ping loss issue at those times, and PL makes playing online games horrible when everyone is skipping around. I thought having time outs on your hops was really bad?

 

Also, those were just average timeouts posted. Quite a few times I can get ping that server, and hops 3-9 all time out. I pretty much average 3 time outs always on hops 3-5 per server tracert.. Is that my side or isp side then?

Thank you for the responses, but is there no problem within the first few timeout areas? Honestly it's not as much of a ping issue as it is a ping loss issue at those times, and PL makes playing online games horrible when everyone is skipping around. I thought having time outs on your hops was really bad?

 

Also, those were just average timeouts posted. Quite a few times I can get ping that server, and hops 3-9 all time out. I pretty much average 3 time outs always on hops 3-5 per server tracert.. Is that my side or isp side then?

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

[ Edited ]
7 of 11 (3,607 Views)
0
(0)
  • Rate this reply
View profile
Mar 11, 2013 3:22:57 PM
0
(0)
Professor
Go back and re-read what we posted in follow up to your original question.
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________
Go back and re-read what we posted in follow up to your original question.
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

8 of 11 (3,590 Views)
0
(0)
  • Rate this reply
View profile
Mar 11, 2013 4:01:32 PM
0
(0)
Voyager

I understand i'm being routed through texas to atlanta. What is causing the ping infrequency issues would be high traffic load in the atlanta area and connecting to the VA area based host is quite poor on there part. That my peak times are being caused by people getting off work, school and whatever else and there is the latency issue when connecting to the VA located server.

 

I'm asking is it normal for your time outs to be numerous at the start of your tracert?? No matter what server that I pull up hops 3,4, and 5 are  normally always timed out on servers from, dallas, nyc, va and california along with other request timed out errors. Wouldn't that cause ping loss if those hops won't take packets?

 

I also read that you say having those time-outs are normal. Is that a u-verse exclusive to be okay in that state? I can get ping times from other gamers and they won't register "request timed out" on their server tracerts through those hops, unless u-verse bypasses those or that is from my home set-up which makes this post moot.

I understand i'm being routed through texas to atlanta. What is causing the ping infrequency issues would be high traffic load in the atlanta area and connecting to the VA area based host is quite poor on there part. That my peak times are being caused by people getting off work, school and whatever else and there is the latency issue when connecting to the VA located server.

 

I'm asking is it normal for your time outs to be numerous at the start of your tracert?? No matter what server that I pull up hops 3,4, and 5 are  normally always timed out on servers from, dallas, nyc, va and california along with other request timed out errors. Wouldn't that cause ping loss if those hops won't take packets?

 

I also read that you say having those time-outs are normal. Is that a u-verse exclusive to be okay in that state? I can get ping times from other gamers and they won't register "request timed out" on their server tracerts through those hops, unless u-verse bypasses those or that is from my home set-up which makes this post moot.

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

9 of 11 (3,570 Views)
0
(0)
  • Rate this reply
View profile
Solved
Mar 11, 2013 4:53:00 PM
0
(0)
Professor
It is not the problem in Atlanta, it is once it leaves Atlanta, it is going through some bad routing.

Next time it happens, contact the Party that is showing the lag, whether it is Level-3, Sprint, etc..
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________
It is not the problem in Atlanta, it is once it leaves Atlanta, it is going through some bad routing.

Next time it happens, contact the Party that is showing the lag, whether it is Level-3, Sprint, etc..
________________________________________________________________

"Ren: Now listen, Cadet. I've got a job for you. See this button? Don't touch it! It's the History Eraser button, you fool!

Stimpy: So what'll happen?

Ren: That's just it. We don't know. Maybe something bad, maybe something good. I guess we'll never know, 'cause you're going to guard it. You won't touch it, will you?"
________________________________________________________________

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

10 of 11 (3,557 Views)
Solution
0
(0)
  • Rate this reply
View profile
Solved
Mar 11, 2013 7:53:37 PM
0
(0)
ACE - Expert

infrared wrote:

 

I'm asking is it normal for your time outs to be numerous at the start of your tracert?? No matter what server that I pull up hops 3,4, and 5 are  normally always timed out on servers from, dallas, nyc, va and california along with other request timed out errors. Wouldn't that cause ping loss if those hops won't take packets?

 

I also read that you say having those time-outs are normal. Is that a u-verse exclusive to be okay in that state? I can get ping times from other gamers and they won't register "request timed out" on their server tracerts through those hops, unless u-verse bypasses those or that is from my home set-up which makes this post moot.


Yes, this is normal.  Charter used to block inbound traceroutes, I don't know if they still do since I disconnected.

 

Traceroute uses an error condition to work.  Handling the ICMP error consumes more resources than simply routing the packet.  For this reason, and I'm sure for other reasons, AT&T causes the routers to dump ICMP packets with TTL errorrs.  ICMP (and real TCP and UDP) packets for which the TTL has not expired transit through these routers just fine, thank you very much, or the next hops couldn't reply, either (but they do).

 

 


infrared wrote:

 

I'm asking is it normal for your time outs to be numerous at the start of your tracert?? No matter what server that I pull up hops 3,4, and 5 are  normally always timed out on servers from, dallas, nyc, va and california along with other request timed out errors. Wouldn't that cause ping loss if those hops won't take packets?

 

I also read that you say having those time-outs are normal. Is that a u-verse exclusive to be okay in that state? I can get ping times from other gamers and they won't register "request timed out" on their server tracerts through those hops, unless u-verse bypasses those or that is from my home set-up which makes this post moot.


Yes, this is normal.  Charter used to block inbound traceroutes, I don't know if they still do since I disconnected.

 

Traceroute uses an error condition to work.  Handling the ICMP error consumes more resources than simply routing the packet.  For this reason, and I'm sure for other reasons, AT&T causes the routers to dump ICMP packets with TTL errorrs.  ICMP (and real TCP and UDP) packets for which the TTL has not expired transit through these routers just fine, thank you very much, or the next hops couldn't reply, either (but they do).

 

 

*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

Re: Lag with online games, ping tests at 3:30pm and 8:35pm central Missouri

11 of 11 (3,525 Views)
Solution
Share this post
Share this post