[desynced]

Im interested in your script but your servers have a problem with ALOT of lag spikes. Is this a problem with your servers or the script itself?

[OmegaZero_Alpha]

It is probably an issue with you or your connection. If you are far away from the server's location or if you are on a slower or preoccupied connection (maybe you or somebody around you is downloading a lot, or you are in an area where your ISP has a heavy volume of customers) most people don't experience a significant amount of latency when they play on our servers, so I would imagine that it is an isolated incident.

In any correlation, the SourceOP script has no negative effect on ping.

[desynced]

Ping is fine. (Around 50). I asked others playing if they were having problems (both on the instant spawn server and the no BS server) and both were complaining about the lag.

[Drunken F00l]

Hi,

At the moment this seems to be an isolated issue. Only a specific subset of users are experiencing the lag. I have contacted technical support about the issue. They have excellent networking staff and hopefully the issue will be resolved soon.

[Drunken F00l]

I had to convince them that the problem was at their end and not the individual users' ISPs, but I think I've made progress.

Official response from support:

Tomy D. - Tuesday January 29th, 2008; 7:58 PM CST
Our networking group is working with ATT regarding an issue which lies outside of our network, but may be related. Unfortunately, since it isn't quite in our network, there is very little we can do but wait on ATT to investigate. I am unable to provide an ETA on any possible resolutions at this time.

Tomy Durden
Supervisor, Data Center Operations


This seems like it's probably the cause because all of the complaints come from people that use a route through ATT.

[Drunken F00l]

They have implemented a temporary workaround for the ATT problem.

Tomy D. - Tuesday January 29th, 2008; 8:38 PM CST
Our networking group has taken some measures which should alleviate the effects of this issue. Can you provide a new trace and ping?

The traceroute shows that they cut ATT out of it.
Tracing route to xx.xx.xx.xx
over a maximum of 30 hops:

1 5 ms 1 ms <1 ms c1.18.364a.static.theplanet.com [74.54.24.193]
2 <1 ms <1 ms <1 ms vl1.dsr01.dllstx2.theplanet.com [12.96.160.9]
3 <1 ms <1 ms <1 ms 75.fd.5746.static.theplanet.com [70.87.253.117]

4 3 ms <1 ms <1 ms et5-1.ibr04.dllstx3.theplanet.com [70.87.253.13]

5 <1 ms <1 ms <1 ms GigabitEthernet7-3.ar2.DAL2.gblx.net [64.208.170
.197]
6 <1 ms <1 ms <1 ms te2-1-10G.ar3.DAL2.gblx.net [67.16.129.118]
7 <1 ms <1 ms <1 ms 151.164.251.161
8 13 ms 13 ms 13 ms bb2-p5-2.ksc2mo.sbcglobal.net [151.164.92.62]
...

Ping statistics for xx.xx.xx.xx:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 308ms, Average = 53ms


I think the problem may have gone away now because of this.