Server lag/packet loss?

Go to http://acmectf.com for more info and file downloads!

[WORM]

I have heard a few complaints of server lag/packet loss lately. Although I appreciate being told of a problem that happened hours ago/last-night/the-other-day there is more needed than just saying you had a problem.

Let me ask this of you guys...again. 

Please help me to help you...do the following for me when there are problems and we have something to work with:

1) If running R1Q2, type "lag" in console and write down the info it gives you.

2) Drop your connection to the game for a few minutes and do the following two items:

   A) Run a tracert to the server. You can do this in command prompt or download R1CH's GUI tracert
       program,  http://www.r1ch.net/stuff/ftrace/wftrace.exe Save to a text file for me.

   B) Run a ping summary. Use the command prompt and type "ping  -n 100 208.43.95.250" It will return
    something like this:

    Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
   Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 47ms, Average = 45ms
   
   Copy the results to a text file also.

3) Note the date, time (including timezone you are in) and your IP then email the above files to me, along with   any other info you think may help.

This way I will have documentation to present to SoftLayer.

I have run the above checks and so far haven't seen any problem...at the times I ran them. No doubt there are some problems at times but it's extremely hard to nail it down with them being intermittent and no test data to show.

Thanks in advance for your help!

[angry]

I realize this isn't e-mail, but I logged the data in question earlier tonight.

This is right when I connected.



Disconnected, ran a traceroute:

Code:

Target Name: www.acmectf.com
         IP: 208.43.95.250
  Date/Time: 12/31/2011 4:59:40 PM to 12/31/2011 5:00:19 PM

Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
 1     8   0  0.0   0   1   0  [192.168.1.1]
 2     8   0  0.0  23 130  36  L100.LSANCA-DSL-33.verizon-gni.net [71.103.160.1]
 3     8   0  0.0  23  25  23  P11-1.LSANCA-LCR-04.verizon-gni.net [130.81.45.154]
 4     8   0  0.0  25  96  34  so-6-1-2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.28.229]
 5     8   0  0.0  25  27  25  0.xe-11-1-0.BR1.LAX15.ALTER.NET [152.63.112.5]
 6     8   0  0.0  25  26  25  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
 7     8   0  0.0  25  26  25  ae-1-60.edge1.LosAngeles6.Level3.net [4.69.144.16]
 8     8   0  0.0  25  57  31  te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
 9     8   0  0.0  26  54  35  ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
10     8   2 25.0  60  61  60  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
11     8   0  0.0  59  61  59  ae7.bbr02.eq01.dal03.networklayer.com [173.192.18.209]
12     8   0  0.0  85 118  99  ae1.bbr01.tl01.atl01.networklayer.com [173.192.18.135]
13     8   0  0.0  96 102  97  ae0.bbr01.eq01.wdc02.networklayer.com [173.192.18.152]
14     8   0  0.0  95 102  97  ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]
15     8   0  0.0  95  98  96  po2.fcr01.sr01.wdc01.networklayer.com [208.43.118.138]
16     8   0  0.0  95 107  98  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
17     8   0  0.0  95 101  97  acmegamers.com [208.43.95.250]

This was at 5:00 PM Pacific (8 PM EST), 31 December.

[angry]

Logged more data. This was after the lag had stopped.

Again, right when I first connected:



Disconnected, ran another traceroute:

Code:

Target Name: www.acmectf.com
         IP: 208.43.95.250
  Date/Time: 12/31/2011 9:39:11 PM

 1    1 ms  N/A       0 ms  N/A       0 ms  [192.168.1.1]
 2   24 ms  N/A      25 ms  N/A      24 ms  L100.LSANCA-DSL-33.verizon-gni.net [71.103.160.1]
 3   24 ms  N/A      25 ms  N/A      25 ms  P11-1.LSANCA-LCR-04.verizon-gni.net [130.81.45.154]
 4   27 ms  N/A      79 ms  N/A      26 ms  so-6-1-2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.28.229]
 5   26 ms  N/A      27 ms  N/A      26 ms  0.xe-11-1-0.BR1.LAX15.ALTER.NET [152.63.112.5]
 6   26 ms  N/A      26 ms  N/A      26 ms  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
 7   26 ms  N/A      28 ms  N/A      26 ms  ae-1-60.edge1.LosAngeles6.Level3.net [4.69.144.16]
 8   26 ms  N/A      27 ms  N/A      27 ms  te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
 9   27 ms  N/A      27 ms  N/A      28 ms  ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
10   62 ms  N/A      61 ms  N/A      62 ms  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
11   95 ms  N/A      60 ms  N/A      71 ms  ae7.bbr02.eq01.dal03.networklayer.com [173.192.18.209]
12   86 ms  N/A      86 ms  N/A      85 ms  ae1.bbr01.tl01.atl01.networklayer.com [173.192.18.135]
13   98 ms  N/A      98 ms  N/A      97 ms  ae0.bbr01.eq01.wdc02.networklayer.com [173.192.18.152]
14   98 ms  N/A      98 ms  N/A      96 ms  ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]
15   95 ms  N/A      97 ms  N/A      97 ms  po2.fcr01.sr01.wdc01.networklayer.com [208.43.118.138]
16   95 ms  N/A      95 ms  N/A      95 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
17   97 ms  N/A      98 ms  N/A      98 ms  acmegamers.com [208.43.95.250]

Ping statistics for www.acmectf.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 97ms, Maximum = 98ms, Average = 97ms

This was at 9:39 PM Pacific, 31 December (1 January, 12:39 AM EST).

[spec]

Tracert and ping sended by pm

Netgraph:

http://imageshack.us/photo/my-images/844/quake117.png/

[WORM]

Nodody runs a ping summary? 100 ping? Please do so when you are experiencing the worst problems. Along with a tracert, thes two items are utmost importance.

Netgraph doesn't help me. Yes, it shows you have lag..but we already knew that. 

Is there a pattern to when the problems occur? Checks I run during day don't show any problems at all. Is it same time at night? Same duration?

SoftLayer has been having load balancer issues in WDC, I have asked them to check us out but they do need some data.

Thanks, I appreciate it.

[WORM]

Softlayer, and myself, have performed tests today on our server and the network. No issues were found.

I have asked them to monitor traffic for us tonight and they have agreed to do so. We have scheduled this for 1/1/12 between the hours of 8:00 - 11:00 PM EST. Stay with the server tonight and let's get a report from them.

Thanks!

[Bones]

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:
This was run about 10pm

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms     8 ms    17 ms  gig5-2-21.ardlme04-rtr001.ne.northeast.rr.com [24.31.155.110]
  4    17 ms    11 ms    12 ms  g10-4-1-0.ptldmehx-rtr001.ne.northeast.rr.com [204.210.69.246]
  5    20 ms    17 ms    17 ms  rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]
  6    36 ms    27 ms    27 ms  ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
  7    32 ms     *       27 ms  ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
  8    28 ms    26 ms    32 ms  66.109.11.126
  9    28 ms    26 ms    27 ms  ae7.bbr01.tl01.nyc01.networklayer.com [173.192.18.176]
 10    33 ms    33 ms    33 ms  ae1.bbr01.eq01.wdc02.networklayer.com [173.192.18.156]
 11    38 ms    47 ms    35 ms  ae0.dar01.sr01.wdc01.networklayer.com [173.192.18.197]
 12    33 ms    33 ms    37 ms  po1.fcr01.sr01.wdc01.networklayer.com [208.43.118.134]
 13    35 ms    33 ms    34 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
 14    33 ms    37 ms     *     acmegamers.com [208.43.95.250]
 15    34 ms    34 ms    33 ms  acmegamers.com [208.43.95.250]

Trace complete.


Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:

the 1% loss was done while right after i bailed out of game to run the test. I was phone jacked like every 2 to 5 seconds. From what i was told, it did that for almost half the map.

[NQK Ramirez]

Usually happens when a map load and not all the time.  Then it can go on for more then 5 minutes into the map.  Where you can move a little then freeze, move a little then freeze over and over again.

[angry]

Nodody runs a ping summary? 100 ping? Please do so when you are experiencing the worst problems. Along with a tracert, thes two items are utmost importance.

Fuck, I misread your original post. I thought it said run traceroute OR ping, not that it said to do both.

My bad, boss.


Just ran this:

Code:

Target Name: www.acmectf.com
         IP: 208.43.95.250
  Date/Time: 1/1/2012 8:27:24 PM to 1/1/2012 8:27:51 PM

 1    1 ms  N/A       0 ms  N/A       0 ms  N/A       0 ms  N/A       0 ms  [192.168.1.1]
 2   23 ms  N/A      23 ms  N/A      23 ms  N/A      24 ms  N/A      23 ms  L100.LSANCA-DSL-33.verizon-gni.net [71.103.160.1]
 3   23 ms  N/A      23 ms  N/A      23 ms  N/A      24 ms  N/A      24 ms  P11-1.LSANCA-LCR-04.verizon-gni.net [130.81.45.154]
 4  101 ms  N/A      25 ms  N/A     110 ms  N/A      25 ms  N/A      26 ms  so-6-1-2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.28.229]
 5   71 ms  N/A      83 ms  N/A      75 ms  N/A      70 ms  N/A      72 ms  0.xe-11-1-0.BR1.LAX15.ALTER.NET [152.63.112.5]
 6   78 ms  N/A      76 ms  N/A      79 ms  N/A      82 ms  N/A      73 ms  ae6.edge1.LosAngeles9.level3.net [4.68.62.169]
 7   54 ms  N/A      61 ms  N/A      59 ms  N/A      62 ms  N/A      59 ms  ae-1-60.edge1.LosAngeles6.Level3.net [4.69.144.16]
 8   27 ms  N/A      26 ms  N/A      26 ms  N/A      26 ms  N/A      26 ms  te2-5.bbr01.cs01.lax01.networklayer.com [4.26.0.70]
 9   70 ms  N/A      26 ms  N/A      28 ms  N/A      26 ms  N/A      47 ms  ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
10  N/A     N/A      60 ms  N/A      *      N/A      *      N/A      60 ms  ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
11   59 ms  N/A      59 ms  N/A      59 ms  N/A      60 ms  N/A      66 ms  ae7.bbr02.eq01.dal03.networklayer.com [173.192.18.209]
12  123 ms  N/A     137 ms  N/A     113 ms  N/A     114 ms  N/A     113 ms  ae1.bbr01.tl01.atl01.networklayer.com [173.192.18.135]
13  109 ms  N/A     104 ms  N/A     108 ms  N/A     109 ms  N/A     104 ms  ae0.bbr01.eq01.wdc02.networklayer.com [173.192.18.152]
14  103 ms  N/A     107 ms  N/A     107 ms  N/A     104 ms  N/A     102 ms  ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]
15  105 ms  N/A     108 ms  N/A     107 ms  N/A     103 ms  N/A      *      po2.fcr01.sr01.wdc01.networklayer.com [208.43.118.138]
16  104 ms  N/A     106 ms  N/A     105 ms  N/A     102 ms  N/A     106 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
17  106 ms  N/A     107 ms  N/A     109 ms  N/A     103 ms  N/A     106 ms  acmegamers.com [208.43.95.250]

Ping statistics for www.acmectf.com
Packets: Sent = 5, Received = 5, Lost = 0 (0.0%)
Round Trip Times: Minimum = 103ms, Maximum = 109ms, Average = 106ms

Code:

Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 102ms, Maximum = 110ms, Average = 107ms

1 January, 2012; 8:27 PM Pacific (11:27 EST)

[WORM]

Everything looks okay. SoftLayer spent time to check last night as stated and provided me with results that show no problems at all.

I ran tests myself last night from the server and found nothing.

If this happens again, get me some data as stated above...tracerts and ping summaries with date/time/ip info.

[ex]

According to quadz @ tastyspleen, the problem is Time Warner...at least for now.

http://tastyspleen.net/quake/forums/index.php?topic=17911.0

From Time Warner Cable:

Time Warner Cable is performing a maintenance on their network equipment in Dallas. Certain TWC routers will be unavailable until the maintenance is complete, which explains the routing through Atlanta. The maintenance is expected to end at 0700 CDT today (1 hour from now). However the possibility exists that some of the maintenance activity may extend beyond the change window due to the complexity of this maintenance.

That explains it I think, at least if you have Time Warner (Road Runner).  They had some servers down here in Dallas, and I was getting routed through altanta, to new york, then back to dallas. 

I notice it gets really bad at night, from midnight through 6 a.m.  Apparently, this should be temporary (at least with Time Warner).

[Legend]

WORM the lag is pretty bad, 3 maps in a row, everyone lags out. I felt p2450 servers run smoother. I have a 21 ping and it feels like its an 80. I am not sure wether it is connection or the box itself.

[Bones]

10:35pm 1-5-12

connection quality 0%
server to client   6.19%
client to server  11.72%

10:50pm

connection quality 100%
server to client   5.88
client to server   4014.16

Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
    minimum = 33ms, Maximum = 53ms, Average = 36ms

11:05pm

connection quality 100%
server to client   1.75%   
client to server   2624.81%

Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 99, Lost = 1 (1% loss)
Approximate round trip times in milli-seconds:
    minimum = 32ms, Maximum = 130ms, Average = 36ms

[WORM]

Legend: Please read up and give me some data.

Bones: No tracert to go with that? I appears your problem could be routing to the server, but hard to say.

[Bones]

Map changed and I was getting phone jack every 3 to 5 seconds. others asked about the lag as well
1/8/12  9PM

connection quality 0%
server to client   1.43%   
client to server   48.52%

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mark>tracert acmectf.com

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    15 ms    10 ms    16 ms  gig5-2-21.ardlme04-rtr001.ne.northeast.rr.com [24.31.155.110]
  4    10 ms     9 ms    10 ms  g10-4-1-0.ptldmehx-rtr001.ne.northeast.rr.com [204.210.69.246]
  5    22 ms    24 ms    20 ms  rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]
  6    28 ms    27 ms    28 ms  ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
  7    29 ms    26 ms    29 ms  ae-0-0.pr0.nyc20.tbone.rr.com [66.109.6.157]
  8    32 ms    29 ms    27 ms  66.109.11.126
  9    28 ms    27 ms    44 ms  ae7.bbr01.tl01.nyc01.networklayer.com [173.192.18.176]
 10    34 ms    33 ms     *     ae1.bbr01.eq01.wdc02.networklayer.com [173.192.18.156]
 11    37 ms    33 ms    34 ms  ae0.dar01.sr01.wdc01.networklayer.com [173.192.18.197]
 12    33 ms    35 ms    39 ms  po1.fcr01.sr01.wdc01.networklayer.com [208.43.118.134]
 13    36 ms    35 ms    33 ms  208.43.108.254-static.reverse.softlayer.com [208.43.108.254]
 14    35 ms    33 ms    34 ms  acmegamers.com [208.43.95.250]

Trace complete.



ping  -n 100 208.43.95.250

Pinging 208.43.95.250 with 32 bytes of data:



Ping statistics for 208.43.95.250:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 70ms, Average = 38ms