I'm playing CS:GO for a while now and on some days I'm really bad.

It was noticeable that on these days even my teammates from the same city I live in were lagging and "flying" from one point to another without a fluent movement. My Ping is about 15ms and I've got an average of 250FPS (according to the steam fps viewer overlay).

Do you have any idea if it depends on my CS:GO settings, G Data Internet Security or something else? The game runs on a SSD with an Intel i5, a Radeon HD7870 and I've got a stable 50K down and 10K up internet connection.

Thank you!


  • 15ms ping with 250FPS sounds like you're fine. Unless you're stuttering, it's not you.
    – Frank
    Nov 3, 2015 at 13:20
  • But they've got the same ping as me, better computers and don't have these lags with other players
    – Johannes
    Nov 3, 2015 at 13:21

1 Answer 1


That sounds like you have heavy packet loss somewhere between your home NAT router and the server you are playing on.

As a first step, you could enter net_status in the CS:GO console. This will give an output like the following:

] net_status
Net status for host
- Config: Multiplayer, listen, 1 connections
- Ports: cl0 27005, sv1 27015, htv2 27020, htv13 0, 4 total.
- Latency: avg out 0.04s, in 0.01s
- Loss:    avg out 0.0, in 0.0     <====================== This line show packet loss
- Packets: net total out  65.0/s, in 64.5/s
           per client out 65.0/s, in 64.5/s
- Data:    net total out  8.9, in 10.3 kB/s
           per client out 8.9, in 10.3 kB/s

This shows the packet loss of incoming and outgoing packets (I don't know the units, maybe percent). If it says anything other than 0.0, that's a reason to be suspicious. Something on the route between you and the server throws away packets. You should probably contact your internet service provider about the problem, unless you are willing to investigate further.

If you want to investigate furhter, you'll need the server's IP address. Enter status in the CS:GO-console and look for the line udp/ip:

] status
hostname:  xxxxxxx
version : 6171 secure  
udp/ip  :          <============== The part before the : is the IP
os      :  Linux
type    :  community dedicated
map     : de_dust2
players : 1 humans, 3 bots (12/0 max) (not hibernating)

Once you got that, you can test packet loss using the ping command1. This will tell you if the problem just exists inside CS:GO or if it really is a network problem. Just open a terminal (enter "cmd" in the start menu and press Enter) and enter the following (with the correct IP, obviously):

ping -t ip.of.the.server

Your PC then sends requests to that server and measure the time until it answers. Pressing Ctrl+Break will show you statistics like this:

Ping statistics for ip.of.the.server
    Packets: Sent = 467, Received = 467, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 23ms, Average = 21ms

Pressing Ctrl+C will terminate the ping program and show the same statistics.

If it says anything but 0% loss, you've got a problem.

If you know something about how network protocols work and/or are willing to invest some time learning, you can try to find the cause of the issue yourself. Here's a good tutorial about debugging packet loss, which you can use as a starting point. (archive link)

1. Disclaimer: Obviously this only measures loss of ICMP packets, not UDP or TCP, but normally these should correlate.

  • This is a good answer, though I'd include an explanation on how to fix the packet loss, if it can be rectified/helped.
    – ʰᵈˑ
    Nov 3, 2015 at 14:57
  • @ʰᵈˑ You're right, of course, but debugging packet loss is really hard, if not impossible, for the average home user, because it requires some expert knowledge on internet protocols. That's why I suggested contacting the ISP.
    – Fritz
    Nov 3, 2015 at 15:06
  • In case you are interested: You would need to find the route the packets are taking using tracert (which might or might not work due to the configuration of remote routers which you don't control), find out which of those routers drops packets (again, this might fail due to router config), and contact the operator of said router (I wouldn't even know how to find that out). Here's a writeup of the general process, though not a tutorial: serverfault.com/questions/207375/…
    – Fritz
    Nov 3, 2015 at 15:07
  • @ʰᵈˑ I think it's better now. :)
    – Fritz
    Nov 3, 2015 at 15:17
  • I tried "ping -n 100 google.com" and I lost 2 packages (directly after boot of my PC, maybe firewall was initialised?) the first time, 0 packages the second and again 2 the third time... I also used tracert and no * were visible so I think my connection is very stable. I don't know how to get the IP adress of the CS:GO MM-servers but maybe I can use net_graph to see package loss.. Is it possible that these settings influence my performance: rate cl_cmdrate cl_updaterate cl_interp_ratio cl_interp fps_max?
    – Johannes
    Nov 3, 2015 at 16:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .