CRASH REPORTS

**Rad** · 09-04-13, 08:37 PM

I saw the tickrate @ 64 and that seemed ok, but then about 90% of the server started lagging tonight with 150+ ping. Almost like a separate ISP issue was going on. Server was full around 8:30 CST tonight when it happened.

Steam Community :: Screenshot :: lag

**Rad** · 09-05-13, 08:53 PM

That strange CSGO lag is actually happening again right now. 9pm CST with only 3players. Here is a tracert showing the problem. According to this it appears to be with ColoCrossing's connection.

Code:

Tracing route to 131.124.249.72.hypernia.com [72.249.124.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  x
  2    21 ms    38 ms    29 ms  x
  3    10 ms    27 ms     9 ms  x
  4    24 ms    14 ms    15 ms  tge0-10-0-4.lsvqkydb-ccr01.mwrtn.rr.com [65.29.25.134]
  5    22 ms    23 ms    28 ms  network-065-189-140-166.mwrtn.rr.com [65.189.140.166]
  6    33 ms    31 ms    31 ms  107.14.19.58
  7    60 ms    59 ms    60 ms  ae-0-0.cr0.dca10.tbone.rr.com [66.109.6.30]
  8    59 ms    59 ms    60 ms  ae-5-0.cr0.hou30.tbone.rr.com [66.109.10.11]
  9    58 ms    59 ms    59 ms  66.109.6.109
 10    66 ms    71 ms    71 ms  agg1.dllatx10-cr02.texas.rr.com [24.175.49.9]
 11    70 ms    71 ms    64 ms  agg10.dllatx10-cr01.texas.rr.com [24.175.49.6]
 12    62 ms    71 ms    79 ms  xe-1-0-0.DLLUTXJR1CW.tx.twcbiz.com [71.40.237.85]
 13    58 ms    57 ms    58 ms  rrcs-24-153-208-146.sw.biz.rr.com [24.153.208.146]
 14   159 ms     *        *     ge-1-1.core1.colo4dallas.net [206.123.64.26]
 15   166 ms   181 ms   173 ms  65.99.208.122
 16   164 ms   166 ms   165 ms  host.colocrossing.com [206.217.135.118]
 17   168 ms   165 ms     *     131.124.249.72.hypernia.com [72.249.124.131]
 18   166 ms   165 ms   165 ms  131.124.249.72.hypernia.com [72.249.124.131]

Trace complete.

**Kanati** · 09-05-13, 09:19 PM

Thanks for the trace. Definitely seems to be a network issue.

**Rad** · 09-06-13, 01:34 AM

No problem. The good thing is that when it happens it doesn't seem to last longer than 30 minutes or so from what I can tell over the past two days. The bad thing is that it's happening right around the time the server gets primed.