Jump to content



Recommended Posts

So for the past couple months I have been noticing a lot of lag on the L4D2 servers and it's getting very frustrating. High ping is not a big deal, I could play with 200 ping(if it was consistent).. the problem is that I should have around 50-70 ping and sometimes I do, but most of the time it's spiking up to over 100. You might be thinking "100 ping, big deal", but like I said it's different when it is spiking. I experience rubber banding a lot and it makes simple movements impossible in the game. I'm not here just to whine about it, rather to discuss what the problem is and if there is a possible solution. Does anyone else experience lag spike like this? I've tried everything I can think of at this point. I've verified game cache, reinstalled the game, upgraded PC'S, messed with NAT type(it's Open now), reset my modem and router a few times and done speed tests to ensure it's not my internet. 

Does anybody have an idea what the problem could be? I really doubt I'm being DDOS'd as it has been happening for over a month now and nobody would waste their time doing that. Could I just have a bad route to the server or something? I don't know how it all works. Or is it something on the host's end? 

And no, it's not just my connection. I actually have decent internet, almost always 100 down and 20 up with around 10 ping according to speed tests. 

So what could this be then? Any input would be appreciated. Thanks -Logan







Link to comment
Share on other sites

I used the trace route command to both servers and it's the same, the ping increases once it gets to the 10th hop which is "cr1.cgcil.ip.att.net ". Idk what that is but I feel like it's not really my problem. Considering it only took 16 hops to get to the server, so that's pretty far along. I googled "cr1.cgcil.ip.att.net " and saw some people on wow/diablo forums complaining about a Chicago server.. I'm new to tracerouting but could that just mean there's a bad router on the way to Chicago? 

Link to comment
Share on other sites


I say bad route to server.  Peeps end up going through a major hub somewhere and the more hops, the worse your connection to the server.  When my old clan had our server in Chicago, and I lived in S/E Wisconsin, I'd hop around and go through a Dallas hub before hopping back to Chicago.  If I remember correctly, I had like 22 hops...CRAZY.  Chicago is only a couple of hours from me.  Our ISP insisted that they couldn't do anything about the route.  Ping was still good and our connection wasn't laggy per se, but I imagine it would have been nearly perfect if we connected right to Chicago without all the extra hops and the hub in Dallas.  Made me so mad lol.


Sounds like you don't go through any other major hubs though.  It's probably getting hung up somewhere in the Chicago routing before you connect to the gc servers.

Edited by DiXie
Link to comment
Share on other sites

IIRC you guys said you are loyal to NFO right? I don't think you guys are going to consider moving the server, but is there anyway to upgrade the servers? Or are they the best available? Would upgrading tick rate help?

I am willing to donate for lag free servers. 

Link to comment
Share on other sites

Here's my tracert to server 1



Tracing route to c-216-52-148-77.managed-vds.premium-chicago.nfoservers.com [] over a maximum of 30 hops:



2 7 ms 6 ms 5 ms xx.xxx.xx.xxx

3 7 ms 7 ms 5 ms dtr02mnplmi-tge-0-1-0-9.mnpl.mi.charter.com []

4 18 ms 11 ms 11 ms crr02bycymi-bue-13.bycy.mi.charter.com []

5 9 ms 9 ms 10 ms crr02sgnwmi-bue-11.sgnw.mi.charter.com []

6 15 ms 15 ms 15 ms bbr01sgnwmi-bue-2.sgnw.mi.charter.com []

7 15 ms 13 ms 14 ms be4309.rcr21.dtw04.atlas.cogentco.com []

8 21 ms 22 ms 21 ms be2103.ccr42.ord01.atlas.cogentco.com []

9 22 ms 21 ms 21 ms be2217.ccr41.ord03.atlas.cogentco.com []

10 22 ms 21 ms 21 ms cogent.e9.router.chicago.nfoservers.com []

11 23 ms 21 ms 21 ms c-216-52-148-77.managed-vds.premium-chicago.nfoservers.com []


Trace complete.

and I very rarely feel any lag. The servers are on a pretty decent VDS, which I've never seen go above 25% CPU / memory usage even when full. And yes, they are on NFO. I haven't seen anything about server DDOS lately from NFO either.

Link to comment
Share on other sites

I guess you're lucky you don't go the same route as me then? The 10th hop that I mentioned earlier is the one that has the highest latency, and I know it's not my internet that's the problem because 1) its so far along the tracert amd 2) i dont even have att.

And so the servers don't need an upgrade, they aren't being ddos'd, it's not my connection... So I guess the lag will remain. Thanks for trying to help anyways.. At least I learned about trace routes.

Link to comment
Share on other sites

Wow, 17 hops.  No wonder...


Tracing route to c-216-52-148-77.managed-vds.premium-chicago.nfoservers.com []
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms
  2    31 ms    28 ms    29 ms  xx.xx.xx.xx
 3    13 ms     9 ms     8 ms  te-1-2-ur01.hamburg.pa.pitt.comcast.net []
  4    10 ms     9 ms     8 ms  te-2-3-ur01.newshaffrtwn.pa.pitt.comcast.net []
  5    12 ms    11 ms    10 ms  te-0-10-0-19-ar01.lancaster.pa.pitt.comcast.net []
  6    20 ms    20 ms    19 ms  he-0-9-0-1-ar01.mckeesport.pa.pitt.comcast.net []
  7    25 ms    27 ms    25 ms  be-7016-cr02.ashburn.va.ibone.comcast.net []
  8    25 ms    25 ms    23 ms  he-0-11-0-0-pe04.ashburn.va.ibone.comcast.net []
  9    24 ms    24 ms    24 ms
 10    35 ms    42 ms    32 ms []
 11    31 ms    31 ms    30 ms []
 12    32 ms    35 ms    34 ms []
 13   250 ms    49 ms    53 ms []
 14    49 ms    50 ms    49 ms []
 15    51 ms    52 ms    51 ms  border5.po2-bbnet2.chg.pnap.net []
 16    50 ms    49 ms    50 ms  inap-b5.e3.router.chicago.nfoservers.com []
 17    51 ms    48 ms    50 ms  c-216-52-148-77.managed-vds.premium-chicago.nfoservers.com []
Edited by Architect
Link to comment
Share on other sites

Hops are not the issue.   A ISP will have multiple routers to separate or minimize saturation on a subnet or vlan or network or a partner network.  


Server 2 for me is laggy as hell.  Especially when its full.  



Tracing route to c-74-91-113-10.managed-vds.premium-chicago.nfoservers.com []
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  FIOS_Quantum_Gateway.fios-router.home []
  2     6 ms     7 ms     6 ms  L100.NYCMNY-VFTTP-212.verizon-gni.net []
  3     9 ms    11 ms    12 ms  T1-6-0-13.NYCMNY-LCR-22.verizon-gni.net []
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    10 ms    13 ms    11 ms  0.ae8.GW10.EWR6.ALTER.NET []
  7    10 ms    10 ms     9 ms  teliasonera-gw.customer.alter.net []
  8    10 ms     9 ms    10 ms  nyk-bb2-link.telia.net []
  9    29 ms    32 ms    29 ms  chi-b21-link.telia.net []
10    28 ms    30 ms    29 ms  telia.e8.router.chicago.nfoservers.com []
11    29 ms    29 ms    29 ms  c-74-91-113-10.managed-vds.premium-chicago.nfoservers.com []

Trace complete.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...