[CueBee]

Some folks are complaining about lag spikes on 2fort nomods. The spikes generally seem to be resulting in freezing/rubberbanding.

I was lagging pretty bad around 8pm CDT, so I did some tracerts to attempt to find out the reason. Here's one that might shed some light on the subject:

Tracing route to tf22fortnomods.sourceop.com [67.228.59.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 9 ms 10 ms 74-222-208-1.dyn.everestkc.net [74.222.208.1]
3 11 ms 12 ms 10 ms 64-126-2-113.static.everestkc.net [64.126.2.113]

4 10 ms 12 ms 11 ms 64-126-2-5.static.everestkc.net [64.126.2.5]
5 10 ms 13 ms 12 ms 64-126-2-14.static.everestkc.net [64.126.2.14]
6 9 ms 13 ms 8 ms te-4-2.car1.KansasCity1.Level3.net [4.53.32.33]

7 35 ms 19 ms * ae-5-5.ebr2.Dallas1.Level3.net [4.69.135.230]
8 27 ms 18 ms 25 ms ae-1-60.edge3.Dallas1.Level3.net [4.69.145.8]
9 20 ms 20 ms 25 ms te2-1.cer01.sr01.dal01.networklayer.com [4.71.19
8.18]
10 21 ms 21 ms 32 ms po1.fcr05.sr06.dal01.networklayer.com [66.228.11
8.221]
11 22 ms 22 ms 20 ms tf22fortnomods.sourceop.com [67.228.59.147]

Trace complete.

That seventh hop timed out on at least 3 tracerts.

A group of 100 pings to the server resulted in this:

Ping statistics for 67.228.59.147:
Packets: Sent = 100, Received = 97, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 1230ms, Average = 34ms

[KockEyedNerd]

I can confirm what Cuebee is saying, the nomods server has been getting laggy lately.

[Drunken F00l]

Haven't noticed, but will check it out more myself. I am not seeing loss either, but thanks for the pings and trace. It could help.

[jwstohr]

Valve Maps 2 has been laggy the last couple days as well.

[Guest]

I can confirm what Cuebee is saying, the nomods server has been getting laggy lately.

Yeah that